Software pricing pages usually require a meeting to interpret. Tiers are named like trim levels, the feature matrix runs to thirty rows, and the number a small business will actually pay hides behind a calculator, a sales call, or the phrase "starting at." For a tool whose entire job is to recover money predictably, that fog is more than an annoyance — it prevents the one calculation the buyer most needs to make: what does recovery cost me in a normal month, and in a bad one?
Try the one-sentence test on any pricing page. Can you state, in a single sentence, what you will pay next month and what that payment covers? If the answer needs a subordinate clause about percentages, seats, contacts, transactions, or overages, the price is not really published — it is merely advertised. A business owner running a subscription store at midnight does not need a pricing model with moving parts. They need a number they can hold against the recovered revenue and judge, immediately, whether the exchange is fair.
Percentage-of-recovery pricing fails this test in a specific way worth naming. The sentence sounds simple — you only pay when it works — but the amount is unknowable in advance, and it grows in exactly the months when failures spike and cash is tightest. Worse, it charges for recoveries the business substantially produced itself: the subscriber who updated their card after one plain email, the retry that would have succeeded on any schedule. Untangling earned recoveries from gravitational ones becomes a permanent argument conducted on the vendor's scoreboard.
A flat monthly fee passes the test trivially, and its honesty can be checked before any invoice exists. Take a realistic failure pool, apply a cautious recovery rate, and compare the recovered total with the fee across twelve imagined months including the ugly ones. If the arithmetic survives the bad months, the decision is made and stays made; there is nothing to renegotiate when volume moves. That is the whole pitch behind flat monthly pricing stated before the first renewal is ever retried: one fee, everything included, judged against your own numbers rather than a vendor's example customer.
Flat pricing also disciplines the vendor, which buyers rarely think to value. A provider paid the same amount for a restrained recovery as for an aggressive one has no financial reason to over-retry cards, stretch dunning sequences past courtesy, or claim credit for payments that arrived on their own. Its only route to keeping the fee is keeping the merchant — which means recovering what should be recovered, leaving what should be left, and keeping records clean enough that the merchant can verify both. Incentives are a feature, and pricing is where they are set.
None of this argues that flat is right for every business at every size. A very small, irregular failure volume may rationally prefer paying only in months when something recovers. But that preference should be chosen with the arithmetic done — twelve months simulated, both columns totalled — not absorbed from a pricing page designed to make one column look painless. The test remains the same either way: if you cannot say the price out loud in one sentence, you do not yet know what you are buying.
Predictability is not a lack of ambition. For the small teams who run most subscription businesses, it is the difference between a tool that gets budgeted, renewed, and trusted, and a tool that gets re-litigated every quarter.
That is the bet printed plainly at Swipe Again: state the fee in one sentence, include everything, and let the recovered revenue — all of it — belong to the business that earned the subscribers.
Top comments (0)