SaaStr's editorial rule of thumb tells SaaS founders to wait: build a second product by 10,000 customers or $100 million ARR, whichever comes first (SaaStr). Samsara's Chief Strategy Officer Kiren Sekar says that number is off by a factor of ten. He advises launching a second product by $10 million ARR, and points out that Samsara's second product, not its first, is now the company's largest revenue generator (SaaStr).
Two credible operators, two numbers ten times apart. That gap is the tell. If the right answer were a revenue milestone, the advice would converge. It hasn't, because revenue was never the real signal. Customer behavior is.
The failure mode nobody plans for
Steve Jobs named this problem in 2007, describing what the industry now calls "second product syndrome":
I lived through Apple, the Apple II was incredibly successful and Apple III was a dud, and I've seen a lot of companies not make it through that.
(Wikipedia, citing The Pixar Story). The pattern he's describing isn't a timing failure. It's a listening failure. A company that hits big with product one starts trusting its own instincts as the product engine, rather than the customers who told it, with money and usage, what to build first.
Airtame chose the opposite failure mode. Its first product raised $1,268,148 from 12,369 backers on Indiegogo in January 2014, a European crowdfunding record at the time (Crowdfund Insider). Airtame 2 didn't ship until October 10, 2018, four years later (Entrepreneur.com). Four years is long enough for a market to move on without you.
What the signal actually looks like
HubSpot didn't wait for a revenue threshold or a customer count. It watched what its CRM customers were already trying to do with the product and built toward that. At INBOUND14 in Boston (September 15-18, 2014), co-founder and CEO Brian Halligan introduced a free CRM alongside Sidekick, a sales acceleration tool, unveiling the sales platform on the Tuesday night of the conference (HubSpot company news). The second product wasn't a bet on a new market. It was a bet on where the existing customer base was already leaning.
Veeva Systems is the clearest proof that this bet compounds. Veeva built Vault, its R&D and Quality Solutions line, as a second product beyond its original Commercial CRM offering. By the end of fiscal year 2026, Vault-based Solutions had 1,196 customers against 767 for the original CRM line (Veeva Systems, PR Newswire). The second product overtook the first. Nobody at Veeva was checking a revenue milestone to decide it was time. They were watching pharmaceutical and life sciences customers pull the company into an adjacent workflow, then building the product that workflow demanded.
The signal, not the number
Stop asking what revenue number or customer count justifies a second product. Wrong question. The right one: are customers already using product one to hack together a second job it wasn't built for? Are support tickets, feature requests, or your own sales team describing the same workaround independently, without prompting? That repetition, showing up unprompted across separate customers, is the signal both milestones are crude proxies for. Sekar's $10 million ARR number works for Samsara because Samsara's customers hit that workaround pattern early. SaaStr's $100 million number holds for companies where it took longer to show up. The number was never the cause. It was a byproduct of when the pull became undeniable.
This week, pull the evidence instead of guessing at a milestone:
- Read your last 90 days of support tickets for the same unmet need showing up across unrelated accounts.
- Ask sales what workaround prospects keep asking about, unprompted, on calls.
- Check whether your own team has quietly built an internal tool to patch the same gap.
Find the same need three or more times and you're not early. You're late, and the market has already told you what to build.