Why launching a second product is usually a bad idea

Executive overview

Most founders face the temptation to launch a second product — often as a reaction to slow growth rather than a genuine opportunity. The real problem is nearly always something fixable in the first product: wrong pricing, untapped marketing channels, or unresolved product-market fit.

The default answer should be no — unless you can demonstrate asymmetric upside, a short feedback cycle, and a non-catastrophic downside if it fails.

Rob Walling and Ruben Gámez walk through the pitfalls, the rare valid exceptions, and the mental frameworks for making the decision well.

Why founders reach for a second product

• Growth stalls and founders look for a shortcut rather than addressing the root cause.
• Common misdiagnosis: "we've tapped out the market" when fewer than 1% of potential customers have been reached.
• Slow growth is usually exhausted marketing channels, not an exhausted market.
• Shiny object syndrome and launch dopamine drive premature decisions.
• Platform risk is one of the few legitimate reactive reasons to diversify.

The focus problem

• Every person added to a second product is taken away from the first — true even at 170 employees with $38M in funding (Leadpages/Center example).
• Code is roughly 10% of a product; the other 90% — SEO authority, brand equity, support knowledge, marketing — all restart from zero.
• Two products under one domain still splits positioning, roadmap decisions, and dev attention.
• A 50/50 attention split between two products reliably prevents either from reaching momentum.
• Momentum compounds: revenue, brand, and team capability build on each other — splitting prevents compounding.

The portfolio-of-products trap

• Diversification as a motivation is fear-driven and undermines the momentum needed to build a meaningful business.
• A portfolio of small products rarely reaches seven figures; each product stays sub-scale.
• The stair-step path (one small product, then a focused larger one) is more reliable than running parallel products indefinitely.
• A handful of founders build a sustainable portfolio; thousands more build one focused product to real scale.

When a second product can make sense

Three conditions should all hold:

1. Asymmetric upside — if it works, the outcome is disproportionately large relative to the effort.
2. Short feedback cycle — you will know within weeks, not 12+ months, whether it has traction.
3. Non-catastrophic downside — failure doesn't materially harm the core business.

Additional factors that improve the odds:

• The opportunity is a green open field, not a "grass is greener" escape from existing problems.
• The new product shares proprietary infrastructure or data with the first (e.g., Stratosphere/Finchat).
• There is a plausible path to reunifying the products if the second succeeds.
• The founder has a track record of finishing things rather than bouncing between launches.

Case studies

Bitsketch → Signwell (Ruben Gámez)

• Bitsketch (proposal software) had accrued technical debt and needed a near-rewrite.
• During that process, market pull toward document signing was strong and came from high-value customers.
• Decision was made iteratively, with constant re-evaluation rather than a single committed bet.
• Signwell now receives the majority of growth focus; Bitsketch runs as a stable, low-maintenance product.
• Outcome: the right call, but only because of deep deliberation and willingness to change course.

Cart Hook → Post-purchase upsells (Jordan Gall)

• Cart Hook was a cart-abandonment email tool at low-tens-of-thousands MRR.
• An unpublished Shopify API enabled checkout modification — a capability nobody else had.
• Build-and-test cycle: ~two to three months of engineering.
• Strong founder intuition, corroborated by external advisors, confirmed the asymmetric upside.
• Outcome: post-purchase upsell product took over entirely; original product was sold or wound down.

Stratosphere → Finchat.io

• Stratosphere had proprietary financial data; Finchat added a chat interface to that same data.
• Built and shipped in six weeks when AI chat products were gaining rapid market interest.
• Shared data infrastructure meant Finchat was not a true second product — it was another interface.
• Outcome: instant traction; the two products could feasibly merge back under one roof.

Moz (cautionary tale)

• Attempted to expand from SEO tooling to a full marketing suite.
• Insufficient validation; founder hubris after early success.
• Outcome: significant resource drain, widely acknowledged as one of Rand Fishkin's biggest mistakes.

How to take feedback without confirmation bias

• Treat an idea as a starting point, not a finished position — expect it to be wrong and ask how wrong.
• David Cancel's framing: assume the idea is wrong; determine whether it's 10% wrong or 90% wrong.
• Negative or unexpected feedback is a signal to examine emotional attachment, not a reason to defend.
• Collect multiple data points, weight them by the source's relevant context and experience.
• The goal is not "do it or don't" — it's "how does this feedback improve or invalidate the idea?"

Cross-selling and product suites

• Adding a complementary product to cross-sell to existing customers is harder than it looks.
• Customers do not automatically buy a second product just because they trust the first.
• Companies that do this well (Intercom, HubSpot, Zoho) are typically at significant scale with specific growth mandates.
• Moving in this direction too early is one of the more common mistakes.
• FreshBooks approach: launch the new product under a different name, validate growth, then rebrand once traction is confirmed.