- 00
Overview
You do not have a revenue system. You have three departments.
Shared language. One diagnosis. A one-page charter — not a software tour.
- Read
The briefing
The leak is in the seams, not inside the teams. One sentence for what RevOps is, what it is not, and three questions for the next leadership meeting.
- Download
Speaking script
A 45–60 minute script for CEO, CRO, CFO, CMO, and Customer Success. Spoken lines, board prompts, and how to handle derailments.
- Download
One-page charter
Purpose, one shared revenue goal, reporting line, what RevOps owns and does not own, three workstreams, and signatures — including Finance.
- 01
People
RevOps fails first on reporting lines, not on CRM.
Who referees the seams — and who that person reports to.
- Read
The briefing
Specialist ops versus RevOps, three org shapes, a short cast, and why a shared scorecard comes before compensation redesign.
- Download
Speaking script
The political session. Draw current lines, name one referee, write the reporting line on the charter — or write the blocker in one sentence.
- 02
Process
A sales methodology is not a revenue process.
One seam, written, owned, and timed — before anyone automates it.
- Read
The briefing
Walk a real deal and a real leak. Write one corridor, not a mural. Good process is boring on purpose.
- Download
Speaking script
Sixty to ninety minutes. Output is one signed SLA and a thirty-day pilot. No workflow product.
- Download
Current-state leak map
A blank path for one closed deal and one failed handoff: owner, criteria, lost data, wait, and where the customer repeated themselves.
- Download
Handoff SLA
One seam, entry criteria, five required fields, a clock, an escalation, a thirty-day metric, and three signatures.
- 03
Data
You do not have a data problem. You have three meanings of the same word.
Freeze the dictionary before you clean the CRM. Finance co-signs. Dashboards come last.
- Read
The briefing
A dashboard is a view. A definition is law. Eight to twelve words, one meaning each, and change control that is not a Slack poll.
- Download
Speaking script
Put last month’s three official numbers on the table and freeze the words that caused the split.
- Download
Shared metric dictionary
ICP through attribution. One sentence, a system of record, and a Finance signature on revenue terms.
- 04
Technology
Most failed RevOps programs start with a platform.
Tools enforce a model. They do not create one. Architecture and a kill list — not a bake-off.
- Read
The briefing
Stop asking which CRM. Map jobs, not brands. AI multiplies whatever you already have. Freeze net-new purchases.
- Download
Speaking script
Vendors stay out. Unused seats go on the kill list. Output is a freeze and one or two integration breaks.
- Download
Stack map and freeze list
Each tool under the job it actually does, whether it obeys the dictionary, and what you will not buy for ninety days.
- 05
Standing it up
If it is not on the charter, it is not in the quarter.
Ninety days. Three workstreams. A stop-doing list. Not a transformation program.
- Read
The briefing
Do not start the clock on theater. Diagnose, stabilize, institutionalize. Name an interim or do not begin.
- Download
Speaking script
Five decisions written down, then day 30, 60, and 90 on the sponsor’s calendar before anyone leaves.
- Download
90-day mandate
Sponsor, reporting line, three workstreams, who does the work, and the habits that die this quarter.
- 06
After it exists
If RevOps is working, one meeting should die.
Few metrics. One owner. One definition. Then stop briefing and run the quarter.
- Read
The briefing
A short executive scorecard, four meetings, a blunt maturity read, and the failure modes to name while you still like each other.
- Download
Speaking script
The last briefing. Pick ten legal numbers, name the meeting that dies, set a six-month review. There is no Session 7.
- Download
Executive scorecard
One page for the executive meeting: growth quality, predictability, efficiency, retention. Strike any row not in the dictionary.