Roy
Get early access
Agents

One agent you talk to. A team behind it.

Roy is the executive agent. You talk to Roy. Behind him is a named team of specialists, each with their own domain and their own memory, and Roy decides which of them a question belongs to.

Get early access

Why a team beats one chat window

A single context holding everything you do is a single context that is wrong about most of it.

Depth

A specialist keeps its own memory

The agent that watches your pipeline remembers every deal and every touch. It is not competing for room with your house plan or last quarter's board paper.

Routing

You ask once

Ask a question that crosses three domains and Roy fans it out, collects the answers, and comes back with one. You do not pick the right tab first.

Boundaries

Separation is enforced, not promised

Specialists hold separate stores. The health agent cannot read your deals. That is a property of how the team is built, not a setting.

How work gets routed

  1. You ask Roy. One place, in your words. No routing decision to make and no syntax to learn.
  2. Roy picks the specialists. A question about your market reaches Marlowe and the research desk. A post to write reaches Ellis. A change to Roy itself reaches the builder.
  3. They answer from their own memory. Each specialist brings what it has been watching, with the evidence attached.
  4. Roy returns one answer. Reconciled, cited, and with a proposed next step you can approve or throw out.

The roster

Each one has a name so you can read its thread. All software, all gated, all handing their work to the same queue.

R
RoyChief of staff. Reads everything, proposes, runs the queue.
H
HarmonHealth companion. Its own notes, its own Telegram bot, kept apart from work.
M
MarloweResearch lead. Runs the daily brief with four specialist researchers.
E
EllisEditor. Drafts your LinkedIn posts and runs the optional public site.
T
Trading deskResearch, technicals, macro, risk, execution. Practice account by default.
C
Product councilWatches what you actually use and proposes improvements.
B
The builderWrites changes to Roy's own code on an isolated branch. Hands them to you; never merges.
Y
YouThe only one who can approve, send, merge or unlock.
Never A specialist acts on its own. Every desk proposes into the same queue, and every outbound action waits for the same approval.

Give it a week. It'll know your job.

Private beta is open to a small group of operators. Tell us what you run and we'll get you in.

Get early access