Scoped to the role
The assistant knows the responsibilities, standards, and tools of one job, so its assistance fits the person doing it.
Service
Personal Assistants
A personal assistant is scoped to one person or one role. Narrow scope is what makes the output useful.
What this is
High-leverage work at the personal level: coordination, briefs, research, and follow-through.
We build assistants with the tools and context a specific role needs, including MCP servers and memory that stay inside that scope. They prepare the day: briefs, research, meeting prep, drafted replies, and to-do tracking. They are not company-wide agents. They are built so one person can move faster without losing the thread.
What we build
The visible experience and the system underneath it.
Tooling and context
MCP servers, mail, calendar, and files, with memory limited to what that role should see.
The day’s coordination
Handle briefs, research, meeting prep, drafted replies, and to-do tracking so people have more time for decisions.
How the engagement moves
A real sequence, from ambiguity to something the team can run.
- 01
Define
Shadow the role and mark the recurring preparation, communication, and follow-through.
- 02
Implement
Connect the tools, set the boundary of what the assistant may draft or send, and start supervised.
- 03
Improve
Widen responsibility only where the output holds up in live work.
A good fit when
- A role loses the day to prep and coordination
- Useful context lives in one person’s head
- The company wants leverage on a person, not another shared inbox
What changes
- A clearer day for the people who set direction
- Consistent briefs and follow-through
- Role knowledge that does not leave when the person does
Connected services