Guides

Kill thresholds: how to decide in advance when to stop

A strip of paper like a path, crossed near its end by a taut gold thread, with a small grey pebble stopped just before it

A kill threshold is the result that would make you stop. How to set one before you test, read results against it, and tell stopping apart from pivoting.

The problem with deciding later

Most founders never decide what result would make them stop. They run an experiment, get a disappointing number, and then decide what it means. At that point the decision is made by the person who most wants the idea to work. The number is too small, so the sample must have been wrong; the timing was bad; next month will be different. Months pass.

A kill threshold fixes this by moving the decision to before the data arrives, when you can still think clearly.

Step 1: set the bar the idea has to clear

Start with the outcome that would make the idea worth your time. State it in four parts:

  • a measure, such as annual recurring revenue or paying customers;
  • an amount;
  • a month by which it has to be reached;
  • a sentence on why that bar matters, for example that it is the point at which the business pays two founders.

The sentence matters more than it looks. It turns an arbitrary target into a commitment you understand, and it is the thing you will come back to when you are tempted to move the line.

Step 2: work out a stop value for each assumption

Now go through your load-bearing assumptions one at a time. For each, ask: how bad would this value have to be before the plan no longer clears the bar? That value is the assumption's kill threshold.

Take a made-up example. A weekly warehouse rental plan needs a certain share of small online brands to have a seasonal peak. If the share falls below some level, there are too few customers in the city to reach the bar by the chosen month, however well everything else goes. That level is the kill line for that assumption. Every load-bearing assumption has one.

Step 3: ask how likely it is you are already past it

A kill line on its own is half the picture. The other half is how likely it is that the truth already sits on the wrong side of it, given what you know. As a rule of thumb, an assumption whose kill line sits well inside the range you think plausible deserves attention before one whose kill line sits at the far edge. That is a good way to decide which line to test first.

Step 4: decide what you will do when a result crosses the line

Write it down now. If the first experiment lands past the kill line, will you stop? Change the customer? Change the price? The point is not to forbid pivots. It is to make sure a pivot is a decision about a new plan, with its own threshold, and not a way of avoiding the result of the old one.

Reading results against the line

When a result comes in, compare it with the line you wrote, not with how you feel. If it is clearly on the safe side, move on to the next assumption. If it is clearly past the line, act on what you decided. If it is close, that usually means the experiment was too small to settle it, which is a reason for a slightly bigger test, not for a new story.

How Startup Intelligence shows it

When you start a Startup Intelligence run, you state the bar in the same spirit: a measure, an amount in rupees, the month by which it has to be reached, and a sentence on what counts, exactly, which is printed in the report word for word so nobody can read the metric two ways. Keep your sentence on why the bar matters in your own notes. The engine simulates the outcome across thousands of possible futures, shows the spread, and tells you how many of those futures clear your bar. Then, for each load-bearing assumption, it finds the value at which the plan stops clearing it and shows how likely the truth is to be on the wrong side already.

Those figures are only as good as the assumptions behind them, and today the base figures come from the AI model's own knowledge, labelled as the weakest kind of evidence. The share of futures that clears your bar is a reading of your assumptions against the bar you chose, not a rating of the idea, not a chance that the business succeeds and not advice.

Takeaway

Decide where you would stop before you look. Turn your goal into a stop value for each assumption that carries the plan, and write down what you will do if a result crosses it. Then run the cheapest experiment that could take you past a line. To see how a report lays this out, read about outcome ranges and kill thresholds.

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

Key takeaways

  • Set the bar the idea must clear before you collect any data.
  • Translate it into a stop value for each load-bearing assumption.
  • Write down what you will do when a result lands past the line.

Questions

What is a kill threshold?

A value, decided before you test, at which an assumption is wrong enough that the plan no longer reaches the bar you set. If a result lands past it, you stop or change the plan.

Is stopping the same as failing?

No. Stopping early on a clear result saves the time and money a weak plan would have used, and leaves you free to try a better version.

Startup Intelligence: what it does

Related articles

See Startup Intelligence for yourself

Request access