The math of keeping a product on life support

Published September 11, 2026 · 6 min read

Most advice about struggling products offers two endings: double down or shut it down. There is a quiet third option operators of small internet businesses reach for constantly and almost never discuss — running something on deliberate life support, indefinitely, for less effort than either alternative.

The false choice operators are handed

Every piece of startup advice about a plateaued product assumes urgency: pivot hard or walk away clean. That framing makes sense for a venture-funded company burning a monthly number that forces a decision. It makes much less sense for a small internet business that costs almost nothing to keep running and already covers its own hosting bill. For that kind of product, the honest options are not two — they are three, and the third one is the one nobody puts in a deck.

Life support is the decision to keep a product exactly as it is: no growth investment, no active marketing, just enough maintenance to keep it functioning and its existing customers unharmed. It is not romantic. It will never make a case study. But for an operator running several properties at once, it is frequently the correct answer, and dismissing it because it lacks drama is a mistake dressed up as ambition.

The three real questions

Deciding whether a product qualifies for life support comes down to three questions, in order. First: does it cover its direct costs — hosting, any paid tools, and the minimum support time it demands — without subsidy from elsewhere in the portfolio? Second: does keeping it running create any liability, technical or reputational, that will get worse the longer it sits untouched? Third: does maintaining it cost you anything you could otherwise spend on a property that is actually growing?

If the answers are yes, no, and no, life support is not a compromise — it is the optimal allocation of your attention. The product becomes a small, quiet asset that exists without asking anything further of you, which is a genuinely rare thing to own and worth more than its revenue line suggests.

Where life support turns into a trap

The framework breaks in one specific way: when "minimum maintenance" quietly expands because customers keep asking for things, and every reasonable-sounding request gets a yes. A product on life support that accumulates small commitments stops being low-effort and starts being a second full-time job you never agreed to take, just distributed thinly enough across months that you never noticed accepting it.

The discipline required here is saying no to good ideas, which is harder than saying no to bad ones. A feature request from a paying customer is, by definition, evidence of real demand. Building it anyway, on a product you have decided not to invest in, is how life support silently becomes a second full commitment while your attention was supposed to be elsewhere.

• Set a hard ceiling on monthly hours before you commit to life support — write the number down
• Route every new feature request into a list you review quarterly, not one you act on the week it arrives
• Automate renewals and support replies wherever a template answers 80% of the question
• Revisit the three-question test twice a year — a life-support product can wake up
• Never let a life-support product borrow your attention from the property you are actively growing

Why a portfolio makes this easier, not harder

Operators running a single product often feel life support as a kind of failure, because the product is the whole business and anything less than full effort feels like giving up on themselves. Running several properties removes that emotional charge. A product on life support is simply one line in a portfolio, sitting next to others that are actively growing, and its quiet stability is doing real work: paying for itself while you spend your attention where it compounds faster.

This is the version of diversification that actually matters for a solo operator — not spreading bets to reduce risk in the financial-portfolio sense, but having enough properties that no single one has to justify your entire identity as a builder. A life-support product stops feeling like abandonment and starts feeling like what it is: a small, finished thing, still quietly useful, that no longer needs you.

The exit that is not really an exit

A product left on well-run life support for long enough often becomes acquirable, in a small, unglamorous way, to someone who wants exactly what it is: a stable niche tool with paying customers and low operating cost. That buyer is not looking for growth potential — they are looking for a machine that already works. Ironically, the discipline of leaving a product alone is often what makes it sellable, because a product still being tinkered with has no settled shape for a buyer to evaluate.

The lesson is not that every plateaued product deserves a dramatic pivot or a clean shutdown. Some of them deserve to be left exactly where they are, quietly earning their keep, while you spend the only truly scarce resource you have — attention — on whatever is actually still moving.

Common questions