Low Product Adoption Conversation: CS Drill

Why rehearse a usage review before the live call?

Rehearse it because the sponsor call happens on a live account, and your first response there cannot be re-run. A low product adoption conversation asks a CSM to do four things in one sitting: raise an uncomfortable fact, hear a deflection, diagnose a cause and leave with a commitment. We want each of those moves practised and scored before a real sponsor hears them.

The opposing view holds that CSMs learn best purely on live calls and that practice environments add little. We disagree on one point. A CSM's first attempt at a hard conversation should not happen on a live account. We consider a live sponsor relationship the wrong place to find out whether a first response holds.

A customer adoption roleplay lets you score the same moment against the same rubric until the response holds. Then the CSM takes it to the sponsor. A CSM should fail the busy deflection in practice, not in front of the sponsor. The stages below make up the call. The drill at the end is how you rehearse it.

Stage one: set the up-front contract

Open with a Sandler up-front contract. It is a mutual agreement made before the conversation that covers purpose, time, both parties' agendas and the acceptable outcomes. One of those outcomes must be that no is acceptable. Skip it and you are presenting a dashboard to someone who has not agreed to discuss it.

A line that works: Thanks for making time. I wanted to look at how the team is using the platform since kickoff. Logins have dropped, and I'd rather understand why than guess. We have until the top of the hour. Does that still work? I'd like to hear what's changed on your side, and I'll share what we're seeing. By the end, I'd like one of these outcomes: a plan to get the team back in, a date to revisit if the timing is wrong, or a plain answer that it isn't working and a conversation about what that means. Any of those is fine. What would you add?

The rubric row is binary. Purpose, time, both agendas and acceptable outcomes must all be audible in the transcript before the CSM shares usage data. A missing element fails the row. An up-front contract that omits no as an acceptable outcome is a meeting agenda, not a contract. For more repetitions on the opening alone, use our up-front contract practice guide.

How should you answer the busy deflection?

Acknowledge it in a clause, then ask a question that makes busy specific. Do not defend the product. Do not explain features. The agreed first response we recommend: That makes sense. When you say busy, what's taking the team's time now that used to go into the platform?

The fair objection to an agreed line is that it sounds canned. We agree that canned branches sound canned. The first response is the one line worth agreeing on as a team, because everything after it depends on the sponsor's answer. Drill the first response until it is automatic. Strong CSMs then improvise the branches from understanding instead of getting caught flat.

A failing first response sounds like this: Totally understand. Actually, the new dashboard makes that much faster. Let me show you. That answer defends instead of diagnosing, and it ends the sponsor's explanation before it starts. If the sponsor sounds overloaded, keep your ask small. Our frazzled-buyer drills practise exactly that.

The first response to busy should make the sponsor more specific, not make the product sound better.

Workflow gap or lost champion: which questions tell them apart?

Ask who owns the rollout today. Score the call as a workflow gap if the sponsor names a current owner and a specific step people skip. Score it as a lost champion if nobody owns it. To reach that question with a real answer, run the Sandler pain funnel in its order: surface issue, then concrete cost, then feeling.

A worked sequence: Tell me more about busy. Then Can you be more specific? Which team stopped logging in, and when did you notice? Then What have you tried to get them back in? Then What has that cost you? What is the reporting running on instead? Then How do you feel about where the rollout stands? Asking how they feel before the surface issue is clear reverses the funnel. That is a misuse, and it fails the discovery row.

Now ask the separating question: Who on your side is accountable for adoption today? Suppose the answer names someone, plus a step such as exporting to a spreadsheet. The close then assigns that person to fix that step. Suppose the answer is a pause or a former colleague's name. The close then has to get the sponsor to name a new owner. Our champion re-entry drill works that branch in depth.

Score a usage drop with no named current owner as a lost champion, whatever the login data shows.

What counts as a passing close?

In the scored drill, a passing close has three parts: one named owner, one usage commitment and a dated follow-up. The sponsor must confirm each one in their own words. The persona is written to commit once the CSM diagnoses the branch correctly, so anything short of all three fails. These are exit criteria, which means buyer-verified evidence rather than the CSM's opinion that the call went well.

A passing close sounds like this: So your ops lead owns getting the team back in. They'll run the weekly forecast report in the platform instead of the spreadsheet. And we'll review logins together on the date in the invite I'm sending now. Have I got that right? The sponsor's answer has to restate the owner and the commitment, not just agree. A usage commitment names a team, a task and a place. Use it more fails. The ops team runs its weekly report in the platform passes.

On a live call, the up-front contract also made no an acceptable outcome. If the sponsor gives a plain no, close on that instead: who made the decision, what happens to the account next, and the date you revisit it, restated by the sponsor. What never passes, live or in practice, is a close with no owner and no date. A follow-up without a date on both calendars is a hope, not a next step.

The customer success drill: setup and buyer lines

We recommend a weekly 30-minute run: 5 setup / 15 drill / 10 debrief. Budget ~10 minutes beforehand. Use that time to pick an account from your live book and choose the rubric row you will debrief. Before the session, the manager picks the workflow-gap branch or the lost-champion branch and does not tell the CSM. Diagnosing the branch is the test.

Run it as a usage review call. The CSM opens and the sponsor persona uses these lines in order:

Opening: I've got a few minutes before my next meeting. What did you want to cover? Deflection: Honestly, we've just been busy. It's not the tool. Workflow-gap reveal, given once the CSM asks a specific question: The team still pulls the numbers into a spreadsheet. The report they need isn't where they look. Lost-champion reveal: The person who pushed for this moved teams. Nobody really picked it up. Re-training bait: Can you just send some training videos and we'll get people back in? Discount bait: If nobody's using it, maybe we should be talking about fewer seats. Close test: Sure, let's touch base again sometime.

Play the bait lines whether or not the CSM diagnosed correctly. A CSM who has the cause in hand should be able to set the bait aside and return to the owner question. Once the CSM has named the branch and asked for an owner, the persona commits.

Rubric rows, pass bar and failing attempts

To pass, every row below must be marked pass, and a manager must be able to verify each row from the transcript alone. Talk/listen ratio sits on the scorecard as a diagnostic. Read it alongside the rows to investigate why a row failed. It is not a pass bar.

Failing attempts fall into recognisable shapes, and each fails a named row. Feature re-training: I'll set up a refresher session on the new reports for the whole team. Discount offer: We could look at a lower seat count to make it easier. Vague close: Let's check back next month and see how things look. Re-run every failed attempt against the same branch. Read results per CSM per scenario, never as one blended number across the team.

A drill passes only when a manager could verify every row from the transcript alone.

Debrief one moment, then book the re-run

Isolate one moment and one behavior. Let the CSM diagnose it first. End by booking the re-run. Start the debrief at the moment of the failed row: Play back from the sponsor's busy line. What did you want to happen next, and what happened? Give your verdict only after the CSM answers, and give it on that row alone.

Feedback on every mistake at once is entertainment; feedback on one moment with a booked re-run is coaching. In XL Roleplay, flags in the coaching report link back to the exact moment in the transcript, so the moment to replay is already marked. Our debrief guide covers the full script.

For CSM coaching that survives a busy quarter, we recommend a 15-minute 1:1 built around one flagged moment from a scored session. Hold it in addition to the account or pipeline 1:1, never in place of it. Put it on the calendar as a recurring block. Run the drill this week, debrief one row, and book the re-run before you leave the room.