There's a pattern that repeats at SaaS companies after reaching $5-10M ARR: growth slows in the core product, the board asks about expansion opportunities, and the team starts building a second product. Sometimes this is a new module. Sometimes it's an expansion into an adjacent market. Sometimes it's a fundamentally new product category.
The second product expansion usually underperforms the first product, consumes disproportionate resources, and causes the core product to stagnate precisely when it needed investment.
Why the second product trap is so common:
Growth slowdown looks like a product problem. When growth slows at $5-10M ARR, the instinct is that the first product has reached its ceiling and expansion is required. More often, the growth slowdown is a distribution problem — the team hasn't built the channels to reach the addressable market, not that the addressable market is exhausted.
The second product gets the best people. The new, exciting initiative attracts your best engineers and PMs. The core product gets the people who remain. This accelerates the core product's decline while the new product starts from scratch.
Customers don't buy the second product the way they bought the first. The first product had a genuine breakthrough for customers who had an acute pain. The second product often solves a less acute pain for the same customers, or a different pain for different customers. Neither replicates the original product-market fit dynamics.
When second product expansion is the right move:
When the first product has genuinely saturated its addressable market (not just slowed growth — genuinely saturated).
When the second product is built for the same buyer persona and represents a natural expansion of the workflow the first product serves.
When the first product has enough organizational momentum to sustain itself while the second product is developed.
Exhaust the first product first. The expansion will still be there.