From RevOps to COO Cheat Sheet (Free)

What's the difference between Strategic RevOps and Tactical RevOps, and why does it matter for moving toward a COO role?

Tactical RevOps is execution-focused — pulling reports, fixing routing logic, managing CRM hygiene. Strategic RevOps is about influencing decisions, owning planning cycles, and connecting GTM execution to company-level outcomes like ARR, CAC payback, and NRR. The cheat sheet maps this out explicitly: tactical ops gets you perceived as a "fixer," while strategic ops gets you perceived as a "force multiplier." The COO path runs through the second lane.

Do I need a specific title or team size before the progression checklist in this cheat sheet applies to me?

No — the checklist is built around behaviors, not org chart position. The six checkpoints (contributing to annual planning, leading QBR cadence, turning data into revenue-tied insights, etc.) are things a solo RevOps practitioner or a team lead can start working toward right now. If you're scoring 0–1 checkmarks, the cheat sheet is direct: it's time to reset your strategic posture, not wait for a promotion to do so.

Which of the 10 skills in the Strategic Skill Map should I prioritize first if I'm still stuck in reactive mode?

Start with Charter and Strategic Prioritization — skills 1 and 6. Without a defined scope, you'll keep absorbing every inbound request, which is exactly what keeps RevOps practitioners in ticket-mode. Drafting a one-pager that outlines your team's purpose and priorities, then building a prioritization matrix ranked by revenue impact and strategic alignment, gives you the foundation to say "not yet" with a reason instead of just saying yes to everything.

How do I know if my data storytelling is actually landing at the COO level, versus just being good reporting?

The signal is whether leadership uses your framing in their own conversations — specifically, whether your insights show up in board decks or the CRO quotes your analysis in exec meetings. The cheat sheet gives a concrete test: if you're presenting data as "here's what the numbers say," you're reporting. If you're presenting it as "churn spiked 2pts in Q2 in Segment A, and here's our plan to reverse it," you're operating at COO level. The "What – So What – Now What" framework is the practical tool to get there.

How often should I run the GTM health review described in the Strategic Shift section?

The cheat sheet recommends blocking one hour weekly to review GTM health across segments, funnel stages, and teams — separate from your standard reporting cadence. The goal is to operate as an early warning system, surfacing revenue-impacting risks before they become escalations. Pipeline coverage, velocity trends, and churn signals are the core inputs to review each week.

What financial fluency do I actually need before I can credibly engage in COO-level conversations?

You need to be conversant in CAC, LTV, GRR, NRR, CAC payback period, and operating margin — and more importantly, you need to be able to model "what-if" scenarios using those numbers (e.g., "what if win rate improves 5%?"). The cheat sheet recommends partnering with Finance to understand how these metrics connect to budget decisions and board reporting. You don't need to be a CFO, but you do need to ask sharper, revenue-driven questions and get looped into financial modeling conversations.