CS Operating System · The full system for running a CS function that’s ready to scale.
This is the full methodology a customer service function runs on: the four-pillar lifecycle, segmentation and health scoring, the renewal and expansion engines, and the governance that keeps it honest. Ships with eight companion documents that turn the methodology into daily practice.
Instant download · Methodology guide + 8 companion documents
Secure checkout · instant download of all files.
The problem
Most customer service functions under 150 customers are held together by one senior person who remembers how it all works: which customer needs the different renewal cadence, why account X gets QBRs and account Y does not, what the escalation ladder actually is, when it’s fine to bend a rule and when it isn’t. When they take annual leave, everyone quietly holds their breath. When they resign, half the function walks out with them.
A function whose quality lives in one person is one resignation away from collapse. The goal is consistent delivery from defined process, not heroic delivery from talented individuals.
You cannot template your way out of that. Templates give you the pieces. What you need is the system beneath them: the constraints those pieces respect, the lifecycle they run on, and the governance that keeps them honest even when the person who built the whole thing walks out the door.
What’s actually inside
The Operating System is a customer experience management framework, not a longer Playbook. It reframes the same work as a four-stage customer lifecycle and adds the operating layer above it: the segmentation model, the health signals, the renewal and expansion engines, and the governance rhythm that turns a set of good practices into a function that runs without you.
What you get
The methodology tells you what to do. The companions give you the artefacts to do it with: the difference between a guide you read and a system you run.
Six parts, one system. The constraints an SME function has to respect, the four-pillar lifecycle, the segmentation and health models, the renewal and expansion engines, and the governance that ties it together. Written to be read cover to cover, then returned to when you’re building.
The whole system on ten cards: the constraints, pillars, segmentation model, health thresholds, QBR agenda, renewal engine, expansion triggers, metrics, failure modes, and what “done” looks like. For the wall, the weekly review, and the new-hire day-one pack.
The SOP Library (twenty-four procedures), the Template System (seventy-five-plus templates), the Metrics Workbook and its twenty-six-page Companion Guide, the Hiring Kit, the Compensation Benchmarks, and the Implementation Roadmaps. Every artefact the methodology references, ready to adapt and standardise across the function.
The measurement layer
Nine working tabs. Function-level KPI summary. Account-level health scoring with the five-input composite. Ninety-day renewal pipeline with 30/60/90 cohorts. Separate expansion pipeline with the twenty-three-trigger taxonomy. Monthly cohort retention. A two-page Quarterly Board Summary that rolls up automatically. And a twenty-six-page companion guide that walks a CS leader through every tab, every KPI, and every operating rhythm, with defensible benchmarks and a manager’s move on each page.
This is the layer most SME CS functions never build. And it is the layer boards ask to see first.
Most SME CS functions track a few metrics in a shared sheet. This is what the layer looks like when it’s built as a system: one leader can run it, one board can read it, and it doesn’t fall over when the person who set it up moves on.
See it properly
Not a mock-up. The six rules that govern every decision in the rest of the system: the ones that override any tactic, template, or exception the operating reality throws at you. Print this and put it on the wall.
Why this shape
We run multilingual customer service operations for clients around the world. The four pillars are the same work as the Playbook’s eight: same function, different lens. Where the Playbook lives in customer service operations, the OS lives one layer up, in CX operations: the layer that decides how the function is designed, not just what its people do. The operating layer above them is what makes the difference between a function that runs on process and a function that runs on the person who built it.
Six principles govern every design decision in the system. Triage is the central skill. Process beats personality. Scaled touch is the default. Documentation is leverage. Risk gets surfaced, not absorbed. The system outranks the account.
The system is more important than any single account, because the system serves all of them. That is the sentence that decides how every exception, every escalation, and every one-off request gets handled.
Adopt the six, and everything else (segmentation, health scoring, SOPs, governance rhythms) follows from a place that will hold up when the person who wrote them leaves.
How it runs
Part V gives you the implementation sequence: the order to install the operating layer without breaking the function that’s already running. A function that tries to install segmentation, health scoring, SOPs, and governance simultaneously installs four weak versions.
The five constraints and the four pillars are the lens everything else depends on. Ninety minutes, then you know what the system is asking of you and what it isn’t.
Everything downstream (health scoring, motion design, expansion triggers) reads from segmentation. Get this decided before you install anything else.
Weekly, monthly, and quarterly cadences from Part V. This is the rhythm that keeps the rest honest. Set it up before the SOPs, so the SOPs land on a schedule that will actually use them.
Not simultaneously. One pillar at a time, in the sequence the Implementation Roadmap gives you, using the Template System and SOP Library companions as you go.
Honesty about fit
We would rather lose the sale than have you open the files and find the system was built for a function you do not run.
The guarantee
Thirty days. No form, no argument, no “what went wrong?” survey. One email and the money goes back.
And you keep the files: the methodology guide and every one of the eight companions. We cannot claw a PDF off your hard drive and we are not going to pretend otherwise. We would rather you kept a good opinion of us.
We can afford to say that because the product is good, and because €249 is not the point. A function of your size loses more than that when one senior person walks out with the institutional knowledge in their head.
Before you buy
The Playbook is organised around eight buildable pillars: how to build each one, with templates and scripts. The Operating System reframes the same work as a four-stage customer lifecycle and adds the operating layer above it: segmentation, health scoring, governance, and team design. If you want to build pillar by pillar, the Playbook is right. If you want the function to run as a system rather than as a set of practices, this is the level up.
The Audit Kit tells you where the function stands today. The Operating System tells you what a function should look like when it’s running well, and gives you the artefacts to install that. Diagnostic first, system second. Most buyers do them in that order.
Quick Reference Cards (ten cards, one per key concept), SOP Library (twenty-four documented procedures), Template System (seventy-five-plus editable templates), the Metrics Workbook (nine working tabs), the Metrics Workbook Companion Guide (twenty-six pages walking through every tab, every KPI, and every operating rhythm), Hiring Kit (job descriptions, interview rubrics, reference scripts, comp templates), Compensation Benchmarks, and Implementation Roadmaps.
Yes. Every SOP is an editable document, every template is copy-and-adapt. English throughout. Print, share, standardise across your function.
PDF for the methodology, the Metrics Workbook Companion Guide, and the Quick Reference Cards. Editable documents for the SOPs, templates, and hiring materials. Excel for the Metrics Workbook and Compensation Benchmarks. Opens in whatever tooling your team already uses.
Yes. One payment, the files are yours, no per-seat pricing. The licence covers internal use across your organisation: the whole team can read, print, and adapt everything you receive.
No. One payment, no renewal. You get updates when we ship them, but nothing turns off if you stop paying, because you are not paying anything.
Fair. The Operating System is the self-service version of what our team installs on client engagements. If installing this yourself sounds like the wrong use of your quarter, Support Solutions is where our team takes the function on, with the same methodology, running as a service. And if what you need first is the routine questions answered and every conversation quality-checked, our AI customer service platform does that daily work (launching soon).
The system will still help, but past 150 you are into a different kind of operating discipline: segmentation, governance, and enterprise tooling become non-optional. That is what the Operating Reviews are built for, or Support Solutions if you’d rather our team took the function on directly.
One decision
Six parts, eight companions, one system. Enough to stop being one resignation away from chaos.
Get the System for €249One-time · Instant download · Methodology + 8 companions · 30-day money back