Stories With Data: The CSM Skill Nobody Trains
My first job was covering high school sports in New York. Every night I kept my own stats, did the post-game interviews and filed on deadline. It turned out to be some of the best Customer Success training I ever got, because it taught me one thing I still repeat to my teams: the box score is not the story.
Anyone can report that a team won 3–2. The story is why. The play that turned the game, the number that explains it, what it means for next week. Readers don't remember scores. They remember what the scores meant.
CS has a box-score problem
Most CSMs are good at reporting data. Usage is up 14%. Three teams adopted. Forty active users this month. Tickets resolved inside SLA.
All true, and almost none of it lands. Executives don't make decisions from a list of metrics. They make decisions from a narrative they believe. When we hand them a box score, we're asking them to write the story themselves, and most won't.
The CSMs who drive renewals and expansion take the same numbers and turn them into something a leader can repeat in their own meeting the next day.
What that sounds like
Here's a made-up example to show the difference.
The box score version: "Your team's usage is up 22% this quarter, and the marketing team onboarded 12 new users."
The story version: "Last quarter your marketing team was making campaign calls without much visibility into how the brand was performing. This quarter twelve of them are in the platform every week, and they've used what they found to change two big campaigns. That's why usage is up 22%. The question now is whether the insights team should have the same access before planning season."
Same data. One is a report. The other gives someone a reason to act.
How I structure it
The newsroom structure works almost unchanged in a customer conversation.
Lead with the most important thing. What changed, and why should this person care? Don't make them wait until slide 14.
Pick one or two numbers that prove it. Not ten. The more metrics you show, the less any single one matters.
Put people in it. Which team did something differently, and what did they decide? Numbers become real when they're attached to people.
Say what it means for their goals, in their terms.
Point forward. What should happen next, and what do you recommend?
That last step is where a good business review earns its keep.
Why it doesn't get trained
We train CSMs on the product, the process, the CRM and objection handling. We almost never train them on narrative. It gets filed under soft skills that some people just have.
I don't buy that. It's learnable, and it's one of the most valuable things a CSM can get better at. On my teams we practice it directly. A CSM brings a data point from one of their accounts, turns it into a two-minute story, and the group pushes back. Is the lead clear? Too much data? Would an executive repeat this? After a few rounds the difference shows up in business reviews, renewal calls and even internal forecasts. It's the same muscle behind focusing on outcomes instead of activity.
We've also started using AI to help CSMs find the stories in their data faster by surfacing patterns and moments worth raising. I wrote about that setup in giving every CSM a copilot. The AI can find the material. The CSM still has to tell the story.
Try it on your next update
Before your next customer email or review, write one sentence that captures the most important thing that happened on the account this quarter, the way a reporter would write a headline. If you can't, you don't have a story yet. You have a box score.
Customers renew stories, not spreadsheets.
If you'd like help building this skill across your team, let's talk.
