Pre-Revenue Valuation Guide

Why revenue multiples fail pre-revenue assets

Traditional acquisition valuation uses revenue multiples — "3× ARR" or "12× MRR." That works when revenue exists. When it doesn't, buyers either walk away or grossly underprice real IP.

Pre-revenue doesn't mean no value. It means the value sits in what the asset unlocks rather than what it currently produces. But the follow-up question matters enormously — and for several years the industry, DayXero included, was asking the wrong one.

Why "what would it cost to rebuild?" stopped working

The obvious replacement for revenue multiples was replacement cost: what would it cost to hire developers and rebuild this from scratch? A $200K rebuild commands more respect than a $10K prototype.

That logic held until roughly 2024. It doesn't hold now.

AI code generation has collapsed the cost of producing software. A platform that genuinely took $80K and eight months to build in 2023 can often be approximated in weeks by a competent developer with current tooling. Weekly SaaS product launches roughly tripled through 2025. Rebuild cost is deflating every quarter, and any valuation anchored to it is anchored to a melting number.

We're stating this plainly because we used to anchor on it. Replacement cost is no longer a defensible price floor. If a marketplace tells you otherwise, ask what happens to that number next year.

The useful insight is what follows. If code is becoming commodity, then everything that isn't code is becoming more valuable, not less. That is where durable value now sits, and it is what the Asset Durability Report measures.

The 90-Day Test

Every question in the ADR reduces to one:

Could a competent competitor, with unlimited AI tooling and $50,000, reach this exact position within 90 days?

If yes, the asset has close to no moat — however sophisticated the codebase. If no, something specific is blocking them, and that blocker is what you are actually buying.

Note what the test is not. It is not "could this be built." Almost anything can be built. The test is whether the position can be reached. Only four blockers survive that scrutiny:

• Time — calendar months that cannot be compressed. Money and compute do not age a domain.
• Permission — a third party has to say yes. Approval queues are not a technical problem.
• Data — records that exist only because the thing actually ran. Synthetic data is not true data.
• Embedment — users and integrations that already depend on it. Distribution is the hardest thing on earth to rebuild.

The four moat axes

Each axis scores 0–25. Together they produce a Moat Score out of 100.

Time moat. Domain age, backlink profile, review and rating history, months genuinely live with users. The purest moat, because it is non-negotiable — no amount of capital ages a domain.

Permission moat. Regulatory licences, restricted API or banking partnerships, compliance certifications like SOC 2 or HIPAA, approval in gated app store categories. The integration takes an afternoon; the approval takes nine months and may never arrive.

Data moat. Volume of proprietary records, how unique they are, and whether the data measurably improves the product. With one critical qualifier: data that cannot legally transfer to you is worth less than nothing. If user consent didn't cover a change of control, or a processor agreement forbids it, you inherit a liability rather than an asset. The ADR scores that negatively. Most valuation methods ignore it entirely.

Embedment moat. Active users with genuine usage, third parties who have integrated against the asset, contracted commitments, and how costly switching would be. Registrations are not embedment. Usage is.

Commodity Risk: the number sellers dislike

Every ADR publishes the inverse of the moat score — what share of the asset is reproducible code.

An asset on a mainstream stack with no novel algorithm, or a thin wrapper over third-party APIs, scores high commodity risk. One carrying a proprietary model or genuinely novel algorithm scores lower.

Sellers rarely enjoy seeing this number. We publish it anyway, because a valuation you can only trust when it flatters the seller isn't a valuation. It also gives sellers a concrete reason to build real moats before listing — which improves what you see on the deal board.

What build cost still tells you

Replacement cost hasn't become worthless. It changed meaning.

You are not primarily saving developer salary — that saving is shrinking every quarter. You are saving elapsed time in a market where the window is often the whole game. Six months of build time skipped is six months of market presence a competitor doesn't have.

That is why the first DX Score quadrant is now called Time-to-Position rather than Replacement Cost. Same measurement — development cost and months to build — read as months of market entry skipped rather than dollars saved.

Time-to-Position sets the base of the valuation range. The moat sets the multiple applied to it.

Reading DX Score and Moat Score together

They answer different questions, and confusing them is the most common valuation mistake in this market.

• DX Score — is this asset any good today? It decides whether the asset makes your shortlist.
• Moat Score — will it still be good in five years? It decides what you should pay.

Combining them produces a durability projection. Two assets can both score DX 78 today and diverge sharply:

• A thin API wrapper on a new domain with a handful of users — Moat 9, projecting to DX 35 in five years. Eroding.
• A licensed fintech with six years of domain history, millions of proprietary records and 7,000 active users — Moat 93, projecting to DX 71. Fortified.

Identical scores today. Very different assets. Price the second accordingly, and be sceptical of anyone pricing the first as though it were the second.

Arriving at a number: how to make your first offer

A principled first offer starts from Time-to-Position, applies the moat multiple, then adjusts for your own circumstances.

Step 1 — Start with the ADR range. The range is anchored to Time-to-Position and multiplied by moat strength. A Fortified asset carries roughly 1.3–2.8× its time-to-position figure; an Open Field asset carries 0.1–0.5×. Two assets that cost the same to build are not worth the same.

Step 2 — Add strategic fit. The ADR prices an asset generically. It cannot know that a KYC module saves you six months of compliance work, or that a competitor acquiring it would hurt. Ask what this unlocks that you couldn't build faster, what the delay costs you, and what happens if someone else gets it first. That calculus is where much of the value in any specific deal sits.

Step 3 — Adjust for deal structure. An outright acquisition costs more than a licence, because the seller gives up future optionality. A revenue share shifts risk onto the seller and should price lower upfront.

Step 4 — Subtract transfer and integration cost. Code transfers easily. Customers, domain reputation and brand do not. And getting the asset running inside your own stack is a real, frequently underestimated cost. Discount for both.

Your offer = ADR range positioned by moat strength, plus strategic premium, minus transfer and integration risk. Write that calculation down before you walk into the deal room. A number you can defend beats a number you feel.