The hit-rate math: how many product tests it really takes to find a winner

Fast answer

A scalable winner shows up in roughly one in ten honest product tests — the vault uses a 10% minimum hit rate as the reference. That means a winner typically costs you several controlled failures first, and the operators who quit are usually the ones who expected the first or second test to work. CommonWealth Ops plans for the hit rate by capping the cost of each test.

Testing is a rate, not a coin flip

The single most damaging belief a new operator holds is that the right product, chosen carefully enough, will work on the first try. Product testing does not behave that way. It behaves like a rate: run enough honest tests and a certain fraction succeed, but you cannot know in advance which ones.

The vault uses a 10% minimum hit rate as its reference — roughly one scalable winner per ten controlled tests. That number reframes everything. A failed test is not a sign you chose badly; it is one of the nine that statistically precede the one that works. The operators who quit almost always quit because they treated a normal failure as a personal verdict.

What the rate actually costs

Here is the part that decides whether the math is survivable: the cost of a 10% hit rate depends entirely on the cost of a single test. If each test runs uncapped — left alive for weeks, hoping for a turn — ten tests is a ruinous number. If each test is bounded by a pre-set cap, ten tests is simply a planned budget with a known ceiling.

This is why the expensive failures are never the products themselves. They are the uncapped tests: the one creative someone could not bring themselves to kill, quietly eating the budget that was supposed to fund nine more attempts. The rate is fine. The lack of a cap is what bankrupts people.

Deciding a failure honestly

A test fails when it crosses the thresholds you set before launching it: a click-through rate below the kill floor, a cost-per-acquisition above the niche band, a return under breakeven. Crossing those is a decision, not an abandonment. Giving a clearly-failed test more time is exactly how one of your ten attempts consumes the capital meant for the rest.

How CommonWealth Ops fits

CommonWealth Ops is built around the hit rate rather than against it. It caps the daily spend of each test by your capital band, so a failure costs a bounded amount and the budget survives to fund the next attempt. It validates demand before a paid test where it can, removing some failures before they spend at all. The 10% figure is a reference prior, not a promise; your own results refine it. The system does not claim to make every product win — it makes sure the failures it takes to find a winner do not end the search.

The next step

If you have ever quit after two or three products did not work, the hit-rate math says you stopped mid-process, not at the end of one. Alvaro is the first operator running this on the EUR 49/month plus 20% of net profit model, EUR 0 in any month without profit. For the first real operator data when a slot opens, join the waitlist and see how it works for operators.