How do you decide between subscription and one-time pricing?

The right pricing model isn't about what's trendy — it's about matching how value is delivered to how money changes hands. Subscription works when your product creates ongoing value that compounds over time; one-time pricing works when value is delivered in a single, complete transaction. Get the match wrong and you'll either leave revenue on the table or constantly fight churn you didn't need to create.

Start with the value delivery pattern, not the revenue model

Before you open a spreadsheet, ask one question: does your product deliver its core value once, or does it keep delivering new value every week or month the customer uses it? A logo design tool delivers value in a burst — the customer gets the logo, done. A project management platform delivers value daily, accumulating shared context, historical data, and team habits that make it more valuable over time. The pricing model should mirror that delivery pattern.

One-time pricing makes sense when the product is a discrete artifact or outcome — a template, a piece of software with no ongoing hosting or updates, a report, a tool that does one job completely. Subscription makes sense when the product is a service in the economic sense: continuous access to infrastructure, data, features, or a network that the customer would lose meaningful value from the moment they stopped paying.

A trap many early founders fall into is choosing subscription because SaaS multiples look attractive to investors, not because their product actually warrants recurring billing. Customers can tell when they're being charged monthly for something that isn't genuinely evolving or serving them continuously. That mismatch shows up immediately in churn numbers.

Four diagnostic questions to force a decision

If you're still on the fence after examining value delivery, work through these four questions before picking a model.

First: does the customer's situation change over time in ways your product must respond to? Tax software, security tools, and analytics platforms all qualify — the underlying data, threats, or metrics are never static. One-time tools built around a fixed problem (file conversion, PDF editing) typically don't.

Second: what is your cost structure? If you bear meaningful ongoing costs to serve each customer — hosting, API calls, content creation, support — subscription aligns your revenue with your costs and prevents margin erosion. If you ship software once and your marginal cost per customer is near zero, one-time pricing won't create a cash flow mismatch.

Third: how long is your natural usage cycle? If customers use your product daily or weekly, subscription is natural. If they use it once a quarter or once a project cycle, monthly billing will feel punitive and generate support tickets every billing cycle.

Fourth: who is the buyer? B2B buyers with operating budgets often prefer predictable subscription costs that sit in opex rather than capex. Individual consumers making personal purchases often have lower friction with a single payment that doesn't require them to remember to cancel. Neither rule is universal, but both are directionally reliable.

Hybrid models and when they actually make sense

There's a third path that founders often overlook: charging once for the core product while offering subscription add-ons for ongoing services. This works well when you have a clearly defined core deliverable (a one-time fee) and a clearly defined ongoing service layer (support tiers, automatic updates, new content, cloud sync). The problem is execution complexity — you're now managing two billing relationships, and the handoff between them has to be frictionless or customers will just buy once and churn off the subscription.

Usage-based pricing is a variant worth considering if your customers' consumption patterns vary widely. Instead of a flat subscription or a one-time fee, you charge per unit of value consumed — API calls, seats, projects, documents. This lowers the barrier to entry for small customers and grows revenue automatically with large customers. The downside is revenue unpredictability, which makes operating and fundraising harder. Usage-based works best when you have a clear unit of value that customers understand intuitively and can control, and when your cost to serve scales proportionally with usage.

Don't adopt a hybrid model because it sounds sophisticated. Adopt it only when a single model genuinely fails to serve a real segment of your customer base.

How pricing model affects fundraising and valuation

Paul Graham's writing on fundraising makes clear that investors evaluating later-stage companies want to see a trajectory toward profitability — and that how you structure revenue affects how investors read your business model. Recurring subscription revenue is valued at a significant multiple of annual recurring revenue in most SaaS markets, while one-time revenue is valued closer to a multiple of earnings. That's a real difference in how your business is valued at exit, and it's worth factoring in if you're building toward institutional fundraising.

However, this investor-facing logic should be secondary to product-market fit logic. A subscription model with 40% monthly churn is not an asset — it's a sign your pricing model is misaligned with your value delivery. Investors who see that pattern won't be fooled by the recurring label. The best outcome is a model where customer behavior validates the pricing structure: low churn, expansion revenue, and customers who renew without friction because the product genuinely earns its keep every cycle.

If you're pre-revenue or very early, start with the model that gets the fastest conversion and clearest signal. One-time pricing often wins here — it removes the customer's risk calculus about future charges and gets you to a payment event faster. You can always layer subscription on top once you've validated that customers come back and want continued access.

Switching models later is harder than it looks

Migrating an existing customer base from one-time to subscription pricing — or the reverse — is one of the more operationally painful moves a startup can make. You're not just changing a checkout page; you're renegotiating the implicit contract you made with customers when they first paid. Customers who bought a one-time license often feel entitled to that relationship indefinitely and will object loudly to being pushed onto a subscription. The PR risk is real, as multiple developer tools companies have discovered.

If you think you'll want to switch models within 18 months, either pick the right model from the start or design your initial pricing to make the transition explicit. For example, you can offer early customers a lifetime one-time price as a founding tier, while making clear that new customers will pay on subscription. This lets you test the subscription model on new cohorts without breaking promises to early adopters.

The practical implication: treat the pricing model decision with the same seriousness as a technical architecture decision. It's not trivially reversible. Think about where you want to be in three years, not just what closes the next ten sales.

“Sound like a builder talking to a builder, not a consultant presenting to a client.”

— Garry Tan, source

The one thing to do

Map your pricing model to your value delivery pattern first — if the product earns its keep every month, charge every month; if it delivers value once, charge once — and only reconsider when customer behavior proves you wrong.

Frequently asked questions

Can I test pricing models without fully committing to one?

Yes — run a clean A/B test on new visitors only, keeping existing customers on their original terms. Measure conversion rate, average contract value, and 90-day retention separately for each cohort before drawing conclusions.

Does subscription pricing always mean monthly billing?

No. Annual billing upfront is a subscription with a very different cash flow profile — you collect 12 months of revenue at once, which reduces churn risk and improves working capital. Many B2B SaaS companies offer monthly and annual options simultaneously, with a discount (typically 15-20%) for annual prepayment.

What if my competitors all use one model — should I match them?

Not automatically. If your competitors' pricing creates visible friction or customer complaints, a different model can be a genuine differentiator. But if customers in your market are deeply habituated to a particular pricing structure, fighting that expectation adds sales friction you'll have to overcome on every deal.

How does pricing model affect customer support load?

Subscription models generate predictable, ongoing support relationships — customers feel entitled to help because they're paying every month. One-time models often generate a burst of support post-purchase that tapers off. Staff and tooling accordingly, because getting this wrong creates a cost structure that quietly kills margins.

Sources

More playbook answers · Growth Prophet home