QoE & Sell-Side Prep for SaaS Companies
SaaS gets valued on revenue quality, which is a polite way of saying a buyer will spend two weeks deciding whether your ARR is as real and as sticky as your pitch deck claims. This is where you make sure the answer is yes, in writing, before they ask.
What a buyer is really paying for
A SaaS buyer is paying for the durability of recurring revenue, not the top-line growth chart. The metrics that set the price are annual recurring revenue and how it's defined, net revenue retention, gross and logo churn, and gross margin after real cost of hosting and support. A business with high, sticky, well-defined ARR earns a revenue multiple; one where ARR quietly includes one-time services and hopeful renewals does not.
The accounting core is revenue recognition. Subscriptions are earned over the term, which means most of what you collect up front is deferred revenue — a liability, not income. Buyers scrutinize how you recognize revenue, how you treat setup and services, and whether contracted ARR ties to signed agreements. Getting recognition and the ARR bridge right is the entire ballgame.
EBITDA matters for profitability, but for SaaS the revenue-quality metrics decide the multiple — and clean, defensible definitions decide whether a buyer believes them.
The ARR bridge and retention proof
The usual add-backs apply — founder comp, personal expenses, one-time fundraising or R&D costs — and they matter for the profitability picture. But the numbers that move a SaaS deal are the recurring-revenue metrics: a defensible ARR definition, a bridge showing new, expansion, contraction, and churned ARR, and cohort retention that proves customers stay.
We build the ARR walk from signed contracts, quantify net and gross retention with real cohort data, separate recurring subscription revenue from one-time services, and correct deferred-revenue treatment — so a buyer's diligence confirms the recurring engine rather than discovering it's smaller than advertised.
How Kaizen runs it
We run a diligence-grade scan of your trailing twelve months, tie ARR to signed contracts, build the new/expansion/contraction/churn ARR bridge, quantify net revenue retention and cohort behavior, correct deferred-revenue recognition, separate services from subscription, and build the profitability bridge a buyer's QoE firm will respect. You get a workbook, a narrative memo, and a clean-up list of the things to fix before the buyer's team finds them.
The goal: present ARR that ties to contracts and retention that holds up in cohorts, so diligence confirms your revenue quality instead of quietly repricing it.
What's included
- Defensible ARR definition tied to signed contracts, not projections
- ARR bridge: new, expansion, contraction, and churned recurring revenue
- Net revenue retention and gross/logo churn quantified with cohort data
- Recurring subscription revenue separated from one-time setup and services
- Deferred-revenue recognition corrected so income matches the subscription term
- Gross margin restated after true hosting and support costs
- Founder compensation and one-time costs normalized as documented add-backs
- Narrative QoE memo plus a defensible workbook you can hand to advisors
Pricing
Straight answers
My ARR number moves depending on who calculates it. Is that bad?
It's a red flag waiting to happen. If ARR isn't defined consistently and tied to signed contracts, a buyer will build their own definition — and theirs will be smaller. Locking down a defensible ARR definition and bridge is the first thing we do, because everything downstream hangs on it.
How much does net revenue retention actually matter?
A lot — it's often the metric a buyer anchors the multiple on. Retention above 100% means the base grows even without new sales, which is exactly the durability a buyer pays up for. We prove it with cohort data so it survives diligence rather than living only in the pitch.
We recognize revenue when we get paid. Problem?
Yes — subscriptions are earned over the term, so collecting up front creates deferred revenue, not immediate income. Recognizing on payment overstates current revenue and understates the deferred balance, and diligence will correct both. We fix the recognition so the numbers hold.
Isn't this what the buyer's QoE firm does anyway?
They do it to protect the buyer, and their ARR and retention math is skeptical by design. Sell-side prep runs it first, on your side, so you bring proof instead of claims.
Related
Free 20-minute books assessment
We'll show you the five things we'd fix first in your books — useful whether you hire us, hire someone, or do neither.
Talk to SalesOr call us directly: +1 786 789 0969