Glossary
The vocabulary of founder operations.
Plain definitions for the terms Crew One is built on.
What a Chief of Staff is. What operating memory means. Why human-in-the-loop is the default. Every term has its own link, so you can point straight at a definition.
- Founder Operations Platform
- A founder-facing name for Crew One’s category — the operating system for AI-native companies: it turns a founder’s decisions, approvals, workflows and company context into private operating memory an AI crew can act on. It sits beneath your existing tools as the operating layer a company runs on, not another app on top of the stack.
- Chief of Staff
- In Crew One, the orchestrator between the founder and eight specialist teams. It triages every request, plans the work, delegates it to the right team, and follows through — the way a human Chief of Staff runs an executive’s operations, but always on and with a memory of every decision made.
- Founder OS
- A founder operating system: the layer beneath a company’s apps where its decisions, approvals, workflows and context live as the system of record. It is the shape of a company with judgement concentrated in the founder, authority distributed to an AI crew, and memory that compounds over time.
- Company brain
- The institutional memory a startup usually never builds — the record of how the company decides, not just what it produced. It holds precedent, decision traces, exceptions and standards, and survives contractor turnover, new hires and pivots because it belongs to the company rather than to any one person.
- Operating memory (institutional memory)
- The private, shared memory an AI crew acts on — every decision, approval, rejection and exception, kept and made available to all of Crew One’s specialist teams. Also called institutional memory, it is what lets work compound, so a company stops re-deciding and re-explaining the same things.
- Specialist team
- One of the eight domain teams in Crew One — Executive Assistant, Finance, GTM, RevOps, Marketing, Product, Ops and Legal. Each is a crew of domain agents scoped to work it can be genuinely good at, rather than one do-everything bot, coordinated by the Chief of Staff.
- Domain agent
- A single AI worker within a specialist team, scoped to one kind of work — reconciling invoices, drafting outreach, reviewing a contract. Crew One composes domain agents into teams rather than relying on one general-purpose agent stretched thin across every task.
- The Crew
- Crew One’s product metaphor: a fractional team of AI crews — a Chief of Staff coordinating eight specialist teams — that remembers your decisions and executes the work. Product and copy default to team-level naming (“ask Finance”, “the EA team”) rather than talking about individual agents.
- Orchestration
- How Crew One routes a request to the right work: the Chief of Staff assesses how involved a task is, then sends simple requests straight to one team and plans complex ones across several. You describe the outcome in plain language; the orchestrator decides the shape of the job and coordinates the hand-offs.
- Human-in-the-loop (HITL)
- Crew One’s control model: the crew proposes and executes routine work on its own, but anything with real stakes — payments, sensitive changes, external actions — waits at an approval gate for the founder’s sign-off. Control is the default, not a setting you switch on.
- Approval gate
- The checkpoint where a high-stakes action pauses for a founder’s decision before it happens. Reversible, low-stakes work runs through; anything that moves money, sends an external message in your name, or makes an irreversible change stops and waits — along with anything you flagged when you briefed the crew.
- Decision trace
- The record behind a decision — who chose what, when, and on what evidence. Crew One keeps the trace so a past call stays legible: you can see why something was decided, correct it, and let it inform the next similar decision instead of starting from scratch.
- Precedent
- A past decision that shapes the next one. In Crew One every approval, edit, rejection and exception is written back to memory as precedent, so the company’s judgement accumulates — each decision narrows the next, and the operating layer gets sharper the longer it runs.
- Human API
- The bottleneck Crew One is built to remove: the founder as the company’s human API — the single point every system, agent and workflow routes through for context, instructions and approval. When the company cannot move without going through your head, you are the human API.
- AI-native company
- A company built to run on AI crews from the start, rather than bolting AI onto existing processes. Crew One is the operating system for AI-native, founder-led companies — where an AI crew executes operations and the founder governs from above.
- Compounding
- Why Crew One gets more useful over time. Because every decision, approval and exception becomes precedent in operating memory, judgement accumulates instead of evaporating — a workflow the crew learns it can repeat, and context that survives new hires, turnover and pivots. An app you replace; an operating layer compounds.
The words are the easy part.
The operating memory is the product.
Crew One turns these ideas into an operating system an AI crew can act on — with you in control.