All startup casesRapid Iteration
Case overview
The challenge
Iteration cycles
Four iteration cycles
Each version tested a different path from voters to influence—and measured whether people actually used it.
| Version | Product | Outcome |
|---|---|---|
| V1 | Social network for voters | Failed engagement |
| V2 | Micro-donations to campaigns | Low conversion |
| V3 | Verified constituent petitions | High validation |
| V4 | B2B advocacy API platform | Product-market fit |
Metric tracking
Cohorts and split tests beat vanity numbers
Binetti tracked cohort retention and ran split tests instead of celebrating raw signups. That discipline killed versions that looked busy but did not move advocacy outcomes—and funded the petition and API bets that did.
For founders
Key takeaways
How to iterate toward product-market fit without lying to yourself with vanity metrics.
- Treat each product version as an experiment with a kill criteria.
- Cohort analysis shows whether users come back—not just whether they signed up.
- Split tests settle arguments faster than opinions.
- Pivot when the metric fails; keep the learning when the channel or packaging works.
Stuck between product versions?
Book 30 minutes. Bring the iteration you are on and the metric that should kill or keep it.