How to communicate the value of product work - Rich Mironov (CPO Coach)

What It Covers

Rich Mironov, CPO coach and author of *Money Stories*, explains how product managers can communicate the value of product work to executives by translating technical roadmaps into financial language, using order-of-magnitude revenue estimates instead of precise metrics to win prioritization decisions and protect roadmap commitments.

Key Questions Answered

• •Order-of-magnitude pricing: Executives make funding decisions at the digit level, not decimal level. A range of $2M–$8M is sufficient to distinguish high-value work from $50K requests. Product managers should stop seeking false precision and instead present ranges that sort six-digit opportunities from three-digit ones, removing low-value items from executive debate entirely.
• •Upsell story formula: Quantify feature value using three numbers: total customers in the lower tier, incremental price to upgrade, and an estimated conversion rate. Example: 22,000 bronze customers × $360 upsell price × 1–5% conversion = $200K–$900K annually. Share this estimate with sales or marketing to pressure-test and gain cross-functional buy-in before roadmap presentation.
• •Roadmap swim lanes with revenue tags: Label roadmap swim lanes with associated revenue ranges rather than feature descriptions. If a churn-reduction lane is worth $10M–$20M per quarter, any sales request to redirect that team must be justified by equivalent revenue. This reframes roadmap disruption as a business trade-off, not a product versus sales conflict.
• •Retention churn math: Calculate churn cost by multiplying lost customers by annual subscription value. Example: 200,000 churned users × $100/year = $20M at risk. A 10% churn reduction saves $2M, which justifies spending several hundred thousand dollars on onboarding improvements. Presenting this math removes the need to explain design or engineering specifics to decision-makers.
• •Earning your keep benchmark: Product and engineering teams typically represent one-sixth of company headcount and must generate roughly six times their cost in revenue to justify investment. A team costing $4M annually needs to drive approximately $24M in product revenue. CPOs who cannot articulate this ratio risk losing budget autonomy and inviting executive micromanagement of technical decisions.