The Death of the Three‑Act Startup Playbook: How AI Lets Companies Reach $100M ARR in 12‑24 Months
Former Sequoia partner Mike Vernal argues that the traditional three‑act SaaS growth model is obsolete, citing AI‑native companies like Cursor that achieve $100 M ARR in 12‑24 months, and urging founders to abandon protective wedges in favor of ambitious, full‑product launches.
Mike Vernal, former Sequoia partner, posted a tweet titled “The Death of the Three‑Act Playbook,” claiming the standard SaaS growth roadmap that has guided startups for the past two decades is dead.
Old Playbook: Three Acts Over Ten Years
The classic model consists of:
Act I – Unbundling : Launch a narrowly focused feature that can generate $10‑50 M ARR within 3‑5 years.
Act II – The Suite : Expand into adjacent tools, aiming for $200‑500 M ARR over another 3‑5 years.
Act III – The Platform : Re‑package the suite into a platform that can support $5 B+ ARR.
This sequence typically takes more than a decade, with each act providing a “protective wedge” that shields the company from larger competitors.
New Reality: $100 M ARR in 12‑24 Months
AI‑native startups such as Cursor, Cognition, Clay, Harvey, Sierra, Baseten, Fireworks, and Lovable have reached $100 M ARR in just 12‑24 months, whereas legacy SaaS firms like Salesforce (7 years), Slack (5 years) and Snowflake (4 years) needed 4‑7 years for the same milestone.
The driver is AI‑assisted code generation, which reduces engineering cost to near zero and lets a single developer accomplish the work of five to ten engineers.
Because the time bottleneck has vanished, the protective wedge of Act I no longer provides a moat; founders can now build a complete product in six months.
Cursor’s Counterexample
When Cursor (formerly Anysphere) raised a seed round in 2023, its plan was to fork VS Code and build a brand‑new IDE. Vernal initially thought this was reckless, suggesting a more rational path: first release a VS Code extension to prove the AI coding assistant’s value, then later replace the editor.
Cursor ignored the advice, built a full IDE from day one, and ultimately succeeded, demonstrating that an ambitious “full‑replace” strategy can create a stronger moat than a modest extension.
Investor Perspective Shift
Vernal now looks for “unreasonable, unrelenting ambition” rather than a protective wedge. He says the new standard is to “jump straight into the deep end” because engineering speed is no longer a constraint.
“I find myself wanting founders to dive straight into the deep water.”
Implications for Chinese B2B Startups
China’s SaaS market faces weaker customer willingness to pay and higher acquisition costs, making the traditional wedge even less effective. With AI lowering development cost, the critical factor becomes distribution speed and the ability to deliver a complete solution that large incumbents cannot copy easily.
Product speed is no longer the bottleneck; distribution speed is.
The wedge strategy may be less applicable in China.
Building a full‑stack solution from day one can serve as a stronger defense.
Teams must be capable of delivering a full product within 6‑12 months—a feat that was previously impossible without AI.
New Playbook
The revised roadmap compresses the timeline from ten years to roughly three:
Act I – Build the full product (6‑12 months, target $10 M ARR).
Act II – Rapidly expand into categories or verticals (6‑12 months, target $100 M ARR).
Act III – Redefine the category (12‑24 months, target $500 M+ ARR).
This shift also changes the founder’s skill set: from deep expertise in a single area to the ability to coordinate multiple initiatives simultaneously, with AI acting as the execution engine.
Conclusion
Vernal’s tweet has sparked debate, but the consensus is that time is no longer a natural ally for startups. Investors now ask why founders don’t aim for Act III from the start, and the emerging AI‑driven cohort of companies proves that the old three‑act script is dead, even if the drama continues.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Code Mala Tang
Read source code together, write articles together, and enjoy spicy hot pot together.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
