Five real companies. The signals available. The patterns identified. The call the engine made. See how it compares with what happened next. Validate it on your own signals.
Retool
B2B SaaS Startup
The signal
Retool had a functioning product built around reusable components for internal applications, but its first two customer and positioning hypotheses produced little commercial pull. "Excel-like" positioning generated no responses, while outreach to roughly 300–400 FileMaker users produced a response rate below 2% and negative feedback.
What SID called
The team demonstrated strong delivery capability while failing to generate commercial response across two distinct customer hypotheses.
ACT
Return to customer discovery and test a new segment and positioning hypothesis before resuming feature development or scaled outreach.
What happened
Retool broadened beyond the initial FileMaker positioning toward developers building internal applications and found materially stronger commercial response.
Before shipping its card, Ramp spoke with more than 100 finance and founder teams and manually analyzed transaction data to identify savings opportunities. One early analysis surfaced roughly $100K in unused software and approximately $200K in broader potential savings, demonstrating material customer value through a manual process.
What SID called
The team was proving customer value through a labor-intensive manual process while attempting to ship a product business.
ACT
Instrument the manual savings process and translate the repeatable decision logic into automated product capability.
What happened
Ramp embedded the savings thesis into its product and expanded from a corporate card into a broader finance-automation platform.
By July 2020, more than 95% of new customers were choosing cloud and subscription revenue was growing rapidly, yet approximately 75% of paid Jira Software and Confluence users remained on-premises. Server-to-Cloud migrations were accelerating while Atlassian continued expanding enterprise cloud capability and investment.
What SID called
Subscription revenue was accelerating while three-quarters of the paid user base remained on legacy on-premises infrastructure.
ACT
Accelerate enterprise migration tooling and support, and track Server-to-Cloud migration cohorts and post-migration economics.
What happened
Atlassian announced the end of new Server license sales and established a multi-year Server retirement timeline while continuing to invest in cloud capability and migration support.
Veeva's core CRM depended on Salesforce's platform under an agreement expiring in 2025. The relationship constrained expansion beyond defined life-sciences markets, while replacing the underlying platform would require significant time, investment, and customer migration.
What SID called
Veeva faced an expiring platform dependency with growth restrictions and a replacement path requiring significant time and expense.
ACT
Initiate a replacement-platform build-or-buy analysis and model renewal, non-renewal, and migration scenarios.
What happened
Veeva announced that it would move CRM onto its own Vault platform and would not renew the Salesforce platform agreement.
More than 70% of Samsara customers subscribed to two or more products, rising above 90% among large customers. At the same time, the company's core vehicle market remained only single-digit penetrated while R&D investment continued across core products and adjacent equipment and physical-operations use cases.
What SID called
Strong multi-product adoption pointed to a need to test whether packaging and pricing were fully capturing the existing land-and-expand value.
ACT
Analyze single-product versus multi-product customer economics and model packaging aligned to the existing land-and-expand motion.
What happened
Samsara continued scaling its multi-product land-and-expand model, with later large new-customer and expansion deals increasingly including multiple products.