Your first request
Describe an outcome to your Chief of Staff and watch it become work your team runs.
Foreman is driven from one conversation. You describe what you want to be true; your Chief of Staff works out who should do it and comes back when it needs you.
Describe an outcome, not a task
This is the single habit that changes what you get back.
A task tells the system what to type. An outcome tells it what you are trying to achieve, which is what lets it choose the steps — and notice when a step is wrong.
| Instead of | Say |
|---|---|
| "Write an email to Acme" | "Get Acme moving again — they went quiet after the pricing call" |
| "Make a list of competitors" | "Tell me where we're losing to competitors, and what to do about it" |
| "Draft a LinkedIn post" | "Get a week of LinkedIn posts ready that I'd actually publish" |
Steps
- Open Chat.
- Type an outcome in your own words. Don't worry about phrasing it for a machine.
- Answer the clarifying question your Chief of Staff asks back. It asks when the answer would change the work — not to fill in a form.
- Read the proposal it returns. It says what it intends to do and what you'll have at the end.
- Approve it, or reply with a correction. A correction is just a sentence; you don't need to restate the whole request.
You're done when an objective appears under Objectives with the status in progress.
If you'd rather not start from a blank box
The first screen offers several complete, runnable requests — a competitor teardown, a week of LinkedIn posts, a qualified prospect list, a website audit, an inbox triage. These are not examples to copy; clicking one starts the real work. They exist because the hardest part of a first session is deciding what to ask for.
What happens without you
Your Chief of Staff routes the request to a CEO agent, which breaks it into a handful of tasks and delegates each to the department chief who owns that function. You don't operate any of that. You'll be asked to approve anything that leaves your workspace.
Gotchas
- Chat is not a search box. Asking "what is X" gets you an answer. Describing an outcome gets you work. Both are valid — just know which one you're doing.
- Stopping a response does not undo the objective. Pressing Escape stops the reply being written. If an objective was already approved, stop it from the objective itself.
- Vague in, vague out. "Help with marketing" produces a plan about marketing. "Get me 20 qualified leads in UK manufacturing by Friday" produces leads.
Walkthrough video: 60s: typing an outcome, the clarifying question, the objective card appearing.