What Makes This Journey Different
by Braden Kelley and Art Inteligencia
Most customer experience frameworks are written with a single decision-maker in mind — one person, one moment of dissatisfaction, one chance to leave. B2B SaaS almost never works that way, and an audit approach borrowed from consumer retail will miss most of what actually matters in a software buying and renewal relationship.
The journey has more than one customer in it
A single SaaS account often includes a buyer who approved the budget, an admin who configured the product, and a set of end users who never spoke to sales at all and may not even know your company name. Each of these roles experiences a completely different journey, forms a completely different opinion, and has completely different influence over renewal. An audit that only interviews the buyer — the person easiest to reach — misses the end users whose day-to-day frustration is often what actually drives churn, quietly, long before a renewal conversation happens.
Onboarding failures don’t show up until months later
In consumer contexts, a bad first experience usually shows up immediately — a return, a one-star review, a quick churn. In B2B SaaS, a confusing onboarding often doesn’t kill the relationship on day one. It just means the product never gets adopted the way it was sold to be used, usage stays shallow, and the account quietly becomes a non-renewal a year later for reasons that trace directly back to week one. Walking the onboarding journey firsthand — not reviewing the onboarding flowchart, but actually going through it as a new user would — is where this kind of audit consistently finds the most expensive gaps.
Support tickets are a lagging indicator, not a leading one
By the time a SaaS customer files a support ticket, they’ve usually already tried to solve the problem themselves, asked a colleague, checked the help docs, and given up more than once. The ticket is the tip of a much larger iceberg of friction that a support-ticket dashboard alone will never show you. This is exactly why data evaluation in an audit has to be paired with firsthand journey walking — the tickets tell you what people were frustrated enough to report; the journey walk tells you everything they weren’t.
Expansion revenue depends on trust building quietly in the background
Upsell and cross-sell in SaaS rarely happen through a single sales conversation — they happen because a champion inside the account has quietly built confidence in the product over months of ordinary use. Every piece of friction in that ordinary use is a small tax on that trust, invisible individually, but cumulative. An audit that maps the full post-sale journey — not just the support-facing parts — is usually where the connection between “small usability annoyance” and “expansion revenue we didn’t get” becomes visible for the first time.
Competitive benchmarking means something different here
In B2B SaaS, your real competitive benchmark often isn’t your closest direct competitor — it’s the best onboarding flow or support experience your buyer has encountered anywhere in their software stack. B2B buyers import their expectations from whatever consumer-grade product experience they use daily, which means “good enough” is a moving target set well outside your own category.
Where to start
If any of this sounds like it’s describing gaps you suspect exist but haven’t confirmed, the Customer Experience Revenue Leakage Self-Assessment is a good first step to see where your own program stands across the five core audit activities. From there, a Customer Experience Audit scoped specifically to a multi-stakeholder SaaS journey — buyer, admin, and end user — finds what a single-persona review structurally can’t.
Content Authenticity Statement: The topic area, key elements to focus on, etc. were decisions made by Braden Kelley, with a little help from Claude to clean up the article.
Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.
