2 min lesson
The strongest narrative pairs hard usage data with one specific story
Respond to "Why can admitting where AI doesn't help actually strengthen your ROI case with a technical executive?" Name the reason and the detail behind it.
Step 1 of 2
Never quote a productivity percentage you didn't measure in that customer's environment. "Studies show 40% faster" invites the one question you can't answer: "in our codebase, on our team?" The moment you can't defend the number, every other claim you've made gets re-examined.
Anchor instead on outcomes the customer already measures, then layer developer-experience signals on top. You're not inventing a new scoreboard, you're showing movement on theirs.
- Outcomes they already track: review turnaround, time-to-first-PR for new hires, toil tickets closed, on-call load.
- Adoption telemetry as evidence of value, not as the value itself: weekly-active depth, acceptance, feature breadth.
- 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.”
Saying out loud where AI doesn't help - generated tests that need scrutiny, a domain Cursor is weaker in, a workflow it didn't change - builds more credibility than any upside claim. It's also on-brand for Cursor's truth-seeking culture and it signals you'll tell the customer hard truths, which is exactly what a CTO wants from the person owning their account.