6 min read · 1,290 words
The customer experience programme that taught me the most wasn’t the one that succeeded cleanly — it was the one that worked for the customers we designed it around and quietly failed the ones we didn’t think to ask. Good CX design in B2B isn’t about running one more survey; it’s about knowing which stakeholder inside the account you’re actually designing for, because a programme built for one persona can be invisible, or actively frustrating, to another — the same multi-stakeholder blind spot I’ve argued distorts B2B budget conversations in how much a B2B company should spend on brand.
What we set out to build
The brief was straightforward on paper: reduce friction in the post-sale onboarding process for new accounts, which internal data showed was where a meaningful share of early churn originated. We mapped the journey from the day-to-day operational contact’s perspective — the person actually using the service week to week — and built the programme around making their first ninety days smoother: faster response times, proactive check-ins, a dedicated point of contact during ramp-up.
What worked
For the operational contact, it worked well. Satisfaction scores from that specific persona improved meaningfully, response-time complaints dropped, and qualitative feedback was consistently positive. If we’d measured success purely by that persona’s experience, the programme would have looked like an unambiguous win, and for a while, that’s exactly how it was reported internally. Bain’s own research on customer retention — from the firm that originated NPS — has itself moved toward emphasising the whole-account relationship over any single satisfaction metric, which is a notable shift given NPS’s origin.
What we missed, and how we found out
Six months in, churn in the accounts we’d “fixed” hadn’t actually moved. The operational contact was happier. The executive sponsor — the person who’d actually signed the contract and who reviewed the relationship at renewal — had received almost none of the programme’s benefit, because nothing in the onboarding experience had been designed with their concerns in mind. They weren’t asking “is my day-to-day contact responsive,” they were asking “is this investment delivering the outcome I told my own boss it would deliver,” and our entire CX programme had nothing to say to that question.
This is a specific, well-documented failure mode in B2B CX design. Gartner’s research on B2B buying groups puts the average number of stakeholders involved in a purchase decision at six to ten people, and that group doesn’t disappear after the contract is signed — it’s often the same group reviewing whether the relationship continues. Designing a CX programme around a single persona, even the persona with the most day-to-day contact, leaves the rest of the buying committee’s experience entirely up to chance. Forrester’s CX Index research has made a related point at the account level: CX quality correlates with revenue outcomes only when it’s tracked across the full account relationship, not a single respondent’s experience.
The fix: a stakeholder-mapped CX programme
We rebuilt the programme around three distinct experience tracks running in parallel rather than one generic journey. The operational contact kept the responsiveness and check-in cadence that was already working. The executive sponsor got a quarterly outcome review — a short, structured conversation tied explicitly to the business case they’d made internally to justify the purchase, not to service tickets or response times. Finance, where relevant to the account size, got a simplified cost-and-usage summary they could use in their own internal reviews without having to request it from anyone.
| Stakeholder | What they actually care about | What the original programme gave them |
|---|---|---|
| Operational / day-to-day contact | Responsiveness, ease of use, fast issue resolution | Everything — this was the only persona designed for |
| Executive sponsor | Whether the outcome they promised internally is being delivered | Nothing structured — occasional informal updates at best |
| Finance / procurement | Cost, usage, easy internal reporting | Nothing — had to request information manually when needed |
What changed once all three tracks existed
Renewal conversations got measurably easier, because the executive sponsor arrived at the renewal review already having seen a quarter of documented progress against their own stated business case, rather than being handed that argument cold by our sales team at the last minute. That’s the part of B2B CX design that’s easy to miss if your programme design starts and ends with the person who logs the most support tickets: the account’s actual survival depends on the person who isn’t in your support queue at all. Qualtrics’ XM Institute research has documented the same pattern across B2B accounts generally: retention outcomes track much more closely with executive-level relationship health than with day-to-day satisfaction scores alone.
Why NPS didn’t catch this problem earlier
Our NPS survey, sent primarily to the operational contact, kept reporting healthy scores throughout the period the executive-sponsor gap existed — which is exactly the blind spot I’ve written about separately in the CX score trap: what NPS never tells you. A single-respondent sentiment score cannot surface a problem that only exists for a stakeholder the survey never reaches. We found the executive-sponsor gap through account-level churn analysis and direct conversation, not through the metric that was supposedly measuring CX health.
What this means for you
Before building or auditing a B2B CX programme, map every distinct stakeholder role in your typical account, not just the one who generates the most support volume. Ask what each one actually needs to feel the relationship is working, and check honestly whether your current programme has anything designed specifically for them — or whether, like ours initially did, it only has something for whoever happens to be easiest to reach. Zendesk’s CX Trends research backs this up from the buyer side: a majority of B2B buyers now weigh experience as heavily as the product itself in renewal decisions, and “experience” in that research spans the whole buying committee, not one contact.
Frequently asked questions
Why did a CX programme with strong satisfaction scores fail to reduce churn?
Because it was designed around one stakeholder persona (the day-to-day operational contact) while churn was actually being driven by an unaddressed gap with a different stakeholder (the executive sponsor), whose experience the satisfaction survey never measured.
How many stakeholders typically need to be considered in a B2B CX programme?
Gartner’s research puts the average B2B buying group at six to ten people, and many of the same people remain involved in reviewing whether the relationship continues after the sale — CX design needs to account for the full group, not just the most visible contact.
What does an executive sponsor actually want from a CX programme?
Evidence that the outcome they promised internally to justify the purchase is being delivered — not faster support response times or day-to-day service quality, which is what most CX programmes default to measuring.
Why didn’t NPS catch the executive-sponsor experience gap?
The survey was sent primarily to the operational contact, so it structurally could not surface a problem affecting a different stakeholder who never received the survey at all — a single-respondent score can only ever reflect that respondent’s experience.
What’s the simplest first step to fix a single-persona CX programme?
Map every distinct stakeholder role in a typical account and check what, if anything, your current programme delivers specifically for each one. Gaps usually appear immediately once the mapping is done honestly.
Which stakeholder in your accounts is least likely to be reached by your current CX programme? I’d like to hear what mapping that gap actually surfaced.
Related reading: how to build a B2B journey map that actually gets used.
