The model, with every assumption on the table
Take 100 buyers who start on the same day. Offer three ways to pay for the same app:
- One-time: $79 once.
- Monthly: $6 a month, charged on day one and then every month the subscriber stays.
- Annual: $59 a year, charged on day one and on each renewal.
The churn numbers are assumptions picked to show how the answer moves. They are not measurements from any product. Monthly churn is the share of subscribers who cancel each month. Annual renewal is the share who renew each year. Stripe fees use the US card rate of 2.9% plus 30 cents; your country may differ. Stripe Billing, which subscriptions use, has its own fee on top, and Lemon Squeezy’s comparison page notes that Billing fees apply. The subscription rows below leave it out, so they are slightly optimistic.
This Node script produces the numbers. It needs no packages.
// node model.mjs
const fee = (price) => price * 0.029 + 0.3;
const ONE_TIME = 79, MONTHLY = 6, ANNUAL = 59;
// c = share of subscribers who cancel each month. The first charge is at month 0.
function monthly(c, months) {
let gross = 0, charges = 0, alive = 1;
for (let m = 0; m < months; m++) { gross += MONTHLY * alive; charges += alive; alive *= 1 - c; }
return { gross, net: gross - charges * fee(MONTHLY) };
}
// r = share of annual subscribers who renew each year.
function annual(r, months) {
let gross = 0, charges = 0, alive = 1;
for (let m = 0; m < months; m += 12) { gross += ANNUAL * alive; charges += alive; alive *= r; }
return { gross, net: gross - charges * fee(ANNUAL) };
}
for (const c of [0.03, 0.05, 0.08]) {
console.log(`monthly, ${c * 100}% cancel/month:`, [12, 24, 36].map((m) => monthly(c, m).gross.toFixed(2)).join(' / '));
}
for (const r of [0.8, 0.65, 0.5]) {
console.log(`annual, ${r * 100}% renew:`, [12, 24, 36].map((m) => annual(r, m).gross.toFixed(2)).join(' / '));
}
Revenue per customer over 36 months
Gross revenue per customer at months 12, 24 and 36, before fees:
| Plan and assumption | Month 12 | Month 24 | Month 36 | Passes $79 one-time |
|---|---|---|---|---|
| One-time $79 | $79.00 | $79.00 | $79.00 | n/a |
| Monthly $6, 3% cancel each month | $61.23 | $103.72 | $133.19 | month 17 |
| Monthly $6, 5% cancel each month | $55.16 | $84.96 | $101.07 | month 21 |
| Monthly $6, 8% cancel each month | $47.43 | $64.86 | $71.27 | never |
| Annual $59, 80% renew | $59.00 | $106.20 | $143.96 | year 2 |
| Annual $59, 65% renew | $59.00 | $97.35 | $122.28 | year 2 |
| Annual $59, 50% renew | $59.00 | $88.50 | $103.25 | year 2 |
Month 12 means the first twelve months, so an annual renewal at the start of year 2 first shows in the month 24 column. Two results are worth stating plainly. First, a monthly subscriber who never cancels is worth $6 a month, but the average subscriber is worth much less, because the pool shrinks. At 8% monthly churn the whole lifetime value is capped at $6 divided by 0.08, which is $75, below the one-time price. The ceiling for 5% is $120 and for 3% is $200. Second, the annual plan beats monthly at the same price level because the customer commits for twelve months before they can leave.
Fees favour the larger charge
Stripe’s fixed 30 cents is charged every time. A $79 one-time sale costs $2.59, which is 3.3%. A $6 monthly charge costs $0.47, which is 7.9%. An annual $59 charge costs $2.01, which is 3.4%.
At the middle assumptions, net revenue per customer over 36 months is $76.41 for one-time, $93.08 for monthly at 5% churn, and $118.11 for annual at 65% renewal. The monthly plan keeps 92% of its gross after card fees, against 97% for the other two, before any Billing fee.
Cash flow
For the same 100 buyers on day one, one-time brings in $7,900, annual $5,900 and monthly $600. If you pay for development, a launch or a first year of costs, that gap matters more than the 36-month total. A one-time price is also easier to sell: buyers see one number and no cancellation to remember.
A subscription gives steadier income, and it creates an obligation. Buyers pay monthly and expect the app to keep working and improving. A one-time buyer expects the version they bought to keep working. Pick the model whose obligation you can keep.
When each model leans ahead
| Situation | Leans toward |
|---|---|
| The app costs you money per user each month: servers, storage, API calls | Subscription |
| Self-contained tool, few updates, works offline | One-time |
| Frequent updates that buyers notice | Annual, or one-time with paid major upgrades |
| You need cash soon to fund the next version | One-time or annual |
| Buyers are businesses that expense monthly | Subscription |
| Strong comparison against subscription competitors you undercut | One-time, priced as months of their plan |
The last row is arithmetic buyers do themselves. If a competitor charges $9 a month, a $79 one-time price is under nine months of it.
A hybrid: perpetual license with a year of updates
Many desktop apps sell a perpetual license that includes one year of updates, then charge for further updates. With assumptions of $79 up front and a $35 yearly renewal that 40% of buyers take, the 36-month gross is $79 plus $14 plus $5.60, which is $98.60 per customer. That is close to the 5% monthly case, with most of the cash arriving up front.
The license stays valid forever, so the update rule has to live somewhere else. Your app can read the license’s created_at from a validate call and the release’s published_at from the update check, and allow installs of releases published inside the window:
const UPDATE_WINDOW_DAYS = 365;
function mayInstall(release, license) {
const purchased = Date.parse(license.created_at);
const published = Date.parse(release.published_at);
return published <= purchased + UPDATE_WINDOW_DAYS * 86_400_000;
}
This is a courtesy check, not enforcement. Clavem returns download links for any valid license, so someone who calls the update endpoint directly can still get the newest release. If you need a hard cut-off, publish newer versions under a separate product, as upgrade pricing for major versions describes.
How each model maps to a license
| Model | Stripe objects | License behaviour in Clavem | Event that changes it |
|---|---|---|---|
| One-time, perpetual | One-time price, Checkout Session | Never expires | checkout.session.completed issues it. A full refund, charge.refunded, disables it |
| One-time, fixed term | One-time price | Valid for a set number of days from issue | Buyer repurchases for a new license |
| Monthly or annual subscription | Recurring price, subscription | Follows the subscription: paid period plus 3 days | invoice.paid extends it. customer.subscription.deleted expires it |
| Perpetual with update window | One-time price | Never expires; the window is your app’s rule | As one-time |
For subscriptions, a customer who cancels keeps the license until the paid period ends, plus three days of grace, and a late payment that finally settles revives it. A past_due subscription stays valid while Stripe retries the payment. Subscription licenses with Stripe Billing goes through the failure cases.
Doing this with Clavem
All three models use the same Stripe connection. In Clavem, a product’s validity is perpetual, a fixed number of days, or following the subscription. A Stripe price maps to a product, so you can sell a monthly price and a lifetime price of the same Stripe product as two different Clavem products. Active licenses count toward your plan, so a perpetual license counts as long as it is not revoked or expired. That is worth modelling if you sell many of them. Clavem does not handle tax or act as a merchant of record, and it has no hosted checkout, so the payment side stays in Stripe. See Connecting Stripe for the events involved.
Questions
Which earns more, a one-time price or a subscription?
It depends on how long subscribers stay. With a $79 one-time price against $6 a month, the subscription passes the one-time total after 17 months at 3% monthly churn and 21 months at 5%. At 8% monthly churn the subscription never reaches $79.
Can I sell a perpetual license with a year of updates?
Yes. Issue a perpetual license and let your app compare each release's publish date with the license's creation date. That check runs in your app. If you need a hard cut-off, sell newer versions as a separate product.
What happens to a license when a subscription is cancelled?
With Clavem, a license that follows a Stripe subscription expires at the end of the paid period plus three days of grace. A customer who cancels keeps the license until then, and a renewal revives it.