SaaS Business Models: 6 Ways Software Actually Makes Money
This article covers six SaaS business models, their economic risks, how to select a billing unit, and what revenue claims can—and cannot—show.
Contents: this article covers the six SaaS business models and how to choose
This article covers six SaaS business models, their economic risks, how to select a billing unit, and what revenue claims can—and cannot—show.
The six SaaS business models are distinct billing systems
SaaS monetization is broader than recurring subscriptions: the six useful models are flat subscription, per-seat, tiered, usage-based, freemium-to-paid, and hybrid service plus software. They differ in payment basis, bill expansion, and retention risk.
SaaS is more than hosted software. AWS describes it as a business model shaped by agility and efficiency, so commercial design matters alongside architecture. AWS explains the business-model foundation of SaaS.
Model | Billing unit | Best fit | Common failure mode | Useful metric --- | --- | --- | --- | --- Flat subscription | One recurring plan | Similar customer needs | Value differences ignored | Retention by plan Per-seat | Number of users | Collaboration software | Users limited to control costs | Paid seats/account Tiered | Feature/capacity package | Multiple segments | Confusing tiers | Tier conversion Usage-based | Consumption | Infrastructure or transactions | Unpredictable bills | Usage expansion/churn Freemium-to-paid | Free access with upgrades | Low-friction adoption | Low conversion/support burden | Free-to-paid conversion Hybrid service plus software | Software plus services | Complex workflows | Services overshadow software | Software retention/service margin
Microsoft identifies subscription, freemium, usage-based, and tiered pricing as common SaaS approaches. “Subscription” describes recurring payment; the others describe how access, features, or consumption determine the amount paid. Microsoft outlines common SaaS pricing strategies.
Readers can review actual project records on ProvenStartups by business shape and evidence grade, then compare pricing logic with the company type.
Choose the billing unit that follows customer value
Choose the billing unit that rises with customer value without making the bill feel arbitrary. Per-seat pricing may fit when customers benefit from adding colleagues. Usage-based pricing may fit when value rises with processed work. Tiered plans may communicate the tradeoff when needs differ mainly by capability.
Start with the value event: the action or outcome that makes the product worth paying for. It might be completing a workflow, serving a team, processing a transaction, or reducing manual work. The billing unit should visibly relate to that event.
Then ask whether customers can forecast the bill. Usage-based billing can align closely with value, but customers may resist it if they cannot estimate future costs. A predictable model can be more persuasive even when less precise.
Finally, connect pricing to retention and expansion. Stripe explains that monthly recurring revenue and annual recurring revenue track recurring revenue over time. Stripe’s guide to MRR and ARR helps distinguish it from one-time services or irregular payments.
Every model hides a different economic risk
Every model hides a different economic risk, so recurring payments alone do not prove durable customer value.
A flat subscription is easy to explain and forecast. It works when needs are similar, but may undercharge large accounts and overcharge smaller ones. It becomes fragile when customer value differs sharply.
Per-seat pricing grows with team adoption, making expansion intuitive. Customers may limit seats, share accounts, or delay invitations when each user increases the bill. It works best when every user adds value.
Tiered pricing serves multiple segments through capability levels. The risk is confusing packaging: if tier differences are unclear, prospects may choose the cheapest option or delay.
Usage-based pricing ties revenue to measurable consumption such as transactions, storage, or processing. The tradeoff is budget uncertainty when usage can spike.
Freemium-to-paid lowers the barrier to trying a product. It works when free access demonstrates value and paid features give a clear reason to upgrade. It must lead to activation and a credible upgrade path.
Hybrid service plus software combines recurring software with onboarding, implementation, training, or specialist support. It helps customers change an existing process. The danger is letting services become the real product while software becomes hard to retain independently.
A public revenue claim identifies scale, not profitability
A public ARR claim shows scale, not the pricing mechanism behind it or whether the company is profitable. Revenue may come from plans, usage, seats, services, or a mixture, so the headline number cannot explain the model by itself.
ProvenStartups grades revenue claims rather than treating a claim as audited profit. Its methodology explains how claims are evaluated, which matters when comparing companies with different evidence levels.
Readers can explore SaaS projects with revenue information, but should ask what the revenue represents. Recurring software revenue, implementation fees, consulting income, and one-time contracts have different implications for predictability and retention.
The same caution applies to unit economics. Revenue does not prove profit, satisfaction, or durable success. The ProvenStartups unit economics guide provides a lens for considering acquisition, delivery, retention, and expansion together.
Test willingness to pay before building broad product scope
Test willingness to pay and the billing unit before expanding product scope. Founders can build a wide feature set first and postpone how customers will be charged, producing a useful product with unclear commercial logic.
- 1.State the pricing hypothesis. Define the customer, value event, billing unit, and reason the price should rise as value rises.
- 1.Test the buying conversation. Present a concrete problem and ask what customers would expect to pay for, not merely whether the concept sounds interesting.
- 1.Compare two or three billing units. Consider flat subscription, per-seat, tiered, or usage-based pricing. Look for the option customers understand most easily and connect most naturally to value.
- 1.Measure behavior after adoption. Track activation, continued use, expansion, downgrades, and cancellations. A model that wins the first sale but discourages ongoing use needs revision.
- 1.Stress-test edge cases. Consider large accounts, low-usage customers, sudden spikes, dormant users, service-heavy onboarding, and customers who need to pause.
A solo founder should consider burden. Sophisticated pricing creates billing questions, exceptions, and support work. Simplicity is valuable when it preserves alignment with customer value.
The best default is the simplest value-aligned model
The best default is the simplest model whose billing unit follows customer value and whose retention can be measured. For some products, that is a flat subscription. Others may need per-seat, tiered, usage-based, freemium, or service-assisted software.
Do not choose a model because it is fashionable or another company uses it. Choose it because customers understand what they receive, the bill is predictable enough, and expansion preserves the commercial logic.
The durable choice is a clear exchange: customers pay according to the value they receive, and the company can observe whether that value continues.
Related guides
Frequently Asked Questions
The most common SaaS business model is subscription: what does that mean?
The most common SaaS approach is recurring subscription payment, but subscription alone does not identify billing logic. It may be flat-rate, per-seat, tiered, usage-based, or combined with services.
Usage-based pricing can still be SaaS: when does it qualify?
Usage-based pricing can still be SaaS when customers receive ongoing software and their recurring charge changes with measured consumption. The defining feature is the continuing service, not whether every customer pays the same amount.
SaaS can include services: how should they be treated?
SaaS can include implementation, onboarding, training, or specialist support. Evaluate services separately from recurring software revenue because they may require different delivery effort and have another retention profile.
The best model for a solo founder is usually the narrowest one: why?
The best model for a solo founder is the narrowest one customers understand and the founder can operate consistently. A simple billing unit reduces support and administration while leaving room to learn whether customers continue receiving value.