Startup COO Mandate Template: What to Decide Before You Hire
A startup COO mandate is the working agreement behind the job description. It says what the COO will own, what the founder will stop owning, how decisions will move, and what evidence will prove the hire is working.
Write the mandate before you publish the role. If you cannot describe the operating problem, the authority, and the first 90 days, the company may not need a COO yet. It may need a Chief of Staff, VP Operations, Head of Operations, or fractional operator first.
Use this template as a practical pre-hiring brief. Keep it short enough that candidates can challenge it in conversation.
The one-page COO mandate
| Section | What to write | Good answer sounds like | |---|---|---| | Operating problem | The three to five bottlenecks the COO must improve | “Leadership decisions do not turn into owned weekly work” | | Scope | Teams, systems, metrics, and rhythms the COO will own | “Quarterly planning, business review, customer-delivery handoffs, hiring cadence” | | Decision rights | What the COO can decide without founder approval | “Can change operating cadence and assign cross-functional owners inside agreed priorities” | | Founder handoff | What the CEO will stop doing | “CEO stops running weekly delivery follow-up and manager cadence” | | Success evidence | What should be visibly better after 90 days and 12 months | “Fewer CEO escalations; clearer owners; reliable forecast and delivery rhythm” | | Non-fit | What this role is not | “Not an EA, generic fixer, board-deck owner, or process layer without authority” |
The mandate should make the job smaller and sharper. If it keeps expanding, pause the search and choose the first operating problem to solve.
1. Name the operating problem, not the title
Start with the pain the founder can no longer carry.
Useful examples:
- weekly priorities change and managers do not trust the planning rhythm;
- customer delivery, product, and sales keep dropping handoffs between teams;
- the CEO is still approving every cross-functional decision;
- hiring is growing but onboarding, manager routines, and role clarity are weak;
- operating metrics exist in separate tools but do not drive decisions;
- finance, headcount, delivery, and customer health are not connected.
Weak examples:
- “bring structure”;
- “make us more mature”;
- “own operations”;
- “free up the founder”;
- “scale the company.”
Those may be true, but they do not tell a candidate what they will own.
2. Decide whether this is really a COO mandate
A COO is not the default senior generalist. Use the title only when the operating surface is broad enough and the founder is ready to hand off authority.
| If the main problem is... | Start with... | Why | |---|---|---| | Founder bandwidth, priorities, meetings, board prep, follow-through | Chief of Staff | The constraint is CEO leverage, not operating ownership | | One broken function such as customer ops, revenue ops, people ops, or finance ops | VP Operations or Head of Operations | The need is functional, not company-wide | | Unclear bottleneck and uncertain permanent role | Fractional operator or diagnostic | You need the brief before the hire | | Several teams need one owner for cadence, metrics, operating decisions, and delivery | COO | The company needs executive operating ownership |
If you are still choosing the role, compare Chief of Staff vs COO, COO vs Head of Operations, and what a VP Operations actually does.
3. Write the decision-rights section carefully
Most COO failures start with vague authority.
Do not write:
The COO will improve execution across the company.
Write:
The COO can set the weekly business review agenda, require functional owners to update operating metrics, assign owners for cross-functional handoffs, and escalate unresolved tradeoffs to the CEO in the weekly founder-COO session.
Decision rights usually fall into four buckets:
- Operating cadence: planning, weekly reviews, manager rhythm, leadership meetings.
- Cross-functional ownership: handoffs between product, sales, customer success, finance, people, or delivery.
- Resource tradeoffs: priority, headcount, tooling, vendor, and sequencing recommendations.
- Team accountability: manager follow-up, performance visibility, and unresolved decision escalation.
Be explicit about limits too. A COO may recommend strategy changes, but the CEO and board may still own final company strategy, fundraising, major executive hires, and budget approvals.
4. Define the founder handoff
A COO creates leverage only if the founder releases work.
Use this prompt:
After this hire starts, the founder will no longer personally own...
Good answers:
- weekly operating follow-up across functions;
- recurring delivery escalations that have clear owners;
- manager cadence design;
- first-pass operating metrics review;
- handoff enforcement between customer, product, and sales teams;
- turning leadership decisions into owned work.
Bad answers:
- “everything operational”;
- “whatever the founder does not have time for”;
- “keeping the team aligned”;
- “making sure people execute.”
If the founder cannot give up a recurring decision, do not put it in the COO mandate.
5. Turn the mandate into interview evidence
The mandate should shape the interview process. Test the work, not the vocabulary.
| Mandate area | Interview test | What to look for | |---|---|---| | Planning cadence | “How would you rebuild our quarterly and weekly operating rhythm?” | Sequencing, owner clarity, restraint | | Cross-functional handoffs | “A launch keeps slipping between sales, CS, and product. What do you inspect first?” | Diagnosis before process | | Founder handoff | “Where would you need CEO backing in the first month?” | Honest authority requirements | | Metrics | “Which operating metrics would you trust first, and which would you distrust?” | Judgment about signal quality | | Team accountability | “How do you create follow-through without adding meeting tax?” | Practical operating leverage |
For a fuller interview process, use the startup COO interview questions and operations-hire scorecard.
6. Set first-90-days ownership
Do not onboard a COO around orientation only. Onboard them around authority, context, and first operating wins.
| Period | COO owns | Founder owns | |---|---|---| | Days 1-15 | Listen to customers, managers, metrics, finance, operating rituals, and decision history | Share the real operating picture and current founder bottlenecks | | Days 16-30 | Diagnose the highest-friction operating loops and recommend the first fixes | Protect diagnosis time; do not force premature answers | | Days 31-60 | Install one or two operating changes: cadence, handoff, metrics, or owner clarity | Publicly back the agreed decision rights | | Days 61-90 | Make the rhythm durable and decide what moves next | Stop re-owning handed-off work |
See the dedicated guide to the first 90 days for a startup COO if onboarding is the main risk.
7. Use this mandate as the candidate brief
Send a short version to serious candidates before deep interviews. It should help both sides decide whether the role is real.
A useful candidate brief includes:
- company stage, team size, geography, funding or revenue context where appropriate;
- the operating problem;
- the role archetype: company-wide COO, functional operator, founder complement, or interim/fractional operator;
- direct reports or functional surfaces;
- decision rights and founder handoff;
- expected working rhythm;
- compensation range or pricing model where known;
- first 90 days;
- what the role is not.
If compensation and scope are still open, read the fractional COO cost guide, operator salary guide, and startup COO equity guide before asking candidates to guess.
Copy this COO mandate template
Company context:
- Stage / team size:
- Business model and operating complexity:
- Current leadership team:
Operating problem:
- Problem 1:
- Problem 2:
- Problem 3:
COO mandate:
- Systems / rhythms owned:
- Teams / functions influenced or managed:
- Metrics owned:
- Cross-functional handoffs owned:
Decision rights:
- COO can decide without founder approval:
- COO recommends, founder decides:
- Escalation rhythm:
Founder handoff:
- Founder will stop owning:
- Founder will still own:
- Where founder sponsorship is required:
First 90 days:
- Days 1-15:
- Days 16-30:
- Days 31-60:
- Days 61-90:
Candidate evidence:
- Interview tests:
- Reference questions:
- Work-session scenario:
Non-fit:
- This role is not:
- Candidates who should opt out:
Sources and further reading
- First Round Review: Make Operations Your Secret Weapon — guidance on timing, COO archetypes, red flags, and onboarding an operations leader.
- Sifted: How to hire a chief operating officer — founder-COO fit, autonomy, complexity, and early-stage COO expectations.
- Sifted: How to define the type of COO you need — practical framing on CEO gaps, organisational review, and why COO roles vary by company.
- Kruze Consulting: What Does the VP of Ops or COO at a Startup Do? — examples of startup COO/VP Ops responsibilities and job-description components.
Bottom line
A COO mandate should answer one question: what operating ownership is the founder actually handing over?
If the answer is clear, use the mandate to write the role, run the interviews, and onboard around authority. If the answer is still vague, start with diagnosis before hiring a permanent COO.
When the brief is ready, use FindOperators to browse operator profiles, compare role pages, or submit an operator profile so the next founder can find stronger operating matches.