RevOps Playbook: How to Document Processes So They Work Without You
Playbook structure for RevOps: processes, owners, SLAs, and checklists.
Why You Need a RevOps Playbook
As a company grows, knowledge scatters: managers work "their own way," marketing understands leads differently than sales, and processes exist only in people's heads. A Playbook is a way to turn chaos into a unified standard of work: what we do, who does it, how we measure, and when we consider a task complete. A single standard of work for the team.
This isn't a long document "for the shelf." It's a working instruction manual for training new hires and maintaining quality.
What to Include
1. Processes: Lead Routing, Qualification, Handoff
Lead routing, qualification, handoff—key processes in RevOps.*
Each key process must be described so that any employee can understand:
- the process goal;
- the starting trigger (what starts the action);
- the execution steps;
- readiness criteria (how to know if a lead is qualified);
- where the lead goes next (handoff);
- what tools are used.
Examples of processes:
- Lead routing: rules for distributing leads (by ICP, segment, workload).
- Qualification: binary MQL/SQL criteria, questions, scenarios.
- Handoff: procedure for transferring between marketing → sales → support.
MQL (Marketing Qualified Lead)—a lead ready to be handed over to sales according to marketing criteria. A lead from marketing that "looks like" a potential customer. SQL (Sales Qualified Lead)—a lead ready for active work with the sales department. A lead that sales has verified and recognized as a real opportunity.
2. Owners and RACI for Key Tasks
If a task has no owner—it has no future. The RACI model helps eliminate confusion:
- R — Responsible: who does it.
- A — Accountable: who is responsible for the result.
- C — Consulted: with whom to consult.
- I — Informed: whom to keep informed.
Application:
- who is responsible for updating KPIs;
- who monitors SLAs;
- who controls data quality;
- who conducts quarterly process reviews.
3. SLAs, Metrics, and Communication Triggers
These are the "rules of the game" that keep the system in shape.
What to record:
- response time (e.g., ≤ 15 minutes for MQL);
- processing deadlines (contact attempts within 48 hours);
- SLA for handoff (transfer within 5 minutes);
- escalation criteria (when and to whom to raise a flag);
- work quality metrics: conversion, speed, % of returns, data contamination.
Communication triggers: notifications, auto-tasks, reminders—anything that helps the team not miss steps.
4. Checklists and Practical Instructions (Runbooks) for Operations
Checklists—to not forget basic steps. Runbooks—to understand what to do in non-standard situations.
Examples of checklists:
- initial lead qualification;
- demo checklist;
- handoff to support checklist;
- deal preparation checklist.
Examples of runbooks:
- what to do if a lead doesn't respond;
- what to do in case of an SLA violation;
- how to process a lead from a "gray" channel;
- how to act in a dispute between marketing and sales.
Playbook Format
"One Page—One Process"
A concise, understandable format:
- Goal: why the process exists.
- Inputs: what starts the action.
- Outputs: what result should be achieved.
- Owners: RACI.
- Steps: specific actions, without fluff.
- Checks: how to know if the process is completed correctly.
- Tools: CRM, forms, templates, automations.
- Links: to checklists and runbooks.
Short, practical, applicable.
Mini-Calculator of the Cost of No Playbook
Cost of Chaos = (Number of Employees × % Loss of Efficiency × Average Hourly Cost)
Example: 15 employees × 20% × 1,800 ₽ ≈ 54,000 ₽ daily is wasted on uncoordinated work.
Conclusion
A good RevOps Playbook is not bureaucracy. It's how a company maintains quality even as it grows.
You document processes → set a unified standard → accelerate onboarding → reduce errors → grow predictably.