Three-Reasons Launch Test
Launch only when you need customers, capital, or candidates.
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 4
- Confidence
- 99%
The Three-Reasons Launch Test treats a public launch as an expensive intervention rather than a rite of passage. Before launching, ask whether the company needs more customers, more capital, or more job candidates. If none of those inputs constrains growth, the launch has no clear operational job. It may instead generate a one-time wave of users who uncover many defects while overwhelming the team's ability to repair them, creating disappointed customers and reputational damage. The test is especially relevant to complex products entering established markets, where alternatives already work and users expect a high-quality experience. It does not argue against feedback or gradual releases; a company can onboard customers continuously and grow without declaring a singular public-launch moment. Launch when it unlocks a needed resource and the organization can absorb the consequences.
Origin
Rahul Vohra learned this decision rule from Coda founder and CEO Shishir Mehrotra while the two founders discussed why their productivity companies had held back from conventional public launches.
Core principles
- 01A public launch is a means, not a mandatory startup milestone.
- 02Launches should resolve a specific constraint on company growth.
- 03A large influx can damage trust when the product cannot support it.
- 04Strong private growth can make a public launch unnecessary.
- 05Existing-market products face a higher quality bar than new-market products.
How to run it
- 1
Identify the Growth Constraint
Determine whether growth is currently limited by customer supply, available capital, or the hiring pipeline. Use operating data rather than launch enthusiasm.
Pro tip Name the precise metric the launch is expected to improve.
Watch out Do not launch merely because conventional startup advice says it is time.
- 2
Match Launch to the Constraint
Specify how publicity will bring the needed customers, investors, or candidates. Confirm that the likely audience overlaps with the constrained resource.
Pro tip Design launch messaging around the particular resource the company needs.
Watch out General awareness is not enough unless it translates into the required input.
- 3
Model the Influx
Estimate signups, support requests, defects, infrastructure load, and onboarding demand. Compare the likely influx with the team's capacity.
Pro tip Use evidence from existing referrals and controlled cohorts to estimate behavior.
Watch out A launch can permanently disappoint users if problems cannot be corrected responsibly.
- 4
Launch or Continue Controlled Growth
Proceed when the launch addresses a real constraint and the company can absorb demand. Otherwise continue private, referral-based, or cohort-based growth.
Pro tip Revisit the test whenever one of the three resource constraints changes.
Watch out Delaying a launch should not become an excuse to avoid all customer exposure.
In the wild
Superhuman had users, revenue, capital, hiring ability, and strong referral growth while still being described as pre-launch. Because a conventional launch did not solve a pressing resource constraint, the company continued onboarding controlled numbers of users each week rather than creating an unmanageable influx.
→ The team preserved product quality and controlled growth without relying on a single public event.
A hypothetical developer-tool startup has enough beta customers and funding but cannot attract specialized compiler engineers. It uses the test to define recruiting as the binding constraint, then launches with technical material designed for that candidate audience and sufficient capacity for new-user support.
→ The launch has a measurable purpose and targets the resource the company actually lacks.
Common mistakes
Launching for Ceremony
Treating launch day as an obligatory milestone creates work without establishing what business problem it will solve.
Ignoring the Support Shock
A publicity surge can expose more defects than the team can resolve, leaving thousands of users with a poor first impression.
Confusing Delay With Secrecy
Avoiding a singular public launch does not mean avoiding users. Continue controlled onboarding, observation, and growth.
Is it for you?
Best for
It is best for startups already acquiring customers privately and deciding whether a large public launch will accelerate or destabilize the company.
Not ideal for
It is not ideal for time-sensitive network-effect markets where immediate scale is itself the primary competitive advantage.
From the transcript
“And he said, a startup should only launch for one of three reasons.”
“Number one, either you need more users or customers to sell to. Number two, you need more capital to spend.”
“Or number three, you need more candidates to hire. If you're benchmarking well across all three, if you're attracting all the users you need to,…”
From the episode
Superhuman (with CEO Rahul Vohra)
Rahul Vohra