Skip to main content

Tavism
All startup casesRapid Iteration

Rapid Iteration Cycles & Political Advocacy

Votizen — 4 Iterations to Product-Market Fit

Kill vanity metrics. Run short product versions. Keep what cohorts and split tests prove.

Case overview

The challenge

David Binetti built a political advocacy platform to connect voters with legislative representatives. The first product shape failed. He needed a way to iterate without mistaking signups for traction.

Iteration cycles

Four iteration cycles

Each version tested a different path from voters to influence—and measured whether people actually used it.

VersionProductOutcome
V1Social network for votersFailed engagement
V2Micro-donations to campaignsLow conversion
V3Verified constituent petitionsHigh validation
V4B2B advocacy API platformProduct-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.

V1–V2V3–V4

Vanity traps cut; validated path scaled

For founders

Key takeaways

How to iterate toward product-market fit without lying to yourself with vanity metrics.

  1. Treat each product version as an experiment with a kill criteria.
  2. Cohort analysis shows whether users come back—not just whether they signed up.
  3. Split tests settle arguments faster than opinions.
  4. 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.

Accelerate Your Iteration Cycles