Imagine you're responsible for choosing the next major product investment. Your team has spent weeks gathering feedback from customers, sales, customer success, and engineering. Several opportunities look promising, but your capacity allows you to pursue only one.
You make a decision based on the evidence available. Then, during the executive review, you learn something about the business that changes how you see every option on the table.
What would you do if no new customer insight had emerged, but the business evidence suggested that your original priority might be wrong?
What Changed in the Room
I explored this question during a recent webinar with Pragmatic Institute. We asked participants to act as the Head of Product for Meridian Cloud, a fictional B2B software company with $30 million in ARR and 400 customers.
They had to choose one investment for the next two to three quarters: an AI workflow assistant, an enterprise integration hub, onboarding automation, or advanced analytics. Each option addressed a plausible customer or business need, and initially many participants chose the AI assistant.
That decision made sense based on what they knew. An AI capability might help differentiate the product and attract new customers. But we hadn't yet examined whether acquiring more customers was the company's most important economic problem.
Next, we introduced the financial picture. ARR was growing 18%, while net revenue retention had fallen to 94%. Gross margin was declining, and the cost of implementing each new customer was increasing.
Those numbers told a very different story. The company was growing, but some of that growth was compensating for revenue it couldn't retain. At the same time, acquiring and onboarding customers was becoming more expensive. Increasing sales might improve the top line without improving the underlying economics of the business.
Finally, participants learned that Meridian Cloud was private-equity-backed, with a potential exit in 18 months and expectations around profitability and retention. Their choices shifted toward onboarding automation and enterprise integrations.
What I found particularly interesting was that we never changed the customer problems or introduced a new product opportunity. We changed what participants understood about how the company made money, where it was losing value, and how much time it had to improve the business.
Why an Attractive Opportunity Is Not Necessarily the Right Investment
Product leaders are trained to understand customer problems, identify market opportunities, and build products that customers value. None of that becomes less important when you start operating at a more strategic level.
But customer demand alone does not establish where the company should invest next. We also need to understand the economic mechanism behind each option. Will it bring new revenue, protect existing revenue, improve margins, or reduce the cost of delivering value? How much will we need to invest, and when are we likely to see the return?
Consider the AI workflow assistant. It could still be a good investment for Meridian Cloud. But if each new customer is becoming more expensive to onboard while existing customers are not renewing or expanding at the expected rate, investing primarily in acquisition might compound the very problems the company needs to solve.
Onboarding automation could have a more direct impact on implementation cost and time to value. Enterprise integrations might help customers adopt the product more deeply and improve retention. These are hypotheses, not guaranteed outcomes, but they are connected to the specific economic pressures the company is facing.
This is where the discussion changes from which feature looks most promising to which business outcome we are actually investing in.
The Decision Is Not Always Obvious
During the Q&A, someone asked whether participants who continued to favor a different option were wrong. I don't believe they necessarily were.
Product strategy is not a formula that gives us one correct answer. Different leaders can look at the same information and make different, defensible choices. What matters is whether they can explain the investment, the expected return, the timing, and the opportunity cost in the context of the company's actual needs.
That last point is often missing from roadmap conversations. If we invest in acquiring new customers, what are we choosing not to fix in retention or delivery cost? If we redirect capacity toward efficiency, what growth opportunity might we be delaying? Neither choice is inherently better. But both have consequences, and those consequences become more significant when the business is operating against a financial deadline.
The responsibility of product leadership is not simply to select an attractive opportunity. It is to make a business investment decision that you can defend.
Join Me for Follow the Money
In my upcoming live pop-up workshop with Pragmatic Institute, Follow the Money, we'll take this approach beyond the fictional Meridian Cloud case and apply it to your own company.
We'll look at how to understand the commercial and financial pressures facing the business, identify the economic problems Product can influence, and connect those problems to product investment decisions that leadership can evaluate.
If you're responsible for product strategy and want to make stronger, business-grounded investment decisions, I'd love to see you there.
Until next week,
Until next week,
Elena Leonova
Executive product & business-strategy leader
I work with senior product leaders, Directors, and VPs to help them master product strategy when decisions are high-stakes, ambiguous, and made at scale - where trade-offs matter and the cost of getting it wrong is real.
This newsletter reflects the thinking behind my work across:
• Product Executive education - From PM to Product Executive (Maven cohort)
• Advisory & coaching - product strategy and executive decision-making
• Writing & research - including my forthcoming book The Art of Platform Products
