What B2B SaaS Is: 12 Examples and Their Pricing Models

B2B SaaS is vendor-hosted software sold to businesses through subscriptions, usage fees or combinations of the two. “B2B” identifies the customer; “SaaS” describes delivery as an ongoing service. A customer can be a sole operator or a large team. Some services also have desktop or mobile clients, so the category does not mean that no software is ever installed locally.

The examples below show purchasing patterns. Screenshots were captured on September 15, 2026; a homepage capture does not verify a current plan price. Seats, annual commitments, usage and add-ons determine the actual bill.

Key Takeaways

• B2B identifies the customer; SaaS describes delivery.
• Enterprise software can also be SaaS.
• Seats, usage, tiers and negotiated terms can coexist.
• Check client software, integrations and data responsibilities as well as hosting.

Customer type and delivery model are separate

Buyers can be founders, individual professionals, managers or procurement teams. The vendor operates the service, but customers may still update desktop clients, agents and integrations or administer their own configurations. Enterprise describes the organizational market or scope; it is not the opposite of SaaS.

The four ways B2B SaaS is priced

Per seat. A price tied to users or roles. Slack, Notion, Figma, Jira and support platforms illustrate this model. Billable-seat definitions matter: viewers, editors, administrators and occasional users may be treated differently.

Per usage. A defined unit drives the bill: transactions, monitored resources, data or model operations. Some charges are labeled outcomes. Intercom defines billable Fin outcomes that can include a completed procedure or handoff; billing does not itself prove customer satisfaction or a fully resolved problem.

Per tier. A bundle of features, service levels or allowances. A tier can also include a defined number of seats or add per-seat charges; inspect both dimensions.

Negotiated pricing. Some plans require a sales quote based on volume, scope and terms. Others publish enterprise prices, including the Figma and Datadog examples. A contact-sales action can also sit beside a published starting price.

Several examples combine these approaches. The combination describes a charging structure, not a complete account of the customer's needs. B2B SaaS pricing models explains how to evaluate one for your product.

Twelve B2B SaaS examples

1. Slack: team messaging. Seat-based plans illustrate why active-user definitions, billing period and administrative features belong in the comparison, alongside any free entry tier.

2. HubSpot: marketing, sales and service. Compare the particular hub, edition, included seats, contacts and onboarding requirements. A bundle name alone does not describe the total bill.

3. Salesforce: CRM. Editions, seats and add-ons create different scopes. Compare the required workflows, implementation and contract rather than assuming one headline seat price includes the entire system.

4. Notion: workspace. Its pricing page distinguishes workspace plans and AI-related allowances. Self-service adoption and enterprise sales can coexist; do not infer that every customer buys without a salesperson.

5. Stripe: payment infrastructure. Transaction-based charging illustrates usage pricing. Payment method, location, currency, negotiated terms and additional products can change fees; one domestic-card example is not the whole service.

6. Figma: design and collaboration. Figma's pricing separates seat types and plan levels. Match each person's required capabilities to the role, and check AI allowances and billing commitments. Enterprise does not automatically mean an undisclosed price.

7. Jira: work tracking. User counts, edition and administrative requirements affect the plan. Evaluate how a team moves from a limited entry tier to a paid one without inferring the vendor's acquisition economics from the tier alone.

8. Zendesk: customer service. Human-agent seats and AI-related features or usage can have different charging rules. Clarify which agents and channels are included.

9. Intercom: customer messaging. Its pricing combines human seats with Fin charges advertised from $0.99 per outcome in the October 20 check. Read the outcome definition and exclusions. An integration announcement or partner banner does not establish corporate ownership.

10. Gusto: payroll and HR. A base fee plus a per-person charge illustrates a hybrid model. Compare employee and contractor treatment, service scope and any additional fees.

11. Rippling: HR, IT and finance. A modular proposal can require a quote based on selected products and users. Request an itemized commitment; the sales process alone does not establish whether the product is a platform or tool.

12. Datadog: monitoring. Different products use different units, such as monitored resources or data volume. A published enterprise unit price can coexist with negotiated arrangements. Model the actual workload rather than treating every monitored service as the same unit.

What the twelve have in common

Several examples combine a self-service entry point with sales-assisted enterprise purchasing. That is a pattern, not a requirement of B2B SaaS. Usage and outcome charges can sit beside seats and platform fees. For example, Intercom's pricing defines billable Fin outcomes; a billed outcome should not be interpreted as a measured customer-satisfaction result.

For direct plan references, see Figma, Notion and Linear. Check the actual billing period and seat type before comparing their numbers with the dated examples.

What B2B SaaS means for the people building one

For a new product, define who buys, who uses it, which value the meter represents and how customers predict their bill. Trials and free tiers are options rather than requirements. Test the actual first-use task, purchasing path and ongoing administration; B2B design mistakes supplies questions for that review.

TripLeads.AI is a B2B SaaS we designed and built for travel-advisor lead capture and pipeline work, with 76 prerendered marketing pages on the same stack. It illustrates a specialized workflow without establishing that general CRMs cannot serve the audience. The Apstra icon language illustrates a design system for enterprise operations. Our Product Sprint, dashboard design and B2B services describe distinct scoped offers; the B2B label alone does not determine which engagement fits.

The definition, once more

B2B SaaS combines a business customer with vendor-hosted software delivery. A subscription, usage meter, tier or negotiated agreement describes how it is sold. Read the pricing page alongside the product's actual scope, data terms and exit options; the price alone does not define the service.

The SaaS design outlook turns interface predictions into questions to test against an actual product roadmap.