The one-page playbook
A customer success playbook has six parts: the trigger that starts it, the owner, a diagnosis step to find the cause, the plays for each likely cause, a deadline, and the condition that ends it. It should fit on one page.
Playbook: [Name of the situation]
Trigger: [The observable event that starts this. Specific enough that two people would agree it happened.]
Owner: [Role]
Start within: [How many days from the trigger]
First, find the cause. Don't act until you've checked:
| Likely cause | How to check | If this is it |
|---|---|---|
| [Cause A] | [Who to ask, what to look at] | [The play: two or three actions] |
| [Cause B] | [How to check] | [The play] |
| [Cause C] | [How to check] | [The play] |
| Something else | [Ask the champion what changed] | [Escalate to: role] |
Tell the customer: [What you'll say, and to whom]
Done when: [The observable result that ends the playbook]
If it isn't working after [n] days: [Who decides what happens next]
The step most playbooks are missing
Open a typical playbook and it reads like a recipe. Trigger: usage down 20%. Step one, send the re-engagement email. Step two, offer a training session. Step three, escalate to the manager.
It's tidy, and it treats every drop in usage as the same problem. They aren't. A drop caused by a reorganization needs a different response from one caused by a champion leaving, and both are different from a team that's trying a competitor. Send all three the training offer and you've handled the trigger without touching the cause.
That's why this template puts a diagnosis table in the middle. The trigger tells you something changed. The table makes you find out what, before you pick a response. It adds a day. It saves the six weeks you'd spend fixing the wrong thing.
A completed example
Playbook: the champion leaves
Trigger: the customer's day-to-day champion announces they're leaving, changes role, or goes quiet for 30 days.
Owner: the customer success manager.
Start within: 2 working days.
| Likely situation | How to check | If this is it |
|---|---|---|
| A successor is named | Ask the champion before they go | Get an introduction while they're still there. Rerun a short kickoff with the successor: goals, baseline, what's been achieved. |
| No successor yet | Ask the sponsor who owns it in the meantime | Ask the sponsor to name an interim owner this week. Train them as admin. Put a 30-day check-in on the calendar. |
| The role is being cut or merged | Ask the sponsor what's changing in the team | Treat it as a change in the customer's priorities. Ask whether the goals in the success plan still stand, and bring the answer to an early review. |
| Something else | Ask what changed | Escalate to the account manager. |
Tell the customer: to the sponsor, within the week: "We want to make sure nothing drops while [name]'s role is open. Who should we work with, and can we take 20 minutes to bring them up to speed?"
Done when: a named person on the customer's side has made a change in the product without help, and has confirmed the goals.
If it isn't working after 30 days: the account manager and CS lead decide whether to ask for an executive conversation.
Four playbooks to write first
| Playbook | Trigger | The first question |
|---|---|---|
| The champion leaves | Departure, role change or 30 days of silence | Who owns this on your side now? |
| Usage drops | A sustained fall over four weeks, in the team it was bought for | What else changed around the time it started? |
| Renewal at risk | 120 days out with a red or yellow health score | What would you need to see to feel good about renewing? |
| Onboarding stalls | A milestone missed by two weeks | What's in the way, and who can move it? |
Write these four, use them for a quarter, and rewrite them from what you learned. A playbook nobody has edited since it was written is describing last year's customers.
Get the QBR kit
Fifteen slides in meeting order, with notes on every slide: what goes there, what to ask and what to avoid. It also includes AI prompts that draft the deck from your notes, the prep timeline and a 60-minute run-of-show. PowerPoint, opens in Google Slides, $39.
Checkout opens soon. Get the free starter deck now, and the scorecard if you want to hear when the kit is ready.
Playbook questions
What is a customer success playbook?
A customer success playbook is a short document that says what a team does when a specific situation occurs with a customer: what triggers it, who owns the response, the steps to take and how to tell whether it worked. A CSM playbook is the same thing.
What should a customer success playbook include?
A trigger, an owner, a short diagnosis step to find the cause, the actions to take for each likely cause, a deadline, and an exit condition that says when the playbook is finished.
Which playbooks should a customer success team write first?
Start with the situations that cost the most when handled badly: a champion or sponsor leaving, a sustained drop in usage, an at-risk renewal, and onboarding that has stalled. Four good playbooks beat twenty nobody reads.
How long should a playbook be?
One page. If it doesn't fit, it's probably two playbooks, or it's describing a process that belongs in training.
How is a playbook different from a success plan?
A success plan is specific to one customer and describes their goals. A playbook is general: it describes how your team responds to a type of situation, across all customers.