How is a SaaS company valued?

Start by defining the business and the purpose of the valuation. A cloud software company may combine subscriptions, implementation projects, consultancy, transaction charges and resale income. Those activities have different margins and renewal characteristics, so treating them as one homogeneous revenue stream can obscure value. A valuation for a proposed sale also has a different brief from one prepared for financial reporting or a statutory tax purpose.

The subject might be the whole trading business, all the shares in its holding company or a particular shareholding. Establish which entity owns the software, employs the development team, signs customer contracts and holds cash or borrowings. Where intellectual property sits outside the trading company, the valuation must reflect the actual ownership and licensing arrangements rather than assuming a purchaser receives everything needed to operate independently.

The valuation date matters because SaaS performance can move faster than annual accounts reveal. A major renewal, price increase, security incident or change in funding requirements may affect expectations. The valuer should distinguish information available at the valuation date from later developments, treating subsequent evidence consistently with the purpose of the work rather than automatically valuing the company with hindsight.

Finally, define the basis of value and any transaction assumptions. A strategic buyer may identify cross-selling opportunities or cost savings unavailable to other purchasers, but those benefits should not automatically be attributed to the standalone business. International valuation principles provide a framework for specifying the subject, basis, assumptions and methods; they do not prescribe a single SaaS multiple or guarantee an achievable sale price.

Reference framework:[1] IVSC[3] ICAEW

Annual recurring revenue, or ARR, is an operating metric rather than a universally standardised accounting measure. It commonly annualises the recurring subscription revenue in force at a particular date, but company definitions differ. A defensible valuation states exactly what is included: contracted subscriptions, cancellable monthly plans, usage charges, discounts and paused accounts all require consideration. One-off implementation income should not become recurring revenue merely because new implementations occur every year.

ARR must also be reconciled with recognised revenue, invoices and cash receipts. Annual advance billing can produce cash before the related service is delivered, while a signed contract may not yet contribute to live subscriptions. Uncommenced contracts, free trial users and speculative pipeline should not be blended into current ARR. Where management presents a forward ARR estimate, identify it separately and explain the assumptions needed to achieve it.

Retention shows whether the existing revenue base is durable. Gross revenue retention measures the remaining revenue from an opening customer cohort after losses and reductions, excluding expansion. Net revenue retention also captures expansion within that cohort. In a hypothetical example, an opening annual revenue cohort of £1 million loses £100,000 and adds £150,000 through upgrades: gross retention is 90% and net retention is 105%, assuming no other changes.

The same headline retention percentage can conceal different risks. Expansion from one large customer may offset widespread cancellations among smaller accounts, while customer-count retention can look strong despite losing a commercially significant contract. Analyse cohorts, customer size, product, geography and cancellation reasons. For usage-based software, test whether apparent recurring income reflects sustained customer activity or a temporary spike that annualisation would exaggerate.

Reference framework:[1] IVSC[2] IPEV[3] ICAEW

There is no defensible universal revenue multiple for a private SaaS company. Market evidence must be relevant to the business and valuation date. A listed software group with diversified customers, strong liquidity and global distribution is not directly comparable with an owner-managed subscription business. Equally, a reported acquisition price may incorporate strategic benefits, contingent payments or a different mix of subscription and service revenue.

The numerator and denominator must match. An enterprise value-to-ARR multiple should use a consistently defined enterprise value and a comparable ARR measure. It should not be casually interchanged with an equity value-to-revenue ratio or a multiple of next year's forecast sales. Where comparable information is incomplete, the uncertainty belongs in the analysis rather than being concealed by a precise-looking average.

Relevant comparisons consider growth, retention, gross margin, customer concentration, addressable market and the expenditure required to sustain performance. They also consider scale, governance and dependence on particular individuals. Adjustments need explanation: simply calling a company 'smaller' or 'higher risk' is not enough to demonstrate how the evidence supports the selected valuation range. Apparent comparability should be tested against the underlying business models.

Revenue multiples are particularly sensitive to assumptions about eventual profitability. Two businesses with identical ARR may require very different levels of development, support and acquisition spending. A multiple-based result should therefore be checked against plausible future cash generation and other available evidence. IPEV guidance is relevant to private capital valuation methodology, but it is not a published tariff of SaaS sale multiples.

Reference framework:[1] IVSC[2] IPEV[3] ICAEW

For a mature SaaS company with stable growth and established margins, an earnings-based approach may provide a useful primary method or cross-check. For an earlier-stage company, current losses may reflect deliberate investment rather than an absence of value. The distinction is whether the evidence supports profitable customer relationships and a credible route to cash generation, not simply whether management describes expenditure as investment.

Analyse gross profit after the costs genuinely required to deliver the service. Hosting, third-party software, customer support and implementation resources can materially affect economics, although accounting classifications vary. Customer acquisition cost and payback analysis can help, provided the calculations include relevant expenditure and use consistent cohorts. A short apparent payback period is less persuasive if the acquisition calculation excludes substantial sales salaries or channel commissions.

Software development accounting also needs attention. Capitalising qualifying development expenditure can increase reported operating profit compared with expensing it immediately, while the cash still leaves the business. Where FRS 102 applies, its requirements govern the accounting treatment; the valuation must separately assess the economic expenditure needed to maintain and improve the product. Capitalised development assets are not automatically additional value on top of an income-based valuation.

A discounted cash flow approach makes these dependencies explicit by forecasting cash generation and discounting it for time and risk. Forecasts should reflect support capacity, product investment, tax, working capital and funding needs, with sensitivities for growth and retention. Terminal assumptions deserve particular scrutiny: a forecast that becomes valuable only after unusually high margins or indefinitely strong growth may be describing an aspiration rather than an adequately supported commercial outcome.

Reference framework:[1] IVSC[2] IPEV[4] FRC

Customer concentration affects more than the probability of cancellation. A major account may demand bespoke development, unusually long payment terms or pricing concessions that reduce the value of its revenue. Review contract duration, renewal mechanics, termination rights and any provisions triggered by a change of control. A multi-year agreement is not equivalent to guaranteed cash if contractual rights allow early exit or substantial reductions in usage.

Technology ownership must be established rather than inferred from possession of the code. Employee and contractor arrangements, third-party components and open-source licences may affect the company's rights to use, modify and commercialise its product. A valuer does not replace a specialist legal or technical review. However, unresolved ownership questions can change the valuation assumptions, the expected transaction timetable or the commercial protections a purchaser seeks.

Product resilience matters because recurring revenue depends on continued delivery. Consider platform reliability, security practices, recovery arrangements, scalability and dependence on individual developers or external providers. Technical debt is relevant where it creates identifiable future expenditure or restricts development. It should not become a vague blanket deduction: the analysis should connect a specific weakness to its likely financial consequences and distinguish evidence from speculation.

Growth quality should then be assessed alongside these risks. Revenue supported by diversified demand, repeatable customer acquisition and successful onboarding is different from growth driven by heavy discounting or one unusually favourable channel relationship. Risks can be reflected through forecasts, scenarios or valuation parameters, but the same exposure should not be penalised repeatedly without justification. Otherwise, the valuation may understate value while appearing appropriately cautious.

Reference framework:[1] IVSC[2] IPEV[3] ICAEW

A SaaS valuation and a proposed offer need to be compared on consistent terms. A business value derived from subscription performance does not itself establish the amount payable for the shares. Borrowings, cash, working capital arrangements and other agreed adjustments may affect the equity proceeds. The treatment of each item depends on its economic nature and the transaction definitions, not merely its accounting label.

Consider an explicitly hypothetical company with £1.2 million of assessed ARR. A purely illustrative multiple of four times produces enterprise value of £4.8 million; three times produces £3.6 million. These multiples are arithmetic assumptions, not market benchmarks. The £1.2 million difference demonstrates why defining ARR and supporting the valuation parameter matter more than selecting a number from an unsourced online range.

Annual subscriptions paid in advance require particular care. The cash may have been received, but the business still has an obligation to provide future services. Deferred revenue should not automatically be treated as borrowing or ignored entirely. Its treatment should be consistent with forecast delivery costs, the working capital mechanism and the agreed cash and debt definitions, avoiding double counting across different parts of the price calculation.

An offer may also include deferred consideration, an earn-out or shares in the purchaser. A headline amount payable only if retention or revenue targets are achieved is not equivalent to the same amount in unconditional cash at completion. Evaluate timing, conditions, credit exposure and who controls the relevant business decisions. A standalone valuation helps owners assess the proposal, while transaction and legal advisers address the detailed contractual allocation of risk.

Reference framework:[1] IVSC[2] IPEV[3] ICAEW

Begin with financial information that connects the statutory accounts to current trading. Supply management accounts, budgets and cash forecasts, together with explanations of unusual items and changes in accounting policy. Separate subscription revenue from implementation, consultancy and other income. Identify capitalised development expenditure and the cash costs behind it so that apparent profitability can be reconciled with the resources needed to operate the product.

Prepare a customer-level subscription schedule that reconciles opening ARR to closing ARR through new business, expansion, contraction and cancellation. Include contract commencement dates, renewal dates, billing frequency and relevant discounts. Provide consistent historic periods where available, but do not manufacture missing data. If the billing platform cannot reproduce earlier metrics reliably, explain the limitation and identify alternative evidence rather than presenting estimates as verified records.

The commercial pack should explain the product, customer use cases, competitors and route to market. Forecasts should distinguish contracted revenue, renewal expectations and new sales assumptions, showing the expenditure needed to deliver them. Include material customer contracts, ownership documents and details of funding arrangements. Legal and technical documents can initially be indexed so that the valuer can identify which issues require closer review or specialist input.

Finally, tell the valuer what decision the report must support, who may rely on it and when it is needed. A proposed shareholder transaction, confidential sale planning exercise and financial reporting instruction may require different scopes. Clear instructions and reconciled information reduce avoidable queries, but speed should not come from overlooking gaps. Where evidence remains incomplete, the report should explain the resulting assumptions and limitations.

• Financial records: accounts, current trading, forecasts and development expenditure.
• Subscription evidence: ARR reconciliation, customer cohorts, churn and concentration.
• Commercial and legal records: contracts, software ownership, funding and share rights.

Reference framework:[1] IVSC[3] ICAEW[4] FRC

An independent valuation turns management's operating information into a documented assessment that other decision-makers can interrogate. For a SaaS owner, that means explaining not just a range of values but why recurring revenue is considered sustainable, which comparisons are relevant and how investment requirements affect the result. The objective is a reasoned conclusion, not the highest figure that a spreadsheet can be made to produce.

XVAL's work is human and expert-led, not an automated calculator. The analysis considers the actual business model, financial records, subscription evidence, ownership structure and purpose of the instruction. Relevant methods are selected and reconciled, with material assumptions and sensitivities documented. Where specialist legal, accounting or technical questions sit outside the valuation brief, they should be identified rather than disguised as issues the valuation alone can resolve.

A useful report also separates sources of uncertainty. Incomplete retention data is a different issue from a genuinely uncertain product launch or an unresolved contractual right. Explaining those distinctions helps owners and advisers decide what to investigate, what to negotiate and what to address before approaching purchasers. It can also reveal whether better evidence would narrow the range without requiring any change in the underlying business.

XVAL reviews enquiries on the same working day and establishes the purpose, information requirements and delivery timetable at the outset. Fast delivery depends on a proportionate scope and the availability of reliable records; it does not mean replacing judgement with a formula. For a proposed SaaS sale, the resulting independent assessment gives owners and their professional advisers a clearer foundation for evaluating offers, discussing terms and understanding the assumptions driving value.

Reference framework:[1] IVSC[3] ICAEW

Questions owners ask

Frequently asked questions

Reference desk

Sources & further reading

Legislation states the legal provisions; HMRC manuals describe HMRC’s guidance. Professional standards and research guides inform valuation practice. Illustrations and commercial checklists above are explanatory analysis, not prescribed legal formulas or market benchmarks.

1. [1]IVSC — International Valuation Standards
2. [2]IPEV — Valuation Guidelines
3. [3]ICAEW — Business and share valuation
4. [4]FRC — FRS 102

This article provides general technical information, not legal, tax or investment advice. Its application depends on the facts, the valuation purpose and rules in force at the relevant date. A reference to a professional body does not imply XVAL accreditation or endorsement. All numerical examples are hypothetical, not XVAL fees, client results or market evidence.