B2B SaaS meaning: how business software sold as a subscription works, is priced, sold and measured.

Definition

B2B SaaS, short for business-to-business software as a service, is cloud-based software that companies use over the internet, hosted and run by the vendor, and paid for as a recurring subscription instead of a one-time license.

The B2B SaaS meaning has two halves. "B2B" says who the customer is: the Cambridge Dictionary defines B2B as trade "between different businesses, rather than between businesses and the general public."

"SaaS" says how the software is delivered: as a service the vendor operates, not a program the customer installs and maintains on its own servers.

A CRM your sales team logs into through a browser, a payroll system HR pays for per employee, and a project tracker the engineering team uses under an annual contract are all B2B SaaS. The customer rents access; the vendor keeps the software running, secure and updated.

B2B SaaS meaning, in plain words

Think of B2B SaaS as renting a fully serviced office instead of building one. The business moves in, uses the rooms it pays for and adds more when the team grows. The landlord fixes the plumbing, secures the building and upgrades the lifts without asking the tenant to do anything.

Microsoft's Azure glossary puts the same idea in vendor language: SaaS is a cloud-based delivery model in which individuals or organizations subscribe to applications rather than buying and installing them locally, while the provider manages the underlying infrastructure, security, maintenance and updates. For business buyers, that is the whole point: use without ownership.

B2B SaaS is one part of the wider group of B2B companies: the ones that sell software rather than materials, goods or services. It overlaps with B2B technology companies, a wider group that also sells cloud infrastructure, hardware and technical services.

This page covers the software part in full: how it works, how it is priced, sold and bought, and how its revenue is measured.

What is B2B SaaS, and what is it not?

Three conditions make a product B2B SaaS. If one is missing, the product is something close to it, but not the same thing. This three-part test is this page's working summary of the definitions cited below, not a legal or accounting rule.

• The buyer is an organization: a company, public body or nonprofit pays, even when individual employees are the users.
• The vendor runs the software: the application runs on the provider's cloud infrastructure and is reached through a browser, desktop app or mobile app, with no servers for the customer to manage.
• The payment recurs: the customer pays monthly or annually for continued access, and stops having access when it stops paying.

Software a company buys once and installs on its own hardware is traditional on-premises software. A cloud app sold to individuals for personal use is B2C SaaS. Cloud servers, storage and databases rented to engineering teams are infrastructure or platform services, which NIST treats as separate service models, covered below.

The official definition: what NIST says SaaS is

A formal definition comes from the U.S. National Institute of Standards and Technology. NIST Special Publication 800-145, The NIST Definition of Cloud Computing, published in September 2011, describes cloud computing as five essential characteristics, three service models and four deployment models. Software as a service is one of the three service models.

In NIST's words, SaaS gives the consumer the capability to use the provider's applications running on a cloud infrastructure, reached through a thin client such as a web browser or through a program interface. The consumer does not manage the infrastructure, network, servers, operating systems, storage or even individual application capabilities.

NIST allows one exception: the customer may control limited user-specific application configuration settings. That single line explains a lot about B2B SaaS in practice. Admins can set permissions, fields, workflows and integrations, but they cannot change the code or the servers underneath.

The right column is this page's illustration of each characteristic, not NIST text. NIST's definition covers all cloud services; the B2B part, who buys, is not in it. That is why the precise answer to "what is B2B SaaS" combines the NIST service model with a business buyer.

How B2B SaaS works

Behind the login screen, a B2B SaaS product follows the same basic pattern whatever it does. The vendor builds one application, runs it in the cloud and gives each customer company its own secure space inside it.

Hosted by the vendor

The software and the customer's data live on cloud infrastructure the vendor runs or rents. Microsoft's Azure definition says the provider manages software maintenance, including updates, security and backups, so customers always have the latest features and security patches without installing anything locally.

Paid by subscription

Instead of a large upfront license, the customer pays a recurring fee for as long as it uses the product. Azure describes SaaS as subscription-based, with customers able to adjust their subscription levels as their needs change. In practice, contracts are often monthly for small teams and annual or multi-year for larger accounts.

Multi-tenant, in plain words

Most B2B SaaS is multi-tenant: one running copy of the application serves many customer companies at once, and each company, the tenant, sees only its own data, users and settings. It is like an apartment building where every tenant has a private locked flat but shares the foundations.

Azure explains that SaaS providers use multitenant architecture, where a single instance of the software serves multiple customers and spreads infrastructure and maintenance costs across them.

NIST adds that customers generally do not know the exact location of the resources, but may be able to specify it at a higher level, such as country, state or datacenter.

That last point matters in B2B sales. Large or regulated buyers often ask where their data is stored and who can reach it, and some vendors offer a regional or dedicated environment as a separate option. Sellers should know their own product's answer before the security review starts.

SaaS vs PaaS vs IaaS

People often call every cloud product SaaS. NIST separates three service models by how much the customer controls. The further down the table, the more the customer manages, and the less the product looks like ready-to-use business software.

U.S. industry classification draws a similar line. In the 2022 North American Industry Classification System, published by the Census Bureau, industry 513210, Software Publishers, covers establishments that may publish and distribute software through subscriptions and downloads.

Industry 518210, Computing Infrastructure Providers, Data Processing, Web Hosting, and Related Services, lists infrastructure as a service and platform as a service among its illustrative examples, and its web hosting scope excludes software publishing.

For a seller, the practical lesson is simple: SaaS buyers are business users, while IaaS and PaaS buyers are technical teams.

B2B SaaS vs traditional on-premises software

The comparison below describes typical patterns, written for this page. Individual products and contracts vary, so treat it as a guide to the questions buyers ask, not as fixed rules.

The trade is control for convenience. SaaS removes the work of running software, and the customer accepts the vendor's roadmap, security practices and uptime in return. That is why security reviews and data processing terms are a normal step when businesses buy B2B SaaS, especially larger ones.

B2B vs B2C SaaS

B2B and B2C SaaS share the delivery model and differ in almost everything about the sale. The comparison below, a summary written for this page rather than a measured study, is the one most people mean when they search for B2B vs B2C SaaS.

Some products are both. A note-taking or video app can be sold to individuals on a personal plan and to companies on a business plan with admin controls, single sign-on and invoicing. The business plan is the B2B SaaS part, and it usually has its own sales team and pricing page.

Types of B2B SaaS: horizontal and vertical

B2B SaaS products are usually grouped two ways: by the business function they serve and by whether they target many industries or one. Both groupings are conventions used by sellers and analysts, not official categories.

• Horizontal SaaS: serves one function across many industries. A CRM, an accounting system or a team chat tool works the same for a law firm, a factory and a software company.
• Vertical SaaS: serves one industry with industry-specific workflows, data and compliance needs, such as software built only for restaurants, clinics, construction firms or logistics businesses.

For prospecting, the split matters. Horizontal SaaS sells to a role, such as every head of support, so targeting starts with job titles. Vertical SaaS sells to an industry, so targeting starts with the company list and industry codes, then finds the right person inside each business.

B2B SaaS examples, checked on each company's site

The companies below illustrate common categories. Each description was checked against the company's own website on Oct 1, 2026. They are examples, not rankings or recommendations, several also sell to individuals, and their product lines are broader than one line can describe.

CRM, sales and marketing

• Salesforce sells customer relationship management (CRM) software, and its Sales Cloud pricing page lists plans charged per user per month.
• HubSpot offers a CRM that its site says powers customer support, sales and marketing, and its CRM page lists free and premium plans.

Communication and collaboration

• Slack describes itself as a work platform for managing projects, automating workflows and connecting teams, and prices its paid plans per user per month.
• Zoom lists video meetings, chat, VoIP phone, webinars, whiteboard, contact center and events among its collaboration tools.
• Atlassian sells Jira, which its site describes as a project management product teams use to plan and track projects.

Commerce and customer service

• Shopify calls itself a commerce platform for businesses and lists tiered plans paid monthly or yearly.
• Zendesk sells a customer service platform, and its pricing page says pricing is primarily seat-based, per agent per month, with plan tiers.

The B2B SaaS business model

The SaaS business model trades a large payment today for many smaller payments over time. A vendor spends money up front to win a customer, and earns it back month by month for as long as the customer stays and, ideally, grows. This section explains that logic; it quotes no industry figures.

That shape explains most of what B2B SaaS companies do. They care about renewals as much as new deals, they employ customer success teams to drive adoption, and they track revenue as a recurring stream rather than as one-off sales.

• Recurring revenue: each customer adds a monthly or annual amount, which makes future income easier to plan than one-off sales.
• Acquisition cost first: marketing, sales and onboarding are paid before the customer has paid much back.
• Retention decides profit: a customer who leaves early may never repay what it cost to win them.
• Expansion inside accounts: more users, higher tiers and add-on products grow revenue without a new customer.
• Shared cost base: Azure notes that multitenant architecture spreads infrastructure and maintenance costs across customers, so one more customer adds relatively little running cost.

Read together, these points explain why B2B SaaS growth is judged on two numbers at once: how fast new recurring revenue arrives, and how much of the existing revenue stays and grows. A company that is strong on the first and weak on the second is filling a leaky bucket.

B2B SaaS pricing models

NIST lists measured service as an essential cloud characteristic and notes that metering is typically done on a pay-per-use or charge-per-use basis. In B2B, metering combines with subscriptions into a few recognizable pricing models. No prices are given here, only the categories.

The examples above show several of these models on the vendors' own pages: per user per month at Salesforce and Slack, seat-based tiers at Zendesk, tiered plans at Shopify, and free and premium plans at HubSpot. The "fits when" and "watch out for" columns are this page's advice.

Enterprise deals usually sit on top of these models as negotiated annual contracts, with committed volumes, discounts and custom terms. The list price on the website is the starting point, not the deal, which is why many B2B SaaS pricing pages end with a "contact sales" tier.

How subscription revenue is recognized

Cash and revenue are not the same thing in B2B SaaS. A customer may pay a full year up front, but the vendor reports that revenue as it delivers the service. The rules come from two converged standards: IFRS 15 internationally and Topic 606 in the FASB Accounting Standards Codification in the United States.

The IFRS Foundation explains that the Board issued IFRS 15 in May 2014, together with the introduction of Topic 606 by the FASB, effective for annual periods beginning on or after January 1, 2018.

Its core principle: recognize revenue to depict the transfer of promised goods or services, at the amount the entity expects to be entitled to.

1. Identify the contract

   The order form or subscription agreement with the customer.

2. Identify the performance obligations

   The distinct promises in it, such as the subscription itself, onboarding services or a separate support plan.

3. Determine the transaction price

   What the vendor expects to receive, including estimates for any variable amounts such as usage.

4. Allocate the price

   Split the price across the obligations based on their relative stand-alone selling prices.

5. Recognize revenue

   As each obligation is satisfied. IFRS notes that obligations are satisfied at a point in time, typically for goods, or over time, typically for services.

The step names follow the IFRS page; the SaaS examples in each step were written for this page. Because a subscription is a service delivered across the term, a one-year contract is generally recognized over that year. The revenue recognition section of our revenue entry works through an allocation example and explains deferred revenue.

B2B SaaS metrics, with formulas

Because the revenue arrives over time, B2B SaaS metrics measure the recurring stream and what it costs to build it. MRR and ARR get full treatment in the recurring revenue section of our revenue entry; the table below shows how they connect to the rest.

These are the simple versions this page uses to show how the metrics fit together. There is no single official formula for any of them. Companies choose what counts as recurring, which costs go into CAC and whether churn is counted by customers or by revenue.

Why definitions differ, and what public companies must disclose

The SEC addressed this in its 2020 guidance on key performance indicators in MD&A, Release 33-10751. It notes that such metrics vary significantly from company to company and names examples including total customers or subscribers, average revenue per user and monthly active users.

When a company includes a metric, the SEC generally expects a clear definition and how it is calculated, why it is useful to investors, and how management uses it. If the calculation method changes between periods, the company should consider disclosing the differences, the reasons and the effects.

The practical lesson for anyone reading a SaaS company's numbers, including sellers researching a prospect: find the company's own definition before comparing a metric with anyone else's. Two companies can report "net retention" and mean different calculations.

A worked example, with made-up numbers

The company and every number in this example were made up for this page, to show how the formulas connect. They are not benchmarks and describe no real business.

Read together, the invented numbers tell a story. Existing customers grow a little faster than others leave, which is what NRR above 100% means. But at 5% monthly churn, the average customer stays about 20 months, so each one returns about twice what it cost to win.

How B2B SaaS is sold: product-led vs sales-led

The sales motion is how a B2B SaaS company turns interest into paying accounts. It is a core choice in any go-to-market strategy, and many companies end up running a mix. The four motions below are common labels, described in this page's words.

In a sales-led motion the work looks like any other B2B sales: a defined sales process with stages, qualification and a buying group to win over. The pipeline is filled by inbound and outbound lead generation aimed at accounts that match the ideal customer profile.

The B2B SaaS buying process

A B2B SaaS purchase is rarely one person's decision. Even a small tool touches several roles once it holds company data or connects to other systems. The roles and stages below are this page's summary of a typical purchase, not a measured study.

• Users: the people who work in the product every day and judge whether it saves them time.
• Champion: the person who wants the product and pushes the purchase internally.
• Budget owner: the department head who pays for it and needs a business case.
• IT and security: check single sign-on, permissions, data location and the vendor's security documents.
• Procurement and legal: negotiate the contract, renewal terms and data processing agreement.

What buyers check before they sign

• Fit: does it solve the specific problem, for this team's size and process, better than the tools they use now?
• Security and compliance: where is data stored, who can access it, and which security reports and independent audits can the vendor share?
• Integrations: does it connect to the CRM, identity provider and other systems the company already runs?
• Total cost: what will it cost at next year's team size and usage, not only today's?
• Exit: can the company export its data in a usable format if it leaves?

The larger the customer, the more of these roles appear, and the longer the sale tends to take. Our advice: a short pilot run with real users and a written success measure answers most questions faster than another demo, and a clear value proposition for each role in the buying group keeps the deal moving.

How B2B SaaS companies grow

B2B SaaS growth comes from two places: new customers and expansion inside existing ones. The channels below are the usual options for the first, described as categories, without performance figures. Which ones work depends on the product, the price point and the market.

• Content and SEO: guides, comparisons and templates that answer the questions buyers search before they talk to sales.
• Outbound: sales development reps prospecting target accounts by email, phone and LinkedIn.
• Account-based marketing: coordinated campaigns aimed at a named list of high-value accounts.
• Paid acquisition: search, social and review-site ads aimed at in-market buyers.
• Partners and marketplaces: integration partners, consultants and app marketplaces that bring the product to their customers.
• Product-led loops: free plans, trials and invitations that let users pull colleagues into the product.

Most of these are demand creation and capture problems, covered in depth in SaaS demand generation. Whatever the mix, the metrics above tell you whether growth is healthy: new ARR is only worth what retention lets you keep.

The B2B SaaS customer lifecycle

In B2B SaaS, the sale is the middle of the customer relationship, not the end. Revenue depends on what happens after the contract, so companies manage the whole lifecycle with dedicated teams and tools.

• Acquire: marketing attracts and qualifies accounts, and sales or self-serve signup turns them into customers.
• Onboard: the customer configures the product, imports data, connects integrations and trains users. In our view, a slow start is one of the easiest ways to put a renewal at risk.
• Adopt: users make the product part of their daily work. Customer success tracks usage and steps in when it drops.
• Expand: a team adds users, moves up a tier or buys another product. Expansion revenue is what can push NRR above 100%.
• Renew: at the end of the term, the customer renews, renegotiates or leaves. The renewal is decided by everything that happened since the first day.

Selling to B2B SaaS companies on LinkedIn and by cold email

B2B SaaS companies are also buyers. They purchase data, sales tools, agencies, recruiting, infrastructure and services, and their teams are visible on LinkedIn. The approach below is this page's advice for prospecting them, built on how they make money.

• Target by motion: a sales-led company buys pipeline and sales tools; a product-led company cares about activation and conversion of free users.
• Pick the role that owns the metric: VP of sales for new ARR, head of customer success for churn and NRR, RevOps for data and tooling, the CFO for CAC payback.
• Use visible signals: open SDR roles, a new pricing page, a new product line or a move upmarket are public and specific.
• Speak their metrics: tie your offer to one number they already track, and use their definition, not yours.

On LinkedIn, research the account and the person first, then send a short, specific note. Our guide to LinkedIn prospecting covers search, connection requests and follow-ups. By email, one clear reason and one question beats a feature list; see how to write a cold email for structure.

The rules apply to business email too. The FTC's CAN-SPAM compliance guide states that the law makes no exception for business-to-business email. Commercial messages need a clear opt-out, a valid physical postal address and honest headers and subject lines, and opt-out requests must be honored within 10 business days.

Subject: {{companyName}} hiring {{roleCount}} SDRs

Hi {{firstName}},

Saw {{companyName}} is hiring {{roleCount}} SDRs for {{segment}}. New reps usually need a list on day one, and building it by hand eats their first weeks.

We {{whatYouDo}} for {{similarCompanyType}}, matched to the ICP you define.

Worth a 15-minute look before the new hires start, or is {{otherPerson}} the right person?

{{senderName}}
{{postalAddress}}
{{optOutLine}}

Benefits and trade-offs of B2B SaaS

For the businesses buying it, B2B SaaS has clear advantages and some real costs. Azure lists cost efficiency, access from any internet-connected device, automatic updates and adjustable subscription levels among the advantages; the trade-offs column is this page's summary of what buyers weigh against them.

Common mistakes with B2B SaaS

• Calling any cloud product B2B SaaS. If individuals are the buyers, it is B2C, and if engineers rent servers or a development platform, it is IaaS or PaaS.
• Treating the first contract as the finish line, when renewals and expansion decide whether the customer was profitable.
• Comparing your churn or NRR with a published figure calculated a different way, or measured on a different customer segment.
• Treating cash collected up front as revenue earned, when a subscription is recognized as the service is delivered.
• Choosing per-seat pricing for a product whose value does not grow with users, which pushes customers to share logins.
• Running a sales-led motion on a product small teams could buy alone, or a product-led motion on a product that needs a buying committee.
• Selling to "the company" instead of the users, budget owner and IT reviewer who each decide part of the purchase.
• Cold emailing SaaS teams without an opt-out or postal address because "it is B2B." The FTC says CAN-SPAM has no B2B exception.

In a sequence

Expansion is where B2B SaaS revenue grows inside existing accounts. The template below, written for this page, is an email to a customer whose usage is close to its plan limit. It names what you saw, offers a choice and asks one question.

Subject: {{teamName}} is close to its {{limitType}} limit

Hi {{firstName}},

Your team at {{companyName}} is using {{usageNow}} of the {{planLimit}} included in your {{planName}} plan, up from {{usageBefore}} at the start of {{period}}.

Two options when you reach it: move to {{nextPlan}}, which adds {{mainBenefit}}, or keep your plan and we cap usage at the limit. Either is fine.

Do you want me to send the numbers for both, or is someone else handling the renewal this year?

{{senderName}}

Frequently asked questions