Use this when
- Someone just signed and sales is “throwing it over the wall.”
- CS, support, and account management cannot say who owns renewals and upsells.
- Churn is explained as a vibe. There is no book, no tier, no weekly at-risk list.
- You are hiring the first CSM and the only artifact is a culture slide.
Do not use this when
- There are no customers yet. Stay in first ten.
- You need the first-meeting pitch. That is sales enablement.
- You need employee SDR ramp. That is SDR onboarding.
- Legal/privacy owns the relationship (health, government). Get a qualified owner.
Keep this in mind
Write where renewals and upsells live, and how those people are paid, before you write values. If CS is compensated on logo hugs and sales is compensated on expansion, you have designed a war. Point at sales compensation for the live plan.How to do it
Step 1: Understand the customer’s history
A new CS hire should not learn the book from folklore. Write:- Count of customers, revenue in the book, mix by industry / size / region if it changes how you staff
- Who spends, who is engaged, who is referenceable—named, not “we have logos”
Step 2: Agree on team responsibilities
Roles only exist if the sentence “this person is paid to ______” is different. Typical split (labels vary; the work does not):- Associate / CSA: queue, first response, known how-tos. Time-bound (for example first response in hours you can actually hit).
- CSM: adoption, risk, QBR-shaped conversations, the relationship after launch.
- Account manager: commercial expansion if that is not the CSM—or write that the CSM owns both.
- Senior AM / lead: named top accounts, exceptions, hiring bar.
Step 3: Define team and individual measures
Team weekly: at-risk accounts, percent to the CS number, business reviews this week. Individual 1:1: QBRs done, tickets received/answered if they own a queue, renewal win rate, churn. Break the scorecard by role if an associate should not be judged as a hunter. If you need a town hall, its job is wins and losses across tiers, not a pep talk.Step 4: Make the sales handoff a conversation
Close is not the handoff. The handoff is:- Agreement signed; the facts CS needs are in the system of record (not only in the AE’s head).
- Sales introduces the people who will live through onboarding, invoicing, and day-to-day.
- CS (or implementation—see customer onboarding) owns kickoff, the project tool, and the success metric the customer already heard.
- The commercial owner (CSM or AM) stays in the relationship instead of vanishing until renewal.
Step 5: Give customers a clear support route
Write where requests come from (inbox, in-app, bot, named queue). Then the path: Request → automated ack → first human response → resolved or escalated to technical support → closed. If CSMs are bad at implementation, do not hide implementation inside “be a CSM.” Split the work. Introduce support at the start of a project, not as a surprise at go-live.Step 6: Set triggers for renewals and expansion
Your CS file should answer:- What happens at a success milestone that implies expansion—and who orchestrates it internally and with the customer
- What happens at a milestone that implies advocacy (public or internal)
- What happens when an external trigger (new exec, competitor, usage spike) exposes expansion or advocacy
- How renewals are created and tracked in the CRM; whether upsells are a different object; how churn is reported
Step 7: Build a practical onboarding plan for the CS team
A new hire needs, in writing: product, this playbook, shadowing, demo/call listening, email/call patterns, renewal conversation, CRM how-to, territories and rules of engagement, ICP. Then live queue or a tiny book with a manager on the first accounts. Same spirit as SDR onboarding: exit tests, not “sit with Jordan.” Values (customer-first, speed, teamwork) go last. They cannot substitute for a compensation program or a staffing plan.Worked example (illustrative)
Forty customers. One CSM, one associate. AE still closes. Renewals sit in CS; upsells over a threshold return to the AE with CS attached.Copy: CS one-pager (fill)
- Book: count · revenue · mix that changes staffing:
- Where renewals live · where upsells live · how those roles are paid (link to plan):
- Role sentences (associate / CSM / AM / other):
- Team weekly metrics · individual 1:1 metrics:
- Handoff: required CRM fields + conversation agenda:
- Ticket path and first-response clock:
- Tier rule and what coverage each tier actually gets:
- Renewal object, upsell object, churn report:
- Success-milestone → expansion and → advocacy:
- Exception plays we have in writing (dark, unpaid, champion-left, churn types, outgrow):
- New-hire weeks and exit tests:
Before you start
- Renewals and upsells have a home and a pay rule.
- Each CS role has a one-sentence job.
- Handoff is a meeting plus fields, not a Slack “fyi.”
- Ticket path has a clock and an escalation.
- Tiers change work, not only a label.
- At-risk is a weekly list with owners.
- New hires certify on ICP, CRM, and handoff—not only product tours.
Metrics
Do not count town halls held, values posters, or resemblance to a sample 2021 CS deck as success.
Common mistakes
- CS compensated on “happiness,” sales on expansion, nobody on retention.
- Four titles, one human.
- Handoff as a converted opportunity with no briefing.
- Support introduced at go-live.
- Tiers in a slide, equal coverage in the calendar.
- QBRs with no at-risk list.
- Copying another company’s CS org because the titles looked mature.
What to read next
First value is customer onboarding; what they receive in writing is onboarding communication. The record CSMs open on Monday is CS workspace. A new CS executive’s first 90 days are CS-leadership ramp. Gross vs net on the book is revenue churn. Additional value on evidence is expansion marketing; the clock before the commercial path is renewal marketing. The commercial number is sales compensation and forecasting. Named-account thinking stays in account planning. If they have not bought yet, this page is premature.Sources and evidence boundary
This is an owner-maintained operating synthesis. It is not a licensed CS operating system, not a support-tool shortlist, and not legal advice. The people / process / performance frame, the insistence on writing structure, renewals/upsell ownership, measurement, sales→CS handoff, support path, renewal tracking, milestone-triggered expansion and advocacy, and a staged new-hire curriculum are distilled from a Pavilion-circulated customer-success playbook (sample deck dated July 2021). That file is a method prompt, not a source to copy. Its “Sample” company programs, 2021 dollar targets, and placeholder SLAs are not imported as benchmarks. Pavilion as a paid community is listed in RESOURCES.md.Copyright © 2026 Ivan Xu. All rights reserved. See the copyright and reuse terms. Canonical source: github.com/weilun88313/B2B-Playbook