This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Peon
Name the client. Peon routes the right apps.
Peon routes Claude, ChatGPT, Codex, Cursor, and other AI agents to the right app accounts when agencies and consultants name a client.
The issue was basically this:
I might be working on Georgi’s account, but his stuff is spread across Gmail, Drive, Notion, Slack, etc.
So I kept doing this with agents:
“check Gmail for Georgi” “also check Drive” “look in Notion” “see if anything happened in Slack”
The agent has access to all of these tools, but I’m still acting as the router every single time.
Peon stores the client connection instead.
I create Georgi once, attach the apps that belong to him, optionally set boundaries, then I can ask: what’s latest from Georgi?
The agent uses Peon to figure out which connected sources belong to him and search across those.
One of my tests pulled together an email about a BoxNow integration, files from Drive, project state from Notion, and a related Slack thread into one answer. The part I care about isn’t the aggregation. It’s that I didn’t have to tell the agent where any of it lived.
This gets more useful when a client has 10–20 sources. Contacts, folders, channels, repos, whatever.
I’m not trying to rebuild Gmail or Slack MCPs. Peon sits on top of Composio for the actual app connections. It’s a routing/context layer in front of them.
I’ve been comparing the same tasks with and without the client routing. In my current tests it’s about 18% fewer tokens. I want a much larger set before I lean on that number.
It’s free to start: create a client, attach a couple of apps, connect it to Claude / Cursor / ChatGPT.
Curious if anyone else working with multiple clients has run into the same problem, or if you’ve solved it differently.
About Peon on Product Hunt
“Name the client. Peon routes the right apps.”
Peon was submitted on Product Hunt and earned 2 upvotes and 2 comments, placing #158 on the daily leaderboard. Peon routes Claude, ChatGPT, Codex, Cursor, and other AI agents to the right app accounts when agencies and consultants name a client.
On the analytics side, Peon competes within User Experience and Developer Tools — topics that collectively have 886.4k followers on Product Hunt. The dashboard above tracks how Peon performed against the three products that launched closest to it on the same day.
Who hunted Peon?
Peon was hunted by mithun chandar. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Peon including community comment highlights and product details, visit the product overview.
mithun chandar