Why Micro-SaaS Often Sells at “Only” 2–4× ARR

By Joshua Chen · About / experience · urbanu619@gmail.com

A house can clear twenty-plus years of rent. A micro-SaaS clearing two to four years of recurring revenue looks “cheap” until you price what can vanish overnight.

This page explains the compression, not a price oracle. Use it after you classify the asset (three types).


The planning band (not a promise)

Across public buyer/seller guides checked on 2026-09-30, micro and small private SaaS deals are commonly discussed in roughly:

Lens Band often cited for small / micro deals Notes
ARR multiple about 2×–4× (sometimes ~2.5×–4.5×) Applies when revenue is truly recurring and verified
SDE / profit multiple about 2.5×–4.5× (wider tails) Common when the buyer is buying a job-like owner role
“Dev complete” / no revenue not an ARR multiple Rebuild / time-saved lens only

Sources disagree on medians once you leave the micro tier; some blogs quote higher ARR multiples for cleaner or larger assets. Treat any number as a prior, then underwrite the file.

If ARR is approximately zero, stop reading multiples. You are in Type C territory.


Three fractures that make “low” multiples rational

Think of the product as virtual property. The analogy helps — until it breaks.

1. Distribution can go to zero

Search rank, store featuring, a single API, a social channel — any of these can be repriced by a platform overnight. Brick-and-mortar rarely loses the street outside in one release note.

Buyers therefore refuse real-estate-like 20–30× rent math. They buy a risky cash-flow stream with a kill switch.

2. “Passive income” is usually a story

Unmaintained apps rot: OS changes, dependency CVEs, payment policy updates, support debt. Cash flow is often “keep paying labor so revenue does not fall.”

If the trailing profit only exists because founder labor was free, a 3× ARR sticker is already too high.

3. Title is scattered

Code, domain, trademark, store account, payment entity, API keys, inbox — miss one, and you did not buy the business. That transfer risk is why diligence is not optional (checklist).


When a “low” multiple is still expensive

Low headline multiple can mean:

See also: what not to buy.

Method (anonymous): high traffic + tiny revenue → audit traffic quality and paywall before celebrating “upside.” Near-100% churn → do not average it away. Asking price near or below one year of claimed revenue → ask what the seller knows that the multiple is advertising.

(We do not publish unverified listing financials here. Case studies come later, after re-check.)


A buyer underwriting stack

1. Type A only for ARR multiples; else rebuild lens
2. Read-only revenue, refunds, concentration, trend
3. Retention / churn that matches the story
4. Transfer score (store, domain, payments, data)
5. Your 90-day fix cost (engineering + ops)
6. Then ask: does price ÷ durable profit make sense?

Rough mental model:

Justified price ≈
  verified durable profit
  × risk-adjusted multiple
  − migration and rewrite you cannot avoid

If step 5 eats most of the “bargain,” there was no bargain.


What this is not

For where inventory lives: marketplace comparison.
For buy-or-build routing: decision hub.


Verification log

Claim Basis Date
Micro/small SaaS often discussed near ~2–4× ARR Public guides (e.g. buyer education posts citing 2–4× / 2.5–4× bands) 2026-09-30
SDE multiples often ~2.5–4.5× for owner-operated micros Same class of public commentary; method varies by ARR size 2026-09-30
Higher multiples appear for larger/cleaner assets Same; do not import into micro diligence blindly 2026-09-30

Re-sample live asking multiples on Acquire/Flippa/Microns before you treat any band as “the market.”