What works at $5M ARR breaks at $100M. Tailor everything.
There is no universal CS playbook. A 3-person team managing 200 SMB accounts operates fundamentally differently from a 40-person team with enterprise logos. Stage of growth, customer segment, team size, and product complexity all shape which practices matter most and which benchmarks to target. Every recommendation in this framework adapts to your context, because best practices without context are just guesses.
A CS playbook that works for an SMB with a four-person CS team fails when pasted into a 30-person enterprise CS org, and vice versa. What matters is not the specific play; it is whether the play is calibrated to the team's stage, segment, and operating constraints. "Best practice" without context is the fastest way to spend a quarter on a motion that was never going to fit. The framework's stage-plus-profile model exists because the same domain-level gap needs a different response at a two-person SMB team than it does at a fifty-person mid-market team.
The same principle looks different at every stage. Calibrate the expectation to where the team actually is.
The team borrows plays from whatever CS content it reads: vendor blogs, conference talks, whatever the last leadership hire did at their previous company. Fit-to-context is a lucky accident. Strategy is a synonym for "whatever the CSM lead thinks will work this quarter." Playbooks exist only as vibes.
The team distinguishes its plays by segment at minimum (high-touch vs. tech-touch). There is a shared awareness that a Fortune 500 customer and a fifteen-person startup should not get the same onboarding journey. Strategy documents reference the team's own constraints (headcount, tooling, data maturity) rather than importing a template whole.
Plays are explicitly calibrated to the team's stage and the customer's profile. New initiatives include a "why now, why us" section that names the operating context. The team stops adopting practices because they worked elsewhere and starts adopting them because they match the current state of the business. Run teams also update their playbooks based on their own outcomes data. If a play consistently underperforms for a specific segment or motion, it gets revised. Strategy becomes self-correcting rather than treated as a fixed library.
Where this principle shows up in the rest of the framework.
Take the five-minute assessment to see how your CS function scores across the eight maturity domains, with priority actions tailored to your stage.