Pillar 1: Operationalizing CS — the foundation everyone skips

There is a pattern that plays out in almost every company that decides to "start doing Customer Success": they hire two or three talented CSMs, split the book by feel, and for six months it seems to work. At 200 clients per CSM, the system locks up. Hiring more CSMs becomes prohibitively expensive. And no one built — along the way — what would have made it scale.

That's the problem Pillar 1 — Operationalizing Customer Success exists to solve. Wayne McCulloch (The Seven Pillars of Customer Success, 2021) calls it "the most important and least understood" pillar. It's no accident this is the first pillar in the framework: without it, the other six collapse under their own weight.

The definition that matters

The customer success team delivers proven best practices at scale, in a repeatable way and with efficiency, to drive the desired outcome of your customer and your company, wrapped in an exceptional customer experience. — McCulloch 2021, ch. 3

Three things stand out:

Best practices at scale — captured knowledge, not individual heroics.
Repeatable — same process, same outcome, customer after customer.
Wrapped in exceptional experience — efficiency without dehumanization.

The value verb here is Value Managed: value delivered in a governed, predictable, managed way.

Why this pillar gets skipped

The typical story:

The company adopts CS in the "first wave" — basically firefighting. Talented firefighters.
The first CSMs build the operation "in their heads." Each one their own way.
The customer base grows. The natural answer is to hire more CSMs.
But there are no written playbooks, no health score, no segmentation, no journey map.
Every new CSM has to be trained by osmosis from the veterans.
Around 200 clients per CSM, the model breaks. There's no longer a way to hire your way out of the problem.

McCulloch's prescription is blunt: hire CS Ops before your third or fourth CSM. Most companies hire CS Ops last — once the problem is entrenched and expensive to fix.

CS Ops is not a reporting function. It's a capability function. Ops is the engine, not the dashboard.

What CS Ops actually does

Operationalization isn't "documenting what we already do." It's building and maintaining the infrastructure that makes CS scale:

The CS toolbox — the company's library of playbooks, success-plan templates, health-score models, segmentation rules.
The journey maps — customer journey and churn-journey mirror. Where are the moments of truth? Where do people drop?
The operating cadence — when do QBRs happen? Who runs them? When does escalation trigger?
The data infrastructure — CS platform, integrations, dashboards. Where is the truth about every customer?
The shared vocabulary — does yellow health mean the same thing across the team? Does onboarding complete have an operational definition?

Without this, "doing CS" is individual heroics. With it, it's a company capability.

Three signs Pillar 1 is weak

A fast diagnostic — no interviews required:

Each CSM runs onboarding "their own way." Ask three CSMs how they run the kickoff. If the answers differ in structure — not just style — you don't have a playbook.
You can't hire a CSM and get them productive in a week. If the ramp curve is 3 months, "the company's way" isn't written down. All scaling depends on new CSMs absorbing by osmosis from the veterans.
You can't explain, in 30 seconds, which customer is at risk today and why. Either the health score doesn't exist, or it lives in a static PDF somewhere.

If two of three sound familiar, this is the pillar to attack first. Whatever the rest of the company is asking for.

Digital CS — don't confuse with tech touch

The most common confusion in this pillar is treating "tech touch" as a synonym for "automation." McCulloch is surgical:

Tech touch removes humans. Digital CS embeds them.

A concrete example: a $20M ARR company with one customer can afford a dedicated CSM. The same $20M ARR company with 200 customers can't. The default response — flip the long tail to tech touch — leaves most customers without empathy or expertise. Digital CS does something different: it delivers the human moment of truth through the product.

How that looks in practice:

Contextual in-product guides. Not a generic tour. A guide that fires when the user is about to make a costly decision.
Alerts that trigger human action at the right moment. The system detects a risk signal; a real human reaches out — not a chatbot.
Real-CSM videos explaining features. Not corporate video. Named CSM, on camera, walking through how to use it.
Curated communities. Customers help customers, with a CSM present moderating and capturing patterns.

The distinction is cultural before it's technological: tech touch starts from "how do I remove humans to cut cost?"; digital CS starts from "how do I deliver the human moment to more customers with the same team?"

Where to start — the three highest-leverage levers

McCulloch points to three toolbox tools as the "starter kit" for this pillar (ch. 3):

1. Customer journey map + moments of truth

Before operationalizing anything, map the surface. Every customer goes through moments of truth — kickoff, first login, first value delivered, first complaint resolved, QBR. Which of these moments are you operationalizing? If you can't name 8–12 moments of truth in your journey, there's nothing yet to operationalize.

2. Playbooks

The heart of this pillar. For each priority moment of truth, what's the playbook? Who triggers it? What's the expected outcome? How do you know it ran well? Without playbooks, every CSM is doing things their own way — and the company is paying for individual heroics instead of buying capability.

Rule of thumb: start with the 3 playbooks that cover 80% of the critical moments. Don't try to write 30 playbooks in the first quarter.

3. Customer success plans

When a moment fires and the playbook runs, what happens to the individual customer? The success plan is the record. Without it, the playbook runs in a vacuum — there's nowhere to anchor the outcome.

What "healthy" looks like

Four observable signals:

A new CSM can run a typical engagement on day one using existing playbooks.
The team absorbs 30% more accounts year over year without proportional hiring.
Sales, marketing, and support can see a customer's success plan and contribute to it.
The customer experience feels coherent across pillars — onboarding, adoption, retention sound like the same team talking, even though they're separate functions.

The most common failure modes

Three traps that show up in teams trying to operationalize:

Operationalizing before listening. Teams build generic playbooks from "industry best practices" before mapping what their own customers actually need. The result: pretty playbooks no one uses.
Treating CS Ops as a reporting function. Ops produces pretty dashboards but doesn't build capability. The engine was never built — only the gauges were painted.
Choosing tech touch over digital CS at scale. Saves margin in the short run, destroys retention in the long run. The long tail gets orphaned. When new-logo growth slows, the entire base is exposed.

The question that defines everything else

Before trying to sharpen onboarding, adoption, retention, expansion, or any other pillar, ask a single question:

If I double the customer base in the next 12 months without doubling the CS team, what breaks first?

The honest answer always points to Pillar 1. That's why McCulloch is direct: operationalize first. It's not the sexiest pillar to build. It doesn't win awards. It doesn't make the board deck.

But it's the only one that lets the other six exist as company capability, instead of dependence on your most senior CSM.

Based on McCulloch, Wayne. The Seven Pillars of Customer Success: A Proven Framework to Drive Impactful Client Outcomes for Your Company (2021), ch. 3. Adapted by the Partenero team. This post is part of a series on the 7 Pillars — see also the overview post.