Evidence Milestone Prototype Ladder
Build each prototype to retire the next risk and earn the next stage
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 99%
Whoop's early development followed a sequence of evidence-producing prototypes. Ahmed's team first identified measurements it believed were essential, including wrist-based heart-rate variability, accurate heart rate during motion, and sleep. Instead of making a polished consumer device immediately, the team built a large, unattractive wristband to test whether a difficult measurement could be collected non-invasively. That proof helped support the next financing and a smaller, more accurate version. The pattern repeated across successive funding stages until the company could manufacture. The reusable mechanism is to map the venture's critical risks, choose the next blocking uncertainty, and build only enough to produce credible evidence. Each prototype earns the right to tackle the next risk rather than pretending to be the final product.
Origin
Ahmed describes Whoop's early prototypes and financings as successive milestones that improved measurement, form factor, and readiness for manufacturing.
Core principles
- 01A prototype should answer a critical question rather than imitate a final product
- 02Technical proof can justify the next tranche of capital
- 03Appearance matters after the core measurement or mechanism works
- 04Each stage should reduce a different material risk
How to run it
- 1
Map the fatal risks
List the technical and commercial assumptions that could make the product impossible or unworthy of further investment. Rank them by how strongly they block the next stage.
Pro tip Start with the uncertainty that can invalidate the most downstream work.
Watch out Do not begin with cosmetic work when feasibility is unresolved.
- 2
Define milestone evidence
Specify what measurement, test result, or user behavior would credibly reduce the selected risk. Make the standard clear before building.
Pro tip Tie the evidence to a concrete next decision, such as further engineering or financing.
- 3
Build the narrow prototype
Construct the smallest version that can generate the required evidence. Accept rough appearance when it does not affect the question being tested.
Pro tip Spend on the part of the system that produces the proof.
Watch out A broad prototype can hide whether the critical mechanism actually works.
- 4
Test against the bar
Evaluate the prototype against the predeclared standard and document what remains uncertain. Reject vague claims of progress that do not answer the milestone question.
Watch out Do not move the success criterion after seeing the result.
- 5
Earn the next stage
Use successful evidence to authorize or finance the next prototype. Select the next blocking risk and repeat until the product is ready for manufacturing or sale.
Pro tip Explain precisely what the last prototype proved and what the next one must prove.
In the wild
Ahmed says the early team built a large, cumbersome wristband that could measure heart-rate variability from the wrist. The device was not intended to look ready for consumers. Its purpose was to demonstrate that the measurement could be collected non-invasively and support the case for a smaller next version.
→ The technical proof helped the company raise capital and continue reducing product risk.
Illustrative example: a sensor startup builds a bench prototype solely to prove that its battery can support a full operating day. Only after passing the endurance test does it invest in miniaturization and enclosure design.
→ The company avoids polishing a device whose power requirements might make it unusable.
Common mistakes
Building the polished device first
A finished appearance consumes capital without proving that the underlying measurement or mechanism works.
Using prototypes without decisions
A prototype that is not tied to a risk and a next-stage decision can create activity without reducing uncertainty.
Claiming more than the test proved
Proving one measurement is possible does not prove demand, manufacturability, or the performance of the final form factor.
Is it for you?
Best for
It is best for hardware or deep-technology ventures with sequential engineering, form-factor, and manufacturing risks.
Not ideal for
It is not ideal when a cheap customer-facing test can validate the central uncertainty without building technology.
From the transcript
“the first prototype we built was to drisk some of the challenges”
“our early prototypes were less about making it look good”
From the episode
537: He Made $3.6B Selling Fitness Trackers
Will Ahmed