You bill on a schedule. So does the leak.

The retry ladder is a default nobody has touched

Every subscription platform ships with a retry schedule, and almost every brand is still running the one the app installed itself with. It is flat: the same number of attempts, on the same days, for the card that hit its limit on the 1st, the card that expired in March, and the card the bank flagged over an address mismatch.

In a one-off business a bad default costs you once. In a recurring one it bills again in thirty days, fails again for the same reason, and posts the same loss to the same line of the P&L — twelve times a year, compounding against a base that is also shrinking.

The information needed to do better is already in the payload. Every failed charge arrives carrying a decline code that says which of those three cards it is, and almost nobody reads it. A ladder that routes on the code rather than on the calendar behaves differently in each case: a soft decline retried on the schedule that code deserves, an expired card skipping the retries entirely and going straight to a one-tap update page, a hard decline handed to a person on the first failure rather than the fourth. Same platform, same subscribers, different system.

Cancel is the only door in the room

Three unopened bottles on a shelf is not a product failure. It is a cadence failure being expressed as a cancellation, because cancel was the only self-serve option on the page. The customer wanted the next one in March. They were offered leaving.

Households change quantity and cadence constantly — someone moves in, someone stops taking it, the last order is still half full. Pause, skip, resize, swap the SKU and change the interval all exist in your platform. Whether they are reachable in two taps, and whether the cancel flow offers them before it offers the exit, is a build decision nobody made.

A cancel flow worth the name reads the reason before it offers anything, then picks the door from it: “too much product” gets a cadence change, “too expensive” gets a smaller size, “I am travelling” gets a pause with a date on it. Discounting everybody is not a save strategy, it is a way of teaching your best subscribers to threaten to leave — and it is exactly what a flow with no logic in it does by default.

Reorder timing runs off the billing date, not the consumption curve

A 30-day supply at two capsules a day is a predictable reorder window. A 60-serving tub at one scoop a day is a two-month one. Both get billed on the same 30-day cycle because that is what the app defaulted to, and the second customer accumulates product until they pause — or until the shelf makes the decision for them.

The reorder prompt landing three days early beats it landing two weeks late, and both beat a prompt timed against a calendar that has nothing to do with how fast the product is actually used.

This is the one on the page that is genuinely a prediction problem rather than a configuration one. The fix is a model of consumption per SKU and per customer segment, built from your own order and reorder history, with the prompt, the education sequence and the billing cadence all timed against that curve instead of against the charge date. The platform cannot infer it, because the platform has never been told how much is in the tub.

The second order decides everything, and month three ends it

The first delivery is a trial. The second is the decision, and it is made in the gap between them — the weeks where nobody sends anything because the flows stop at the order confirmation.

Where the result is slow to show — a supplement, a skincare regimen, anything with a 60- to 90-day effect window — subscribers quit before the product has had time to work. That is a content and timing problem sitting inside a billing system, and it is the single most fixable cliff in a subscription business.

It is also the same consumption model as the row above, used for a different message: the education has to land while somebody still has product in the cupboard and no result yet, which is a date you can calculate rather than guess.

Three of the four are systems problems with a marketing symptom. They get solved in the retry ladder, the cancel-flow branch and the consumption model — not in the subject line.