Most SaaS founders spend 6 hours total on pricing decisions — less than they spend on their homepage copy. That number comes from Paddle’s PriceIntelligently research, and it shows up in the results: wrong pricing model chosen early, changed under pressure at Series A, changed again after enterprise deals start landing, each change leaving customer relationships and positioning in disarray.
The pricing model you pick shapes who buys (self-serve vs. sales-qualified leads), how billing scales as customers grow, and how hard it becomes to raise prices when you need to. Getting it right in year one avoids the renegotiation problem later.
This guide covers 7 SaaS pricing models in active use today — what each one actually looks like in production, which companies run on it, the real trade-offs, and a four-question framework for choosing between them.
The 7 SaaS pricing models
1. Flat-rate pricing
One price, full access, no per-seat or usage calculation. Basecamp has charged $99/month for unlimited users since 2014. Every customer — a 3-person agency and a 200-person consultancy — pays the same bill. The simplicity is the product: sales calls contain no seat negotiation, customers never face bill shock, and pricing pages need one number instead of a feature grid.
Real example: Basecamp ($99/month flat) and Transistor (podcast hosting, $19–$99/month by plan, not by user).
Pros
- Easiest to sell — one line item, no calculation required
- Predictable revenue for both the vendor and the customer
- No billing disputes over seat counts or usage spikes
Cons
- Leaves money uncaptured from high-value, high-usage customers
- No natural expansion path — once a customer is on the plan, there’s nowhere to grow revenue without a price increase
- One size rarely fits all — a 3-person team and a 150-person team get the same product for the same price
Best for: Product-led tools with a single clear value proposition targeted at small-to-mid-market customers where simplicity is itself a selling point.
2. Per-user / per-seat pricing
Charge per person who accesses the software. Slack charges $7.25–$12.50 per active user per month. Notion charges $8–$15 per user. Most CRMs and collaboration tools land here. The logic: in a B2B context, each additional user represents additional value derived, so revenue scales naturally with adoption inside a customer’s org.
Real example: Slack, Notion, Asana, and most CRM tools (HubSpot’s per-seat Sales Hub, Salesforce’s per-license pricing).
Pros
- Revenue grows automatically as the customer’s headcount grows — no upsell conversation required
- Simple to model for investors preparing to raise funding
- Natural expansion: a 10-seat customer that becomes 50-seat quintuples your MRR without a sales touch
Cons
- Creates an incentive to share logins, especially at the enterprise level where billing is scrutinised
- Can become a barrier to adoption inside a company — teams resist adding seats to avoid the bill going up
- Revenue drops directly if the customer downsizes or runs a layoff
Best for: Collaboration tools, project management software, CRMs — any product where value is clearly tied to the number of people using it daily.
3. Tiered pricing
Different packages at different price points, each with a defined feature or usage ceiling. HubSpot runs Starter/Professional/Enterprise. Mailchimp runs Free/Essentials/Standard/Premium. The point is segmentation: the Starter tier serves the solo user or small team; the Enterprise tier serves the procurement team that needs audit logs, SSO, and a dedicated CSM.
Real example: HubSpot (3 tiers by feature set + contact volume), Mailchimp (4 tiers by sends and automation features), Zoom (Basic/Pro/Business/Enterprise).
Pros
- Captures multiple customer segments in one product without building multiple products
- Creates a natural upgrade path — customers self-select their tier and graduate as they grow
- Higher average contract value than flat-rate pricing on the same product
Cons
- Feature-allocation decisions are hard: what goes in Starter vs. Pro vs. Enterprise is a strategic choice that affects conversion, not just a packaging one
- More than 3–4 tiers causes decision paralysis — research from PriceIntelligently found 3 tiers performs best for most SaaS products
- Buyers often can’t tell which tier fits them without a call — adds friction to self-serve conversion
Best for: Products with a clear small/mid/enterprise segmentation, or any product where different customer types need meaningfully different feature sets.
4. Usage-based pricing
Customers pay for what they consume. AWS charges per compute hour, storage GB, and data transfer. Twilio charges per SMS and API call. Stripe charges 2.9% + $0.30 per transaction. The model aligns cost directly with value received: low-usage customers pay little, high-usage customers pay proportionally more.
A 2021 survey cited in Stripe’s guide found only 39% of SaaS companies take a value-based approach to pricing — yet usage-based pricing is the closest model to value-based that most SaaS products can operationalise.
Real example: AWS (compute + storage), Twilio (per SMS/call), Stripe (per transaction), Vercel (per GB bandwidth and build minutes).
Pros
- Low barrier to entry — customers can start for near-zero and scale cost alongside value
- Revenue scales automatically with customer growth without requiring a formal upgrade conversation
- Aligns incentives: the more a customer uses (and the more value they get), the more they pay
Cons
- Revenue is unpredictable — one customer’s quiet month drops your MRR
- Sales and financial forecasting are harder without fixed commitments
- Customers who get comfortable at low usage levels are a churn risk when a cheaper competitor appears
Best for: Developer tools, APIs, infrastructure products, and AI tooling — any product where usage volume is an accurate proxy for the value the customer receives.
5. Freemium
A free tier with enough functionality to be genuinely useful, plus paid tiers that unlock additional features, usage, or limits. Dropbox gives 2GB free and charges for more storage. Zoom caps free meetings at 40 minutes and charges for longer. Slack limits message history for free workspaces.
Honest admission: freemium is not primarily a pricing model — it’s a customer acquisition strategy. The free tier is where users build the habit and prove the product’s value to themselves; the paid tier is where that habit converts to revenue. Most companies that run freemium generate 90%+ of their revenue from less than 5% of their users.
Real example: Dropbox, Zoom, Slack, Figma (collaborative features gated), Linear (seat limits on free tier).
Pros
- Removes the friction of the first conversion — no credit card required to start building the habit
- Product can spread virally inside organisations before a purchase decision is needed
- Large free user base creates distribution and brand data you can’t buy with ads
Cons
- Free users consume infrastructure and support without generating revenue
- Free-to-paid conversion is harder than most founders expect — typical consumer SaaS converts 2–5% of free users
- If the free tier is too good, it cannibalises paid — Zoom’s 40-minute limit exists for exactly this reason
Best for: Products with viral adoption potential, consumer-adjacent B2B tools, and products where demonstrating value requires real usage rather than a demo.
6. Feature-based pricing
Access to specific capabilities is gated by plan. Salesforce charges separately for Sales Cloud, Service Cloud, and Marketing Cloud — each module priced individually on top of a base platform fee. HubSpot gates automation, custom reporting, and sequences behind higher tiers.
Feature-based pricing differs from tiered pricing in one way: tiered pricing bundles features into fixed packages, while feature-based pricing lets customers configure their own combination of capabilities. In practice, many products use both — tiers for simplicity, with add-on modules for enterprise customisation.
Real example: Salesforce (module-by-module pricing), HubSpot (features gated by hub and tier), Zendesk (Support/Sell/Service as separate products).
Pros
- Customers pay for features they actually use — reduces the “I’m paying for things I don’t need” objection
- Creates precise upsell conversations: “You’re using manual outreach — the automation module would save 4 hours a week”
- Enterprise buyers can assemble a configuration that matches their exact workflow and budget
Cons
- Feature grids with 20+ rows create decision fatigue — buyers stop reading and call sales instead of converting self-serve
- High support and sales overhead explaining what each feature does and which plan includes it
- Customers feel nickel-and-dimed when basic expected functionality sits behind a paywall
Best for: Enterprise SaaS with distinct buyer personas needing different capability sets, or products with genuinely modular value that different teams within a company use independently.
7. Hybrid pricing
A subscription base plus usage-based charges layered on top. Databricks charges a platform subscription plus usage-based “Databricks Units” (DBUs) for compute. HubSpot charges per seat plus additional fees when contact volume exceeds tier limits. This model gives customers predictability on the base bill while preserving expansion revenue for the vendor without a formal upgrade conversation.
Hybrid pricing has become the default for modern data platforms, AI tooling, and marketing automation — categories where a core use case is consistent (justifying a subscription) but variable intensive use (heavy compute, large campaigns, API volume) creates additional value worth capturing.
Real example: Databricks (subscription + DBUs), HubSpot (seat subscription + contact volume overage), many AI API providers (monthly base + token consumption).
Pros
- Predictable baseline revenue from the subscription component — easier to forecast and finance
- Expansion revenue from usage without requiring a sales motion — customers opt into higher spend by using the product more
- Serves cost-conscious buyers (who cap their variable usage) and power users (who spend freely) with the same model
Cons
- More complex to communicate on a pricing page — two billing dimensions require more explanation than one
- Bill-shock risk: customers who underestimate their usage face unexpected charges, which generates support tickets and churn conversations
- Finance teams at your customers need to budget for both a fixed and a variable component, which can slow procurement sign-off
Best for: Data platforms, AI tooling, and marketing automation — products with a stable core use case plus variable high-value use cases where usage is a reliable signal of customer value.
How to choose the right SaaS pricing model
No pricing model is inherently correct — each is a bet on what your customers value most and how they expect to pay for it. Four questions narrow the choice:
1. What is your primary value metric?
The value metric is what scales as your customer gets more from your product — active seats, API calls, data volume, tasks automated. If your value metric is clear and measurable, usage-based or per-seat pricing captures it naturally. If the value metric is diffuse (the product saves time across an entire team in ways that aren’t easily measured), flat-rate or tiered pricing removes the measurement complexity and the billing friction that comes with it.
2. Who is making the buying decision?
Individual buyers and small teams need pricing they can understand without a call. A 3-tier pricing page with 12 feature checkboxes per tier will lose a solo founder who has 90 seconds to evaluate your product. Enterprise buyers — specifically procurement teams — expect complexity: line items, module costs, and feature comparisons are what allow them to justify internal spend. Match the model’s communication complexity to the buyer’s tolerance for it.
3. What is your sales motion?
Product-led growth (PLG) — where users discover, try, and buy without speaking to sales — requires pricing that communicates itself. Freemium and flat-rate work for PLG because the decision is made without a rep to explain it. Sales-led companies, where a salesperson closes the deal, have room for more complex models because the rep handles the explanation and handles objections live. Your startup stack for billing should match this motion too — PLG companies typically need self-serve checkout; sales-led companies can manage billing through CRM-integrated invoicing.
4. How much revenue predictability do you need now?
Pure usage-based MRR is harder to forecast and typically receives a lower revenue multiple in acquisition conversations than subscription revenue. If you’re preparing a fundraise in the next 12 months, a hybrid or subscription model produces cleaner MRR figures. If you’re optimising for customer acquisition and lower barriers to entry, usage-based pricing’s “start near-zero and scale” structure may outperform a flat subscription in the short term even if it creates forecasting complexity later.
SaaS pricing models: frequently asked questions
What is the most common SaaS pricing model?
Per-user and tiered pricing are the most widely deployed models among B2B SaaS companies as of 2026. Per-user dominates collaboration tools, CRMs, and project management software. Tiered pricing is standard across productivity software and marketing platforms. Usage-based pricing is growing fastest — particularly in developer tools, AI APIs, and infrastructure — but is still less common than subscription-based models overall.
What’s the difference between flat-rate and tiered pricing?
Flat-rate pricing charges one price for full access — every customer pays the same bill regardless of team size or usage volume. Tiered pricing creates distinct packages at different price points with different feature or usage ceilings. Flat-rate is simpler to communicate and sell; tiered pricing captures more revenue across different customer segments by letting buyers self-select the price point that matches their scale.
Is usage-based pricing better than subscription pricing?
Usage-based pricing aligns cost with value more precisely. Subscription pricing produces more forecastable monthly recurring revenue. Neither is universally better — the choice depends on your value delivery mechanism. Products where usage volume is a reliable proxy for value derived (APIs, infrastructure, AI tooling) suit usage-based pricing. Products with consistent daily use regardless of volume — HR software, most project management tools — suit subscription pricing because revenue doesn’t depend on usage intensity.
How do you switch SaaS pricing models without losing customers?
Grandfather existing customers on their current pricing for 12–18 months. Communicate changes at least 90 days in advance and frame them around additional value, not cost increases. The highest-risk transition is flat-rate to per-user: customers who built teams on a flat fee see their bill multiply when pricing moves to per-seat, and they calculate this instantly. Give them a long runway, a transparent reason for the change, and a migration path that acknowledges their current contract terms.
What pricing model works best for early-stage SaaS startups?
Tiered pricing with 2–3 clear tiers works for most early-stage B2B SaaS companies because it’s simple to explain, captures small and mid-size customers in the same product, and creates a natural upgrade path as customers grow. Freemium works for product-led tools where the product markets itself through use. Avoid pure usage-based pricing early unless your value metric is unmistakably clear — billing unpredictability burns early customers who can’t forecast their costs, and it makes it harder for you to forecast revenue ahead of a fundraise.
How do you know your SaaS pricing model is wrong?
Three signals: (1) you regularly discount to close deals — this means your price point is misaligned with perceived value, not just that sales is weak; (2) customers churn disproportionately at a specific plan tier — that tier’s price-to-feature ratio is off, and customers figure it out at renewal; (3) your highest-engagement customers are on your cheapest plan — your value metric isn’t capturing the value they actually receive, which means a different model would expand revenue from your best users without touching acquisition.
Sources
- Stripe’s guide — SaaS pricing models overview (includes 2021 pricing survey data)
- PriceIntelligently — SaaS pricing strategy research (6-hour statistic)
- Insight2Profit — SaaS pricing model trade-offs
