Staged validation: stop/go gates

Staged validation is testing a product through a sequence of gates, each answering one specific question, with an explicit stop or go decision made before spending on the next gate. Instead of one large launch that either works or does not, the product earns its way through cheaper, faster checks before it earns a shot at the expensive one.

Why order the gates by cost

Each gate should answer a question that is cheaper to test than the one after it. Checking whether anyone will click an ad for the product is cheaper than checking whether they will pay for it, which is cheaper than checking whether the business holds together once real ad spend scales. Running the expensive question first wastes money on products that would have failed a cheap question anyway. Ordering by cost means the most likely failure gets caught earliest, before the more expensive gates are ever funded.

The gate sequence

A practical sequence runs roughly:

1. Interest gate. Does anyone stop for the offer? Measured with click-through rate or hook rate on cheap creative and traffic.
2. Intent gate. Will someone start a purchase? Measured with add-to-cart or checkout-initiation rate.
3. Purchase gate. Will someone actually pay? Measured with a small, real sample of completed orders, not survey intent.
4. Retention or repeat gate, where relevant. Does the buyer come back or is this a one-time novelty purchase?
5. Unit economics at volume. This is the gate that actually decides whether to scale. It asks whether contribution margin still covers acquisition cost once spend rises and CPA drifts, not whether the first ten sales were profitable.

The final gate is the one that gates scale. A product can clear every earlier gate and still fail here, because early sales often come from the cheapest, most efficient slice of the audience, and cost per acquisition typically rises as a campaign spends into a broader one. See contribution margin for the number this gate is checked against, and kill criteria and exit velocity for stop rules once a test is running.

Sizing a conclusive test

A gate needs enough spend to produce a readable result, not just a countable one. A rough minimum viable test budget is:

target CPA x conversions needed for a readable result

If a target CPA is $40 and the gate needs 20 conversions before drawing a conclusion, the minimum conclusive test costs about $800. Running $200 into that same gate and reading the result is not a smaller version of the same test; it is a different, less reliable test, because a handful of conversions can swing entirely on a few unusually good or bad days. See statistical significance in ad testing for why the sample size, not the calendar time, determines whether a result means anything.

What to do when a gate fails

A failed gate is a stop decision, not a reason to add budget and hope the next batch of spend performs better. First isolate which variable failed: was it the offer, the creative, the price, or the audience. Changing more than one at a time on the retest destroys the ability to tell which change fixed it. If the same gate fails twice on genuinely different attempts, the product has an answer, and the honest move is to stop rather than keep funding a question that has already been answered.

Retreating a gate is also valid: a product that fails the purchase gate can be sent back to the intent gate with a changed offer or price point, rather than declared dead outright, provided the retest is a real change and not a repeat.

When this does not apply

Staged validation assumes each gate can be tested cheaply and independently. For products with long consideration cycles or infrequent purchases, a gate may need weeks rather than days to produce a readable signal, and compressing the timeline to match a faster product’s gates will produce false negatives.

For the full framework and worked examples, see validating a product before you scale.