RevOps Playbook Operators Can Actually Run
A RevOps playbook is the operating language for how revenue work moves: who owns the object, when it changes stage, and what the next handoff is. It is not a HubSpot tour, a 7-day sprint, or a template pack for an agency book of business.
The live version of this URL used to sell that other thing — “ultimate guide,” unsourced onboarding percentages, a fractional-CMO week. That is not how All Great Things works, and it is not what a systems reader can run on Monday.
What a RevOps playbook actually is
Write it as rules, not inspiration. A usable RevOps playbook answers four questions for each commercial object:
- What is the object? Lead, contact, account, opportunity, ticket — named, not implied.
- Who may create it, and who may edit the fields that change reporting?
- What has to be true to move a stage forward — and what is never allowed to move it backward without a named reason?
- Who is on the hook for the next action, in hours not “soon”?
If those answers live in someone’s head, you do not have a playbook. You have folklore. Folklore does not survive a new AE, a new demand hire, or a PE operating review.
This is the layer Jason sits in as an embedded operator: definitions, routing, and the cadence that keeps them true. It is also why GTM attribution breaks before the model. The playbook is the language. Attribution is what happens when that language is written into the systems.
The four objects the playbook has to name
Skip the 30-page “framework.” Name the four objects that already cause fights.
Inbound and outbound entry
Where a person or account enters the commercial system. Form, sequence, partner, inbound AE. One write path for original source. A second field for last meaningful touch if you need it. Do not let six tools each invent a source.
Qualification
What “qualified” means here. Fit plus intent, or fit plus a meeting, or fit plus a commercial conversation — pick one. Write the disqualify reasons. A playbook that only describes happy path will be ignored the first week a bad lead is worth more to the dashboard than to sales.
Opportunity
When it may be created. Required fields before it counts as pipeline. Who can close-lost and with which reason codes. This is the page the board will eventually ask for, whether you wrote it or not.
Handoff after the close
Who owns onboarding, expansion, and the first renewal conversation. Revenue operations that stop at closed-won leave the rest of the company to invent a second playbook.
Handoffs, not more software
Most “we need RevOps” requests are a tool request. The playbook should make the tool boring.
Routing: one owner per new qualified record, visible in the CRM, with a time-to-touch rule. If marketing can create pipeline that sales never sees, you do not have a funnel. You have two lists.
SLA: a number the room can audit. Not “fast follow-up.” If the SLA is not in the playbook, it will be renegotiated in Slack during the worst week of the quarter.
The living view of those rules is a GTM operations system, not a slide you refresh on Friday. The playbook says what must be true. The system shows whether it is true this week.
How you know the playbook is working
Do not invent a productivity percentage. Watch the fights disappear.
- Stage movement can be explained from the record, not from a side conversation.
- Sourced versus influenced is written once and used in both marketing and sales reviews.
- A new hire can take a deal from inquiry to close-won without a shadow process.
- The quarterly review changes a rule in the playbook, not a color on a chart.
If those are not true, adding AI agents on top of the same mess will only make the mess faster. AI-forward here means the playbook is explicit enough that a workflow can enforce it. It does not mean a prompt sitting on chaos.
What to stop writing into it
Stop writing agency onboarding mythology. Stop writing unsourced “73% faster” lines. Stop writing a 7-day implementation that pretends a commercial system can be stood up like a landing page.
Stop selling a diagnostic, then a packaged project, as if that were the studio offer. All Great Things works as seats and retainers. The playbook is what an embedded operator leaves running — or what a production retainer keeps honest after the first build.
Keep HubSpot, Salesforce, or whatever you already paid for. The playbook does not care which logo is on the login screen. It cares whether two humans would write the same stage on the same Tuesday.
FAQ
What belongs in a RevOps playbook?
Objects, owners, stage rules, handoff SLAs, and the few metrics that use those definitions. Not a tool catalog and not a thought-leadership essay.
Is a RevOps playbook a software implementation?
No. Software stores the fields. The playbook says what the fields mean and who is allowed to change them. Implement the rules first, then automate the ones that are stable.
How is this different from a sales playbook?
A sales playbook coaches conversations. A RevOps playbook governs the system those conversations write into. You need both. Confusing them is how marketing and sales end up with two pipelines.
If the current “playbook” is a deck, the next right step is an operator seat to write the real one into the CRM and the weekly cadence — then a retainer so it does not rot. That is Jason’s work. When the same gaps are a board or PE conversation, bring Jennifer in on commercial design, not as a second byline.
