Most GTM plans define launch conditions in detail. Almost none define stop conditions. That asymmetry is where growth-stage capital gets destroyed.
A kill criterion is a predefined threshold that triggers a mandatory decision when breached. Not a conversation — a decision. Agreed before launch, when everyone was thinking as a fiduciary.
Most growth-stage B2B teams don't have them. The reason is behavioural, not conceptual.
Setting stop conditions before launch feels like a confidence deficit. It isn't. It's the most credible signal you can send a board that you intend to manage capital — not just deploy it.
Without kill criteria, every difficult GTM call becomes discretionary. Under pressure, discretionary defaults to "give it more time."
At ₹40–60 lakhs per month of GTM spend, more time is capital destroyed before the decision that was always necessary eventually gets made anyway.
Why GTM Plans Have No Enforcement Layer
GTM frameworks are detailed on inputs — messaging, channels, budget. Almost entirely silent on output conditions that would trigger a change of course.
Once live, performance is reviewed against projections. The review produces a conversation, not a decision.
Someone notes CAC is up 15%. Someone suggests two more weeks. Two weeks becomes four. Four becomes a quarter. The quarter costs ₹35 lakhs.
The most expensive GTM failure mode isn't a bold bet that fails quickly.
It's a failing motion that runs 3–6 months past the point the data had already declared it — because no one defined what failure looked like in advance.
Three Categories of Kill Decision
Kill criteria produce one of three mandatory decisions. Each must be defined before capital is committed — not negotiated after the signal arrives.
| Decision | Signal Indicates | Capital Response | Time Horizon |
|---|---|---|---|
| Pause | Metric at warning threshold; root cause undiagnosed | Spend frozen; no incremental budget released | Diagnosis within 10 business days |
| Restructure | Root cause identified; approach requires formal change | Investment continues under revised strategy | Board-visible pivot within 2 weeks |
| Kill | GTM motion has failed its economic test | Capital recovered; team redeployed; learning documented | Decision within 48 hours of confirmation |
Critical design principle: leading indicators, not lagging ones.
Revenue miss shows up 6–8 weeks after the damage is done. Pipeline coverage ratio is calculable by week two of any quarter — and predictive of revenue performance 4–6 weeks in advance.
The Five Thresholds
Every growth-stage GTM plan needs predefined thresholds on these five metrics. Each has a calculation, a benchmark, and a mandatory action on breach.
-
1
CAC CeilingMaximum acceptable CAC — derived from LTV and your target LTV:CAC ratio. Not from spend history.At a 3× LTV:CAC target, divide LTV by 3. CAC 25% above ceiling for three consecutive weeks is a structural failure, not variance.
-
2
Pipeline Coverage FloorMinimum qualified pipeline-to-target ratio to maintain spend. At 3× coverage and 30% close rate, you have ~50% probability of hitting revenue target.Below 2.5× — statistically likely to miss. Below 2× — mathematically near-certain to miss.
-
3
CAC Payback CeilingMaximum months to recover acquisition cost. Formula: CAC ÷ (Monthly MRR × Gross Margin %).Series A: 12 months is strong. 18 is acceptable. 24 requires board escalation. Beyond 24, you're consuming future capital faster than revenue can sustain.
-
4
Churn Rate TriggerThe threshold at which the PMF assumption underlying your GTM plan must be formally reviewed.A 1.5× spike in monthly churn compresses LTV and extends payback simultaneously. Within three cohorts, viable unit economics can invert.
-
5
MQL-to-SQL Conversion FloorBelow this threshold, all top-of-funnel spend stops. A conversion rate problem is a targeting or positioning problem — not a spend problem.Increasing budget into a broken funnel multiplies volume on an already broken rate. Most growth-stage capital destruction runs through exactly this mechanism.
| Metric | Strong | Acceptable | Watch | Kill Trigger |
|---|---|---|---|---|
| LTV:CAC Ratio | > 5× | 3–5× | 2–3× | < 2× |
| CAC Payback | < 12 mo | 12–18 mo | 18–24 mo | > 24 mo |
| Pipeline Coverage | 3.5–5× | 3–3.5× | 2.5–3× | < 2× |
| Net Revenue Retention | > 120% | 110–120% | 100–110% | < 100% |
| Gross Margin | > 75% | 70–75% | 60–70% | < 60% |
| MQL→SQL Conversion | > 25% | 15–25% | 10–15% | < 10% |
| Monthly Net Churn | < 1% | 1–2% | 2–3% | > 3% |
How to Implement Kill Criteria Before Launch
Implementation sequence matters as much as the thresholds themselves. Kill criteria set during execution are retroactive justifications — not governance.
-
1Set all thresholds before any capital is committedAll five in one planning session. Once the campaign is live, sunk cost bias contaminates every threshold conversation.
-
2Make thresholds visible to the board before capital releaseInternal thresholds known only to the CMO don't constrain decisions under pressure. Board-visible thresholds do — acting against them requires a board explanation.
-
3Open every weekly review with the five metrics — not a narrativeGreen: continue. Amber: one further week with diagnosis underway. Red: execute the predefined action. No 45-minute attribution debates.
-
4Document every trigger event as institutional learningRecord the metric, root cause, change made, and outcome. Over three to four GTM cycles this becomes a calibrated model of your actual economics.
Milestone-Gated Capital Release
Total GTM budget approved in phases. Each phase's funding is conditional on prior-phase threshold performance.
Phase 2 does not release if Phase 1 gates are breached. The decision is automatic — built into the capital plan, not left to judgment under pressure.
| Phase | Budget | Duration | Gate Conditions (all required) | Kill Trigger |
|---|---|---|---|---|
| 1 — Foundation | ₹20–30L | 6 weeks | Pipeline > 2× · CAC within 120% of ceiling | CAC > 2× ceiling for 4 weeks |
| 2 — Launch | ₹50–70L | 8 weeks | Pipeline > 3× · MQL→SQL within 20% of baseline | Pipeline < 2× for 2 consecutive weeks |
| 3 — Acceleration | ₹1–2Cr | 12 weeks | LTV:CAC > 3× · Payback < 18 mo · NRR > 100% | Monthly churn > 1.5× baseline |
| 4 — Scale | Uncapped | Ongoing | NRR > 110% · Gross margin > 70% · Pipeline > 3× | Two thresholds breached simultaneously |
₹25L allocated to Phase 1. Pre-agreed Phase 2 gates: CAC within 120% of ceiling (₹2.8L), pipeline above 3×, MQL→SQL within 20% of baseline.
End of Phase 1: CAC at ₹4.1L — 46% above ceiling. Pipeline at 2.6×. Two of three gates breached. Phase 2 (₹60L) not released.
Two-week audit finds the issue: ICP targeting the wrong decision-maker level. Parameters revised. CAC drops to ₹3.2L, pipeline reaches 3.1×. Phase 2 releases week eleven.
Governance Roles — Who Owns What
Kill criteria only function when the person who sets thresholds is different from the person who executes against them.
When the same team that built the GTM plan also decides whether its own thresholds are breached, confirmation bias defeats the mechanism entirely.
| Role | Responsibility | Cadence | Output |
|---|---|---|---|
| Founder / CEO | Set threshold levels; sign off on kill decisions | Pre-launch; at each phase gate | Signed governance document |
| CFO / Finance | Independent metric verification; capital release authority | Weekly threshold review | Go / No-Go on phase capital release |
| CMO / GTM Lead | Weekly threshold dashboard; root cause on amber/red | Weekly; immediately on breach | Diagnosis memo within 48 hours |
| Board / Investors | Pre-approve threshold levels; notified on kill actions | At plan approval; on any kill | Threshold approval on record |
"Teams with kill criteria don't fail less often. They fail faster, cheaper, and with better data."
Insigra Research — GTM Capital Governance, 2026Kill criteria frameworks. Milestone-gated capital release. CAC ceiling calculator. Weekly threshold dashboard. Board GTM deck. Excel + PPT + PDF.
