Guides

The cheapest experiments to test a startup idea first

Three small glass flasks in a row of increasing size, the smallest holding a little gold liquid

How to match a cheap experiment to your riskiest assumption, set a pass mark before you start, and act on the result instead of explaining it away.

Why start cheap

The first experiments on a new idea have one job: to find out quickly whether the assumptions holding up the plan are true. At that stage most of what you believe will change. Spending heavily before you know which beliefs survive means paying full price for answers you could have had for little.

Cheap does not mean careless. A good cheap experiment is small, specific and decisive. It costs little, gives an answer in days or weeks, and the answer actually changes what you do next.

Match the experiment to the assumption

Start from your list of load-bearing assumptions, not from a list of favourite tactics. For each one, ask: what is the smallest thing I could do that would show this is wrong? Some common pairings:

  • Is the problem real and frequent? Structured conversations with a defined group, asking about the last time it happened and what it cost them, not about whether they like your idea.
  • Will they switch from what they use today? A manual version of the service for a few customers, run by hand, at the price you intend to charge.
  • Will they pay this price? A pre-order or deposit at a real price. Interest at zero cost tells you little about willingness to pay.
  • Can the channel reach them at a sensible cost? A small, capped campaign in the channel you plan to rely on, measuring cost per qualified conversation.
  • Can you serve them at the cost you assumed? Do the work yourself for a handful of customers and time it.

Each of these tests one assumption. That is the point. An experiment that tests five assumptions at once usually cannot tell you which one failed.

Set the pass mark before you start

Before running anything, write two results down: the result that would let the idea continue, and the result that would end it, or at least end this version of it. Tie the second to the kill threshold of the assumption you are testing. If you would keep going whatever happened, the experiment is not worth running.

Take a made-up example. A founder plans weekly warehouse space for small online brands and believes many of them would move stock out of their current warehouse. A cheap test is to interview a defined group of brands that have left a warehouse provider in the last year and reconstruct why. The founder writes down, before the first call, how many of them would need to cite a reason the new service fixes for the assumption to survive.

Order matters

If you have several experiments, start with the one that is cheapest and most decisive: the one that could end the idea for the least money and time. There is no point paying for a channel test if conversations would show the problem is rare. Each result also sharpens the next experiment, so running them in order is cheaper than running them at once.

What to do with the result

Read the result against the marks you wrote, not against your hopes. If it passes, move to the next assumption. If it fails, act on the decision you made in advance. If it lands in between, the experiment was probably too small; run a slightly larger version rather than reinterpreting the first.

How Startup Intelligence helps

A Startup Intelligence report lists three experiments aimed at the assumptions that carry your plan, cheapest and most decisive first. Each one describes the experiment, an estimated cost and number of days, the result that would be decisive and the result that would end the idea. The costs and durations are the engine's estimates, not quotes, so check them against your own situation.

Takeaway

Aim each experiment at one assumption that carries the plan, decide the pass mark and the kill result first, and start with the test that could end the idea for the least. To set those kill results, read kill thresholds, and for conversations that tell you more than compliments, read how to get honest feedback on a startup idea. For founders, the founders' page shows how the report fits this work.

Reports support planning. They are not investment advice and not a guarantee of results.

Key takeaways

  • Aim each experiment at one load-bearing assumption.
  • Write the pass mark and the kill result before you start.
  • Prefer the experiment that answers fastest for the least money.

Questions

What makes an experiment cheap?

Low cost and short time to an answer, measured against how much the answer changes your decision. A cheap experiment that cannot change your mind is not cheap, it is wasted.

Should I build an MVP as my first experiment?

Usually not. An MVP tests many assumptions at once and takes weeks. Most riskiest assumptions can be tested first by conversations, a manual pilot or a priced pre-order.

Startup Intelligence: what it does

Related articles

See Startup Intelligence for yourself

Request access