Table of Contents
Key takeaways
SaaS charges a recurring fee, usually per user per month or year, for hosted software the vendor operates, updates, and secures on the customer’s behalf.
Salesforce is the company most credited with making software as a service a credible B2B category, through its 1999 “No Software” campaign and hosted CRM launched in 2000.
The metrics that matter are recurring revenue, net revenue retention, and churn, not one time bookings, because the entire value of a SaaS customer is realized over years of renewals.
The second S in SaaS, service, gets underfunded more than any other part of the model. Weak onboarding or support is a leading cause of early churn.
Customers often perceive SaaS as more expensive than perpetual licensing over time. That comparison usually leaves out the hosting, infrastructure, and IT staffing cost a perpetual customer has to carry themselves. A perpetual software license model shifts those costs onto the buyer instead of the vendor.
Where Software as a Service Came From
Salesforce launched in 1999 with a deliberately provocative pitch. A hosted CRM system, accessed entirely through a browser, with no servers, no installation, and no IT department required to get started. Its “No Software” campaign, a red circle and slash over the word software painted on taxis and billboards, mocked the entire perpetual license industry it was about to disrupt.
The company shipped its first hosted product in 2000, and within a decade, subscription based, vendor hosted software had gone from a curiosity to the default way most new B2B software gets sold.
What made the model work commercially was not just the technology. It was the shift in what the customer was buying. A perpetual license customer bought a static asset. A SaaS customer buys ongoing access to a system that keeps improving, hosted and maintained by someone else.
That shift is also why the acronym has two S’s. The first is software. The second, easy to skim past, is service, and it turns out to be the harder half to deliver well.
Recurring Revenue and the Metrics That Actually Matter
SaaS businesses are measured almost entirely differently from perpetual ones. The value of a customer is spread across years rather than realized at the point of sale.
Monthly and annual recurring revenue are the baseline metrics. They track predictable, repeatable revenue rather than one time bookings.
Net revenue retention measures how much revenue a cohort of existing customers generates a year later, including upgrades and expansion, minus downgrades and churn. Strong B2B SaaS companies commonly reach a net revenue retention rate above 110 percent, meaning the existing customer base is growing recurring revenue on its own, even before any new customers are added.
Gross churn and logo churn track how many customers, or how much revenue, is lost outright, independent of any expansion elsewhere. Customer acquisition cost payback period measures how many months of subscription revenue it takes to recover the cost of acquiring a customer. It is the metric that most directly exposes whether the underlying unit economics work.
In a B2B context, a mid-market vendor might sell three tiers: Standard, Professional, and Enterprise, priced per user per month. The Enterprise tier typically adds single sign-on, advanced permissions, and a dedicated customer success manager.
The core license fee is the visible part of the deal. The invisible part, onboarding, support, and account management behind each tier, is what actually determines whether that customer renews. For a structured way to think through how those tiers should be built, see our note on SaaS license model design.
The Forgotten Half of Software as a Service: Onboarding, Support, and Success
Most SaaS planning conversations focus on the product roadmap and the pricing tiers. Far fewer companies budget seriously for the service layer that makes a subscription stick.
This is a mistake. In a subscription model, the sale is not the finish line. It is the start of a relationship that has to be actively managed for years to generate the lifetime value the business case assumed.
Onboarding determines whether a new customer reaches their first meaningful outcome quickly enough to justify the purchase internally. Ongoing support determines whether day to day friction gets resolved before it turns into renewal risk. Customer success, when resourced properly, proactively identifies accounts that are under using the product and intervenes before the renewal conversation instead of during it.
None of this is optional in a subscription business. Yet it is routinely the first budget line cut when a SaaS company is trying to improve near term margins. Weak onboarding is consistently cited as one of the leading causes of avoidable customer churn, which is exactly the trade that shows up as lost revenue twelve months later.
Pro tip: if your SaaS business does not have a documented answer to “what happens in the first 30, 60, and 90 days after a customer signs,” you do not yet have a service model. You have a login page and a hope.
Software as a Service for the Vendor: What It Gets Right and Wrong
For the company selling it, SaaS offers predictable, compounding revenue. A healthy subscription base with strong net revenue retention grows on its own. Public markets reward recurring revenue with materially higher valuation multiples than one time license revenue receives.
The vendor also controls the entire technical stack, so every customer runs the same version. That dramatically simplifies support compared with a perpetual model, where dozens of versions might be in production at once.
The cost of this is that the vendor now owns the hosting, security, and uptime of the product, an operating expense that scales with the customer base rather than a one time engineering cost.
It also means the sales motion has to work in smaller increments. Instead of one large upfront transaction, revenue accrues month by month, so a slow start to the year is much harder to make up than in a perpetual model, where a single large deal late in the quarter can rescue the numbers.
The Customer Side: What Software as a Service Gets Right and Wrong
For the buyer, SaaS is an operating expense rather than a capital expenditure. That is typically an easier approval and a lower entry barrier, especially for a mid-market company that cannot justify a six figure upfront license purchase.
The vendor absorbs the cost of hosting, patching, and securing the system. The customer is always on the latest version without running a separate upgrade project.
The most common customer complaint, especially after several years on the platform, is that SaaS feels more expensive over time than a perpetual license would have been. This perception is often accurate on a narrow comparison of license fee plus maintenance versus subscription fee.
It is frequently inaccurate as a total cost of ownership comparison. It leaves out what the customer would have had to spend on their own servers or data center capacity, the internal IT staff needed to keep a perpetual system patched and secure, and the periodic cost of major version upgrades, which SaaS bundles into the subscription for free.
When a customer says SaaS costs more than the on-premise system it replaced, it is worth asking what they are comparing it against, and whether their own infrastructure and staffing costs made it into that number.
Our overview of B2B software license models walks through that comparison across all three structures side by side.
Quick Facts
Salesforce launched its “No Software” campaign in 1999 and shipped its first hosted CRM product in 2000, effectively founding the B2B SaaS category.
A net revenue retention rate above 110 percent means a SaaS company’s existing customers are growing recurring revenue faster than churn is shrinking it, before any new logos are added.
Customer acquisition cost payback period is one of the clearest signals of whether a SaaS company’s unit economics work at scale.
Onboarding and customer success are the parts of the SaaS model most often underfunded relative to their impact on renewal rates.
A fair SaaS versus perpetual cost comparison has to include the hosting, IT staffing, and upgrade costs a perpetual customer carries on their own.
Frequently Asked Questions
What is software as a service?
Software as a service is a recurring pricing structure in which the vendor hosts, operates, and continuously updates the software. The customer pays a regular fee, typically per user per month or year, for access rather than ownership.
Why is Salesforce considered the founder of SaaS?
Salesforce launched in 1999 with a hosted CRM delivered entirely through a browser, marketed under the “No Software” campaign. It proved that mission-critical B2B software could be sold as a subscription rather than an owned asset, and the model it pioneered became the industry default within a decade.
What is the second S in SaaS, and why does it matter?
The second S stands for service. It refers to the onboarding, support, and customer success work required to keep a subscription customer engaged and renewing. Companies that treat SaaS as purely a software delivery mechanism, without funding this service layer, typically see higher churn than the pricing model alone would predict.
Is SaaS really more expensive than perpetual licensing?
It depends on what is being compared. On a narrow license versus subscription fee basis, SaaS can appear costlier over several years. A fair comparison has to include the hosting, IT staffing, and periodic upgrade costs that a perpetual license customer bears separately, which a SaaS subscription typically absorbs.
What metric matters most to SaaS investors and buyers?
Net revenue retention is usually the single most watched metric. It shows whether the existing customer base is expanding or shrinking independent of new sales, which is the clearest signal of whether the underlying product and service experience are working.
Software as a Service Rewards the Companies That Treat It as a Relationship
Software as a service did not just change how software is priced. It changed what a vendor is responsible for after the contract is signed. A perpetual software license model ends the vendor’s obligation at delivery, aside from maintenance. SaaS never really ends the obligation, because renewal is earned every single billing cycle.
That is also why this model punishes companies that under invest in service and rewards the ones that treat customer success as a core function rather than a cost center.
The next article in this series moves to a model that pushes this idea even further: usage based licensing, where the vendor’s revenue is tied directly, and sometimes uncomfortably closely, to how much the customer uses the product.
If your SaaS pricing, packaging, or renewal motion needs a second look, let’s have a conversation.