1 min lesson
The strongest narrative pairs hard usage data with one specific story
Name the key items in "The strongest narrative pairs hard usage data with one specific story", then explain why each one matters.
Step 1 of 2
Anchor instead on outcomes the customer already measures, then layer two kinds of softer evidence on top. You're not inventing a new scoreboard, you're showing movement on theirs.
- Developer-experience signals from surveys and EBRs: "I'd hate to give this up," perceived friction removed, satisfaction.
- Concrete workflow stories: the migration a team did in two days, the legacy module a new hire understood with @-symbols and Chat.
The strongest narrative pairs hard usage data with one specific story. Numbers earn the meeting; the story is what the CTO repeats to their own boss.
"I won't sell you a productivity percentage. Your engineers would distrust it and so would I. Here's what I can show: weekly-active depth is up across the platform team, their review turnaround dropped and they told us in the last EBR they'd refuse to give Cursor back. That's the value, in your own metrics."
Naming the limits also signals you'll tell the customer hard truths, which is exactly what a CTO wants from the person owning their account. It fits Cursor's truth-seeking culture too.