Guides

How to test a startup idea before you build it

A tower of pale oak blocks with one gold block pushed out of line, carrying the weight of the blocks above it

Start with assumptions, not features: find the few your idea rests on, grade the evidence, set a stop point and run the cheapest experiment first.

Start with claims, not features

Picture a founder with an idea for weekly warehouse space rented by the pallet, aimed at small online brands. The first instinct is to design the booking screen. That feels like progress, and it is the part of the plan the founder controls. But the booking screen is not what decides whether the business works. Whether small brands really have seasonal peaks, whether they would move stock out of the warehouse they use today, whether the price covers the cost of the space: those decide it, and none of them is tested by building a screen.

So the first step is to rewrite the idea as claims about the world. A useful frame has nine parts:

  1. The customer, defined narrowly enough that you could count them and reach them.
  2. Their job and pain: what they are trying to get done and what it costs them today.
  3. What they do now, including spreadsheets, a cousin who helps, or nothing at all.
  4. The mechanism: why your product would cause a better outcome. Not the feature, the cause.
  5. The value created, in the customer's own units.
  6. The value captured: the price, and what share of the value it takes.
  7. The path to the customer: the channel that reaches them again and again, and its cost.
  8. The cost to serve one more customer, on top of the fixed base.
  9. What persists: what builds up that makes the business harder to copy next year.

If you cannot write two of these, especially the customer or the mechanism, that is your first finding. It is cheaper to learn it on paper than after a launch.

Find the assumptions that carry the weight

Every claim rests on assumptions, and an honest list will be long. They are not equally important. A few of them decide the outcome; the rest barely move it. The skill is to find those few.

A simple way is to ask, for each assumption: if this were badly wrong, would the plan still clear the bar I care about? If the answer is no, the assumption is load-bearing. Then ask a second question: what do I actually know about it? An assumption that carries the plan and rests on nothing yet is where your attention belongs. We go deeper on this in load-bearing assumptions.

Grade the evidence honestly

For each load-bearing assumption, write down where your number comes from. Did you measure it? Did you borrow it from a comparable business? Did you work it out from other figures? Or is it your own belief? These are very different kinds of evidence, and a plan built mostly on beliefs should be held more loosely than one built on measurements. A belief also deserves a wider range: if you are guessing a conversion rate, say "somewhere between one and six percent", not "three percent".

Decide where you would stop

Before you test anything, write down the outcome the idea has to reach to be worth your time: a measure, an amount and a date, and a sentence on why that bar matters to you. Then, for each load-bearing assumption, work out the value at which the plan would no longer clear it. That is your stop point. Writing it down first is what keeps you honest when a result disappoints. Our guide to kill thresholds covers how.

Run the cheapest experiment first

Now choose experiments. The best first experiment is the cheapest one that could prove your riskiest assumption wrong. Often that is a handful of structured conversations, a small paid pilot run by hand, or a pre-order page with a real price. Each experiment should say in advance what result would end the idea and what result would let it continue. See the cheapest experiments to run first for patterns.

Where a report fits

Startup Intelligence does this work in one pass. You describe the idea in plain words and set your bar. The engine breaks the idea into the nine claim links and refuses if too few are stated, naming the sentences that are missing. It then grades the key assumptions, simulates the range of outcomes against your threshold, and gives you stop points and the three cheapest experiments.

Two limits are worth knowing. Today the base figures come from the AI model's own knowledge, and the report files them on the lowest rungs of its evidence ladder, so read them as assumptions to test, not as research. And the report gives no single score: it shows ranges and conditions, because nobody can rate an idea. Our About page lists the people who build it: Divya Prakash Jha (CEO), Vaibhav Jain (COO) and Zeeshan Khan (CMO).

The short version

Write the idea as claims. Find the few that carry the weight. Be honest about what you know. Decide where you would stop. Then run the smallest experiment that could tell you that you are wrong. If you would like a report that does the first four steps with you, call the team to ask for access; see what a report contains first.

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

Key takeaways

  • Write the idea as claims about the world, not as a list of features.
  • Find the few assumptions the outcome depends on and grade the evidence for each.
  • Decide in advance the result that would make you stop.
  • Run the cheapest experiment that could prove the riskiest assumption wrong.

Questions

What is the first thing to test in a startup idea?

The assumption that the outcome depends on most and that has the least evidence behind it. Usually that is about the customer or the mechanism, not about the product's features.

Do I need a product to test an idea?

No. Most load-bearing assumptions can be tested with conversations, a small paid trial or a manual version of the service before anything is built.

Startup Intelligence: what it does

Related articles

See Startup Intelligence for yourself

Request access