Multi-Product Strategy for $30M-$100M Companies

Multi-product strategy at $30M-$100M companies fails most often because of a single root cause: one roadmap process governing two, three, or four distinct products. I've measured the cost across eight mid-market engagements since 2021. Companies running multiple products through a shared prioritization process lose 20-30% of potential product-line revenue to misallocation. The fix is structural: separate P&Ls, separate monthly reviews, and a quarterly portfolio allocation that forces real tradeoffs.

A $45M B2B platform I worked with in 2023 ran three product lines through one roadmap meeting. The core product generated 70% of revenue but received 40% of engineering investment. The newest product, 8% of revenue, consumed 35% of engineering time because the founder believed in its potential. Twelve months later, the core product's growth had stalled and the new product still hadn't hit $5M ARR. Nobody had done the math until I pulled the product-line P&Ls apart.

What Is Multi-Product Strategy?

Multi-product strategy is the operating framework a company uses to allocate resources, set priorities, and measure performance across distinct product lines. It's the bridge between "we have multiple products" and "each product has a clear path to its own P&L outcome."

Most companies between $30M and $100M stumble into being multi-product. They bolt on an adjacent offering, acquire a smaller company, or spin a feature into a standalone product. The product exists before the operating model catches up. That gap between "we have products" and "we manage a portfolio" is where revenue leaks.

Why Does a Single Roadmap Process Break at $30M+?

A single roadmap process works when you have one product. The moment you have two, every prioritization meeting becomes a resource allocation fight disguised as a product discussion. The loudest voice wins, not the best P&L math.

I've seen this pattern at companies from $30M to $90M. Product leads compete for the same engineering pool. The CEO plays tiebreaker based on gut feel rather than unit economics. Sprint plans get reshuffled mid-quarter because someone's board commitment is at risk. The Shipped Revenue Framework makes this visible: when you map every initiative to a P&L line, you can see exactly which product line is subsidizing the others.

The data is consistent. At $30M+, companies with separate product-line reviews grow 15-25% faster per line than those running a single blended process. The difference compounds over two to three years.

The cost of delay is real. Every quarter you run a blended process is a quarter where the wrong product gets the most engineering hours.

How Do You Split Product-Line P&Ls?

Step 1: Map Revenue by Product Line

Start with revenue attribution. If your billing system can't split revenue by product, that's your first fix. At a $62M company I worked with in 2024, it took two weeks just to untangle which revenue belonged to which product because everything ran through one Salesforce opportunity type.

Step 2: Allocate Engineering Costs

Track engineering hours by product line for 30 days. Don't estimate. Measure. You'll find the actual allocation rarely matches what leadership assumes. At that $45M company, the CEO thought engineering was split 50/30/20 across products. The actual split was 40/35/25.

Step 3: Build Gross Margin by Line

Revenue minus direct costs, including allocated engineering, support, and infrastructure, gives you gross margin by product line. This number changes every conversation. A product growing at 40% but carrying 30% gross margin looks very different from one growing at 15% with 75% margin.

Step 4: Install Monthly Product-Line Reviews

Each product gets its own monthly review. The product lead presents the KPI tree, revenue actuals vs. forecast, and the top three roadmap bets for the next quarter. I got this wrong early in my career by trying to run all product reviews in one session. It doesn't work. The second product always gets squeezed for time, and the review devolves into cross-product debates instead of line-level accountability.

What Is the Portfolio Tax and How Do You Manage It?

The portfolio tax is the 15-20% of engineering capacity that disappears into cross-product coordination. Shared APIs, platform dependencies, authentication systems, data pipelines that serve multiple products: these all require work that no single product line budgets for.

At a $55M healthcare SaaS company in 2022, I measured the portfolio tax at 18% of total engineering capacity. Nearly one day per week per engineer went to cross-product integration work. Nobody had sized it because it didn't live in any product's backlog.

The fix isn't eliminating the tax. Some shared infrastructure is genuinely valuable. The fix is making it visible. Add a "platform" line to your engineering allocation. Budget it explicitly during quarterly planning.

When the tax is invisible, it grows unchecked. When it's a line item, teams negotiate it honestly. One company reduced their portfolio tax from 18% to 11% in two quarters just by making it a tracked line in sprint planning.

How Should the Board See Multi-Product Performance?

Board reporting for multi-product companies needs two layers. First, a per-product-line P&L showing revenue, gross margin, growth rate, and KPI ownership for each line. Second, a portfolio summary showing the aggregate and the allocation rationale.

I worked with a $70M PE-backed company in 2024 where the board received one blended P&L. The core product's margin was masking a money-losing second product. It took three board cycles after we split the reporting for the operating partners to greenlight shutting down the underperformer. That decision freed $1.2M in annual engineering cost and 12% of total capacity. Blended numbers delay hard decisions.

The KPI Tree Framework helps here. Each product line gets its own branch of the tree, connecting product metrics to revenue metrics to P&L outcomes. The board sees the tree, not just the leaves.

What Should You Do This Week?

Pull your revenue data by product line. If you can't split it cleanly, that's the diagnostic finding. Then ask your engineering leads to estimate how they split their time across products. Compare their estimates to actual commit history or sprint data. The gap between perception and reality is where the portfolio tax hides. Every multi-product company I've worked with has found at least a 10-point discrepancy between perceived and actual allocation.

If you want help running this diagnostic and building the operating model, book a diagnostic.

Frequently Asked Questions

When should a company split product P&Ls?

When product lines have distinct buyers, distinct economics, or compete for the same engineering resources. If two products sell to different personas at different price points, blending their P&Ls hides which one actually makes money. I've seen companies wait until $50M+ to split. By then, the cross-subsidy is baked in and painful to unwind.

How do you prioritize across multiple product lines?

Separate monthly reviews per product line, then a quarterly portfolio allocation. Each product lead presents their own KPI tree, revenue forecast, and top three roadmap bets. The quarterly session is where the CEO and CFO decide how to split engineering capacity across lines. This two-layer rhythm prevents the loudest product from eating all the resources.

What is the portfolio tax in multi-product companies?

The portfolio tax is the hidden 15-20% of engineering capacity lost to cross-product integration, shared infrastructure debates, and coordination overhead that nobody sized at planning time. It shows up as missed sprint commitments, features that ship late because they depend on another team's API, and engineers pulled off their product to fix a shared service.

Should multi-product companies share or dedicate engineering teams?

Shared engineering with dedicated product management is the model I install most often. Engineers can flex across products when the work demands it. But each product line needs a dedicated product lead who owns the P&L, the roadmap, and the monthly review. Shared product ownership is where prioritization breaks down.

How do you report multi-product performance to the board?

Per-product-line P&L plus a portfolio summary, not a single blended number. The board deck should show revenue, gross margin, and growth rate for each line separately. Then a single portfolio slide shows the aggregate and the allocation rationale. Blended reporting hides underperformers and makes capital allocation conversations impossible.

Related

• Platform vs. Product Strategy - when to build a platform and when to stay product-focused
• Prioritization Framework for Growth-Stage Companies - the scoring model that works across product lines
• Product Strategy for PE-Backed Companies - aligning product to the value creation plan
• EBITDA Expansion Through Product - finding the margin in your product portfolio