Should we build a second product?

Product and engineering · Answered by Golden Section from more than 400 B2B software companies observed

The Golden Section answer

Usually not yet. A second product earns its place when the core product retains well, its own roadmap is funded, and the new product sells to the same buyer through the same channel, solving a problem those customers already pay someone else to solve. That is expansion. A second product for a different market is closer to a new startup, with its own discovery, sales motion and years of runway. Expect any second product to take about eighteen months before it shows in revenue, and budget it as a separate initiative with an owner. Platform ambitions deserve the most skepticism: buyers of $10–20M vertical software companies mostly buy them as add-ons and pay for focus. Start by listing what your core customers pay other vendors for.

The decision rule

Build a second product for the customers you already serve, after the core is retaining and funded. A second product for new customers is a new company and should be judged as one.

Usually ready when

  • Gross retention near 95% and net retention above 100% in the core
  • The core roadmap and its reliability lane are fully staffed
  • Core customers already pay another vendor to solve the problem

Probably too early when

  • Growth in the core product has stalled and the second product is the proposed fix
  • The new product needs a different buyer or sales motion
  • Nobody owns it full time

The numbers

MetricValueWhat it meansSource
Time for a structural change to show in revenueabout 18 monthssecond vertical, platform rebuild or acquisition, from investment to revenuethe reason no lender funds this kind of changeGolden Section, publishedGrowth Capital Without Dilution
Exit multiple, $15–20M vertical software4.0x base; 5.5–5.8x with genuine vertical focusenterprise value divided by revenuefocus is priced; breadth is notGolden Section, publishedInvesting in Software, 2026 addendum
PE software platform buyouts, share of deal value41% in 2026 vs 71% in 2025platform buyouts as a share of private equity software deal valueadd-ons roughly doubled as a share; a $10–20M ARR vertical company is now usually an add-onGolden Section, publishedInvesting in Software, 2026 addendum
Engineering allocation for new AI-native productsabout 10% skunkworksshare of engineering and product resources on products that could replace the corebeside about 45% on the core and 45% on AI-native features inside existing workflowsGolden Section, publishedThe Enhancement Doctrine

Why

A second product competes with the first for the same scarce things, engineering capacity and the founder's focus above all. When the core is still leaking customers or missing its roadmap, a second product takes resources from the place they return most. That is why founders who reach for a second product to restart growth usually end up with two products growing slowly.

The distinction that matters is who the buyer is. Selling a new product to customers who already trust you uses the relationship, the sales motion and the data you have, and shows up as expansion revenue. Selling to a new market means rediscovering the problem, the buyer and the channel, which is why we treat adjacent markets as equivalent to a new startup. Before building, run customer segmentation to confirm the demand sits in your core cohorts and monetize the problem with the customer ROI play. Then give the product its own line in the budget.

One kind of second product is the exception we encourage: a small team building an AI-native product that could eventually replace your own core. If you do not build it, someone else will.

Illustrative scenario

The numbers are invented. A company selling scheduling software to home-health agencies is at $6M in annual revenue, with 94% gross retention and 108% net. Its customers pay a separate vendor for payroll, and 40 of them say they would consolidate. The founder also wants to sell the scheduling product to hospital systems. The team scopes both. Payroll uses the same buyer, the same sales team and data already in the product; hospitals need a new buyer, a longer cycle and compliance work. The company funds payroll as a separate budget line with its own product owner, sets an eighteen-month revenue target, and declines the hospital market for now.

When this does not hold

A product that has stalled because its market is shrinking may need a second product to survive, and then the risk of building is lower than the risk of staying. And an acquisition of a small product your customers already use can be faster and cheaper than building one.

What to do on Monday

  1. List the problems your core customers pay other vendors to solve, with the spend if you know it
  2. Check gross and net retention in the core before you scope anything new
  3. Write who buys the second product and through which channel; if either is new, treat it as a new company
  4. Price the second product as its own budget initiative with an owner and an eighteen-month revenue date

Mistakes founders make here

From the Golden Section mistakes list, each paired with the play that prevents it.

Mistake 43: Horizontally scaling

Taking the company into adjacent markets is the version of a second product that behaves like a new startup.

Mistake 153: Diluting Effort Instead of Concentrating Force

Two half-funded products dilute the force a single product needed to win its market.

Mistake 132: Too broad of product

Adding products for different customers makes the company harder to explain and harder to sell.

Plays we would run

In the order we would run them. Each is on its own page, most with a free Excel template.

Customer Segmentation

Confirms whether the demand for a second product sits inside your highest-quality cohorts.

Value Proposition & Customer ROI

Monetizes the problem the second product solves before you build it.

Product Management Process

Gives the new product its own vision document, owner and roadmap lane.

Budget Creation

Funds it as a separate initiative so the core roadmap is not quietly raided.

Development plays The product management and roadmap plays that decide what gets built and who owns it.

Questions this page answers

When should SaaS expand from one product to a platform?

Rarely as a goal in itself. Products connect into a platform when customers adopt several of them and the shared data makes each more valuable, which is an outcome of good second products rather than a strategy to start with. Buyers of $10–20M vertical software companies mostly buy them as add-ons to their own platforms, and they pay for depth in one vertical.

Is a second product better than taking the first product into a new vertical?

Usually, if it sells to the same buyer. A new vertical with the same product means new customers, new references and a new sales motion, which we treat as equivalent to a new startup. A second product sold to existing customers uses the trust you have already earned.

How should a second product be funded?

As a separate initiative in the budget, with its own owner, cost and revenue date. Because it takes about eighteen months to show in revenue, debt is the wrong instrument; operating cash flow or equity fits better.

Funding the next stage

A second product takes about eighteen months to show in revenue, which no lender will fund. Once the core retains, funding that change is what minority growth equity is for; before then, the better move is to fix the core.

Growth equity →

Reviewed by Dougal Cameron, CEO & Co-Founder on 2026-10-22. Golden Section observations are labeled separately from external benchmarks and illustrative arithmetic.