TL;DR:
- A SaaS business model determines how a software company charges customers and earns recurring revenue through various pricing structures such as subscriptions, usage-based fees, freemium tiers, or hybrids. The chosen model influences not only revenue but also customer acquisition, retention, and operational complexity, with hybrid models being the most common among mature SaaS firms. Effective monetization requires aligning the pricing strategy with infrastructure capabilities and understanding the trade-offs between predictability and growth potential.
A SaaS business model defines how a software company charges customers and generates recurring revenue through pricing structures such as subscriptions, usage-based fees, freemium tiers, or hybrid combinations. The 11 main SaaS revenue model types include subscription, usage-based, freemium, transactional, licensing, affiliate, advertising, marketplace, service, data monetization, and hybrid. This saas business models list covers each structure with real-world examples from companies like Slack, Twilio, Notion, and Datadog, giving entrepreneurs a practical framework for choosing the right monetization path. The model you select shapes not just revenue, but customer acquisition, retention, and the operational infrastructure your team must build.
1. The SaaS business models list: subscription-based pricing
Subscription pricing is the most widely adopted structure across the SaaS industry, charging customers a recurring flat or tiered fee for continued access to the software. It comes in three primary variations: flat-rate, per-seat (also called per-user), and tiered pricing. Each variation suits a different product type and customer segment.
- Flat-rate: One price for all features and all users. Basecamp charges a single monthly fee regardless of team size, which simplifies billing but caps revenue growth.
- Per-seat/per-user: Customers pay per active user. Slack and Figma both use this structure, which scales revenue naturally as teams grow.
- Tiered pricing: Multiple plans at different price points, each unlocking additional features or usage limits. This is the most common structure for B2B SaaS because it captures value across small, mid-market, and enterprise segments.
Subscription models deliver predictable monthly recurring revenue (MRR), which makes financial forecasting and investor reporting straightforward. The trade-off is that flat-rate and per-seat models can undercharge high-volume users or overcharge low-volume ones, creating friction at renewal. Tiered pricing addresses this by segmenting the customer base, but it introduces the challenge of defining tier boundaries that feel fair rather than arbitrary.
Pro Tip: When designing tiers, anchor the middle tier at the price point you actually want most customers to choose. Price the bottom tier to qualify leads, not to generate meaningful revenue.
2. Usage-based pricing: pay-as-you-go models
Usage-based pricing charges customers based on what they actually consume, whether that is API calls, data processed, messages sent, or compute hours used. 43% of SaaS companies now use this model, an 8-percentage-point increase year over year. That growth reflects a genuine shift in how buyers want to pay: aligned with the value they receive.
Operationally, usage-based pricing requires metering, rating, and invoicing infrastructure to function accurately. Metering tracks consumption in real time. Rating converts raw usage data into a dollar amount. Invoicing aggregates and presents charges clearly. Without all three working reliably, billing disputes and customer churn follow quickly.
Twilio and Snowflake are the canonical examples. Twilio charges per SMS, per voice minute, and per email sent. Snowflake charges for compute credits and storage separately. Both companies built their billing infrastructure before scaling, which is not a coincidence.
The primary risk in pure pay-as-you-go is bill shock. A customer who underestimates their usage receives an unexpectedly large invoice, which damages trust and accelerates churn. Spending caps and committed-use discounts are the standard mitigations. Only 15% of SaaS companies use pure pay-as-you-go for this reason.
Stripe advises that transparent billing communication — including metric names, rates, effective dates, and example invoices — is the single most effective way to reduce support burden and customer confusion when operating usage-based models.
Pro Tip: Build a usage estimator into your onboarding flow. Customers who understand their expected bill before it arrives convert at higher rates and churn at lower ones.
3. Credit-based billing: abstracted consumption models
Credit-based billing is a variant of usage-based pricing where customers purchase a bundle of credits upfront and spend them across different actions or features within the platform. Credit models abstract multiple action costs into prepaid bundles, offering customers predictability while enabling flexible consumption. Midjourney and Jasper both use this structure for AI-generated outputs.
The practical advantage for the vendor is that credits are recognized as deferred revenue when purchased, which smooths cash flow. For the customer, credits feel more like a budget than a bill, which reduces anxiety about variable charges. The challenge is that credit pricing requires careful calibration: if credits are too cheap relative to infrastructure costs, margins erode at scale.
Credit and outcome-based models add accounting complexity but deliver stronger value alignment, particularly in AI-powered and performance-oriented SaaS segments. Teams building in those categories should plan for this complexity from the start rather than retrofitting it later.
4. Freemium models: acquisition-first monetization
The freemium model gives users free access to a core feature set and charges for advanced capabilities, higher usage limits, or team collaboration features. Notion and Canva are the most cited examples: both offer free access to basic features with paid upgrades that unlock templates, brand kits, version history, or team workspaces.
Freemium works best when the free tier delivers genuine value and the paid tier solves a problem that free-tier users will eventually encounter. The conversion funnel depends on users hitting a natural ceiling, not on artificially crippling the free product. Products that make the free tier too restrictive see low activation. Products that make it too generous see low conversion.
The operational cost of freemium is often underestimated. Free users consume infrastructure, generate support tickets, and require onboarding resources. The model only works financially when the lifetime value of converted users justifies the cost of carrying the free base. For cloud-based SaaS products, this math depends heavily on marginal hosting costs per user.
5. Transactional SaaS models: revenue tied to volume
Transactional models charge a percentage or flat fee for each transaction the platform processes, rather than for access to the software itself. Transactional SaaS charges per transaction and is most common in payment processing, fintech, and marketplace platforms. Stripe takes a percentage of each payment processed. Shopify Payments does the same for merchants running on its platform.
The appeal of transactional pricing is that revenue scales directly with customer success. When your customers process more volume, you earn more. This creates strong alignment between vendor and customer outcomes. The risk is that revenue becomes volatile and difficult to forecast, since transaction volume fluctuates with customer business cycles.
Transactional models also create a natural incentive for customers to seek lower-cost alternatives as volume grows. Stripe addresses this with volume discounts and custom enterprise pricing, which converts high-volume transactional customers into hybrid arrangements.
6. Hybrid SaaS models: combining fixed and variable revenue
Hybrid pricing combines a fixed subscription base with variable charges for usage, additional seats, or transactions. Hybrid pricing improves retention and net revenue retention by approximately 9 to 10 percentage points compared to pure subscription or pure usage models. That improvement reflects the model’s ability to capture expansion revenue without sacrificing the predictability that investors and finance teams require.
46% of SaaS companies now use hybrid models, making it the most common pricing structure among mature companies. Datadog charges a platform subscription plus usage-based fees for hosts, logs, and APM. HubSpot charges per-seat fees plus add-on modules. Both companies use the subscription floor to anchor revenue and the variable component to capture growth.
Kyle Poyar from OpenView characterizes hybrid SaaS pricing as the strategic focus for investors and entrepreneurs because it blends recurring revenue predictability with scalable value capture. The model does introduce billing complexity, particularly when customers need to understand two separate charge types on a single invoice.
Pro Tip: Establish product-market fit on a simple subscription model first. Add usage overlays only after you understand which features drive the most value for your highest-retention customers.
| Hybrid model type | Fixed component | Variable component | Example |
|---|---|---|---|
| Subscription + usage | Monthly platform fee | API calls or compute | Datadog |
| Subscription + seats | Base plan | Per-user expansion | HubSpot |
| Subscription + transactions | Access fee | Per-transaction percentage | Shopify |
| Subscription + credits | Platform access | Prepaid credit bundles | AI tools |
7. Licensing models: traditional software adapted for SaaS
Software licensing in a SaaS context typically means selling the right to use a specific version or module of the software, often for a defined term or in a white-label arrangement. This model is common in enterprise SaaS, where large organizations want to embed a vendor’s technology into their own product stack without a per-user or usage-based arrangement.
Licensing revenue is predictable and often negotiated annually or multi-year, which makes it attractive for enterprise sales teams. The challenge is that licensing deals require significant legal and procurement overhead, which makes them impractical for self-serve or SMB-focused products. Companies like Salesforce and SAP use licensing alongside subscription tiers for their enterprise segments.
8. Marketplace and commission models
Marketplace SaaS platforms connect buyers and sellers and charge a commission on each transaction or listing. This structure is distinct from transactional pricing because the platform itself does not process the transaction. It facilitates the match and takes a percentage of the deal. Shopify’s app marketplace and Salesforce AppExchange both operate on commission structures.
The marketplace model generates revenue without requiring the platform to own the product being sold. It scales with the ecosystem rather than with direct customer acquisition. The operational challenge is that marketplace revenue depends on the health and activity of the ecosystem, which takes time and investment to build.
9. Advertising and data monetization models
Advertising-supported SaaS products offer free or low-cost access and generate revenue by displaying ads to users or by selling anonymized usage data to third parties. This model is rare in B2B SaaS but appears in productivity tools, communication platforms, and analytics products with large free user bases.
Data monetization involves packaging aggregated, anonymized user behavior data as a product sold to researchers, marketers, or industry analysts. LinkedIn’s Talent Insights product is a well-known example of a SaaS company monetizing behavioral data at scale. Both models carry significant privacy and regulatory considerations, particularly under GDPR and CCPA frameworks.
10. Affiliate and partner revenue models
Affiliate models generate revenue by referring customers to complementary products or services and earning a commission on resulting sales. In SaaS, this often appears as a partner program where integration partners, consultants, or resellers earn a percentage of deals they source. HubSpot’s solutions partner program and Shopify’s affiliate program are prominent examples.
Affiliate revenue is typically supplementary rather than primary. It works best when the SaaS product sits at the center of a broader ecosystem and can credibly recommend adjacent tools. The risk is that affiliate incentives can distort product recommendations, which damages customer trust if not managed carefully.
11. Service revenue: professional services and implementation
Service revenue comes from charging for implementation, customization, training, or ongoing managed services alongside the core SaaS product. Enterprise SaaS companies like Workday and ServiceNow generate substantial revenue from professional services that help customers deploy and configure the software.
Service revenue improves customer success outcomes and reduces churn by ensuring customers actually use the product effectively. The trade-off is that service revenue carries lower margins than pure software revenue and requires a different operational model, including a professional services team with domain expertise. For SaaS automation products, implementation services often determine whether customers achieve the ROI they were promised during the sales process.
Key takeaways
The most effective SaaS monetization strategy combines a predictable subscription base with at least one variable revenue layer, whether usage, seats, or transactions, to capture expansion revenue without sacrificing forecast accuracy.
| Point | Details |
|---|---|
| Hybrid models dominate | 46% of mature SaaS companies use hybrid pricing to balance predictability and growth. |
| Usage-based requires infrastructure | Metering, rating, and invoicing systems must be in place before scaling usage-based billing. |
| Freemium math is critical | Free user infrastructure costs must be justified by the lifetime value of converted paid users. |
| Start simple, then layer | Establish subscription product-market fit before adding usage or credit overlays. |
| Transactional models scale with customers | Revenue grows with customer success, but volatility requires volume discounts at scale. |
Why model selection is harder than it looks
The conventional advice is to pick the model that fits your product and move on. In practice, the model you choose at launch is rarely the model you operate at scale. Bitecode has observed this pattern repeatedly across SaaS builds: companies that start with flat-rate subscriptions eventually face pressure to add usage-based components as their highest-value customers consume disproportionately more than their lowest-value ones. The billing infrastructure was never designed for that transition, and the migration becomes a significant engineering project.
The more honest framing is that model selection is a risk allocation decision. Flat-rate subscriptions put risk into revenue predictability. Pure usage-based pricing puts risk into revenue volatility. Hybrid models distribute that risk more evenly but relocate complexity into the billing and customer communication layer. There is no model that eliminates risk. There is only a choice about where to put it.
The operational reality of usage-based and hybrid models is also consistently underestimated. Two-dimensional billing with a subscription floor plus usage overage is industry best practice, but implementing it correctly requires metering infrastructure, clear customer-facing documentation, and a support team trained to explain variable invoices. Companies that skip these steps see churn spikes at the first billing cycle after a usage spike.
The trend toward hybrid models is real and well-supported by the data. But hybrid pricing is not a default setting. It is an earned complexity that makes sense after a company understands its usage distribution, its customer segments, and its expansion revenue drivers. Entrepreneurs who adopt it prematurely often find that the billing complexity outpaces their operational capacity to manage it.
— Bitecode
Build your SaaS model on a foundation that scales
Choosing the right revenue model is only half the equation. The other half is building software infrastructure that can actually execute it, whether that means metering usage, managing subscription tiers, or processing transactions at volume.
Bitecode’s modular development platform starts SaaS projects with up to 60% of the baseline system pre-built, including an AI assistant module for workflow automation and a custom CRM module designed for per-user and hybrid pricing structures. For teams building transactional or fintech SaaS products, Bitecode’s blockchain payment integration handles the infrastructure complexity that typically delays launch by months. If your SaaS model requires billing precision and operational depth, Bitecode provides the modular foundation to build it without starting from scratch.
FAQ
What are the main types of SaaS business models?
The 11 main SaaS revenue model types are subscription, usage-based, freemium, transactional, licensing, affiliate, advertising, marketplace, service, data monetization, and hybrid. Most mature SaaS companies combine two or more of these structures.
What is the most common SaaS pricing model?
Hybrid pricing is now the most common structure among mature SaaS companies, with 46% using hybrid models that combine a fixed subscription base with variable usage or seat-based charges.
How does freemium differ from a free trial?
Freemium offers permanent free access to a limited feature set, while a free trial provides full access for a defined period. Notion and Canva use freemium. Most enterprise SaaS products use time-limited trials.
When should a SaaS company use usage-based pricing?
Usage-based pricing works best when consumption varies significantly across customers and when the value delivered scales directly with usage. It requires metering and invoicing infrastructure before it can be implemented reliably.
What is hybrid SaaS pricing?
Hybrid pricing combines a fixed subscription fee with variable charges for usage, additional seats, or transactions. It improves net revenue retention by approximately 9 to 10 percentage points compared to single-dimension pricing models.
