SaaS Business Model: Revenue, Retention, and Costs

A SaaS business operates software customers access over a network and earns money through subscriptions, usage charges, or a combination. Recurring contracts can make future revenue easier to estimate, but predictability depends on retention, expansion, payment collection, and the cost of delivering the service.

This guide uses explicitly hypothetical examples to separate cash, accounting revenue, and operating metrics. It does not report Hapy client results. Have an accountant apply the relevant accounting framework to your actual contracts and counsel assess refund and cancellation terms.

What the customer buys

Customers buy access to an operated service under defined terms. The provider handles the application and updates, while the buyer still manages responsibilities such as users, configuration, and permitted data use. B2B SaaS serves organizations; B2C SaaS serves individuals. Neither model is inherently guaranteed to grow faster.

The product may be vertical or horizontal SaaS. Choose a customer job and delivery model before choosing billing units. SaaS is one viable software business model alongside licenses, services, embedded software, and other approaches; it is not mandatory for every software company.

Cash, revenue, and MRR are different

Measure	Question answered
Cash collected	What money entered the bank?
Recognized revenue	What amount is recognized under the applicable accounting policy for service delivered?
Contract liability/deferred revenue	What prepaid service obligation remains under that accounting treatment?
Monthly recurring revenue (MRR)	What monthly-equivalent recurring subscription value is active under the company’s metric definition?

IFRS 15 links revenue recognition to satisfying identified performance obligations. Actual treatment depends on the contract and accounting framework. MRR is an operating metric, not a substitute for financial-statement revenue.

A reconciled annual subscription example

Assume one customer pays $1,200 upfront for twelve months of continuous access beginning January 1. Assume a single service obligation delivered evenly, with no tax, separate implementation, discounts, usage charges, refunds, or contract changes.

Point in time	Cumulative cash received	Cumulative revenue in this simplified example	Remaining deferred revenue	Active MRR
Before service begins	$1,200	$0	$1,200	$0 until activation
End of January	$1,200	$100	$1,100	$100
End of February	$1,200	$200	$1,000	$100
End of December	$1,200	$1,200	$0	$100 if still active at the measurement point

At each row, cumulative recognized revenue plus remaining deferred revenue equals the original $1,200 under these assumptions. The table does not show the bank balance: hosting, salaries, and other spending reduce cash separately.

A customer who stops using the product after two months does not automatically acquire a right to recover ten months of payment. Cancellation, continuing access, refunds, and termination depend on the contract and applicable law; they may also change accounting treatment. Deferred revenue is not itself a statement that the customer can demand a refund at any time.

Retention and expansion determine the recurring base

Suppose a hypothetical month begins with 100 customers at $100 MRR each. During the month, five beginning customers cancel, continuing customers downgrade by a combined $200 MRR, continuing customers expand by $1,000 MRR, and ten new customers add $1,000 MRR. Assume no reactivations or currency effects.

Movement	MRR
Starting MRR	$10,000
Churn	−$500
Contraction	−$200
Expansion	+$1,000
New customers	+$1,000
Ending MRR	$11,300

Customer churn is 5 ÷ 100 = 5% for this month. Gross revenue retention excludes expansion and new customers: ($10,000 − $500 − $200) ÷ $10,000 = 93%. Net revenue retention includes expansion from the starting cohort but excludes new customers: ($10,000 − $500 − $200 + $1,000) ÷ $10,000 = 103%.

These values are arithmetic examples, not healthy-market benchmarks. Define whether cancellations count at notice or service expiry, how discounts and failed payments are handled, and which usage charges enter recurring metrics. Use consistent cohort and period boundaries. Ending MRR does not equal the month’s recognized revenue, particularly when changes occur partway through the month.

Revenue is not margin or cash runway

In a separate hypothetical month, assume recognized revenue of $10,000 and $3,000 in consistently classified direct service costs, including hosting, payment processing, and delivery support. Gross profit is $7,000 and gross margin is ($10,000 − $3,000) ÷ $10,000 = 70%. Sales, general administration, and product-development expenses still affect operating profit; confirm cost classification with an accountant.

If acquiring ten paying customers costs $5,000 in attributable sales and marketing expense, illustrative CAC is $500 per customer. At $100 monthly revenue and 70% gross margin per customer, a simple gross-margin payback calculation is $500 ÷ $70 ≈ 7.1 months. This assumes no churn or contraction and stable monthly contribution. A customer who leaves earlier may never repay acquisition cost. With limited retention history, avoid presenting a precise lifetime-value forecast as established fact.

Choose a pricing model around customer value and cost

Model	Useful when	Risk to examine
Flat subscription	A bounded service has similar value and delivery cost across customers	Heavy users may cost more than they pay
Per seat	Value reasonably tracks participating users	Seat restrictions may discourage collaboration
Usage based	A measurable unit tracks value or cost	Unpredictable bills and metering disputes
Tiered packages	Segments need different capacity or administrative features	Confusing limits and unnecessary scope
Hybrid	A base commitment and variable use both matter	More complex quoting, billing, and reconciliation

Freemium means an ongoing free tier with an optional paid offer. An upsell moves an existing customer to additional paid value; a paid add-on alone is not freemium. A free trial is time-limited access under disclosed terms.

Test comprehension, willingness to pay, and actual delivery cost using the SaaS pricing validation guide before expanding features. Security needed to protect every customer belongs in the baseline service, regardless of packaging.

Operate the promise after each sale

Updates can improve the service, but they need testing, release control, communication, and recovery. SaaS does not automatically include every future feature or remove software licensing terms. Define availability commitments, support coverage, permitted use, integrations, export, retention, and cancellation in the offer.

Potential advantages include centralized maintenance, recurring customer relationships, and shared delivery infrastructure. Costs include continuing support, security, infrastructure, vendor dependence, and responsibility for outages. Customers may face migration effort and switching costs; providers may face competitive pricing pressure. Verify these for your segment rather than promising effortless scaling or universal cost savings.

Make stage-specific decisions

Early stage: prove one recurring job

Identify a specific user and budget owner, deliver a narrow outcome, and track repeat use and payment. Keep a budget for support and iteration. Bootstrapping, customer funding, and external investment are alternatives whose fit depends on cash needs and risk.

Growth stage: test repeatability

Review acquisition by channel, onboarding effort, retention by cohort, customer concentration, gross margin, and delivery capacity. More revenue can conceal rising support cost or weak retention. Scale only the channel and workflow that have evidence behind them.

Established product: maintain value and resilience

Review pricing, product use, renewals, reliability, security, and emerging alternatives. Established status does not guarantee profitability. Product-market fit signals should continue to inform expansion decisions.

Diagnose before adding growth tactics

If prospects do not activate, inspect the job and onboarding. If active accounts leave, investigate lost value, service problems, price, and changing needs. If revenue grows while margins fall, examine customer mix and variable costs. If cash falls despite an attractive MRR chart, inspect collection timing, prepaid obligations, acquisition spending, and the operating budget.

Content, paid channels, affiliates, and expansion offers are experiments. No channel has universally superior conversion. Compare qualified acquisition and retained gross profit, account for incentives and attribution, and avoid forcing a statistical conclusion from a small sample.

Turn the model into a build brief

Before commissioning a SaaS build, write the customer job, tenant model, pricing unit, billing states, permission boundaries, success metric, operating budget, and owner for support. Hapy can help scope those SaaS technology decisions; review Hapy’s MVP development approach when the next investment is clear.