RevOps Playbook
Seven team rules and eight one-page SOPs, from the morning check to opening a new country.
Written for the synthetic team behind the other seven modules · Illustrative, not any company's process
1
Team rules
Seven rules everyone follows, so a number means the same thing to everyone.
1.1Seven rules
- 1Every booked founder has one owner and one dated next step.A founder with two owners, or none, is the one who falls through.
- 2No close without its Sub ID.It is the only key the partner's report shares with the deal.
- 3One number, one source.Each metric is read from one place, so a meeting never starts with whose number is right.
- 4Every red has an owner before 9:00.A problem found in the morning is fixed the same day.
- 5No change to a live sequence without the test plan.A broken reminder costs a week of show rate before anyone notices.
- 6Done by hand twice, it goes on the backlog.Repeated work is a design problem, not a staffing one.
- 7Every number explained in plain English.If a closer, a partner or a founder cannot follow it, rewrite it.
2
SOPs, one page each
Pick one. Each names its owner, fits in seven steps and says when it is done.
2.1The morning check
- When
- Every weekday at 8:00
- Owner
- RevOps
- Time
- 10 minutes
- 1Open the board. Read the reds first, then the ambers.
- 2Give every red an owner and the first action its rule names.
- 3Post the board to the team, owners tagged.
- 4Look at every amber today; three mornings amber in a row counts as red.
- 5Log what broke and what fixed it, for the weekly review.
Done when: The post is up by 8:15 and every red has an owner by 9:00.
Where it lives: Morning Health Check
3
Keeping it true
A playbook is only useful while it matches what people actually do.
3.1Three habits
- Whoever changes a process updates its SOP the same day.
- Each SOP is run once by someone new to it; where they get stuck, it gets rewritten.
- Every quarter, any SOP nobody used is merged or removed.