When Should You Add a Second Product? Answers from the CEOs of Twilio, Veeva, Amplitude, HubSpot, Gainsight and More

Editor’s note: This headline keeps the original SaaS debate framing. Some leadership titles have changed since the original conversations, but the strategic lessons still hold up surprisingly well.

Every founder eventually runs into the same awkward dinner-party question: “So… what’s next?”

If your first product works, customers love you, revenue is growing, and the team is finally sleeping at least four hours a night, the temptation to launch a second product shows up fast. Sometimes it arrives as customer demand. Sometimes it arrives as investor pressure. Sometimes it arrives because someone on the board says the phrase platform strategy with far too much confidence.

But adding a second product is not a harmless side quest. It can expand your total addressable market, lift net revenue retention, and create a true second act. It can also eat management attention, confuse sales, dilute product quality, and turn a focused company into a wandering mall kiosk with a Slack workspace.

So when should you actually do it?

The smartest answer is not “early” or “late.” It is this: add a second product when your first product gives you leverage, your customers reveal adjacent pain, and your organization can support real focus on something that is big enough to matter.

The rough rule of thumb: before growth gets awkward

In SaaS circles, one of the most repeated rules is that a real second product should be firmly in place by roughly the time you hit 10,000 customers or $100 million in ARR. That does not mean you wake up at $99 million, slam an espresso, and declare yourself multi-product by lunch. It means the thinking, validation, and early launch work usually needs to start well before that point.

Why? Because growth has gravity. The first product eventually faces market saturation, slower new-logo growth, or a tighter ceiling than everyone hoped. If you wait until the dashboard starts looking emotionally complicated, you are already late. Gainsight learned this the hard way. Nick Mehta has openly said the company began feeling TAM pressure around $50 million ARR and should have started its “Act II” earlier rather than trying to over-scale a market that was already getting maxed out.

That is the key tension. Build too early and you fracture focus. Build too late and you are trying to plant a tree during a drought.

The Twilio answer: if customers want it and you can build it, try it

Jeff Lawson’s historic Twilio-style answer is refreshingly pragmatic: if demand is there, build it, test it, and do not over-romanticize the decision. Twilio came up through a developer-led motion, which made experimentation easier. When the customer base is broad, self-serve, and technically engaged, adjacent products can sometimes be introduced faster because the cost of learning is lower.

That logic fits Twilio’s DNA. The company expanded from communications APIs toward a broader customer engagement platform, later strengthening that move through acquisitions like SendGrid and Segment. In plain English, Twilio did not stop at “send a text.” It kept asking, “What else around communication, data, and customer context belongs in this workflow?”

The lesson is not “be reckless.” The lesson is that for some companies, especially product-led or developer-led ones, the second product can begin as a serious experiment. If customers are already pulling you there, and the extension is not wildly off-brand, speed matters. You can prune later. You cannot learn from products you never ship.

When the Twilio mindset works best

• Your customers already understand the core platform.
• The second product solves an adjacent workflow.
• Your distribution is strong enough to test without building a second company inside the company.
• You can kill or revise the product without traumatizing the whole business.

In other words, Twilio’s model works when the downside of trying is manageable and the upside of learning is huge.

The Veeva answer: do not get distracted by cute add-ons

Peter Gassner’s answer is almost the opposite, and honestly, it is the one that makes founders sit up straighter.

His view is that the easy add-on is often a trap. Customers will absolutely ask for little nearby features. They will want convenient extras. They will want things that are simple to build because those things sit right next to your existing product. The problem is that many of those ideas are too small to matter. They might add 10% or 20% to revenue, but they do not create a real second act. They create extra meetings.

Gassner’s standard is tougher: the second product should be capable of becoming massive, not merely helpful. That is how Veeva thought about moving beyond CRM and building Vault, which became a major business in its own right. The big insight here is that a second product should not just be easier to sell. It should be large enough to justify the distraction, staffing, roadmap tradeoffs, and go-to-market complexity that come with becoming a multi-product company.

This is the bold-founder version of the test: If this new product works, can it someday rival the first one? If the answer is no, you may have found a good feature, a strong add-on, or a pricing lever. But you may not have found your next chapter.

The HubSpot answer: never launch from desperation

Dharmesh Shah adds a different warning, and it is one of the most useful in the bunch: the worst time to build a second product is when you are desperate.

That is such a brutally good filter because desperation makes every bad idea look visionary. If the first product is slowing, a competitor is getting louder, or your category suddenly feels crowded, the second product can start to look like a rescue boat. Usually it is not. Usually it is a very expensive kayak with branding.

Shah’s advice is to know exactly why you are building the product and what leverage you already have. That leverage can be customer trust, market knowledge, code, distribution, brand, data, or existing workflow ownership. If your second product is just as hard to launch as the first one, you may not actually be using any leverage at all. You may just be starting over while pretending it is strategy.

HubSpot is a great case study because it did not stay boxed into a single marketing product. It expanded into sales, CRM, service, operations, content, and commerce over time. But the smart part was not expansion for expansion’s sake. The smart part was using the same core philosophy, customer relationships, and go-to-market motion to solve adjacent problems for growing businesses.

The HubSpot test

• Do you know why this product exists?
• Can you name the customer pain clearly?
• What leverage from product one helps product two win faster?
• If launch is still painfully hard, what leverage are you missing?

That is a much healthier way to expand than saying, “Well, everyone else has a suite now.”

The Amplitude answer: stay close to the use case

Spenser Skates’ lesson is sharp: when you expand, do not drift into a new market too early. Build something complementary to the existing product instead.

This matters because founders often confuse adjacent with random. A new buyer, new category, new motion, new pricing model, and new implementation pattern are not one expansion. That is five expansions wearing a trench coat.

Amplitude’s operator logic is that your product remains your biggest growth lever. Talk to customers. Understand the use case deeply. Expand around what they already value. That approach preserves clarity in positioning and reduces the risk that your second product becomes a science project loved only by the internal launch team and one overly enthusiastic design partner.

More broadly, Amplitude’s evolution into a wider platform reinforces the point that expansion is easiest when it compounds your existing system. The best second products do not make customers ask, “Wait, why do you do this now?” They make customers say, “Honestly, I was wondering when you were going to build this.”

The Gainsight answer: start your second act before the wall appears

Gainsight’s story is a reminder that being early in a category can create its own trap. When you define a market, it is easy to believe there is always more room inside that same market. Sometimes there is. Sometimes there is a wall coming toward you in slow motion.

Nick Mehta has described the mistake clearly: Gainsight saw slowdown signs around $50 million ARR, realized it was becoming TAM-bound, and did not have a second product ready. The company later broadened into a more platform-oriented approach, adding adjacent areas like product analytics and communities, but the lesson was expensive. The second act should have started sooner.

That is why founders should track market penetration, not just revenue growth. A healthy quarter can hide a narrowing future. If you are becoming dominant in a limited category, your next product is not a luxury. It is a strategic necessity.

So when should you add a second product?

Here is the practical answer after looking across all these operator perspectives:

Add the second product when these five conditions are true

1. Your first product has real product-market fit. Not “promising.” Not “loved by three lighthouse customers.” Real fit.
2. Customers reveal adjacent pain repeatedly. Not once at a conference booth. Repeatedly.
3. You have leverage. Brand, distribution, data, workflow ownership, domain expertise, or technical assets that make product two easier to launch than product one.
4. The opportunity is large enough to matter. A true second act, not a decorative upsell.
5. Your go-to-market can support it. If it needs a different buyer, different team, or different sales motion, plan for that honestly.

If those conditions are missing, keep strengthening the core. If they are present, do not wait forever. “Too late” is not safer than “too early.” It is just slower regret.

Add-on or second product? Know the difference before you hire a task force

This may be the most underrated distinction in the whole discussion.

An add-on is something customers can easily tack onto the core purchase. It boosts ACV, deepens stickiness, and can be sold by the same team with minimal drama. A second product is different. It has its own story, roadmap, adoption curve, and often its own internal politics. Confusing the two leads companies to either underinvest in a real opportunity or overcomplicate a simple monetization move.

If customers can buy it with a quick “yes, add that too,” it may be an add-on. If it changes buyer conversations, implementation scope, or the strategic value proposition, it is probably a second product. Treating those two things the same is how companies end up with packaging decks that look like airport terminal maps.

Real operator experiences and lessons from the second-product journey

What makes this topic so fascinating is that no serious operator talks about the second product as a pure innovation problem. They talk about it like a company-design problem. That feels exactly right.

In practice, the second product usually begins with enthusiasm and ends with operational truth. The enthusiasm phase is fun. Customers say they want more. Product people see adjacency everywhere. Revenue leaders imagine bigger expansion motions. Investors nod like they just discovered gravity. Then reality shows up. Who owns the roadmap? Who sells it? Is it bundled, standalone, or both? Does customer success support it with the same playbook? Are we solving for the same buyer or a new one? This is where the great companies separate from the merely optimistic ones.

Twilio’s experience suggests that broad distribution and strong developer trust create room to experiment. When users already view you as programmable infrastructure, adjacent products can feel natural. Veeva shows the opposite muscle: discipline. Instead of chasing little nearby requests, it pushed toward a second product big enough to reshape the company’s future. That takes patience, courage, and the rare ability to say no to ideas that are good but not important enough.

HubSpot’s journey teaches another founder lesson: leverage is everything. The second product should not feel like you are starting from zero with a nicer logo. It should feel like the company has earned the right to solve one more problem for the same customer base. That is why adjacent expansion is so powerful. The best second products borrow trust from the first one.

Amplitude’s view is especially useful for modern SaaS teams because today’s tooling makes it deceptively easy to ship. You can launch faster than ever, but speed does not remove the need for strategic coherence. A company can release a lot of things and still not become meaningfully multi-product. Shipping more is not the same as expanding wisely.

And Gainsight is the cautionary tale every founder should keep taped near the monitor: if you wait until growth is obviously slowing, your second act is already behind schedule. The market rarely sends a polite calendar invite that says, “Your original TAM will be exhausted in six quarters. Best regards.”

So the lived experience behind all this advice is simple: the right second product is less about ambition and more about timing, adjacency, leverage, and scale of outcome. Build it too early and you divide the company before it is strong enough. Build it too late and you discover that your category was smaller than your confidence. Build the wrong one and you get complexity without compounding. But build the right one at the right moment, and suddenly the company stops acting like a single-product vendor and starts behaving like a durable platform.

That is the real prize here. Not more SKUs. Not a prettier pricing page. A stronger future.