SaaS orthodoxy says subscriptions always win: recurring revenue compounds, valuations reward MRR, and one-time sales mean restarting from zero every month. Then there's the boilerplate market (the niche we know best), which runs almost entirely on one-time purchases of $100–$300, sustainably, with happy customers and profitable vendors who've watched subscription experiments in the category mostly fizzle.
That's not an anomaly to dismiss; it's a case study in the actual rule, which is subtler than the orthodoxy: pricing models work when they mirror how value is delivered. Here's what the boilerplate market teaches, and how to apply it to your own pricing.
Why one-time pricing fits boilerplates
Walk through the value mechanics of a starter kit and the pricing model explains itself:
Value transfers at a moment, not over time. A boilerplate's worth lands the week you clone it and skip four to eight weeks of infrastructure work. After your product diverges from the kit, ongoing dependency drops toward zero: you own the code. Charging monthly for value that transferred in week one creates a cancellation decision every month against a product the buyer no longer "uses."
The buyer relationship is transactional by nature. Founders buy a kit per product, extract the value, and move on, maybe returning for the next product. That's a repeat-purchase pattern (like good tools), not a retention pattern (like services). Subscriptions bolted onto transactional value don't create retention; they create churn metrics that describe physics, not failure.
One-time aligns with the buyer's risk math. A founder pre-revenue is rationally allergic to recurring costs (their stack is already $50–150/month). A single $200 line item against weeks saved is an easy yes; the fifth monthly subscription is a budget review. Vendors price where the yes is easy.
Note what the model costs the vendor: no MRR compounding, revenue that demands a constant flow of new buyers, and updates funded by hope. The category's honest answer to "why maintain it, then?" is that maintenance is the marketing: a kit's update changelog is its strongest sales page in a market where staleness is disqualifying. Several vendors thread the needle with one-time-plus: lifetime code, optional paid yearly updates, or a higher "lifetime updates" tier. That's the model converging on the value shape, not away from it.
The general rule: match the model to the value curve
Map any product's value delivery over time and the pricing model falls out:
- Front-loaded value (boilerplates, templates, courses, one-shot tools): one-time purchase, optionally with paid update tracks. Subscription here taxes a relationship that already ended.
- Continuous value (hosting, monitoring, the system of record a vertical runs on): subscription, justified monthly by the product literally working every day. This is where SaaS orthodoxy is simply correct.
- Episodic value (occasional heavy use: tax tools, launch tools, migration tools): credits or per-use pricing usually beats both: subscription churns between episodes, one-time undercharges across them. (The AI-product version of this analysis has its own article.)
Most pricing mistakes in the wild are model-mismatch, not number-mismatch: the subscription product whose users get all the value in onboarding (churn by design), or the one-time product whose costs are ongoing, the fatal version being lifetime deals on products with per-use costs. An LTD on an AI product sells an unbounded liability for a bounded payment; the AppSumo graveyard is full of exactly this. Run lifetime promotions only when your marginal cost per user is near zero, or cap the lifetime tier's usage explicitly.
Applying it to your product
Three questions settle most cases:
- When does the customer get the value? Mostly in week one → one-time. Every week → subscription. In bursts → usage/credits.
- What do your costs do after the sale? Near-zero marginal cost permits one-time; per-use costs (inference, storage, support) demand recurring or metered revenue to stay solvent.
- What does the buyer's budget tolerate? Bootstrappers favor one-time; teams with procurement favor predictable subscriptions; enterprises punish unpredictable bills.
When the answers conflict (front-loaded value but real ongoing costs), hybrid honestly: one-time base plus optional subscription for the parts that genuinely continue (updates, hosting, support). Buyers respect pricing whose logic they can see; the willingness-to-pay math works best when the model itself isn't fighting the product.
Frequently Asked Questions
Why are boilerplates sold as one-time purchases instead of subscriptions?
Because their value transfers at a moment (the weeks saved when you start from the kit), and ongoing dependency drops once your product diverges from it. One-time pricing matches that curve, matches the transactional buyer relationship (one kit per product), and matches bootstrapper budget psychology. Subscription attempts in the category have mostly converted into churn statistics rather than recurring revenue.
Is one-time pricing viable for a software business?
Yes, when marginal costs are near zero and value is front-loaded; the boilerplate, template, and tool markets prove it at scale. The trade-offs are real: no compounding MRR, growth requires continuous new-buyer flow, and updates must be funded by reputation rather than retention. Many vendors hybridize with paid update tracks or higher lifetime-updates tiers to soften exactly those trade-offs.
Are lifetime deals a good idea for SaaS?
Only when marginal cost per user is near zero, and they're actively dangerous otherwise. A lifetime deal on a product with per-use costs (AI inference, storage, heavy support) sells unbounded liability for a bounded payment; this is the classic post-LTD death spiral. If you run one anyway for launch momentum, cap the lifetime tier's usage explicitly and model the worst case before, not after.
How do I decide between one-time, subscription, and usage pricing?
Map when value arrives and what costs persist. Value mostly at purchase + near-zero ongoing cost → one-time. Value delivered continuously (the product works for them daily) → subscription. Value in bursts or costs per action → usage or credits. Mismatches between model and value curve cause more pricing failures than wrong price points do: customers tolerate a price they think is high sooner than a model they think is unfair.