B2B SaaS Pricing: How to Charge for Value
Published on February 17, 2026 · Jules, Founder of NoNoiseMetrics · 13min read
A lot of B2B SaaS pricing advice is written for products with 20-person sales teams, 90-day enterprise cycles, and procurement committees. Most founder-led B2B SaaS products are not those products. They are sold to technical buyers, small teams, and operators who make fast decisions based on the pricing page — or leave because the pricing page created more questions than it answered.
The mistake founders make is borrowing enterprise pricing conventions for a product that should be self-serve. Hidden pricing, “contact sales” buttons next to €49/month plans, vague custom tiers, and 30-row feature comparison tables designed to look serious. These patterns are often cargo-culted from B2B SaaS brands the founder respects — but those brands have the sales infrastructure to justify the friction. A solo founder does not. The result is a pricing page that signals maturity but produces abandonment.
The clean default for most founder-led B2B SaaS: one value metric, three tiers, self-serve clarity, and a pricing structure that makes upgrades feel earned rather than forced. OpenView Partners SaaS pricing benchmarks consistently show that self-serve pricing pages with three clear tiers outperform hidden-pricing setups on conversion for products under €10K ACV.
What is B2B SaaS pricing?
B2B SaaS pricing is how a business-to-business software product charges customers in a way that matches customer value, usage patterns, and buying behaviour. The definition has three parts: how much (price), what for (pricing metric), and how structured (packaging).
The B2B context adds several realities that generic SaaS pricing advice often misses. Buying decisions usually involve accounts rather than individual users — which means pricing by account or workspace is often more rational than pricing by seat. The buyer and the user are sometimes different people, which means the pricing metric needs to make sense to both. Value is often defined in operational or economic terms (revenue tracked, workflows automated, hours saved) rather than consumer engagement terms.
What B2B context does not require: a sales process, hidden pricing, or custom quotes — unless the product genuinely creates procurement-level complexity. Most founder-built B2B tools do not.
For the broader pricing models framework, the minimalist guide covers all five model types with examples.
The B2B SaaS pricing models that matter
Per-seat pricing
Customers pay based on the number of users or seats. Well-suited to collaboration tools, team workflows, and products where each additional user creates marginal value. Works cleanly when collaboration is the primary value driver. Fails when one admin creates most of the value and paying per additional seat feels punitive to the buyer.
The key test: does adding another seat make the product more valuable for all existing users? If yes, seat pricing aligns incentives. If the answer is “not really — the second seat is just someone else who also needs access,” seat pricing feels like a tax rather than a value metric.
Usage-based pricing
Customers pay based on volume — subscriptions tracked, API calls made, workflows completed, invoices processed, reports generated. Aligns price with the output the customer is creating, which makes expansion feel natural rather than arbitrary. The challenge is billing predictability: B2B buyers, even technical ones, prefer to know what their bill will be. Usage-based pricing requires excellent in-product usage visibility so customers can manage their exposure. Stripe Atlas billing guides detail how to implement usage-based billing with good customer visibility.
Works best for infrastructure-adjacent products, API tools, and operations products where value clearly scales with throughput.
Tiered pricing
A small number of plans with increasing limits and value. The most common model for founder-led self-serve B2B SaaS because it combines simplicity (the buyer can scan and self-select) with flexibility (different segments get different limits). Supports expansion naturally as customers grow into higher tiers.
Weakness: tiered pricing requires disciplined packaging — the tiers need meaningful, understandable differentiation. A tiered pricing page with 25 feature rows across three plans creates the same comparison fatigue as too many tiers.
Hybrid pricing
A base platform fee plus a usage or seat component. Provides a floor of revenue per account while capturing value expansion. Appropriate for products where value has both a fixed component (access to the platform) and a variable component (usage volume). Harder to explain than pure tiered pricing, which can hurt self-serve conversion if the pricing page requires arithmetic before the buyer can understand their bill.
Wondering if your last pricing change actually moved ARPU? See plan-level MRR breakdown →
The strongest B2B SaaS pricing strategy for most builders
For most founder-led B2B products, the right default is: three tiers, one core value metric, full self-serve, and no custom pricing until complexity is real.
The three-tier structure (Starter / Growth / Scale, or equivalent naming) gives buyers enough choice to self-select without creating comparison paralysis. One core value metric — the thing that scales with how much value the customer gets — makes the upgrade path legible. Full self-serve means buyers can sign up, choose a plan, and upgrade without a sales conversation.
When to stay self-serve longer than you think you should: most founder-built B2B products targeting technical buyers, startup operators, or small teams benefit from staying fully self-serve through at least €5–10k MRR, often longer. The buyers in this segment are comfortable with self-serve SaaS, move quickly, and are actively put off by sales friction when the product clearly does not need it. A “contact sales” prompt for a €99/month plan signals that the founder does not trust the product to sell itself — which is the wrong signal to send to a technical buyer evaluating it.
Custom pricing becomes appropriate when: deals involve procurement-level complexity (contracts, legal review, compliance requirements), when per-seat negotiations are needed for large teams, or when deployment requirements require custom infrastructure configuration. Not before.
How to choose a B2B SaaS pricing metric
The pricing metric is the most important structural decision in B2B SaaS pricing. It determines what the buyer is actually paying for, what makes upgrades feel earned or arbitrary, and whether ARPA grows naturally as customers expand.
A strong B2B SaaS value metric passes five tests:
1. It correlates with customer value. When the customer gets more value from the product, the metric should increase. Subscriptions tracked, workflows completed, invoices processed — these grow as the customer’s use of the product expands. Page views or logins do not correlate with value in most B2B contexts.
2. It is explainable to the buyer’s team. One person should be able to justify the pricing to a colleague: “We pay more because we track more Stripe accounts, and more accounts is the thing creating value for us.” If the justification requires a product deep-dive, the metric is too abstract.
3. It is measurable within the product. If the product cannot track the metric reliably and display it transparently to the customer, it cannot power pricing. Pricing metrics that cannot be self-monitored create billing anxiety.
4. It is predictable enough for B2B buyers. Unlimited volatility in monthly bills is harder to accept in a business purchasing context than in a consumer context. Usage-based pricing needs usage caps or minimums, or at minimum excellent in-product visibility, to feel safe.
5. It creates natural expansion. As the customer’s business grows, the metric should grow with it — generating expansion MRR without any sales intervention. This is what makes pricing a recurring revenue engine rather than a one-time monetisation decision.
Concrete B2B SaaS pricing example
A SaaS analytics tool targeting founders, indie hackers, and small SaaS teams:
| Plan | Best for | Price | Core metric | Self-serve? |
|---|---|---|---|---|
| Starter | solo founders, 1 product | €19/mo | 1 Stripe account | Yes |
| Growth | active B2B SaaS, small teams | €49/mo | 3 Stripe accounts | Yes |
| Scale | agencies, multi-product teams | €99/mo | 10 Stripe accounts | Yes |
Supporting differentiation (kept to four rows):
| Feature | Starter | Growth | Scale |
|---|---|---|---|
| Team seats | 1 | 3 | 10 |
| Weekly AI digest | — | ✓ | ✓ |
| Failed payment recovery | Basic | Full (Brevo) | Full + priority |
| Data history | 12 months | 24 months | Full history |
Why this works as B2B pricing: the metric (Stripe accounts connected) scales directly with the customer’s business complexity. A solo founder with one product has no reason to be on Growth. A team managing three client products has an obvious reason to be on Growth. An agency managing ten products has an obvious reason to be on Scale. The upgrade trigger is visible without a sales conversation.
How B2B pricing connects to MRR quality
B2B SaaS pricing decisions have direct consequences for recurring revenue metrics. Weak pricing creates low ARPA and poor plan mix — serious customers stay on cheap plans because the upgrade trigger is not compelling or the value at higher tiers is not clear. Good pricing creates natural upgrade events that produce expansion MRR without sales effort.
The plan-level MRR health formula gives a clear signal:
Plan Health = new_mrr + expansion_mrr − churned_mrr − contraction_mrrRun it for each tier monthly. If the Growth plan shows consistently positive health while Starter shows churn-heavy health, the packaging is routing customers correctly — Starter is a trial entry point, not a permanent home. If Growth is also showing negative health, the pricing at that tier may be misaligned with the value it delivers.
Track ARPA by plan, upgrade rate, churn by plan, and expansion MRR monthly. If serious B2B customers are routinely staying on the cheapest plan, the value proposition of the higher tiers needs strengthening — not just in copy, but in actual features or limits. SaaStr’s pricing research finds that ARPA stagnation is the most common signal of a packaging problem rather than a product problem.
Common B2B SaaS pricing mistakes
Copying enterprise pricing conventions too early. Hidden pricing, “contact sales” for self-serve plans, and custom quote requirements add friction that benefits nobody when the product is still pre-product-market fit. The buyer who sees “contact sales” for a €49/month product leaves. The buyer who sees a clear pricing page with three self-serve options converts.
Pricing on the easiest thing to bill, not the most relevant thing to the buyer. Seat pricing is easy to implement. It is not automatically the right metric. The right question is: what is the unit of value that scales most naturally with the customer’s success? That is the pricing metric, regardless of implementation complexity.
Too many feature differences between tiers. A comparison table with 30 rows requires the buyer to evaluate each row individually and decide which ones matter. Most buyers are not willing to do that work. Keep tier differences to the 4–6 dimensions that will actually determine plan choice.
Adding a “contact sales” CTA before it is warranted. A “contact sales” prompt makes sense when deals genuinely require negotiation, compliance, or custom configuration. It does not make sense as a conversion tactic for a product with transparent pricing and a simple self-serve flow.
Reviewing pricing only by intuition, not data. ARPA by plan, upgrade rate, churn by plan, plan mix, and expansion MRR collectively tell the story of whether B2B pricing is working. Founders who adjust pricing based on gut feel rather than these signals make changes in the wrong direction at least as often as they make them in the right one.
JSON model for B2B SaaS pricing
{
"b2b_pricing": {
"model": "tiered_value_metric",
"primary_metric": "stripe_accounts_connected",
"self_serve": true,
"custom_pricing_threshold": "10+ accounts or enterprise compliance requirements",
"plans": [
{
"name": "Starter",
"price_monthly_eur": 19,
"stripe_accounts": 1,
"team_seats": 1,
"best_for": "solo founders, one product",
"upgrade_trigger": "second_stripe_account_needed"
},
{
"name": "Growth",
"price_monthly_eur": 49,
"stripe_accounts": 3,
"team_seats": 3,
"best_for": "active B2B SaaS, small teams",
"highlighted": true,
"upgrade_trigger": "portfolio_growth_or_team_access"
},
{
"name": "Scale",
"price_monthly_eur": 99,
"stripe_accounts": 10,
"team_seats": 10,
"best_for": "agencies, multi-product portfolios",
"upgrade_trigger": "portfolio_level_reporting_or_team_size"
}
],
"pricing_health_signals": [
"arpa_by_plan",
"upgrade_rate_starter_to_growth_90d",
"churn_by_plan",
"plan_mix_revenue_share",
"expansion_mrr_monthly"
]
}
}How to Measure Willingness to Pay
Pricing decisions based on gut feel are common. Pricing decisions based on data are better. Four practical methods for measuring what customers will actually pay:
Van Westendorp price sensitivity meter. Ask four questions: at what price would this be so cheap you’d doubt quality? At what price is it a bargain? At what price is it starting to get expensive? At what price is it too expensive to consider? Plot the responses. The intersection points give you the range of acceptable pricing and the optimal price point. Works well with 30+ responses.
Customer interviews. Ask existing or prospective customers directly: “What would you pay for [specific outcome]?” Frame it around the outcome, not the product. “What would you pay to save 5 hours a week on Stripe reporting?” produces a more honest answer than “What would you pay for our analytics tool?” Run 10–15 interviews to find patterns.
A/B testing price points. Show different prices to different visitor segments on your pricing page and measure conversion. This requires enough traffic to reach statistical significance — typically 500+ visitors per variant. Best for optimizing within a range you’ve already identified, not for discovering the range from scratch.
Competitor pricing analysis. Study what alternatives charge for similar outcomes. This is a proxy, not a target — your product may deliver more or less value than competitors. But competitor pricing sets buyer expectations. If every alternative charges €30–50/month and you price at €200/month, you need a clear justification for the gap.
FAQ
What is B2B SaaS pricing?
B2B SaaS pricing is how a software product charges business customers in a way that matches customer value, usage patterns, and buying behaviour. It involves three decisions: the price of each plan, the metric that drives the price (the value metric), and the packaging structure that defines what changes between tiers.
What is the best B2B SaaS pricing model?
For most founder-led B2B products targeting technical buyers and small teams, tiered pricing with one clear value metric and full self-serve access is the strongest default. Per-seat pricing works when collaboration is the primary value driver. Usage-based pricing works for infrastructure and API products where output volume clearly correlates with customer value.
What is the best B2B SaaS pricing strategy for a solo founder?
One value metric, three tiers (Starter / Growth / Scale), full self-serve pricing with no “contact sales” friction, and upgrade triggers tied to the natural growth of the customer’s business. Review the strategy quarterly using plan-level MRR health, upgrade rate, and ARPA by plan rather than intuition.
Should B2B SaaS always have custom pricing?
No. Custom pricing is appropriate when deals involve procurement-level complexity, compliance requirements, or large-team negotiations. It is not appropriate as a conversion or positioning tactic for products with simple self-serve value propositions. Adding custom pricing too early adds friction that most B2B buyers in the technical/startup segment will not accept.
Is seat-based pricing the right default for B2B SaaS?
Not automatically. Seat pricing works when each additional user creates meaningful marginal value for the team. It fails when the primary value is created by one or two power users and additional seats are just access licenses. The right metric is the one that scales most naturally with how much value the customer gets — which varies by product.
How do I know if my B2B pricing is working?
Track ARPA by plan, upgrade rate from Starter to Growth within 90 days, churn by plan, plan mix by revenue share, and expansion MRR monthly. Good pricing produces a Growth tier that holds the majority of revenue, upgrade rates above 15% within 90 days, and ARPA that trends upward as the customer base matures. Frequent discounting, high Starter concentration, and zero expansion MRR are the clearest signals that pricing is not working.
How does B2B pricing connect to MRR quality?
Directly. Weak pricing creates low ARPA (serious customers stay on the cheapest plan), no expansion MRR (no natural upgrade path), and plan mix weighted toward low-revenue tiers. Good pricing creates visible upgrade triggers that produce expansion MRR naturally as customers grow — which is the difference between a pricing structure that compounds recurring revenue and one that merely monetises customer acquisition.
After you set your price, you need to know if it works. NoNoiseMetrics tracks ARPU and MRR by plan automatically. Connect Stripe →