The kill-switch framework

Every mechanism this course has covered points at a specific, falsifiable signal to watch for. This lesson collects them into a framework for deciding when a SaaS business isn't working — deliberately built from the math and mechanisms already established in earlier modules, so each gate here is a conclusion, not a new assertion.

#Gate 1: distribution — do you have a repeatable way to reach a paying customer at all

Before unit economics can even be evaluated, there has to be a customer to measure them against. The signal to watch, per the distribution problem: after a genuine, sustained attempt at a low-cost channel (founder-led content, direct outreach, community presence — the lower-risk channels that lesson argued for testing first), is there any evidence of organic pull — inbound interest, referrals, or unprompted usage growth — or is every single customer requiring the founder's direct, individual push to acquire? The second pattern, sustained over months rather than the first few weeks, is the clearest available signal that the product-market fit this business needs hasn't been found yet, independent of how good the product itself is.

#Gate 2: unit economics — does the math from module 1 actually clear

Once real paying customers exist, the unit economics math gives a direct, falsifiable test: is LTV meaningfully above CAC (not just barely above it — the reasoning behind the 3:1-ish heuristic, treated with the caveats given in that lesson, is that a thin margin above break-even doesn't fund a company's operations, product work, or a bad quarter), and is payback period fast enough that the business isn't structurally dependent on external capital just to keep acquiring customers at all? A business that's growing revenue while this math doesn't clear isn't a business with a scaling problem — it's a business losing money faster as it grows, which growth makes worse, not better.

#Gate 3: retention — is the recurring-revenue premium actually real

The recurring revenue mechanism established that recurring revenue is only worth a premium because it's a credible claim on future revenue. Churn and retention mechanics gave the diagnostic: is voluntary churn (the value-price gap, not payment failures) stable or improving as the product matures, or is it worsening even as the sales and marketing pitch stays the same? Worsening voluntary churn on an unchanged product is a direct signal that the value-price gap is widening — competitors improving, the market's expectations rising, or the product's differentiation eroding — and it's a signal to look at deliberately rather than let get diluted inside an aggregate "total churn" number.

#Gate 4: the capital runway question, answered honestly

Per bootstrapping vs fundraising, this gate differs by which path was chosen. A bootstrapped founder's honest question is whether the business, at its current trajectory, reaches sustainability (revenue covering the founder's actual required income, not just business expenses) before personal financial runway or motivation genuinely runs out — a real, calendar-bound constraint worth writing down explicitly rather than letting drift. A funded founder's honest question is closer to whether the metrics above are trending toward what the next round (or a sustainable path to profitability) actually requires, since venture-backed companies that stall between the growth trajectory investors expect and profitability face a specific, well-understood failure mode: too far along to be a clean early write-off, not growing fast enough to raise again, and not profitable enough to self-sustain.

#What "kill" actually means, and what it doesn't

None of these four gates failing means "shut down instantly, no further thought" — each failure mode has a genuine diagnostic response before it means stop: distribution failure often means the channel was wrong, not the product; unit-economics failure sometimes means pricing was wrong, not the whole business (see pricing models before assuming CAC or LTV are fixed facts about the business rather than partly a pricing decision); retention failure means there's a specific value-price gap to close, which is sometimes fixable with real product or onboarding work. The actual kill signal is the same gate failing after a genuine, deliberate attempt to fix the specific mechanism behind it — not a bad month, and not a founder's fatigue alone (which is real and matters, but is a different decision from "this business doesn't work," and deserves to be made explicitly as that different decision rather than dressed up as a data-driven one).

The honest version of "when to quit" a SaaS business isn't a vibe — it's these four falsifiable gates, checked against the actual mechanisms, not against whichever survival statistic you saw most recently. Survival rates: what the data actually shows, next, is exactly why that last part matters: most of the numbers circulating on this specific question don't hold up to the check this course has applied to everything else in it.