Which Products or Lines Deserve More Capital in B2B SaaS?

Direct answer: In B2B SaaS, the products that deserve more capital are the ones with high relative market share in high-growth categories (your Stars) and the ones where a defined investment can move a fast-growing product from low share to leadership (select Question Marks). The BCG Growth-Share Matrix gives you a defensible way to sort your product lines by market growth and relative share so capital flows to compounding positions instead of legacy products defended out of habit. Run it on ARR-generating lines, not features, and use net revenue retention and category growth as your axes' real-world proxies.

The BCG Matrix, translated for B2B SaaS

The classic matrix plots business units on two axes: market growth rate (vertical) and relative market share (horizontal). That produces four quadrants:

• Stars — high growth, high share. Fund aggressively; they're your future cash engines.
• Cash Cows — low growth, high share. Milk for cash; reinvest, don't over-fund.
• Question Marks — high growth, low share. Decide deliberately: invest to win or divest.
• Dogs — low growth, low share. Harvest, sunset, or spin off.

The framework was built for diversified industrial portfolios, so B2B SaaS operators need honest translations before it's useful:

• "Market growth" rarely maps cleanly to a public figure. Use the growth rate of the category your product serves (e.g., revenue intelligence, HR compliance, developer tooling). If you can't source it credibly, proxy with your own line's YoY new-logo ARR growth and pipeline velocity.
• "Relative market share" in SaaS is best approximated by your share of the addressable segment you actually sell into, or your win rate against the category leader in competitive deals. Absolute ARR alone will mislead you.
• The unit of analysis is a product line or ICP-specific offering — not a feature and not a pricing tier. If two "products" share the same buyer, GTM motion, and roadmap, treat them as one line.

A concrete walkthrough

Here's the sequence for a multi-product B2B SaaS company running its annual planning cycle.

1. Define the lines. List each product line with its own ARR, gross margin, net revenue retention (NRR), CAC payback, and the primary category it competes in. Kill vanity groupings — combine anything that isn't independently ownable.

2. Score growth. For each line, establish category growth. Where public data is thin, triangulate: analyst category estimates, competitor funding and hiring signals, and your own inbound demand trend. Mark each line high or low growth against a threshold you set (a common cut is whether the category is growing faster than your blended company average).

3. Score relative share. Estimate share against the segment leader. In practice: win rate in head-to-head deals, presence in the buyers' shortlist, and NRR (a line above ~110% NRR is usually defending real share; a line leaking below 95% often is not).

4. Plot and interpret.

• A Star in SaaS looks like: high category growth, NRR above 110%, healthy CAC payback, and a widening competitive moat. Good means you're funding sales capacity and R&D faster than the category is growing.
• A Cash Cow shows durable share but flat category growth and stable-to-declining NRR. Good means efficient operation, minimal roadmap spend, and cash routed to Stars and chosen Question Marks.
• A Question Mark has strong category growth but weak share. Good means a written, time-boxed thesis: "€X and two quarters to hit Y win rate — or we stop."
• A Dog is low on both. Good is a clean decision: sunset, sell, or run it on autopilot with zero incremental capital.

5. Convert to a capital allocation table. Assign each line a mandate — fund, maintain, decide-by-date, or exit — and attach a number. The output is a one-page reallocation, not a color-coded chart.

The matrix's known weakness applies here too: it treats share and growth as the only variables. In SaaS, ignore expansion motion, ecosystem lock-in, and shared-infrastructure economics at your peril. Use it to structure the debate, not to end it.

Where Percision fits — and where it doesn't

Disclosure: I write for Percision, an AI strategic-intelligence platform (percision.app). Used honestly, here's the fit.

Percision runs your business context through structured reasoning steps across multiple frameworks — including the BCG matrix — and returns board-ready output in minutes: the quadrant placement, the supporting financial intelligence (DCF, 60+ ratios, warning signs), and an Excel-exportable model with an audit trail you can defend to a board. For a multi-line SaaS company sizing its next planning cycle, that compresses a normally weeks-long exercise and forces the discipline of scoring every line the same way. It's positioned as a co-pilot: it proposes; your leadership decides.

When you don't need it: if you have two or three product lines and the answer is obvious from your NRR and CAC dashboards, a spreadsheet and a two-hour leadership session will do. If your core question is deeply relationship-driven — a contested divestiture, a nuanced ecosystem partnership — an experienced human strategy consultant who can read the room is worth more than any model. Percision earns its place when the portfolio is complex, the timeline is short, or you need consistent, auditable analysis across many lines.

Broader context, cited correctly: research from Harvard Business School and BCG on AI in knowledge work (the 2023 "Navigating the Jagged Technological Frontier" field study) found consultants using generative AI completed tasks faster and at higher quality within the tool's competence — and performed worse when they trusted it outside that boundary. That's the right mental model here: let AI accelerate the structured analysis; keep humans on judgment.

If you want to run your product portfolio through a structured BCG analysis quickly, you can try Percision here.

What this looks like when the analysis is actually run

Capital allocation across product lines is where strategy becomes arithmetic. Here is a run moving money between horizons and saying what it expects back.

The subject is TechNova Solutions, a sample company profile we use for testing rather than a customer: a $45M ARR DevOps platform, 280 employees, Series B.

The row worth studying is the last one. APAC appears in the table with a $20M peak and a recommended investment of $1.5M, and is then killed anyway — because peak size is not a reason to enter a market you have no right to win. A 2.2–2.7 score against Canada's 4.0 settled it, and the alternative was not "enter Canada instead" but "enter neither yet."

The second point is that the biggest capital move is a withdrawal. $10M comes out of the largest revenue line. Portfolio allocation questions are usually posed as "where do we invest next," and answered honestly they are mostly about what stops being funded.

Read a complete Percision report — every page, no email required.

FAQ

How often should a B2B SaaS company re-run the BCG matrix? Once per annual planning cycle as the anchor, with a lighter mid-year check if a category shifts fast or a Question Mark hits its decision date. Don't re-plot monthly — the noise will make you thrash.

What if I can't find reliable market-growth data? Proxy with your own line-level new-logo ARR growth and pipeline velocity, and flag the estimate as directional. The matrix's value is relative sorting across your lines, not absolute precision.

Is the BCG matrix outdated for software? It's incomplete, not outdated. It ignores expansion revenue, shared infrastructure, and ecosystem effects — so pair it with NRR, CAC payback, and moat analysis rather than using it alone.