The renewal that almost wasn’t
Ninety days before Ambermoor Health’s renewal, Brindlepath’s customer success manager, Tomás Rivera, ran his usual review and found something alarming. Ambermoor was Brindlepath’s largest customer, and on paper everything was fine: no open escalations, a friendly relationship with the director of care management, and an invoice paid on time. But the usage data told a different story. At two of Ambermoor’s five hospitals, the share of high-risk patients with a confirmed owner within 24 hours had fallen from over 80 percent to under 40 percent in three months.
Tomás called the navigator managers at both hospitals. One had lost three experienced navigators to retirement, and the new hires had never been trained on the product. The other had changed how discharges were coded, so a third of high-risk patients no longer appeared in the queue at all.
Neither problem would have reached Brindlepath through a support ticket. Both would have shown up at renewal as a vague sense that “the product isn’t working for us anymore.” Instead, Brindlepath trained the new navigators, fixed the coding mapping with the hospital’s IT team, and walked into the renewal conversation with a chart showing both hospitals back above 80 percent. Ambermoor renewed, and added two more hospitals.
Customer success is the discipline of noticing those signals early, and acting before the customer has to ask.
Customer success is not support
Support responds when something is broken. Customer success works proactively to make sure customers achieve the outcomes they bought the product for, and keep achieving them. Support is reactive and measured by how quickly problems are resolved. Customer success is proactive and measured by retention, expansion and, above all, customer outcomes.
The distinction matters because subscription businesses live or die on retention. A customer who signs a contract has bought the right to decide again at renewal. Every month in between, the product either proves its value or erodes it.
Why retention compounds
Small differences in retention produce large differences over time. Figure 14.1 follows the same $10 million of annual recurring revenue over five years at three different rates of net revenue retention: the revenue you keep from existing customers, including expansion, as introduced in Chapter 6.
At 90 percent net retention, the base shrinks to about $5.9 million in five years, and the company must win more than $4 million of new business just to stand still. At 100 percent, it holds steady. At 120 percent, existing customers alone grow it to nearly $25 million. That is why the best software businesses invest heavily in the customers they already have: retention and expansion are usually cheaper than acquisition, and they compound.
The customer life cycle
Customer success follows customers through a life cycle, with different work at each stage.
Onboarding and implementation. The customer sets up the product, connects data and trains users. In healthcare, this often includes record integration, security review and clinical workflow changes. The goal is time to first value: how quickly the customer sees the outcome they bought. For Brindlepath, first value was the first week in which a hospital’s navigators confirmed ownership of more than 80 percent of high-risk patients.
Adoption. Users build the product into their daily work. Customer success tracks usage, finds teams or sites that are lagging, and helps them catch up.
Value realization. The customer achieves and can demonstrate the outcomes they bought: fewer missed follow-ups, fewer readmissions, saved time. Regular business reviews make this value visible to the executives who will decide on renewal.
Renewal. The customer decides to continue. Renewals should be a formality by the time they arrive, because the value has been shown throughout the year.
Expansion. The customer extends the product to more users, sites or modules. Expansion is the natural result of proven value, not a separate sales campaign.
Onboarding matters most
Of all these stages, onboarding has the largest effect on long-term retention. Customers who reach first value quickly tend to stay; customers who struggle through a long implementation often never fully recover their enthusiasm. Brindlepath’s analysis in Chapter 10 found that customers who reached 80 percent ownership within 90 days almost always renewed.
To shorten time to first value:
- Define first value precisely, for each type of customer, and track it.
- Remove setup work from the customer. Standard integrations, templates and sensible defaults beat custom configuration.
- Start small. Get one team or site to value first, then expand.
- Assign clear owners on both sides, with a shared plan and dates.
- Celebrate first value with the customer’s executives, so they see it early.
Health scores: seeing trouble early
A customer health score combines several signals into an early warning of risk or opportunity. There is no universal formula, and simpler is usually better. A good health score includes:
- Outcome measures: is the customer achieving what they bought? For Brindlepath, the ownership rate and follow-up rate at each site.
- Adoption measures: are the expected users active? Is usage growing or falling?
- Relationship signals: is there an engaged executive sponsor? Has the champion left?
- Support signals: are there unresolved issues or a rising trend in tickets?
- Commercial signals: are invoices paid on time? Has the customer asked about price or contract changes?
Weight outcome and adoption signals most heavily. Relationship signals matter, but a friendly contact can hide a failing deployment, as Tomás found at Ambermoor. Review health scores regularly and, more important, act on them: each at-risk customer should have an owner and a plan.
Turning feedback into product
Customer success teams hear more from customers than anyone else in the company. That knowledge belongs in the product.
Create a regular channel. Brindlepath’s customer success managers met the product trios every two weeks to share patterns: what customers struggled with, what they asked for, where they found workarounds.
Bring evidence, not just requests. “Three customers asked for bulk reassignment” is useful. “At three customers, navigators spend about 20 minutes each Monday reassigning weekend discharges one by one” is far more useful, because it describes the problem.
Close the loop. When customer feedback shapes the product, tell the customers who raised it. Few things build loyalty faster than seeing your suggestion in a release note.
Advocacy
Satisfied customers are your most credible marketing. In business software, and especially in healthcare, where buyers trust their peers far more than vendors, a reference call from a respected customer can decide a deal.
Build advocacy deliberately:
- Help customers tell their story, in case studies, conference talks and peer conversations, with their outcomes and in their words.
- Create a customer community, such as user groups or an advisory board, where customers learn from each other and from you.
- Respect your advocates’ time. Do not overuse a small group of references. Reward them with early access, influence on the roadmap and recognition.
- Get permission and stay accurate. Any claim about a customer’s results should be approved by the customer and supported by data.
Brindlepath in practice: the quarterly business review
Brindlepath’s customer success team rebuilt its quarterly business reviews around one principle: the customer’s outcomes come first, the product second.
Each review followed the same structure and lasted under an hour. It opened with the customer’s own goals, restated from the start of the relationship: for Ambermoor, reducing missed follow-ups and avoidable readmissions across its hospitals. Then came the outcome measures, trended over the quarter and the year, by hospital: the ownership rate, missed first follow-ups and the estimate of avoided readmissions from the outcome report. Then adoption: active navigators by site, with any site falling behind named openly and a plan to help. Then what the customer had told Brindlepath, and what Brindlepath had done about it. Only then the roadmap: what was coming that would help this customer specifically, and what the product team wanted to learn from them. The review closed with agreed next steps, each with an owner on both sides.
Two details made the difference. Tomás and his colleagues sent the outcome data to the customer’s champion a week ahead, so there were no surprises in front of executives. And they always invited the executive sponsor, not just the day-to-day users. If the sponsor could not attend, they rescheduled. A review without the person who decides on renewal is a status meeting.
Over two years, the reviews became one of the most valued parts of the relationship. Several customers began using the same outcome slides in their own board meetings, which was the clearest possible sign that Brindlepath had made its value visible.
Onboarding, redesigned
Before the 90-day finding in Chapter 10, Brindlepath’s onboarding was a sequence of technical steps: contract signed, integration built, users trained, live. Time to first value averaged more than five months, mostly spent waiting on integration work and approvals.
The redesign reorganized onboarding around first value. Integration moved onto the standard connector, which cut the technical work from months to weeks. One hospital and one navigator team went live first, rather than the whole health system at once. The customer’s navigator manager and Brindlepath’s onboarding lead shared a written plan with dates and a single goal: 80 percent ownership within 90 days of go-live at the first hospital. Training became short, role-specific sessions in the navigators’ own environment, followed by a check-in after the first week.
Average time to first value fell to under three months, and the share of new customers reaching 80 percent within 90 days rose sharply. Expansion to the remaining hospitals in each system began sooner, because the first hospital’s results made the case internally.
Common mistakes
Mistaking friendliness for health. A warm relationship with one contact can hide a failing deployment. Watch outcomes and usage, not just sentiment.
Ignoring onboarding. Customers who struggle through a long implementation often never fully recover their enthusiasm, whatever you do later.
Measuring support, not success. Ticket resolution time matters, but it does not tell you whether customers are achieving what they bought.
Treating renewal as a sales event. If value has not been shown all year, a renewal meeting is too late to start.
Burning out your advocates. The same three references asked for every deal soon stop answering. Grow your advocate community and reward the people in it.
Keeping customer knowledge in customer success. Patterns that customer success managers see every week belong in product decisions. Without a regular channel, they stay in their heads.
Try this
Pick your five largest customers. For each, write down their outcome measure, its trend over the last quarter, the number of active users by site, the name of their executive sponsor and the date of your last conversation with that sponsor. Mark any customer where the outcome or usage is falling, or where you are unsure the sponsor is still in place. Each marked customer gets an owner and a plan this week, before the renewal conversation makes the decision for you.
How AI changes this
AI can watch every account. An AI assistant can monitor usage, support tickets, emails and meeting notes across all customers and flag the kind of decline Tomás found at Ambermoor, without waiting for a quarterly review. It can draft the account summary before every call. Treat its alerts as prompts for a human conversation, not as conclusions.
AI can deliver help at the moment of need. In-product assistants that answer questions using your help content, guide users through tasks and explain what changed in a release can shorten onboarding and reduce support load. Make sure they draw only on accurate, current content, and hand off to a person when they cannot help.
AI can scale customer success. With AI handling research, preparation and routine follow-up, a customer success manager can serve more accounts with more attention, rather than less. The relationship itself, the trust built through honest conversations, stays human.
AI features need their own success plan. Customers adopting AI features often need more guidance, not less: what the feature is good at, where to double-check it, and how to give feedback when it is wrong. Build this into onboarding.