The 7 Pillars of Customer Success: a framework for operating CS with method

Most CS teams operate on improvisation. Hire two or three CSMs, split the book by feel, and run in firefighting mode until someone notices retention has become a board problem. The Seven Pillars of Customer Success framework, described by Wayne McCulloch (The Seven Pillars of Customer Success, 2021), is the cleanest architecture we know of for breaking out of that loop.

The book's real insight isn't "do onboarding better." It's recognizing that CS is an organizational capability, not a portfolio function. And that capability has a structure: 5 sequential pillars along the customer journey and 2 cross-cutting pillars holding the whole thing together.

The architecture in one diagram

┌──────────────────────────────────────────────────────────────┐
│  Pillar 1: Operationalizing Customer Success                 │
│  "Value Managed" — the operational foundation                │
└──────────────────────────────────────────────────────────────┘

   Pillar 2 →  Pillar 3 →  Pillar 4 →  Pillar 5 →  Pillar 6
   Onboard  →  Adopt    →  Retain   →  Expand   →  Advocate
   Defined  →  Realized →  Sustained → Expanded →  Championed

┌──────────────────────────────────────────────────────────────┐
│  Pillar 7: Strategic Advisor                                 │
│  "Value Prescribed" — the human elevation layer              │
└──────────────────────────────────────────────────────────────┘

Pillars 2 through 6 happen during the journey — every customer moves through them in sequence. Pillars 1 and 7 happen across the journey — they cut through everything, every customer, all the time.

Before going pillar by pillar, the distinction matters: teams that try to "implement the seven pillars" by starting with Onboarding and walking forward in numerical order almost always stall — because without Pillar 1's foundation, every practice becomes individual heroism that doesn't scale.

Pillar 1 — Operationalizing Customer Success

Value Managed — the CS team delivers proven best practices at scale, repeatably and efficiently.

McCulloch calls this "the most important and least understood" pillar. It's the one companies new to CS skip, and it's why most CS teams plateau around 200 accounts per CSM and can't get past it.

What this pillar contains:

Documented playbooks — not in the senior CSM's head, but in Confluence/Notion/wherever.
Customer success plans with a shared template.
A customer health score with defined weights and triggers.
A customer journey map (and the mirror churn-journey map).
Operating cadence — when QBRs happen, who runs them, when escalation fires.
Clear segmentation — high-touch, low-touch, tech-touch — with objective criteria.

Signal the pillar is weak: every CSM "has their own way" of running onboarding. You can't hire a CSM and have them productive in a week because there's no documented "house way." Scaling depends on copying Maria's vibe.

McCulloch's prescription: hire CS Ops before hiring the third or fourth CSM. Most companies hire CS Ops last — by then the chaos is baked in.

Digital CS, not tech touch. McCulloch is sharp on the distinction: tech touch removes humans; digital CS embeds humans into the product. Contextual in-product guides, alerts that trigger human action at the right moment, real-CSM videos explaining a feature — not chatbots trying to substitute for empathy.

Pillar 2 — Onboarding

Value Defined — jointly define the success plan and guide the customer to value one in the fastest possible time.

Onboarding is finite. Clear start, clear middle, clear end. It's the pillar with the biggest influence on whether the first renewal happens — and tripping here means playing catch-up the entire contract.

The key concept is "value one": the first business outcome delivered during onboarding. It must be achievable and fast. The book's classic example: an aviation customer wanted "roll out across all airports we operate, in 18 months." It was renegotiated to "roll out at one airport" — same direction, realistic scope, fast feedback.

The 5 steps of exceptional onboarding:

Focus on the right people — stakeholders, project managers, admins, the customer's own CSMs.
Understand the specific goals of those individuals — not "the company" in the abstract.
Clear timelines and execution plan — pilot or massive rollout? How long per phase?
Deliver value one.
Map the path to maturity — always think two moves ahead.

Onboarding ≠ Adoption:

	Onboarding	Adoption
Duration	Finite	Ongoing
End	Defined	Never
Goal	Value one achieved	Operational dependence + business value

Dominant risks: launch risk (deployment stalls) and adoption risk (it forms here, even if it surfaces later).

The CSM as easy button:

Explode out of the gate. Start the success plan within days, not months.
Remove obstacles before they appear. "IT typically needs three weeks — let's open the request today."
Learn to listen. Including listening to the competitor — your customer is.

Pillar 3 — Adoption

Value Realized — achieve operational dependence while demonstrating business value.

Adoption is ongoing. Never ends. And it's the point where teams most often confuse their metric.

Adoption is not license utilization. Seats filled tells you very little. What matters is whether the customer is using the right features — the ones tied to the outcomes they promised their own business. The book's example: an identity-management company found that the strongest predictor of churn wasn't license utilization but the use (or non-use) of three specific features.

What the CSM does in this pillar:

Generate operational dependence. Remove barriers. Stage in capabilities — like Candy Crush unlocks skills level by level.
Engage the right stakeholders. Shane Anastasi's four-question test: budget owner? signatory authority? job at risk if it fails? operational owner? Two or more "yes" = real stakeholder.
Monitor consumption with depth. Logins, depth of use, ride-alongs — sit with users and watch them work.
Be release-ready. Be able to demo new features the day they ship.
Lead organizational change. Kill the FUD, evangelize value, make abandoning the old way easy.
Show benchmarks. How does this customer compare with peers? Motivational and instructive.

The red-flag test: ask the customer, during adoption, if they'd be a reference. A "yes" is a positive milestone. A "let's wait and see" is a flag — survey now, find out what's missing.

Dominant risk: relationship risk — acute (sponsor leaves without notice) and persistent (small frustrations stack up, no new champions being nurtured).

Pillar 4 — Retention

Value Sustained — the carefully orchestrated process whereby the customer chooses to extend the relationship.

The subtlety here matters: the renewal is a milestone; retention is the process. And the customer doesn't renew on past value — they renew on the future value you're promising.

Customers don't choose to stay because of historical value. They stay because of the vision and promise of the future you've painted with them.

If a customer leaves saying "we found a vendor with a better vision," that's not a delivery failure. It's a future-value gap. End-of-contract conversations need to overweight forward-looking content — roadmap, vision, transformation.

The math that makes this pillar critical:

A 5% increase in retention → 25% increase in profit (Bain).
A SaaS losing 2–3% of customers per month must grow 27–43% per year just to stand still (Tomasz Tunguz).
Past month 18, a retained customer is practically pure profit.

The mandatory metrics:

GRR = (current ARR − reductions − churn) / starting ARR
NRR = (ARR + expansion − reductions − churn) / starting ARR

GRR ≤ 100%. NRR can exceed 100%.

Three patterns for CSM involvement in renewal:

Guide the process — CSM works alongside a renewal manager.
Transactional increases — CSM handles seat adjustments. Common up to ~$50M ARR.
Manage the renewal — CSM owns the whole thing. Common up to ~$20M ARR.

McCulloch's recommendation: build a dedicated renewals team around $100M ARR, reporting to the same leader as CS (Head of CS or CCO) — never under sales.

Dominant risk: product fit risk — customer isn't using the product as intended, or the product can't actually deliver the promised outcome.

Pillar 5 — Expansion

Value Expanded — the customer sees value and grants you the opportunity to increase it.

The golden rule: CSMs don't sell. CSMs uptell — they educate the customer about capabilities that would increase the value being captured.

Why expansion becomes inevitable at scale:

$1M ARR with 10% churn = $100K to replace. Manageable.
$1B ARR with 10% churn = $100M to replace. Impossible via new logos.

Churn scales linearly with ARR. New-logo acquisition is linear. The only math that closes at scale is in-base expansion.

ProfitWell data cited in the book:

Companies without CS: median ~10% revenue from expansion.
Companies with CS: median ~22%.
Top 75th percentile: as high as 35%.

Cost of acquisition by revenue type (Pacific Crest, 2016):

Activity	Cost per $1 of revenue
New logo	$1.16
Renewal	$0.13
Upsell	$0.27
Expansion	$0.20

Expansion is the second-cheapest revenue your company can earn.

Passive vs. active expansion:

Passive — natural outgrowth of pillars 1–4. The customer buys more on their own.
Active — the CSM creates a CSQL (Customer Success Qualified Lead) and hands it to sales. CSQLs convert at 60–70% vs MQLs at 5–20%, because the CSM has far more account context than marketing does.

The four-phase strategy:

Identify and engage stakeholders.
Identify priorities and improvement areas.
Share (uptell) — industry stories, data, peer references.
Confirm financial viability and capture the CSQL.

Dominant risk: feature idea risk — promised feature not delivered (acute) or customer requests stacking up unanswered (persistent). Customers prefer "no" to silence.

Pillar 6 — Advocacy

Value Championed — a competitive advantage that accelerates new-logo acquisition and solidifies the base through deliberate programs and assets.

The anchor for this pillar is a conversation that opens the chapter:

— "We have a ton of advocates." — "Do you capture that feedback and share it with the market?" — "Oh, no. We don't do that." — "Then you don't have customer advocacy."

Having advocates ≠ doing advocacy. Advocacy is capitalizing on advocates through a program.

The 5 required assets:

Value and maturity assessments. Quantitative proof of value delivered + benchmark against peers.
User-generated content. Testimonials, reviews, case studies. The cautionary tale: a $1B-revenue company with 47 case studies across 40 products — pure fragmentation.
Referrals. Build a reference library segmented by industry, geography, use case. Stop tapping the same three customers every quarter.
"Referring" (distinct from referral). When an advocate changes companies and brings you with them. Pure gold — no outreach needed.
Focused events. Speaking engagements, trade shows, customer events. Elevates the advocate's career alongside your brand.

The three Cs:

CABs (Customer Advisory Boards) — segmented by product/vertical/geo/spend. Mix super-advocates with strugglers; the latter learn fastest from the former.
Champion Programs — equip your fans. Training, certifications, swag, roadmap access. Recertify every 6–12 months.
Online communities — real communities, not ticket-deflection forums. Drive self-service, reveal advocates, surface feature ideas.

The Advocate Maturity Map:

Identify — find the advocate.
Nurture — share assessments, prime them. Start with low-effort asks.
Engage — case studies, references, champion programs.
Promote — they evangelize on their own at events, in communities, on social.

CSMs identify and nurture; customer marketing engages and promotes. Advocacy should be owned by CS, not marketing — CS knows the customer, marketing distributes.

NPS — friend or foe? McCulloch's verdict: use NPS to identify advocates. Don't use it to measure company health. Intent ≠ behavior. For actual experience, use Customer Effort Score (CES).

Dominant risk: sentiment risk — a relationship-risk variant. High sentiment → high advocacy probability.

Pillar 7 — Strategic Advisor

Value Prescribed — the human elevation layer. Actively advises on strategic decisions, unbiased, with deep knowledge.

McCulloch is surgical about separating trusted advisor ("everyone in the company should be one") from strategic advisor (an elevated, specific capability). Being trustworthy is the floor. Being strategic is the ceiling.

A strategic advisor is someone who actively advises organizations on important strategic decisions, in an unbiased fashion, using deep industry knowledge and domain expertise.

The KSE Model (Knowledge × Skills × Experience), co-developed with Shane Anastasi:

Knowledge

Industry — trends, disruptions, influencers. Read trade press. Know the customer's competitive landscape.
Customer — long-term priorities, relationship map (who influences whom), desired outcomes the customer hasn't fully articulated yet.
Product — features, roadmap, use cases, differentiators, sticky features.

Skills

People — assertiveness (the customer isn't always right), empathy, relational intelligence.
Analytical — data analysis, finding meaning in numbers, presenting data-driven solutions.
Prioritization — inbox, calendar, deep work. Don't sacrifice relationship time to a meeting flood.

Experience

Three modes (Anastasi's framework):

Prescribe — advise with the authority of someone who's seen this many times before.
Protect — when the customer decides against your recommendation, name the consequence. Implicit acceptance is dangerous.
Proact — lead the customer to success. Plot the course, watch for deviation, escalate when needed.

The 7 tips for being a strategic advisor:

Listen and seek to understand before acting.
Be proactive — anticipate problems.
Be the customer's advocate — even if that means recommending a competitor.
Educate constantly.
Over-communicate — alignment drifts, reset it often.
Build relationships 3 × 3 — three seniority levels, three contacts at each.
Focus on long-term success.

Dominant risk: noncontrollable risk — pandemics, acquisitions, regulatory changes. You can't prevent these, but you can shape the response. The book's COVID example: vendors that offered pre-approved payment pauses and discounts kept customers. Those that clung to contract terms lost them.

How to use this framework in practice

McCulloch gives an implementation prescription in the closing chapter:

Audit what already exists. Which pillars are partially built? Where are the playbooks, the QBRs, the success plans?
Optimize first, fill gaps second. Sharpening an existing pillar is faster than building one from scratch.
Find gaps and build a strategic plan. Don't try to build all seven at once. Start with Pillar 1 — without operationalization, the rest can't scale.
Audit the org chart. If CS reports to sales, that's the first thing to fix.

The mental shortcut that matters

When you look at a CS team and want to know which pillar is weakest, three questions solve 80% of the diagnosis:

Is onboarding finishing on the agreed timeline, with value one named and achieved? No? Pillar 2 is broken.
Can you forecast renewals 90 days out with low margin of error? No? Pillar 4 is broken — probably because of Pillar 1.
Is more than 20% of your revenue coming from in-base expansion? No? Pillar 5 is dormant — almost certainly because of Pillar 1.

Notice everything falls back to Pillar 1. That's why McCulloch insists: operationalize first. Without that foundation, the other six pillars become dependent on the heroism of your most senior CSM — which is the operational definition of non-scalable.

Based on McCulloch, Wayne. The Seven Pillars of Customer Success: A Proven Framework to Drive Impactful Client Outcomes for Your Company (2021). The illustrations, examples, and prescriptions in this article are interpretations of the framework adapted to B2B reality by the Partenero team.