Free COO Cheat Sheet

What's the difference between the COO owning the revenue engine versus the CRO owning it — and where does this cheat sheet draw that line?

The cheat sheet is explicit: the COO owns the system and guardrails — stage exit criteria, deal desk rules, forecast architecture — while the CRO owns quota and coaching. A practical example from the sheet: the COO sets stage exits, the CRO enforces them in pipeline reviews. If your COO is running sales execution directly, that's the overlap risk the cheat sheet flags, and it tends to create accountability gaps fast.

Do I need a full RevOps team or a mature CRM setup before this cheat sheet is useful to me?

No — several sections are useful before you have clean infrastructure. The First 90 Days framework, the KPI dictionary approach, and the common pitfalls table (especially "metric sprawl" and "cadences without decisions") are all designed for situations where the foundation is still being built. That said, the dashboards and data governance sections assume you have at least a CRM like Salesforce or HubSpot and a data warehouse like Snowflake or BigQuery in place.

Which of the COO archetypes should I use to figure out how to structure my own role or evaluate a COO hire?

Start with your growth motion and where the biggest operational drag lives. The cheat sheet maps four archetypes — GTM Ops-Led, Delivery/Customer Ops, Platform/Corporate Ops, and Product-Integrated — each with a "best when" condition and specific risk flags. For most Series B/C SaaS companies running sales-led growth, the GTM Ops-Led archetype fits, but the sheet warns about CRO overlap and recommends clear decision rights and a pricing/forecast council to prevent it.

How do I know if the operating cadence I'm running is actually working versus just generating meeting overhead?

The cheat sheet gives you a direct test: every cadence should produce a decision log with owners, not just a status update. If your weekly exec meeting or monthly ops review ends without documented decisions and assigned owners, you're running what the sheet calls "status theater." The fix is adding decision logs and clear inputs/outputs to each meeting — the cadence table in the sheet lists exactly what those should be for each meeting type.

What data do I need to have ready before I can build the scenario planning framework this cheat sheet describes?

At minimum, you need current pipeline coverage by stage, NRR by cohort, and a working CAC payback number. The cheat sheet's scenario triggers are concrete — bull case kicks in at coverage above 4× with NRR trending up; bear case triggers at coverage below 2.5× with NRR declining — so if you can't produce those two numbers reliably, scenario planning becomes guesswork. Get your pipeline stage definitions and NRR calculation agreed on first; the KPI dictionary section of the sheet tells you how to do that in 30 days.

How often should I revisit the COO operating model this cheat sheet describes once it's in place?

The cheat sheet treats the operating model as a living artifact — "Operating Model v1" is a Day 90 deliverable, not a final state. The monthly Ops Review is where you catch variance and make keep/kill/scale calls, and the quarterly QBR is where learnings feed back into the plan. A full model review makes sense annually during the integrated planning cycle, with targeted updates any time a scenario trigger fires or a major org change happens.