SD-301a · Module 3
Revenue Operations Playbooks
4 min read
The difference between a sales team and a revenue operation is codification. A sales team has good reps and bad reps and no one can explain why. A revenue operation has playbooks — documented, repeatable processes that encode what the best reps do so that average reps can execute at above-average levels. You do not scale sales by hiring more closers. You scale sales by making the close repeatable.
There are three playbooks every revenue operation needs. The discovery playbook defines how reps run discovery calls: the questions to ask, the order to ask them, the signals to listen for, and the outputs to record. The demo playbook defines how to structure a product demonstration: the opening hook, the problem-to-solution arc, the proof points, and the close. The negotiation playbook defines pricing guardrails, discount authority, concession strategy, and walk-away criteria. Without these three, every deal is an improvisation. Some improvisations work. Most do not.
AI transforms playbook creation and enforcement. Record every call. Transcribe it. Feed the transcripts into AI with the playbook as a rubric. The AI scores each call against the playbook criteria and flags deviations. Which reps skip the budget qualification question? Which reps demo features before discovering the problem? Which reps concede on price before exploring value? The data is in the transcripts. AI extracts it. Managers coach from evidence instead of memory. That is the difference between a sales team and a revenue machine.
Do This
- Document the discovery, demo, and negotiation process as playbooks
- Use AI to score call transcripts against playbook criteria
- Update playbooks quarterly based on win/loss analysis
Avoid This
- Let every rep run their own process and hope for the best
- Write playbooks once and never update them
- Treat playbooks as rigid scripts instead of flexible frameworks