The "5-year customer" model: aligning the whole company around retention

The board meeting comes round, churn is up, NRR is flat, and every eye turns to the same person: the Head of Customer Success. As if keeping customers were their problem, and theirs alone. Yet the customer who leaves was often poorly qualified by Sales, oversold by Marketing or let down by a Product team that never delivered the promised value. Churn didn't start on the day the contract wasn't renewed. It started long before. Here's how to finally make your whole organisation accountable for retention.

There's a line every SaaS company trots out. "We deliver long-term value." "The customer is at the heart of everything we do." "Customer Success is everyone's job."

In practice, it's often just words.

Bob Mathers, a coach to SaaS leaders, puts it bluntly in his "5-year customer" model: most companies are designed, from top to bottom, to attract and sign a customer once. The whole machine (acquisition, budgets, incentives, tools) is built around closing. And once the contract is signed, retention and upsell are handed over to CS with an unspoken instruction: sort it out!

We all know the result. Acquiring new customers is getting ever more expensive, sales cycles are getting longer, and NRR becomes the only way to hit targets, yet nobody other than CS is genuinely held accountable for it. It isn't a question of effort. It's a question of method.

The diagnosis every leader shares

When you talk to founders and CEOs, the same phrases come up, almost word for word. New customers are harder to find and more expensive to acquire. Renewals, once automatic, have become battles, and those who renew sometimes do so for less. Upsell exists, but it only reaches a handful of accounts. And to hit targets, you absolutely have to generate more revenue from the installed base.

So far, everyone agrees. The disagreement starts when it comes to deciding who's responsible.

That's when the organisational reflex kicks in: it's about existing customers, so it's CS. It's about churn, so it's CS. It's about NRR, so it's CS again. But that reflex rests on a basic mistake. The CSM usually only comes on the scene once the account is signed. Yet a huge amount happens before signature, and the customer's future success depends directly on it.

Why churn isn't just Customer Success's problem

Let's retrace the journey of a customer who ends up leaving. Marketing put out slick messages, sometimes a little ambiguous, for a slightly oversold product. The prospect signed with the wrong expectations. Sales, in a hurry to close, accepted an account that wasn't a good fit and threw in a few extras for free to get the deal over the line. The handover to onboarding was done on the back of an envelope, without passing on the customer's real goals. Product never prioritised the features that mattered to them. And twelve months later, the CSM inherits a shaky contract they're asked to rescue.

The truth is that churn is a company-wide issue that needs to run through every level of the business. Marketing, Sales, Product, Onboarding, Support, CS: every department has a direct impact on customer satisfaction and on the company's ability to keep the customer. The CSM is just one link in the chain. The real guardian of retention is the CEO.

The underlying problem is structural. When each department pursues goals disconnected from the common interest, it inevitably works against the team next door. Marketing optimises lead volume, even if that means sending off-target prospects. Sales optimises the number of deals signed, even if that means discounting heavily and over-promising. Everyone gets their bonus. And the customer churns.

What the "5-year customer" model really changes

The value of Bob Mathers's model isn't in sticking NRR on everyone's objectives and thinking the job's done. It's in redefining the role of each function around one shared goal: attracting, acquiring and retaining the customer for five years.

In practice, that means rewriting each team's job description.

Marketing no longer defines the ideal customer by their propensity to buy, but by their propensity to succeed. It doesn't stop at lead generation: it runs customer marketing to drive adoption and value over time.
Sales no longer try to close anyone and everyone: they qualify and sign ideal customers, and above all they organise a clean handover to onboarding and CS.
Product no longer ships features for the sake of it: it prioritises customer feedback to deliver value and prove impact.
Support no longer just resolves tickets: it acts as the voice of the customer with Product, to fix problems at the root.

Each function stops being a silo optimising its own local metric. It becomes jointly responsible for the same customer, over five years.

Source: bobmathers.ca

Why isn't this just OKRs?

At this point, if you use OKRs, you're probably thinking: "A shared goal broken down into metrics for each team is exactly what we already do." There's a real family resemblance. But confusing the two would be a mistake.

An OKR system is first and foremost a cadence: ambitious goals, reviewed every quarter, measured by key results. Mathers's model isn't a cadence, it's a redefinition of roles. It doesn't tell you to "set better goals this quarter". It tells you that the very definition of Marketing's, Sales's or Product's job has to change.

And this is where it matters: an organisation can have flawless OKRs and still be structurally designed to sign the customer once. Because its OKRs remain silo OKRs. Marketing has its lead-volume key results, Sales their deals-signed key results, everyone optimises their own column, and the customer churns anyway. OKRs don't fix that design flaw. They just sit on top of it.

So Mathers's contribution isn't the mechanics. If you like, use OKRs as the vehicle; that's absolutely fine. What changes everything is what you put in them: steering each function towards customer success, not towards its own local performance.

KPIs that make every function accountable

This is where the model becomes operational. Mathers offers a set of example KPIs for each function. They're not meant to be copied as they are, but they show what an organisation genuinely aligned around retention looks like. Here are a few examples from his model.

Marketing, moving from volume to the quality of the promise:

Increase lead conversion using a customer-success-oriented ICP
Generate qualified leads with customer stories based on results achieved
Improve use of new features through training programmes

Sales, with quality goals, not just closing goals:

Raise the ideal-customer qualification rate from 60% to 90%
Document the expected goals and outcomes for 100% of deals at an advanced pipeline stage
Reduce onboarding time through a better handover

Product, committing to value as actually perceived:

Launch features that address customers' main pain points
Achieve a high adoption rate in the months following each release
Drastically reduce time to value for new customers

Customer Success, still at the heart of things, but with measurable commitments:

Build a personalised success plan for 100% of new customers in their first few days
Increase the share of customers who pass their success plan milestones
Generate more qualified opportunities (CSQLs)

Support, becoming proactive instead of reactive:

Improve the first-contact resolution rate
Reduce average response time
Use AI to anticipate and fix problems before the customer runs into them

Revenue Operations, overseeing the process end to end:

Shorten the lead-to-revenue cycle
Improve the accuracy of revenue and churn forecasts
Increase lifetime value through coordinated upsell and cross-sell strategies

The common thread: every function now carries an explicit share of responsibility for retention and expansion. Nobody can hide behind "that's not my job" any more.

Source: bobmathers.ca

Don't fall into the "NRR everywhere" trap

A word of warning, and it comes from Bob Mathers himself. He insists on one point: this isn't simply about adding net revenue retention to everyone's objectives. Putting "+8% NRR" on every team's roadmap isn't enough, and can even be counter-productive.

First, because an overly broad metric doesn't tell anyone what they should do differently when they get to the office. Product has no direct day-to-day grip on NRR; it does have a grip on time to value and adoption. The whole point of the model, Mathers stresses, is to be specific about each function's role in customer success, not to spread the same figure everywhere.

Second, because NRR can mask what's really going on. A healthy figure driven by a few big upsells can hide a steady loss of small accounts. That's why you need to track it alongside the gross churn rate, not instead of it.

And to boost it sustainably, most of the work happens upstream: qualifying the right prospects (the famous "good-fit customers" with a higher LTV), stopping Sales from giving everything away to sign, training CSMs to spot upsell, and breaking down silos between teams, even bringing acquisition and retention together under a single owner such as a CRO.

Where to start in practice

The "5-year customer" model is a new approach, not a magic formula. To get it moving without breaking everything, ask yourself three questions, drawn directly from Mathers's approach.

How do these KPIs differ from the ones we use today? Take each department's objectives and compare them with the "5-year customer" logic. The gap you see is exactly the measure of your current misalignment.
How could these goals finally align every department on the customer's long-term success? Look for the places where two teams are working against each other. A Marketing team paid on lead volume and a CS team paid on retention are, by design, not working for the same customer.
What concrete problems would this solve? The rushed Sales-to-CS handover, oversold customers, non-existent success plans, a Product team disconnected from real needs. Each of these problems has a natural owner in the model.

And don't underestimate the cultural dimension. Getting every department to converge on shared goals requires a deep change, and that can only come from the top. It's the CEO's responsibility, not the Head of CS's. As long as retention remains a delegated issue, it will remain a lost cause.

Conclusion

Bob Mathers's message fits in one sentence: most companies aren't built to keep their customers, they're built to sign them once. As long as that architecture stays in place, no CSM, however good, can make up for a system designed against retention.

Making everyone accountable for churn and NRR doesn't mean adding a line to everyone's objectives. It means redefining each function's role around a customer you want to keep for five years, and giving yourself the KPIs to match. If you remember one thing, make it this: churn is a team sport, and the captain is the CEO.