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.
Chapters
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.
Keep reading
Lessons from games, big tech, & Hollywood - Laura Teclemariam (LinkedIn, Netflix, Warner Bros. Entertainment)
How to align product work to business goals | Corinna Stukan (CEO, Bizzy)
Lessons from Mozilla and Twitter - Alan Byrne (Firefox, Twitter)
Inside modern product game design - Cheryl Platz (Riot Games, Microsoft)