Day 224 of the Daily · Growth Strategy

Zero Defections

5 min read · 4 principles · apply it by lunch

The customer you kept last year is worth more to you this year than they were last. Your reporting almost certainly can’t tell.

The question

Take a customer who’s been with you four years and one who signed last quarter: do you actually know whether the older one costs less to serve, buys more, brings you referrals and argues less about price — or do they land in your accounts as the same line of revenue? For most businesses it’s the same line. That flattening is why a departure gets logged as a number and never as a cause.

The idea

Frederick Reichheld of Bain & Company and W. Earl Sasser Jr. of Harvard Business School published Zero Defections: Quality Comes to Services in the Harvard Business Review in September 1990. The move in the title is the whole argument: manufacturing had spent a decade chasing zero defects, so treat a customer walking away as a defect — something with a cause, worth investigating, never acceptable as background noise. What they found across the service businesses they studied was that profit from a customer rises the longer that customer stays, and it rises for four separate reasons stacked on the base profit from what they buy. They buy more as the relationship widens. They cost less to serve, because they’ve learnt how you work and stop needing help. They refer other people, who arrive at no acquisition cost. And they’re less price-sensitive than a stranger collecting quotes. Stack those four on the base and the arithmetic stops being linear: by their estimates, cutting the defection rate by five points would raise the value of a customer by between roughly twenty-five and eighty-five per cent depending on the business — around thirty in an auto-service chain, eighty-five in one bank’s branch deposits. The trap is reporting churn as a percentage beside other percentages, which makes two points look like a rounding error rather than the largest number on the page.

In the Daily · 4 principles and a template

Zero Defections is Day 224 of 365.

In the Daily, each of its four principles is explained in full, with a one-page template to apply it the same day. A new framework arrives every morning at 7am for a year, across all fifteen courses of the FutureMBA curriculum.

$29 a month · cancel any time · 7-day money-back guarantee

More from Growth Strategy

The next four in the course.

All 24 Growth Strategy frameworks
Day 233 · Growth Strategy

Net Revenue Retention

Take only the customers who were already paying you a year ago — nobody you’ve won since — and ask what that same group pays you this month: is it more than it was, and if you’ve never run that number, what have you been calling growth?

See the framework →
Day 242 · Growth Strategy

Product-Channel Fit

Take the acquisition channel you keep hearing works — the one a competitor appears to run beautifully — and ask what that channel demands of a product before it will carry one: how quickly the value has to land, how broad the appeal has to be, how much a single customer has to be worth in a year? Set your own product honestly beside those demands and the usual answer is that the channel was never available to you, which is a far cheaper thing to learn this morning than after a quarter of spend.

See the framework →
Day 251 · Growth Strategy

The Free Tier

Take everyone using your product without paying you anything — could you say what that population costs to serve in a month, what share of them upgraded last quarter, and what they sent back in referrals or usable data — or is free still filed in your head as a marketing gesture rather than a line of spend?

See the framework →
Day 260 · Growth Strategy

The Bullseye Framework

List every way a stranger could currently discover your business, then list the ways you’ve never tried — and if the second list is far longer than the first, and nothing on it was ever ruled out with evidence rather than instinct, how much of your growth is resting on a channel you inherited rather than chose?

See the framework →