EV/Revenue Calculator
The formula
What the ev/revenue tells you
What the market pays per dollar of sales — the default multiple for profitable-enough-to-ignore-profit companies, used when earnings are absent or depressed.
Calculation: EV/Revenue = enterprise value ÷ annual revenue. Enter your inputs and every substitution is shown below the result.
Reading the result
A revenue multiple is a promise about future margins: 6× revenue can be cheaper than 1× revenue if the first firm converts at 30% and the second at 2%.
Rules of thumb: SaaS cycles 5–15× ARR; services 1–3×; retail <1×; hardware 2–4×
Limitations and best practice
The 2021 lesson: revenue multiples decoupled entirely from any plausible terminal margin for extended periods — treat them as sentiment indicators as much as valuation tools.
This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Frequently asked questions
When is EV/Revenue legitimate?
Does gross margin matter to the multiple?
Source & methodology
Standard valuation multiple; sector ranges from public SaaS compendia (Bessemer, ICONIQ).
EV/Revenue: the number, the method and the caveats
This page was written for one job: turning your own inputs into a defensible figure, with the working shown. There are plenty of pages about EV/Revenue; almost none of them show the working. This one does: the formula, every input, a fully computed example, and a sensitivity analysis calculated live from this engine’s own defaults.
A calculation like this one is worth roughly as much as a careful sentence: it forces several vague considerations into one comparable quantity. Once EV/Revenue is on the table, the argument can stop being about impressions.
The number itself is the easy part. What takes judgement is knowing which inputs are facts in your situation and which are guesses wearing a decimal point — a distinction this page makes explicit for every field above.
Every figure in the prose is generated by the engine rather than written beside it — the worked example resolves to EV/Revenue = 3.02 × on the default inputs, and the sensitivity section ranks the inputs that move the result — Annual revenue first, at ≈11.1 % of the headline for a ten-percent error either way in that input — which is the thread the rest of this guide pulls on.
Every input in EV/Revenue, and what it does to the answer
The engine implements a single stated model: EV/Revenue = enterprise value ÷ annual revenue. There is no hidden coefficient and no login-gated precision — the formula printed is the formula executed, which is also what makes the result citable.
Enterprise value ($) (example value 9,900,000) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. Replace the example with the figure from your own records — the tool recomputes instantly and the printed steps follow your numbers.
Annual revenue ($) (example value 3,275,000) is a quantity rather than a category — precision here is cheap and worth having. The example value is there to demonstrate the mechanics, not to describe your situation — overwrite it.
Revenue growth (%) (example value 16) is a quantity rather than a category — precision here is cheap and worth having. Rates are the most mis-transcribed input on any page like this; copy it from the document rather than retyping from memory.
Gross margin (%) (example value 46) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. Rates are the most mis-transcribed input on any page like this; copy it from the document rather than retyping from memory.
EV/Revenue on the example inputs: the complete substitution
The tool prints its own working; this is the same arithmetic on the example values, reproduced so you can follow it by hand. Starting figures: Enterprise value ($), Annual revenue ($), Revenue growth (%), Gross margin (%). The computed EV/Revenue comes out at 3.02 ×, which the interpretation band labels “Priced on the future — execution must deliver for years”.
- EV/Revenue = $9,900,000 ÷ $3,275,000 = 3.02×
- Revenue multiples only make sense when growth and margin trajectory are stated alongside
EBITDA needed to justify this EV at 10× — $990,000. Read next to the headline, this is the figure that shows the shape of the trade-off.
Growth-plus-margin (rule of 40 read) — 34.4 %. If your inputs change, this is usually the first companion figure to move.
Price per revenue dollar — 3.02 $. Read next to the headline, this is the figure that shows the shape of the trade-off.
Overwrite any input above and every line of this example updates with it — the substitution is live, not a screenshot of somebody else’s numbers.
The EV/Revenue corridor: your result across a realistic band
The honest version of any estimate is a corridor, and this one is cheap to produce: EV/Revenue was recomputed at 5 points along the dominant input, with every other field left untouched.
| Annual revenue setting | EV/Revenue |
|---|---|
| 80 % of the example value | 3.78 × |
| 90 % of the example value | 3.36 × |
| example inputs | 3.02 × |
| 110 % of the example value | 2.75 × |
| 120 % of the example value | 2.52 × |
That spread — 2.52 × at the low end, 3.78 × at the high — is what a careful read of EV/Revenue looks like: a band you can state out loud, with the reason for each edge. Reproduce it in the form above by editing Annual revenue alone; the substitution steps will follow your figures exactly.
Sensitivity: which inputs change EV/Revenue the most
Nobody should have to guess which input matters. The engine was re-run once per field below — ten percent up, ten percent down, everything else frozen — and the results ranked by how far they moved the EV/Revenue. Read it as a map of where EV/Revenue is fragile — drawn for the example inputs, which is the map you want when deciding what to measure carefully.
- Annual revenue +10 % → EV/Revenue = 2.75 × · −10 % → 3.36 × (the EV/Revenue shifts ≈11.1 %)
- Enterprise value: ten percent up gives 3.33 ×, ten percent down gives 2.72 × — ≈10.0 % of the EV/Revenue either way
Annual revenue is the dominant lever here: ten percent either way moves the result by about 11.1 %, from 2.75 × to 3.36 ×. Spend your verification effort there first, and treat Enterprise value as the second priority (≈10.0 % per ten percent). Everything below that can stay approximate, which is a licence to stop chasing data that would not change the decision.
What an EV/Revenue of 3.02 × means in practice
A number on its own is trivia; a number against a range is intelligence. The default case lands in the “Priced on the future — execution must deliver for years” band, and bands are deliberately wide because real situations overlap. Before treating the band as fact, note its width: ten percent either way on Annual revenue already spans 2.75 × to 3.36 ×. The practical reading rules: read the band as a starting hypothesis, then test it: change the two dominant inputs by ten percent and see whether the verdict survives. Verdicts that survive stress are the ones worth acting on.
The comparison worth making is not with somebody else’s EV/Revenue but with the version of your own situation measured last quarter — same formula, same conventions, different inputs.
Common mistakes with EV/Revenue (and the fix)
The 2021 lesson: revenue multiples decoupled entirely from any plausible terminal margin for extended periods — treat them as sentiment indicators as much as valuation tools. This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Stopping at the first plausible answer. If the result surprises you, the productive question is which input would have to be wrong for the surprise to disappear — then go check that input.
This model has its own particular trap: Annual revenue carries ≈11.1 % of the response per ten percent of error, so effort spent elsewhere is largely decorative.
The subtlest error is answering the wrong question precisely. Confirm that EV/Revenue is actually the quantity your decision needs — the arithmetic is flawless either way, which is what makes the mistake invisible.
Six things to confirm before acting on EV/Revenue
- Confirm the example values are plausible for your own situation before replacing them.
- Check that every field the formula needs actually arrived from a document, not from recollection.
- Check Annual revenue before anything else: it is the measured dominant input, ≈11.1 % of EV/Revenue per ten percent.
- Re-run the calculation with a ±10 % stress on the two most sensitive inputs.
- Recompute once with the dominant input deliberately set low, and see whether the decision changes.
- Repeat the ±10 % test on the inputs that matter and see whether the decision — not just the number — still holds.
Five steps from raw inputs to a figure you can defend
The tool does the arithmetic; the routine below is what makes the arithmetic trustworthy. Five steps, a minute total — and afterwards you will know not just what the number is, but which assumption produced it.
Step 1 — start from evidence. The inputs behind EV/Revenue are enterprise value ($), annual revenue ($), revenue growth (%), gross margin (%). Write them down with their source next to each one; if you cannot name where a figure came from, that is the input most likely to be wrong. Suspiciously tidy answers deserve the same scrutiny as untidy ones.
Step 2 — enter the conservative case first. Resist the flattering scenario. Type the inputs you would defend in front of a sceptical reader, read the EV/Revenue (3.02 × for the example values), and note the verdict band. The fastest sanity test is to guess the answer first and see how far the calculation disagrees.
Step 3 — change one input at a time. Nudge a single field by ten percent, watch the headline and its companions move, then undo it. Two or three fields will dominate — the sensitivity table above already ranks them for this engine. The input you reach for first is usually the one you measured longest ago.
Step 4 — stress before you commit. A decision that survives a ten-percent squeeze on its two biggest inputs needs no luck to be sound. One that does not survive is a decision about hope, not about arithmetic. The fastest sanity test is to guess the answer first and see how far the calculation disagrees.
Step 5 — save the story with the figure. A number without its inputs and its date is unusable within a quarter. Record 3.02 ×, the assumptions behind it, and today’s date; your future self will be auditing a stranger’s arithmetic. A calculation you cannot explain to somebody else is a calculation you cannot defend.
The real-world conversations EV/Revenue settles
Most Financial Analysis disagreements are arithmetic disagreements in disguise. When EV/Revenue of 3.02 × sits on the table with its working shown, the conversation stops being about who sounds more confident and starts being about which input is wrong. Repeating a calculation with the same numbers proves only that the arithmetic is reliable — which is worth knowing.
Professionals in Financial Analysis use this style of calculation as a screening filter before spending real money or effort: a quick EV/Revenue check eliminates weak options in minutes, and the survivors earn the deeper, slower analysis. The inputs are the part of the work that nobody else can do for you.
Treat EV/Revenue like a smoke alarm rather than a painting — its value is in being tested periodically, not in being admired once. Estimates improve most when the worst case is written down in ink.
People also ask about EV/Revenue
What affects EV/Revenue the most?
EV/Revenue is driven above all by Annual revenue. Perturbing only that field by ten percent either way produced 2.75 × against the 3.02 × baseline — a ≈11.1 % response, while Enterprise value manages ≈10.0 %.
Which matters more: enterprise value or annual revenue?
By the numbers, Annual revenue: a ten-percent change in it moves the result ≈11.1 %, versus ≈10.0 % for Enterprise value. Spend your measuring effort in that order — precision on the weaker lever buys almost nothing.
What is a typical EV/Revenue?
With the example inputs on this page the result is 3.02 ×, labelled “Priced on the future — execution must deliver for years”. “Typical” varies with situation, which is why every result here ships with its verdict band and its sensitivity list: they turn one figure into a range you can locate yourself inside.
How do I calculate EV/Revenue by hand?
Three steps: write the formula (EV/Revenue = enterprise value ÷ annual revenue), insert your values, and simplify. The worked example section shows exactly that chain for the default inputs; replicating it once on paper teaches you more about EV/Revenue than any number of calculator runs.
What happens to EV/Revenue if annual revenue changes by 10 %?
The engine was re-run with that field moved by ten percent while everything else stayed fixed: the EV/Revenue goes across 2.75 × to 3.36 ×, a swing of roughly 11.1 % around the 3.02 × baseline. That ratio is the practical definition of how much this input matters.
Is the EV/Revenue result of 3.02 × good or bad?
Good and bad are comparisons, so the honest test is three questions: where does your own EV/Revenue sit against the 3.02 × reference above, how far would a plausible input error move it (≈11.1 % per ten percent on Annual revenue), and what does the alternative option compute to?
How do I calculate EV/Revenue manually?
Write down the inputs, then follow the printed steps in order — EV/Revenue = enterprise value ÷ annual revenue. A spreadsheet replicates it with two or three cells. The manual route is worth doing once to build intuition; after that the calculator saves time and eliminates transcription slips.
How often should I check EV/Revenue?
Whenever an input changes by more than a few percent, and otherwise on the rhythm of your decisions — before a purchase, a review, a renewal. EV/Revenue is a snapshot, not a subscription; stale snapshots are the most common silent error in Business & Entrepreneurship planning.
When is EV/Revenue legitimate?
For early-stage or restructuring targets where earnings are meaningless today but the margin path is evidence-based — with the path documented.
Does gross margin matter to the multiple?
It should: two companies at 3× revenue with 20% vs 80% gross margins have almost nothing else in common.
Does this EV/Revenue tool store my numbers?
No. The entire calculation runs in your browser session; nothing entered above is transmitted or saved, which is the correct behaviour for sensitive Business & Entrepreneurship figures and the reason you can re-run this page as often as you like.
The vocabulary of EV/Revenue
- EBITDA needed to justify this EV at 10×
- $990,000 on the example inputs — a companion figure printed beside the headline of EV/Revenue so that no result is read in isolation.
- Growth-plus-margin (rule of 40 read)
- 34.4 % on the example inputs — a companion figure printed beside the headline of EV/Revenue so that no result is read in isolation.
- Price per revenue dollar
- 3.02 $ for the EV/Revenue worked case; it sits next to the main result because it carries context the headline leaves out.
- EV/Revenue
- The primary output of this tool: 3.02 × for the default inputs, computed exactly from EV/Revenue = enterprise value ÷ annual revenue.
- Worked example
- The calculation written out in full so that nothing on this page has to be taken on trust.
- Verdict band
- A named zone on the range of plausible results; the example inputs land in “Priced on the future — execution must deliver for years”, and your inputs may not.
- Sensitivity (±10 %)
- How far the EV/Revenue moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
The provenance of this EV/Revenue calculation
Everything above runs on one stated formula, applied without hidden coefficients: EV/Revenue = enterprise value ÷ annual revenue. Source of record: Standard valuation multiple; sector ranges from public SaaS compendia (Bessemer, ICONIQ). Any other implementation of this model should return the same figure for the same inputs. If one does not, the difference is in its assumptions — which this page prints and that one probably does not.
This page is an estimation aid, not professional advice. The design rule is simple: two people entering identical figures must get identical answers. Nothing is smoothed, weighted or adjusted behind the scenes; where judgement enters, this page says so and names the input responsible.
What to do with your EV/Revenue next
Re-run the calculation with your own figures, stress the two most sensitive inputs by ±10 %, and only then act on the result.
This page was written for people who need one trustworthy number before their next decision, and the promise is that nothing above required trust. Bookmark the tool, re-run it whenever an input moves by more than a few percent, and keep the date with the number.