How to communicate the value of your product work | Rich Mironov

Rich Mironov has spent decades watching product teams lose the room because they were speaking the wrong language. In his new book Money Stories, he makes the case that product managers need a second vocabulary: one built around revenue, retention, and return. In this conversation, he walks through the core framework, why order-of-magnitude estimates beat false precision, how to build a roadmap that holds its ground against sales pressure, and what the AI moment has in common with the early days of mobile.

This episode is brought to you by Mailtrap, end-to-end email delivery platform: test in staging, send in production, and never land in spam: Find out more here: https://tinyurl.com/rkme22af

Chapters

00:00 — Introduction and Rich's move to Portugal
02:03 — What are money stories, and why do executives need them?
03:59 — How accurate do you actually need to be? The case for order-of-magnitude thinking
05:52 — Using money stories as a sorting mechanism — and how to handle the "close this deal now" pressure
10:54 — Tagging roadmaps with revenue ranges and the "or principle"
15:58 — Does every PM need this, or just senior leaders?
21:46 — The two flavors of ROI: earning your keep vs. feature-level returns
26:57 — Why feature-level ROI almost never works — and why product leaders need to push back
30:33 — The story archetypes: upsell stories explained
38:02 — The retention/churn story archetype
41:32 — Why product people get this wrong: fear of commitment and the need to be understood
44:52 — How AI changes (and doesn't change) the money story framework
48:58 — How to build financial literacy as a product manager


Key Takeaways

Speak the language of the room. Go-to-market executives filter for currency symbols. Framing product decisions in revenue terms isn't selling out — it's the only way to get and keep a seat at the table.
Order of magnitude is enough. The goal isn't to forecast the future to five decimal places; it's to separate the eight-digit opportunities from the four-digit ones. Ranges signal honesty, not weakness.
Tag your roadmap with money. Every swim lane should carry a revenue hypothesis — a rough range the whole team, including sales and marketing, has agreed to. That number becomes your negotiating anchor when someone wants to blow up the plan.
The "or" principle is non-negotiable. Executives want to believe in "and" — do everything, close every deal, ship every feature. Product leaders have to hold the line: doing one thing means not doing another, and the tradeoff should be expressed in money.
Feature-level ROI is a trap. Customers don't buy bug fixes or UI redesigns in isolation. Demanding per-ticket revenue attribution demoralises teams and produces numbers everyone knows are fictional. Push back on this — hard.
The upsell and churn archetypes are your workhorses. Both require only three numbers and a back-of-envelope estimate. That's enough to prioritise, negotiate, and get buy-in from the people who control the roadmap.
AI is a feature, not a revolution. The pattern is familiar: browsers, then mobile, now AI. The overcorrection always corrects. The question that survives every wave is the same one money stories answer — will customers pay for this?
Financial literacy is a leadership responsibility. If you're a CPO and your team can't explain how their product makes money, that's a coaching failure. Find your finance ally, buy them lunch, and close the gap in six hours.