Picture the QBR for an account whose rollout slipped by a quarter, whose support queue is full of open tickets, and whose renewal is a few months out. The CSM opens with the usual deck: logins trending up, a slide on new features, a roadmap preview. Ten minutes in, the customer's director stops the screen share and asks when someone is going to talk about the outage. The rest of the hour is spent on defense.
Everyone in the room already knew the account was unhappy. The deck pretended otherwise, and that cost the CSM the one thing a bad quarter usually leaves intact: credibility. The customer did not need to be told things were fine. They needed to hear that the vendor saw the same problem they did.
Why the usual QBR deck backfires on an unhappy account
A standard QBR is built to show progress. That works when the customer's experience matches the charts. When their lived experience is a broken rollout or a month of slow support, every positive slide reads as either ignorance or spin. Both land worse than the bad news itself.
The other trap is burying the problem under activity. Tickets closed, calls held, features shipped. The customer does not measure the vendor's effort. They measure whether the thing they bought is working for their team, and right now it is not.
What changes when the review opens with the problem
The review that saves an unhappy account starts where the customer already is. The first slide names the problem in the customer's own words, what caused it, and what it cost their team. No context slide first and no softening language.
That opening does two things. It ends the guessing about whether the vendor knows, and it turns the rest of the meeting from defense into planning. Customers rarely leave because something went wrong. They leave because nobody owned it and nothing changed afterwards.
Three mistakes teams make in the at risk QBR
Each one feels safe in the moment and makes the renewal harder.
Leading with the usage chart
Usage can rise while the account is furious, because people still have to do their jobs in a tool they dislike. A growing login count on an account whose rollout failed tells the customer you are watching the wrong data. Move the healthy metrics after the recovery plan, or leave them out.
Bringing the wrong people
A CSM alone cannot commit engineering time, a credit or a change to the contract. If the fix needs product or leadership, bring someone who can say yes in the room. An executive sponsor who already knows the account carries far more weight than one introduced for the first time on a bad day.
Offering a discount before a plan
A price concession feels like progress because it is easy to give. On an account whose problem is the product or the rollout, a discount without a fix only moves the churn date. The math behind discounts that save accounts and discounts that delay churn starts with whether the underlying problem got solved.
"RetainSure put LimeChat's customer success program on steroids. MBR preparation that used to consume the entire last week of the month now takes 2 minutes per customer. The AI delivers everything the team needs, data, insights, and next steps, so they can focus on driving real outcomes."
Sridhar Kowtal, Head of Customer Success · LimeChat
How to run the review when the data is bad
Start before the meeting. Talk to the champion one on one and ask what the problem looks like from their side and what their leadership is saying about it. Nothing in the QBR should surprise them. If they have gone quiet or keep moving the date, treat that as a signal of its own and get the conversation going before the formal review.
Then build the agenda in this order:
- The problem, stated plainly. In the customer's words, with what it cost them.
- The cause and what has already changed. Short, specific and free of blame on the customer's team.
- The recovery plan. Actions on both sides, each with one owner and one date.
- How recovery will be measured. Two or three signals the customer agrees matter, and when you will check them together.
Send the recap within a day and track every commitment the way you would track any QBR action item. On an unhappy account, a missed follow up confirms the customer's worst read of the meeting.
RetainSure flags the accounts heading into a hard review, weeks before the meeting.
The risk, the reasons and the history, ready before you build the deck.
How to know the recovery is working
Pick the signals in the meeting, with the customer, and check them together within a month instead of waiting for the next quarterly review. Ticket volume on the broken workflow, adoption by the team that gave up, a working integration. If the signals move, say so. If they do not, say that too and change the plan.
The best at risk QBR is the one you saw coming. An early warning system gives the team weeks to fix things before the review instead of a single hour to explain them. And a recovery that worked, told in the customer's numbers, becomes the value story the champion forwards upward at renewal.
Now replay that QBR with the problem first. The CSM opens with the outage in the director's words, the engineering lead explains what changed, and the room spends forty minutes on a plan instead of a defense. The director leaves with three dated commitments and a check in booked for the following month.
Before your next review with an unhappy account, write the first slide in the customer's words and build the rest of the deck from there.