Kill Criteria Template for Capital-Intensive Startups

Hardware and capital-intensive startups rarely fail because of a single catastrophic bet — they fail because founders refuse, or forget, to define in advance what evidence would mean stopping. Kill criteria are specific, pre-committed thresholds — on demand, cost curve, and capital runway — set before you're emotionally invested in a specific outcome, so that a genuine stop-or-pivot decision is made against objective evidence rather than in-the-moment optimism.

The Kill Criteria Template

1. Demand threshold — the minimum letter-of-intent or offtake commitment volume, by a specific date, below which you stop pursuing the current market
2. Cost curve threshold — the maximum acceptable gap between your techno-economic analysis's projected cost and actual measured cost at each scale-up stage
3. Capital threshold — the minimum runway remaining at which you must have secured your next scale-up stage's funding, or begin winding down
4. Timeline threshold — the maximum acceptable delay, relative to your original plan, before reassessing the entire technology or market approach

Quick Answer: Kill criteria are specific, numeric thresholds set in advance — before you're emotionally invested in a particular outcome — covering demand evidence, cost curve performance, capital runway, and timeline slippage. When actual results breach a pre-committed threshold, the criteria trigger a genuine stop-or-pivot review rather than allowing momentum and sunk cost to carry a failing bet forward indefinitely.

Field-by-Field Explanation

Demand threshold specifies a minimum volume of letters of intent or offtake commitments, by a specific date, following the evidence ladder covered in LOIs and offtake agreements for hardware validation — falling short by this date without a credible, specific reason (not simply "the market is taking longer than expected") should trigger a genuine reassessment of whether real demand exists. Cost curve threshold specifies the maximum acceptable gap between your techno-economic analysis's projected cost and actual measured cost at each stage — a persistent, growing gap rather than a temporary one signals the underlying economics may not close as originally modeled. Capital threshold specifies the minimum runway remaining at which you must have secured funding for your next scale-up stage, preventing the common trap of running out of capital mid-stage with no viable path forward. Timeline threshold specifies acceptable delay before triggering a broader reassessment, since persistent, compounding delay often signals a deeper technical or market problem rather than simple bad luck.

Filled Example: A Climate Hardware Startup at Pilot Stage

A startup piloting a novel materials process sets its kill criteria before pilot operation begins: demand threshold — at least three letters of intent from independent, qualified counterparties within six months of pilot start, or reassess the target market; cost curve threshold — pilot-stage actual cost per unit within 30 percent of the techno-economic analysis's projected figure, or reassess the scale-up cost model; capital threshold — secured commitment for demonstration-stage funding by the time eighteen months of pilot-stage runway remains; timeline threshold — reassess the overall approach if pilot operation slips more than four months behind the original schedule without a specific, addressable technical cause. Six months into the pilot, the startup has two qualified LOIs rather than three — falling short of the demand threshold — triggering a deliberate review rather than simply continuing forward on the assumption a third LOI will eventually materialize.

Adaptation Notes by Capital Intensity

Adapt the specific numeric thresholds to your technology's actual capital intensity and typical scale-up timeline — a technology requiring years and tens of millions to reach demonstration scale needs correspondingly patient thresholds relative to a lighter-capital hardware product reaching market in a shorter timeframe. The structural discipline (specific, pre-committed, evidence-based thresholds set before emotional investment) transfers across capital intensity levels, but the specific numbers should reflect your particular technology category's realistic timelines, not a generic, one-size-fits-all standard borrowed from a different kind of hardware business.

A Closer Look: Why Kill Criteria Need a Named Enforcer, Not Just a Document

It's worth being direct about a specific, well-documented failure mode with kill criteria: founders write them thoughtfully and specifically, genuinely intending to honor them, and then quietly fail to enforce them when the actual moment of a breached threshold arrives — reasoning in the moment that "this time is different" or that stopping now would waste the progress already made, exactly the sunk-cost reasoning kill criteria were designed to prevent in the first place. A kill criteria document that exists but has no real enforcement mechanism behind it provides considerably less protection than founders often assume when writing it — the document itself feels like discipline at the moment of writing, but discipline that lives only on paper, without a genuine external check, tends to erode precisely at the moment it matters most.

The practical countermeasure is to name a specific enforcer — a board member, an advisor, or a cofounder with genuine standing to hold the founder accountable — explicitly responsible for reviewing actual results against the pre-committed thresholds at each specified checkpoint, independent of the founder's own in-the-moment reasoning about why this particular breach is different. This person's role isn't necessarily to force an automatic stop the moment any threshold is breached — a breached threshold should trigger a genuine, deliberate review, not necessarily an automatic shutdown — but to ensure that review actually happens with real rigor rather than being quietly waved through by a founder whose emotional investment in continuing is, understandably, considerably stronger than their emotional investment in the abstract discipline they committed to months or years earlier. Founders who build this external enforcement mechanism into their kill criteria from the start report considerably more genuine adherence than those who rely solely on their own future discipline to honor thresholds set in a calmer, less emotionally invested moment.

It's worth choosing this enforcer deliberately rather than defaulting to whoever happens to be most available or most personally close to the founder. The most effective enforcers tend to be people with enough independent standing to actually deliver an uncomfortable verdict — a lead investor with real board authority, or an advisor whose relationship with the founder isn't so personally entangled that delivering hard news feels genuinely costly to the relationship itself. A well-chosen enforcer, briefed clearly on the specific thresholds and the founder's own explicit request to be held to them, transforms kill criteria from a private aspiration into a real, socially reinforced commitment considerably harder to quietly abandon once the pressure of an actual breach arrives — the act of asking someone else to hold you to a standard is itself part of what makes the standard genuinely binding rather than merely aspirational language sitting quietly in a document nobody ever actually revisits again later on.

Key Takeaways

• Kill criteria are specific, pre-committed thresholds set before emotional investment in a particular outcome makes objective evaluation harder.
• The four core thresholds: demand, cost curve, capital runway, and timeline — each grounded in objective, measurable evidence rather than subjective impression.
• Adapt specific numeric thresholds to your technology's actual capital intensity, while preserving the underlying structural discipline.
• A breached threshold should trigger a genuine, deliberate review, not necessarily an automatic shutdown — but the review needs to actually happen with real rigor.
• Name a specific external enforcer — a board member, advisor, or cofounder — responsible for holding the founder accountable to the criteria, since self-enforcement alone is a documented, common failure point.

Frequently Asked Questions

Should kill criteria be shared with investors, or kept internal?

Sharing kill criteria with investors, particularly board members, generally strengthens rather than weakens their practical value, since investors often become the natural external enforcer this article's closer-look section describes, and a founder transparent about their own pre-committed thresholds tends to build more durable investor trust than one who prefers to keep these decisions entirely discretionary.

What happens if a threshold is breached but the founder believes strongly the situation is genuinely different from what the criteria anticipated?

This is exactly the situation the named external enforcer exists to evaluate honestly — a genuine, well-reasoned case for why a specific breach doesn't warrant the same response as a generic one is worth hearing out, but it should be evaluated by someone other than the founder alone, given the well-documented tendency for founders to find compelling reasons a specific breach doesn't really count once they're actually facing the decision in the moment.

How does this relate to the pivot-or-persevere framework covered in The Lean Startup?

This kill criteria template operationalizes that broader pivot-or-persevere concept into specific, measurable, pre-committed thresholds rather than leaving the decision as a general, subjective judgment call made in the moment — the underlying philosophy is consistent with that broader lean startup framework, but this article's specific contribution is the discipline of setting numeric thresholds and a named enforcer in advance, addressing the well-documented gap between having a general philosophy about pivoting and actually acting on it when a real, emotionally difficult moment arrives.