About Peon
Client work
needs an account layer.
Powerful AI tools are already part of client work. Peon exists because those tools still need a reliable way to know which client's mailbox, workspace, repository, analytics property, or other account the work belongs to.
The observation
AI does not lack capability.
It lacks a client address.
A client name makes sense to a person. It does not automatically select the correct Gmail account, Notion workspace, GitHub identity, Analytics property, or provider boundary for an AI.
Peon turns that name into a deterministic client-account graph, then carries the assigned access and boundary into the provider work.
What we are building
A small product boundary.
A consequential job.
These benefits are deliberately narrower than an automation platform. They are the foundation client-service businesses need before broader AI workflows become trustworthy.
- 01
Right client, right account
Name the client and Peon loads only the app accounts assigned to them. If the name or account is unclear, Peon stops instead of guessing. - 02
Access you control
Choose full, read-only, or curated access for every client and app, then declare which mailbox, folder, property, repository, or workspace belongs in scope. - 03
One setup across AI tools
Create each client once, then use the same client-account graph from Claude, ChatGPT, Codex, Cursor, OpenCode, or another compatible MCP client.
Who Peon is for
People who already know
the client comes first.
Peon is designed around client-service work where the same apps recur across several relationships and the cost of selecting the wrong account is real.
Small agencies
Independent consultants
Technical studios
Multi-client freelancers
How we decide
Quiet in presentation.
Exact in behavior.
Real client work is how we hold these principles accountable. The product story stays focused on what Peon reliably ships today.
- 01
Start with the client
Client work should begin with the person or company it belongs to, not a search for a provider account. - 02
Stop before guessing
A useful ambiguity or access error is better than confident work in the wrong client account. - 03
Keep the agent surface focused
The AI should discover the client workflow it needs without carrying an entire provider catalog in every conversation. - 04
Return an honest result
Counts, pagination, boundary status, truncation, and provider receipts should remain visible when work is reduced or incomplete. - 05
Make continuation practical
Recent outcomes should help another AI continue without pretending Peon stores a complete memory of the conversation. - 06
Earn breadth from the core
Projects, triggers, approval queues, and automation do not belong in the product until client-account routing is dependable.
Start free
Start with one client. Let Peon handle the accounts.
If you manage several clients across the same app stack, tell us where account selection gets in the way of using AI well.