Most "pricing page examples" lists are screenshots with a sentence of praise under each. That tells you what a page looks like, not why it is built that way or what it costs the buyer to get an answer. This gallery takes 11 live SaaS pricing pages from well-known B2B companies, describes what each one actually shows in October 2026, and pulls out the decision behind it: who the page is built for, what it asks the visitor to do, and the one thing we would test if it were ours.
We looked at each page in a fresh browser session from Europe, so some prices appear in euros. Prices change often and vary by region, so we describe the structure rather than quote figures. Every example links to the live page so you can check it yourself.
What We Looked For on Each Pricing Page
A B2B pricing page has three jobs, and most fail one of them:
- Help the buyer self-qualify. Within ten seconds a visitor should know which plan is meant for a company like theirs.
- Explain the pricing model. Per seat, per host, per outcome, per transaction: the unit matters more than the number, because it is what finance will model.
- Route to the right next step. Self-serve sign-up for small teams, a sales conversation for the plans where procurement, security review and contracts are involved.
For each example we note the plan structure, the call to action wording, the proof elements, and what supports a buying committee (comparison tables, FAQs, security notes). If you want the reasoning behind changing these elements per segment, our guide to personalized pricing pages for B2B covers that side.
1. Slack: Recommended Plan Badge and a Billing Toggle
Slack's pricing page opens with a headline aimed squarely at businesses ("Choose a paid plan built for businesses") and a softer line underneath that keeps the free plan in view. Four tiers sit side by side: a free plan, Pro, Business+ and Enterprise Grid. A "Recommended for you" label appears on the plans, and Business+ carries a "Best value" tag. Each paid plan shows both the monthly and the annual per-user price, and when we checked, a time-limited introductory discount was displayed on the paid tiers.
What works: the feature lists are written as outcomes with a short explanation under each ("Messages are saved and searchable for 90 days"). A buyer comparing Free and Pro sees the exact limit that will hurt them, message history, without opening a comparison table.
What we would test: the page lists many AI features under every tier, which makes the columns long and similar. We would test collapsing the shared features and showing only what changes between tiers above the fold.
2. Notion: Plans Grouped Into Two Stories
Notion's pricing page starts with the line "One tool to run your company," then a monthly or yearly switch and a currency selector. The four plans are split under two headings: Free and Plus under "Essentials for staying organized," and Business and Enterprise under a heading about the AI workspace. Business carries a "Recommended" label. Every feature line has a plain-language explanation, for example what a "block" is.
What works: the two headings do the self-qualification job for you. An individual or small team reads the first group, a company evaluating AI and security reads the second. SAML SSO, domain verification and private teamspaces are listed on Business, which is exactly where an IT reviewer will look.
What we would test: the currency selector sits near the top and defaults by region. For a B2B buyer in a multi-country company, we would test showing the billing currency next to the price instead, so the toggle does not compete with the plan decision.
3. Linear: Four Columns and a Long Comparison Table
Linear's pricing page is the most minimal in this list. The headline is one word, "Pricing." Four plans (Free, Basic, Business, Enterprise) each show a short list of what changes, starting with "All Free features +" and so on. Below sits a social proof line ("Trusted by more than 40,000 companies") and then a full comparison table grouped by Core, AI and agent workflows, Integrations, Team management, Analytics, Asks and Security.
What works: the "everything in the previous plan, plus" pattern keeps each card short, and Enterprise lists what procurement asks for: invoice and PO billing, SAML and SCIM, account management, uptime SLA. Business has both a self-serve button and a "Contact sales" link, which suits teams that could buy either way.
What we would test: there is no FAQ on the page. Questions about seat counting and billing changes mid-cycle are common at this stage, and a short FAQ under the table would likely save a few support conversations.
4. HubSpot: One Page for Several Hubs, With Sales on the Upper Tiers
HubSpot's pricing page opens with "Sales. Marketing. Service. All together." and offers four tiers: Free, Starter, Professional and Enterprise. Each tier has a one-line description of who it is for ("For growing teams," "For mature teams," "For sophisticated teams"). The free tier is flagged "Best value." Starter has a "Buy now" button; Professional and Enterprise show both "Buy now" and "Talk to Sales." Below the cards, a compare-features section starts with plan details such as user limits and additional seat costs, and the page closes with sections organised by team size.
What works: the dual CTA on the expensive tiers. Some mid-market buyers want to buy without a call, while others need a quote, onboarding scope and a contract. Offering both keeps either type from bouncing.
What we would test: the "For growing / mature / sophisticated teams" labels are vague. We would test replacing them with concrete qualifiers such as team size or the job the tier is for ("Run automated nurture programs"), so visitors can place themselves faster.
5. Jira: A Team-Size Input Before the Plans
Jira's pricing page uses the headline "Transparent pricing for every team." Above the plans sit a team size field and a monthly or annual switch, so the prices recalculate for the visitor's actual user count. The four plans are Free (for up to 10 users), Standard, Premium (marked "Recommended") and Enterprise, which only shows a price when annual billing is selected. A long FAQ covers how the subscription cost is calculated, how users are billed, payment options and the difference between Premium and Enterprise.
What works: the team size input turns a per-user list price into "what will this cost us." That is the number a buyer needs for a budget request, and it removes a spreadsheet step. The FAQ answers the questions finance will ask.
What we would test: hiding Enterprise pricing behind the annual toggle is easy to miss. We would test a short line on the Enterprise card that says annual billing is required, instead of relying on the toggle state.
6. Figma: Seat Types Explained Inside Each Plan
Figma's pricing page headline is "Pick your plan, choose your seats." Each paid plan (Professional, Organization, Enterprise) lists three seat types, Full, Dev and Collab, each with its own price and AI credit allowance. Every plan has a "Why choose" block that starts with "Choose this plan if you:" followed by three short qualifiers. The page ends with a pricing FAQ that answers what a seat is, how mid-year seat additions are billed, and how to downgrade.
What works: the "Choose this plan if you" bullets are the clearest self-qualification device in this gallery. "Are a business that designs products across your organization" and "Need basic security" tell a buyer exactly where they belong.
What we would test: three seat types times three plans is nine prices to process. A small seat-mix calculator ("5 designers, 10 developers, 30 reviewers") would show a total and make the seat model concrete.
7. Intercom: Outcome Pricing Plus a Cost Estimator
Intercom's pricing page sells two products together: its helpdesk (priced per seat) and its AI agent, Fin (priced per resolved outcome). Three plans, Essential, Advanced and Expert, each state the per-outcome price and the per-seat price, followed by key features. A separate card covers using Fin with another helpdesk, with no seats required. Further down are add-ons, a cost estimator ("Find the right plan for your team"), an ROI calculator and a startup program.
What works: when the pricing unit is unfamiliar (paying per AI resolution), an estimator is close to mandatory. Intercom puts two of them on the page, one for cost and one for savings, so a support leader can build the business case without a sales call.
What we would test: the estimators sit well below the plans. For first-time visitors who have never bought outcome-based AI, we would test moving the cost estimator directly under the plan cards.
8. Zendesk: Most Popular Tier and an FAQ on How Pricing Works
Zendesk's pricing page lets the visitor choose between customer service, employee service and contact center pricing before showing plans. Four tiers follow, each with a one-sentence description of the team it fits ("For teams that have outgrown a shared inbox"). Suite Professional is marked "Most popular." The top tier uses "Talk to Sales," the others "Buy now." Featured add-ons, a savings calculator and an FAQ that opens with "How is Zendesk pricing structured?" complete the page.
What works: the plan descriptions are written as a maturity ladder. Each tier describes the point at which a team outgrows the previous one, which is how support leaders think about upgrading. The FAQ explains the cost components in plain terms (base subscription, usage-based features, add-ons, annual vs monthly).
What we would test: the calculator includes a disclaimer that results are illustrative, which is honest. We would test pairing it with one worked example, a team of a stated size, so visitors see a realistic output before entering their own numbers.
9. Datadog: Per-Host Pricing With a Product Selector
Datadog's pricing page starts with a long product selector (infrastructure, APM, logs, security, and many more) because each product is priced on its own unit. The infrastructure view shows Free, Pro and Enterprise tiers priced per host per month, with a note on the annual vs on-demand rate under each, and DevSecOps bundles beside them. Volume discounts for large deployments point to "Contact us." A comparison table below lists limits such as metric retention and container allotments.
What works: the page is honest about a complex model. Instead of forcing everything into three tiers, it lets an engineer pick the product they are evaluating and see its exact unit. That respects a technical buyer who will check the math.
What we would test: the product list is long enough that a first-time visitor may not know where to start. We would test a short "most teams start with" hint at the top of the selector.
10. Stripe: Pay-As-You-Go Next to Custom
Stripe's pricing page has only two options: Standard, a pay-as-you-go rate per transaction with a statement that there are no setup or monthly fees, and Custom, for large volumes or unusual business models, routed to "Contact sales." The custom card lists what can be negotiated: interchange-plus pricing, volume discounts, multi-product discounts and country-specific rates.
What works: listing what a custom deal can include turns "Contact sales" from a black box into a specific conversation. A finance lead at a high-volume company knows exactly what to ask for.
What we would test: nothing on the Standard card says at what volume Custom starts to make sense. A rough threshold would help mid-sized companies decide whether to talk to sales now or later.
11. Gong: No Prices, Just the Factors and a Short Form
Gong's pricing page shows no numbers. The headline ("Get the scoop on Gong pricing") is followed by the three factors that drive the price: licenses priced per user, a platform fee based on the number of users, and integrations included at no extra cost. A stepped form starts with one question, team size, with four ranges. Analyst and review-site ratings sit beside the form.
What works: if you will not publish prices, explain the model. Gong tells the buyer what the bill is made of, so they can estimate a range before the call. The first form step is a single click on a team-size range, which is far easier than a full contact form.
What we would test: a typical starting range for a small team. Even a broad band would let smaller buyers qualify themselves in or out before investing time.
Patterns Across the Examples
- Self-qualification copy beats feature lists. Figma's "Choose this plan if you," Zendesk's maturity descriptions and Notion's two headings all help the visitor place themselves before reading features.
- The unit is explained, not just priced. Datadog (per host), Intercom (per outcome), Figma (per seat type) and Gong (per user plus platform fee) spend real space on how the bill is built.
- The top tier routes to sales, the middle tier often offers both. HubSpot and Linear show self-serve and sales options on the same mid-to-upper plan.
- Security and procurement items live on the enterprise card. SSO, SCIM, audit logs, invoice billing and SLAs are listed explicitly because an IT or procurement reviewer will look for them.
- Calculators appear when the model is unfamiliar. Jira's team-size input, Intercom's estimators and Zendesk's savings calculator all exist to answer "what will this cost us."
- A single highlighted plan. Almost every page marks one tier as recommended, most popular or best value.
None of these pages show different content to different company types, at least not visibly. Most still show one version of the page to a five-person startup and to an enterprise IT team. That is where pricing page personalization starts: changing the recommended plan, proof and CTA by segment while keeping prices identical for everyone. Our how-to on personalizing a pricing page without changing prices walks through the build.
Pricing Page Checklist for B2B SaaS
Use this to audit your own pricing page against the patterns above:
- Each plan has one sentence that says who it is for, in terms a buyer can check (team size, use case, requirement).
- The pricing unit is named and explained, with an example if it is unusual.
- Monthly and annual prices are both visible, or the toggle is obvious.
- Exactly one plan is highlighted, and the reason is clear.
- Enterprise lists security, compliance and procurement items explicitly.
- The plan where self-serve and sales overlap offers both paths.
- If prices are hidden, the page explains what drives them and what happens after the form.
- An FAQ covers seat counting, billing changes, downgrades and cancellations.
- A calculator or worked example exists if the unit is not per seat.
- The page is tested on its own goal (plan selection or sales form starts), not only on sign-ups.
For the form itself, our post on the B2B lead capture form covers which fields to ask for and when. If you want to compare how other page types are built, see our B2B landing page examples, the companion gallery of B2B homepage examples, and the breakdown of demo request page examples. To see how we price Markettailor, visit our pricing page.
Frequently Asked Questions
What makes a good SaaS pricing page?
A good SaaS pricing page lets a buyer identify the right plan in seconds, understand the pricing unit, and take the next step that fits their buying process. In practice that means a short "who it is for" line on each plan, one highlighted tier, a comparison table, an FAQ on billing, and both self-serve and sales routes where they overlap.
Should B2B companies show prices on the pricing page?
Show prices whenever a meaningful share of buyers can purchase without negotiation. If every deal is custom, explain what drives the price, as Gong does with per-user licenses and a platform fee, and make the first form step light. Hiding both the price and the model is the version that loses buyers.
How many plans should a pricing page have?
Most examples here use three or four, typically a free or entry tier, one or two self-serve tiers, and an enterprise tier routed to sales. More than four usually means the plans are not differentiated enough or the page is mixing products that need their own pages, as Datadog handles with its product selector.
What should the enterprise plan list?
The items a security, IT or procurement reviewer checks: SSO and SCIM, admin controls, audit logs, data residency, uptime SLA, support level, invoice or PO billing and custom terms. Linear, Notion and Jira list these directly on the enterprise card.
How do you test a pricing page with low traffic?
Test bigger changes such as plan descriptions or the highlighted plan, measure a frequent event like plan-card clicks or sales form starts rather than closed deals, and run tests long enough to cover a full buying week. Our A/B test calculator shows how long a test needs at your traffic.