Founder OS · Stage 1 gate
A verdict the founder did not choose.
The first gate in Founder OS, and the only one whose answer can be to stop. It scores the evidence gathered across stage one, then tests conditions that override the score entirely.
Kill / Pivot / Go
- Asks
- Is this problem worth building a company on?
- Decides
- It scores the seven earlier steps out of 35, then tests eight kill conditions. Any one kill condition decides the result, whatever the total. A founder who has spoken to fewer than eight potential customers goes back to discovery, however high the score.
- Result
- Go, Pivot or Kill, with the deciding factor named.
The failure it is built to catch.
Founders do not usually lack conviction. They lack a moment at which conviction is tested against what they can actually show, by something that has no stake in the answer and cannot be talked round.
Left to a conversation, that moment never arrives. Advisors soften, investors decline without saying why, and the founder keeps going on the strength of the last encouraging meeting. Two years can pass this way.
This check produces a verdict the founder did not choose. It is the firm’s third rule built into software: we report what the evidence says, including when it is unwelcome — and a hard finding in week two costs a founder far less than a polite one in month twelve.
Seven steps, scored out of 35.
These are the steps of stage one. The check does not gather evidence itself — it reads what the seven steps before it produced, which is why it cannot be answered directly.
- Idea foundations
- Problem severity
- Technology readiness
- Market sizing and competitive position
- Customer discovery
- Regulatory, IP and risk mapping
- A first go-to-market hypothesis with unit economics
Three verdicts, and the condition that overrides them.
- The override
- Eight kill conditions are tested after the score. Any one of them decides the result on its own, whatever the total. A high score does not survive a condition it has failed.
- Go
- The evidence supports building a company on this problem, and no kill condition fired. The deciding factor is named, so the founder knows what the verdict rests on.
- Pivot
- Something real is here, but not the thing currently being built. The named factor says which part survives and which does not.
- Kill
- The evidence does not support continuing on this problem. Delivered with the deciding factor named, because a verdict without a reason is only an opinion.
Common questions.
What are the eight kill conditions?
One is published, as an illustration of how they work: a founder who has spoken to fewer than eight potential customers goes back to discovery, however high the score. The full set is part of the method itself and is applied in the software during a Pilot Cohort.
Can a high score still be killed?
Yes, and that is the design. The conditions are tested after the score and any one of them decides the result on its own. Averaging would let a strong showing elsewhere hide the thing that actually stops the company.
Is Kill the usual answer?
No. Pivot is the most useful result the gate produces, because it says something real is here and names which part of the current plan does not survive. Kill exists so that the gate can mean something.
Can we disagree with the verdict?
You can improve the evidence and run it again, which is the intended response. You cannot argue the score up — the rules are written in advance and the deciding factor is named, so what would change the answer is visible rather than negotiable.
Founder OS runs this during a Pilot Cohort.
Programmes use it with their cohort, and Dineshwara reviews every cohort's results. If you want a read on your own company first, the founder readiness check is twelve questions and open to anyone.