SaaS Businesses

How it works

A SaaS business sells hosted access rather than a copy of software. The customer subscribes; the operator keeps the code, the infrastructure and the underlying data, and pushes updates to everyone at once. Pricing is usually structured per seat, per usage unit such as API calls or records processed, or in feature tiers, often with an annual plan sold at a discount to monthly.

Revenue is tracked as monthly or annual recurring revenue, but the metric that actually describes the health of the business is net revenue retention: whether the existing customer base, taken together, pays more this year than last once churn and downgrades are netted against upgrades and usage growth. Billing for smaller accounts runs through a payment processor or a merchant of record; larger customers move to invoices, purchase orders and negotiated payment terms, which introduces collections risk that self-serve billing does not have.

Customers arrive through content and search, product-led free tiers, marketplace listings and integrations, outbound sales, or partner channels, and each channel carries a different cost to acquire a customer. Selling to larger organizations adds contractual obligations that a simple content site never faces: uptime commitments, data-processing agreements, security questionnaires and audit evidence such as SOC 2.

Small, single-developer products known as micro-SaaS trade regularly on brokered marketplaces. A buyer of one of these is acquiring an ongoing maintenance obligation at least as much as a stream of revenue.

What it pays

The revenue base is the number of paying customers multiplied by average contract value, expanding with upsells and usage growth and contracting with churn and downgrades. Gross margin tends to be high because hosting and support consume a modest share of subscription revenue, which is the structural reason SaaS is valued at a premium to services or e-commerce businesses with similar top-line revenue.

Usage-based pricing lets growth compound without adding a single new customer: if a customer's own business grows, its usage and its bill rise automatically. Enterprise contracts pay more per account but arrive with procurement cycles, security review, custom contract terms and slower cash collection, while self-serve customers pay less, churn faster, and cost almost nothing to close.

CAC payback — the number of months of gross profit needed to recover what it cost to win a customer — determines whether growth can be funded out of operating cash flow or requires outside capital. Revenue is contracted for its term, which supports genuine forecasting, but nothing obligates a customer to renew, and cancellation at the renewal date is always available to them.

Costs and taxes

Infrastructure costs — cloud compute, storage, bandwidth, managed databases and third-party APIs — scale with usage and can erode margin meaningfully in data-heavy products. Engineering time for bug fixes, dependency upgrades, security patches and framework migrations is non-optional maintenance, distinct from any time spent building new features. Support costs rise with contract size, and understaffed support shows up directly as churn.

Selling to larger customers adds recurring compliance costs: security questionnaires, penetration tests, and SOC 2 or ISO audits are ongoing obligations, not one-time hurdles. Payment processing fees apply throughout, and annual enterprise deals add a working-capital cost from net payment terms and collections.

In the US, subscription revenue is ordinary business income, reported on Schedule C or through a partnership or S-corporation return, with self-employment tax due on net profit for a sole proprietor. Sales tax on SaaS is decided state by state — some states tax it as tangible personal property or a data-processing service, others do not — and economic-nexus rules following the Wayfair decision mean a filing obligation can arise in a state where the business has no physical presence at all.

Software development costs are also subject to specific capitalisation and amortisation rules rather than immediate expensing, which changes taxable income in a given year even when cash flow is unaffected.

Liquidity and time commitment

SaaS is the most saleable asset in the digital-business category. Brokers and acquirers price small SaaS businesses on a multiple of ARR or of seller's discretionary earnings, and the multiple is set by growth rate, churn, and how technical the ongoing maintenance burden is. A sale is a technical migration as much as a legal one — code repositories, cloud accounts, domain and DNS, the payment processor, and customer data with its data-processing agreements all have to change hands, and customer notice obligations may apply.

Buyers discount heavily for customer concentration: a product where a handful of accounts make up most of the revenue is priced closer to a services business than a software business, whatever its label. Ongoing time is a mix of scheduled and unscheduled work — routine patching and upgrades can be planned, but outages and security incidents cannot.

Hiring an operator or a maintenance contractor is what converts SaaS from active work into a semi-passive holding for an owner who is not writing the code personally, and that person's cost comes straight out of margin. Cash flow tends to be smooth on self-serve subscriptions and lumpier on annual enterprise contracts, which cluster renewals in particular months.

How it goes wrong

Churn outrunning new customer acquisition turns a growing business into a melting ice cube, and headline revenue can still look acceptable for a quarter or two before the trend becomes obvious. A security breach is the failure category that ends companies rather than dents them, triggering breach-notification duties under state law, contractual liability to customers, and rapid customer flight. Extended downtime triggers SLA credits, refund demands, and cancellations concentrated at the next renewal date.

A product built entirely on one API, app marketplace or platform ecosystem is exposed whenever that platform changes its terms, raises its prices, or ships a competing feature natively. Technical debt accumulates quietly until routine dependency upgrades require something closer to a rewrite — which is exactly the moment a prospective buyer walks away from the deal.

Unregistered multi-state sales-tax liability can compound silently for years and then surface during a buyer's due diligence, reducing the sale price or killing the deal outright. Customer concentration means losing one enterprise account can remove a third of revenue and much of the valuation along with it, and founder dependency on the code — where only one person understands the system — means the asset is not genuinely transferable at all.