The strongest new product line cases start with a structural constraint in your existing product — something already costing you customers or expansion revenue — not with market whitespace. Your adjacency (what you already have that a competitor would need to build from scratch) is your strongest card. Phase the investment, distinguish feature from product, and directly address the three questions leadership actually cares about: risk to the core, timing, and the cheapest path to proof.
Most product leaders spend most of their careers improving existing products for known customers. Every once in a while, the right move is harder: making the case that a fundamentally new product line should exist within your company.
I've done this work directly, and the process is messier than the post-hoc story suggests. But it follows a logic that's learnable. Here's how I think about it.
Why the case is hard to make
New product lines compete with your core roadmap for resources. The core product is already working, so investment in it has clear near-term ROI. A new product line requires betting resources on a hypothesis, usually displacing something that feels more certain.
The people most skeptical of your proposal are often the people closest to the core business: engineering leads who know how hard it is to build and maintain what already exists, finance leaders who want to see a clear path to return, and GTM leaders who are already stretched selling the current product.
Your job is to make a case that is honest about the uncertainty, compelling about the opportunity, and credible about the path. That requires more than a market size slide.
Start with the structural constraint in your existing product
The best new product opportunities don't come from scanning the market for whitespace. They come from structural limitations in your existing product that are already preventing a valuable user from getting value.
This matters because it changes the risk profile of the case. You're not proposing to enter a market you've never touched. You're proposing to remove a structural constraint that's already costing you customers, retention, or expansion revenue.
I've seen this pattern most clearly in developer-first B2B products. A developer-first platform often works brilliantly for technical users. But it creates a structural dependency for non-technical users in the same organization: marketers, content managers, operations teams who need to do their jobs but can't without a developer's involvement. That dependency isn't a UX problem. It's architectural. The information they need to control is stored in a layer they can't access.
The question to ask: where are your existing customers buying point solutions to work around something your core product structurally can't do? That's your market signal. That's where the new product line lives.
The adjacency argument is your strongest card
The most powerful new product business cases start with what you already have. Not what you'd need to build — what you already have that a competitor would have to build from scratch.
In the developer-first platform example above, the adjacency argument is: we already have the content infrastructure that the new product needs to operate. A standalone visual builder would have to build that from scratch. We already have it, along with the customer relationships, the integrations, and the trust. Our new product line is an extension, not a greenfield build.
Adjacency also matters from the customer's perspective. The easiest sale is to a customer who already trusts you and already has the adjacent problem. They don't need a new vendor evaluation. They need a reason to expand their existing investment.
If your adjacency argument is weak — if the new product requires fundamentally different infrastructure, different go-to-market, or a customer base you don't have access to — that's important to know early. It doesn't necessarily kill the case, but it changes the investment thesis significantly.
Size the opportunity honestly
Market sizing in a new product pitch is often either too precise (a number that sounds credible but is essentially made up) or too vague (a hand-wave at a large TAM that doesn't tell you anything useful).
What actually matters is the structure of the opportunity, not the specific number:
Who is already buying adjacent solutions? If there are established competitors in the space, that's validation that the problem is real and customers are willing to pay. You don't need to estimate the total market from first principles — you can observe what's already happening.
How many of your existing customers have this problem? This is your fastest path to revenue and your strongest product-market fit signal. If a significant portion of your existing base is dealing with the problem through workarounds or competing products, you have a built-in initial market.
What's the expansion revenue potential? New product lines sold into existing customer relationships often expand the contract value significantly. Frame the opportunity not just as new logo revenue but as expansion within your installed base.
The goal isn't a precise forecast. The goal is a compelling answer to: is this genuinely large enough to be worth the investment?
Phase the investment — don't ask for the whole thing at once
One of the biggest mistakes I see in new product line pitches is asking for too much too early. A full multi-year roadmap, a dedicated team, a separate P&L — presented before you've proven anything.
Nobody funds a five-year bet on a hypothesis. You fund the first horizon and earn the right to invest in the next one.
A phased approach looks like: Horizon 1 proves the core problem is real and customers will use a solution. It's low-cost, deliberately limited in scope, and focused on validation signals more than revenue. Horizon 2 builds on those signals to add the features that drive commercial momentum. Horizon 3 extends to the full strategic vision.
Framing it this way does two things. It reduces the perceived risk of the initial investment. And it sets clear criteria for when the next investment is warranted — which is better for everyone than a vague commitment to "iterate."
The feature-versus-product distinction is everything
This is the most common failure mode I see when new product lines are approved but then poorly executed: the new product gets built as a feature of the existing product.
The logic is understandable. It's faster, it leverages the existing codebase, it avoids duplicating infrastructure. But it usually produces something that serves neither the existing persona nor the new one well. The existing product gets distracted from its core jobs. The new offering never gets the dedicated investment and roadmap focus it needs to become independently valuable.
A genuine product line requires its own persona definition, its own jobs-to-be-done, its own roadmap logic, and in most cases its own pricing. That doesn't mean it runs as a completely separate entity — integration with the core product is often a key differentiator. But it needs to be owned and developed with the new persona's needs as the primary design constraint, not the existing product's architecture.
Getting this distinction clear with your leadership team before you start building is more important than anything in the business case deck. If your executives think you're building a feature, they'll fund it like a feature. If they understand you're building a product, they'll commit to the investment level the new product actually needs.
What the pitch actually needs to land
A business case for a new product line has to simultaneously answer five questions:
Is the opportunity real? (Market sizing, existing customer signal, competitive evidence.)
Can we win it? (Adjacency, unfair advantage, strategic fit.)
Is the timing right? (Why now, not in two years?)
What are we risking? (Honest assessment of what the core roadmap gives up.)
How do we prove it cheaply before committing fully? (Phased investment structure.)
Most pitches answer the first two well and skip the last three. The last three are what leadership actually worries about. Addressing them directly — with candor, not spin — is what separates business cases that get approved from ones that die in committee.