Partners Running an agency? Partner with us
The Graylemon Journal Build logs, teardowns and method, by email. Subscribe All resources
Follow the studio LinkedIn Instagram
Partner with usBook a call (opens in a new tab)
Framework · Gate

Kill Criteria

What result would make us stop, decided before we start? Write the stop conditions down before anything is built, while nobody is invested yet. When the result comes in, the decision has already been made; you only have to read it.

  • Stage: Define
  • Discipline: Strategy
  • Graylemon original
The framework

Decide the line, then run the test.

Kill Criteria in four steps: write them down, publish them, run the test, read the result.
Fig. 02: Kill Criteria, as a model · point at a partLoops while in view
Each part

What each step needs

Write them down

Each condition names something you could observe: a behaviour, a payment, a return visit. "If it doesn't feel right" isn't a criterion.

Evidence to move on

Every condition could be checked by someone who wasn't in the room. Where one needs a number, write down where the number comes from; if it's a judgement, say so and give the reasoning.

Publish them

Put them somewhere the team can't edit quietly: the proposal, the kickoff notes, or in public.

Evidence to move on

The criteria are dated, and the people who'll make the call have agreed to them.

Run the test

Test with the people the product is for, not with friends or colleagues who want it to work.

Evidence to move on

The result comes from the users the criteria describe.

Read the result

Compare the result with each condition as written. If it clears them, the next phase starts. If it doesn't, the venture stops, and you keep what you learned.

Evidence to move on

The decision quotes the criteria, not a new argument.

Worked example

apprn, and the rule we hold ourselves to.

Own venture

apprn, our agentic salon management venture, is in a live test with salons. Its go or no-go decision is made against kill criteria set before the test began.

We'll publish those criteria before we publish the result, so the call can't be rewritten afterwards. That's the whole point of the framework: a result can't argue with a line drawn before it existed.

apprn

Illustrative example

What a criterion reads like, from the clinic booking assistant on our homepage: "It goes to market only if the beta clinics keep using it." It names who, and what they have to do. Anyone can check it.

Common misreads

Where it goes wrong

  1. Misread

    Writing them after the first results

    Why Criteria written after the evidence bend to fit it.

  2. Misread

    Using feelings as criteria

    Why A criterion is something you can observe, not something you sense.

  3. Misread

    Inventing a threshold to look rigorous

    Why If a number can't be sourced, call it a judgement and write down the reasoning.

  4. Misread

    Treating a stop as a failure

    Why A diagnosis that stops a bad build is worth more than a build that ships.

Where this fits

In every AI Venture Build, kill criteria are set before anything is built.

AI Venture Build

Download: the kill criteria worksheet, a free Word file.

In the Journal: Is it worth building? · How to evaluate a venture studio · An AI venture beside your family business

Published 24 September 2026. Graylemon original, from our engagement method.

Search Graylemon

↑↓ Move↵ OpenEsc Close