Launching a second product without breaking the first

A second product is one of the most common moves a growing startup makes. A new customer segment asks for something adjacent. A competitor leaves a gap. Investors ask what the next line of revenue will be. The case for building is usually reasonable. The risk is that the second product fails, and takes some of the first one with it.

Most new products fail

The base rate is not encouraging. A Nielsen study of about 12,000 consumer goods launches across Europe found that 76% failed within their first year¹. That data is from consumer goods and is more than a decade old, so treat it as direction, not a forecast for software. But it matches what Clayton Christensen observed: about 30,000 new consumer products launch each year, and "many of them fail"². His explanation was that products fail when they are not built around the job the customer is trying to get done.

You may have seen a claim that 95% of new products fail. We could not trace that figure to a primary source, so we do not use it.

The same pattern shows up in startups. In CB Insights' global study of VC-backed shutdowns since 2023, 43% cited poor product-market fit³. A second product starts from zero on product-market fit, even if the company behind it does not.

Experience changes the odds

McKinsey's global survey of 1,176 executives on corporate venture building is the best recent evidence on what separates new ventures that work from those that do not⁴. It found that:

• Novice venture builders are three times more likely than experienced builders to launch a venture without good product-market fit.
• Experienced builders are about twice as likely to meet or beat their scale targets, and see 12 times more revenue in year five, on about twice the pre-breakeven investment.
• Experienced builders are 1.4 times more likely to use partnerships or alliances, and 1.5 times more likely to have a dedicated venture team.
• Ventures that acquired a business report nearly four times more year-five revenue.

The survey covers corporates rather than startups, and the results are self-reported. The lesson still applies to a growing startup building its second product: the teams that do this well validate before they build, give the venture its own team, and bring in outside capability rather than learning every lesson themselves.

A new market is a new product

Expanding into a new country carries the same risk, because the customer, the regulator and the competition all change. Africa has fragmented regulatory frameworks across 54 countries⁵. One investor-operator told Techpoint Africa that when founders ask about expanding:

"90% of the time, the answer will be no; let's just win the local market."⁵

Even established companies pull back. In October 2024, Jumia exited South Africa and Tunisia, saying their trajectory "did not align with the strategy of the group". The two markets were about 3% of gross merchandise value⁶.

Validate before you build

The cheapest point to stop a second product is before anyone writes code. A validation sprint should answer four questions:

1. What job does the customer need done? Speak to the customers you want to serve. Ask what they use today, what it costs them, and what they would stop using if your product worked. Write down the job in their words.
2. Will they commit? Interest is not demand. Look for a commitment that costs the customer something: a pre-order, a paid pilot, a signed letter of intent, or time given to a structured trial.
3. What will they pay? Test price before you build. A product customers want but will not pay enough for is a cost, not a business.
4. What would make you stop? Set the stop criteria in writing before you start: the level of demand, price and early retention below which you will not build. Teams that set these afterwards almost always find a reason to continue.

Then hold the second product to the same evidence standard as the first. Crelligent's VeloDesk PMF Validation scores product-market fit across 10 weighted dimensions, with retention carrying the highest weight. A second product should earn its build budget on the same evidence.

Protect the core team

The quiet risk of a second product is what happens to the first. The people who know the most are usually the ones who get pulled across: the best engineer, the head of customer success, a founder. When they move, the core business loses the people holding it together.

We found no recent study that measures this distraction cost, so we will not quote a number. But there is evidence on what happens when headcount grows ahead of the system. Startup Genome's study of more than 3,200 high-growth startups found that 70% scaled prematurely, and their teams were about three times larger than those of consistent peers at the same stage⁷. That study is from 2011, but the pattern is familiar: more people, less clarity, slower delivery.

Three rules help:

• Install the core business's operating model first. If onboarding, support and renewals in the first product only work because specific people run them, write down how they work and who owns them before anyone moves. In the ESRE OS, this is L2, the Operating Model layer. It carries a 1.4× weight in the ESRE OS Performance Score because it is the primary constraint in 91% of the enterprises assessed in Crelligent's African Enterprise Health Index (Crelligent AEHI data; mid-market enterprises, not startups).
• Give the venture its own team. McKinsey's experienced builders are 1.5 times more likely to have a dedicated venture team⁴. Part-time ownership of a new product usually means it gets the time left over.
• Watch the core metrics. Track retention and delivery in the first product every month while the second is being built. If they drop, the second product is costing more than its budget.

When to co-build

Not every second product needs an outside partner. Build it yourself if you have spare capacity on the core team, the product is close to what you already sell, and you have built a new product before.

Consider co-building when:

• The new product or market needs skills your team does not have.
• Your best people cannot leave the core business without it slipping.
• You have not taken a new product from validation to launch before.
• You want to test demand before committing your own build budget.

This is what Crelligent Foundry's Venture Build is for. We take a second product, a spin-out or a new market from validation to launch, with our team doing the build: demand, pricing and PMF evidence first, then the product, then the operating system, go-to-market and first customers. You keep the company and own everything we build. Your core team keeps running the core.

Talk to us about your next venture

If you are weighing a second product, a spin-out or a new market, apply to Foundry or request a quote for Venture Build. We scope each venture individually after a discovery call.