Topic 5 — Building relationships and driving adoption

Goal: Turn customers into engaged, loyal users who rely on the product.

Lesson 5.1 — The relationship is what earns you the bad news

Onboarding is over. BrightSmile Dental is live on Cadence, the front desk has stopped emailing in a panic, and Imani could, technically, go quiet until renewal. A lot of vendors do exactly that, and it rarely ends well.

Six weeks later her phone rings. It's Dr. Priyanka Raman, the operations director — calling Imani's cell, not support, not sales. "Between us," she says, "the practice owner circled your tool on next year's budget last night. I wanted you to hear it from me before it turns into a problem."

That call is the entire payoff of the relationship Imani had been quietly building since day one. A customer who trusts you tells you the truth early: when budgets tighten, when a champion is about to leave, when they've started shopping a competitor. This is early warning — the honest, advance signal a CSM earns through trust, and a transactional vendor never receives.

A vendor finds out the customer is unhappy at renewal. A trusted partner finds out months before, while there's still time to do something about it.

Imani recognized the moment instantly — it was her old job in a new costume. In her hotel years she knew which guests were regulars, so the unhappy ones came to her first, before they ever wrote a review. The relationship is the channel every important signal travels down, and losing it means flying blind until the customer is gone.

Lesson 5.2 — How trust actually gets built

So how does a CSM go from "the vendor we email when something breaks" to "the person I call before it becomes a problem"?

Not with charm. Dr. Raman didn't warn Imani because Imani is warm and easy to talk to — plenty of likeable vendors get blindsided at renewal. She warned her because Imani had become reliable, the floor everything else stands on. Four habits do the work.

• Do what you say, then follow through. When Imani tells Dr. Raman she'll chase a bug with Theo's support team and circle back Thursday, she circles back Thursday — even when the only update is "still working on it." Small kept promises compound faster than one heroic save.
• Understand their world. Imani learned how a dental practice runs: why one missed reminder becomes a no-show fee, which long-tenured receptionist resents any change. A customer feels the difference between a CSM who knows their business and one reading from a script.
• Communicate on a steady rhythm. A short, useful note every few weeks — a tip, a "saw your no-shows tick up, want to look?" — keeps the line warm. The CSM who only surfaces at contract time reads as a salesperson in a friendly hat.
• Advocate for them inside Cadence. When BrightSmile needed a calendar-sync fix, Imani didn't just file a ticket and shrug. She pushed Theo and the product team, and kept Dr. Raman posted. Customers always know who actually fights for them.

Lena, Imani's manager and a former senior CSM herself, frames it the same way in every one-on-one: a relationship is a balance. You pay in with every kept promise and useful check-in, and you draw the whole thing down the one time you go silent when it mattered.

Lesson 5.3 — Adoption is the thing that actually locks them in

There's a trap here that catches kind, well-meaning CSMs. Imani could have the warmest relationship in her whole book at BrightSmile and still lose the account.

Because liking you doesn't pay the invoice. Using the product does. Adoption is deep, regular use of the product woven into the customer's daily work — and it, far more than friendliness, is what makes a customer stay.

Picture two clinics. The first logs into Cadence for one thing: printing the day's appointment list each morning. They're paying for scheduling, automated reminders, reporting, and waitlist management, and touching maybe a tenth of it. The second runs its entire front desk through Cadence — bookings, reminders, no-show tracking, the weekly report the owner now reads every Monday.

Which one renews?

The first is a churn risk no matter how much they enjoy Imani's calls. Ripping out a tool you barely use is painless, and when budgets tighten it's the obvious first cut. The second is locked in by genuine value — pulling Cadence out would break their Monday morning and a half-dozen daily habits. The product has become part of how they work.

So adoption isn't a vanity number. Shallow usage is a quiet countdown to churn; deep usage is the strongest retention there is, because the customer stays for reasons that have nothing to do with whether they remember the CSM's name.

Lesson 5.4 — Reading usage data, then leading with value

How does Imani know BrightSmile is the deep-usage clinic and not the print-the-list one? She doesn't guess, and she doesn't go by how friendly the last call felt. She reads the usage data — the record of which features each account touches and how often.

Usage data is the CSM's early-warning radar for adoption, and a few signals are worth knowing cold:

• A healthy primary feature — the thing the whole product exists to do — often clears something like 80% adoption among an account's active users; secondary features tend to land lower, frequently in the 40–60% range, but it varies a lot by product. These are rules of thumb, not hard numbers — real benchmarks span wide ranges (core features roughly 60–90%, secondary 30–60%), and what "healthy" looks like depends heavily on the product and the specific feature. The signal that actually matters is relative: a core feature far below where the rest of your accounts sit is a flag, whatever the headline percentage.
• A sharp drop in usage — roughly a 30% decline in a feature the customer used to lean on — is one of the strongest predictors that an account is drifting toward churn. The bigger and faster the drop, the louder the alarm.
• Many CS teams blend usage, support history, and sentiment into a single health score — a common mix weights usage heaviest, then support trends, then sentiment — so a whole book of accounts can be scanned at a glance for the ones quietly going cold. The payoff is lead time: a usage-based score tends to flag a declining account weeks earlier than a CSM's gut would have.

But spotting underuse is only half the move, and the second half is where beginners fumble. The reflex of a weak CSM is to fire off "you're not using these five features — use more!" Nobody reorganizes their workday because a vendor asked them to.

The strong move is value-led engagement: tie the unused feature to the customer's own stated goal, then offer it.

Don't sell the feature. Connect it to the outcome the customer already told you they wanted.

When Imani saw BrightSmile wasn't touching the automated waitlist, she didn't say "you're underusing the waitlist." Dr. Raman had told her weeks earlier that the practice's biggest bleed was revenue lost to last-minute cancellations. So Imani led with that: "You mentioned cancellations are costing you. The waitlist auto-fills a canceled slot from your waiting patients — for a practice your size that's usually a few recovered appointments a week. Want me to set it up with you in fifteen minutes?" Same feature. The first version is a nag; the second is help. Only one gets used.

Two more levers do quiet, heavy lifting. Share best practices from similar customers — "the physio clinics getting the most out of reminders send them 48 hours ahead, not 24" lands harder than any pitch because it's proof from a peer. And remove friction: if adoption is stuck because one step is confusing or nobody on the front desk was trained on it, fix that. The blocker is almost always a missing skill or an awkward workflow, not a customer who doesn't want the value.

Lesson 5.5 — The QBR: making value impossible to forget

Renewal season arrives. A busy practice owner who hasn't thought about Cadence in four months pulls up the annual cost, and his gut reaction is: "Wait — what are we even paying for?"

The product worked the entire time. He just can't see it anymore.

That renewal-time shock is exactly what the Quarterly Business Review (QBR) exists to prevent. A QBR is a periodic meeting — usually quarterly — where the CSM and customer step back from the daily noise to review progress against the customer's goals, show the concrete value delivered, align on next quarter's goals, and surface risks early. Value fades from memory unless someone keeps holding it up to the light, and the QBR is how the CSM does that on a schedule instead of hoping the customer remembers.

Imani's QBR with BrightSmile follows a deliberate arc, and the order matters as much as the content:

1. Recap their goals. "Last quarter you wanted to cut the revenue lost to no-shows." Start from what they care about, never from a product tour.
2. Show concrete value delivered. "Reminders and the waitlist recovered an estimated 60 appointments this quarter." Numbers tied to their goal, not a count of features.
3. Align on next-quarter goals. "Next, let's get that weekly report in front of the owner himself, so the value is visible above your desk."
4. Surface risks early, with owned action items. Dr. Raman's quiet warning about the budget gets put on the table months before renewal — with a clear next step and a name on each one.

A strong QBR does one more thing: it moves the CSM from help desk to strategic partner. Imani stops being the person you call when something breaks and becomes the person who shows you, every quarter, exactly what you're getting for your money. Lena coaches her newer CSMs that a QBR which turns into a feature demo or a recital of support tickets has missed the point — it's the customer's business under review, with Cadence as the lever.

That points straight at the principle the whole topic is built on. Demonstrate value continuously and proactively. A customer who clearly sees the value renews almost as a formality; one who can't is a flight risk no matter how friendly the CSM has been. The relationship opens the door — Dr. Raman picks up Imani's call — but it's the demonstrated value that keeps her on the other side of it.

Worked example — Imani saves the BrightSmile renewal, one quarter at a time

Marcus closes BrightSmile and hands the account to Imani. Watch trust and adoption do their two separate jobs.

Month 1. Imani learns the practice cold — why no-shows hurt, who resists every change. She promises Dr. Raman a calendar-sync fix and delivers on the exact day she said. Trust starts accruing.

Month 2. The usage dashboard tells a story: BrightSmile prints daily lists religiously but has never opened the waitlist. Instead of a "use more features" email, Imani ties the waitlist to the cancellation pain Dr. Raman named, and sets it up live in fifteen minutes. Adoption deepens because it solved a problem they already had.

Month 3. The trust pays a dividend. Dr. Raman calls to warn that the owner is questioning the budget — months before renewal, while there's room to act. A transactional vendor would learn this from a non-renewal notice.

The QBR. Imani opens with one number: roughly 60 appointments recovered this quarter, mapped straight to the no-show goal Dr. Raman set. The owner, invited in for the first time, finally sees in plain figures what the tool is worth. They align on next quarter, and the budget worry gets handled in the open instead of as a silent cancellation.

Renewal. It's nearly a formality. The value is visible, the product is woven into the front desk's every morning, and the one real risk surfaced early enough to defuse. The relationship got Imani the warning; the demonstrated value got the signature.