Picture a CSM five minutes into a QBR, sharing the account dashboard to walk through usage. Next to the customer's name sits a small red label: churn risk, high. The customer's VP spots it before the CSM does and asks who decided that, and based on what. The next twenty minutes are spent defending a number that was never meant to leave the building.
Nothing on that dashboard was false. The problem was that it was written for the vendor. A churn label helps a CS team decide where to spend time. On the customer's screen it reads as a verdict, and it turns a working session into an argument about the label instead of the account.
Why internal data ends up in the QBR
The same tool holds both kinds of data, and QBR prep is usually rushed. Pulling the internal dashboard straight into the deck is the fastest path to slides. Some teams also do it on principle, because sharing everything feels like transparency.
But internal data is built for internal decisions. It uses the vendor's categories, the vendor's thresholds and the vendor's guesses about people. Shown raw, it tells the customer how they are being scored rather than how they are doing, and very few customers enjoy finding out they have a score.
A simple test for what goes on the customer's screen
Ask two questions about every number before it goes in the deck. Is it about the customer's outcomes, or about the vendor's view of the customer? And can the customer do something with it? Data that passes both belongs in the review. Data that fails either one stays internal or gets translated first.
- Share as it is. Usage tied to the goals the customer set, adoption by team, support response and resolution times, and progress on the plan you agreed together.
- Translate before sharing. Risk signals. Instead of a score, show the evidence behind it: the finance team has not logged in since the summer, or the integration has failed four times this month. Then ask what is going on.
- Keep internal. The health score number, churn probability, expansion likelihood, notes on individual stakeholders, renewal targets, and any other customer's data shared without permission.
Three mistakes teams make with QBR data
Each one costs trust that is hard to earn back in the same meeting.
Showing the score instead of the evidence
A health score compresses many signals into one number using weights the customer never agreed to. Shown raw, it invites a debate about the model. The signals underneath it are facts the customer can recognise and act on. How the score is built matters to your team, not to theirs.
Leaving the bad numbers out
The opposite mistake is cutting every slide that looks bad. The customer already knows adoption stalled in their sales team. A deck that skips it looks either uninformed or evasive. On an account that is clearly struggling, the review should open with the problem, not hide it behind charts.
Filling the deck with data nobody can act on
Total logins, feature counts and page views look busy and say little. If a number does not connect to a goal or a decision, it takes time away from the slides that do. Executives in particular want the one thing that matters this quarter, not a tour of the dashboard.
"Accurate predictions and concise, actionable explanations of churn risk saving my team 2+ hours daily. I love that it reflects the right reasons accounts are at risk without us handcrafting a health score."
Wendy Zingher, VP of Customer Success · LambdaTest
How to build the customer's version of the data
Keep two layers. The internal layer is everything your team uses to prioritise. The customer layer is built from it, slide by slide, and starts from the goals in the mutual success plan rather than from whatever the dashboard shows by default.
For each risk your team sees, write the customer version as one piece of evidence and one question. Then give the champion something they can take upstairs. A short summary in their own numbers becomes the value story they forward to their leadership, which no internal score will ever do. If the deck is generated automatically, review it against this split before it goes out, the same check a QBR deck generator cannot make for you.
RetainSure explains every risk flag in plain reasons, so you can share the evidence, not the score.
The signals behind each account, ready to translate into the customer's view.
How to check your last QBR deck
Open the last deck your team sent and label every slide as outcome, evidence or internal. Outcome slides show progress on the customer's goals. Evidence slides show a fact the customer can act on. Internal slides show your scoring, your targets or your notes. Most teams find at least one internal slide, often the first one, because it was copied straight from the dashboard.
Then check the opposite gap. Look for a problem your team was discussing internally that never made it into the deck in any form. If the customer was going to hear about it eventually, the review was the place to raise it.
Now replay that QBR with the two layers in place. The red label stays on the internal dashboard. On the customer's screen there is one slide on the finance team's drop in usage and a question about what changed. The VP explains a reorg nobody had mentioned, and the rest of the meeting is spent on a plan.
Before your next review, go through the deck once and move every score to the internal layer, leaving only the evidence behind it.