P/S Ratio Calculator
Solve the price-to-sales relation P/S = Market Cap / Annualized Revenue for any of its three unknowns — P/S ratio, market cap, or annualized revenue — with step-by-step math, a clean valuation schematic, and companion metrics including implied revenue at peer multiples and fair-value pricing.
P/S is the "price per dollar of revenue"
A P/S of 10 means you are paying $10 of market cap for every $1 of annual revenue. If the company or protocol never grew and never reinvested, it would take 10 years of revenue to equal the current market cap. A P/S of 1 means you are paying exactly 1 year of revenue. A P/S of 100 means 100 years. P/S is popular because revenue is harder to manipulate than earnings — there is no depreciation schedule or one-off charge to game — so it gives a cleaner cross-company comparison than P/E in many cases.
Growth rate drives the acceptable multiple
A mature utility with 2% revenue growth might trade at P/S 1–3. A 20% grower might trade at 5–10. A 60% grower (top-tier SaaS, hot DeFi) can justify 15–40. The reason is simple arithmetic: if revenue doubles every 3 years, today's P/S of 30 becomes 3.75 in 3 years and 0.47 in 6 years at the same market cap. High multiples are bets on future revenue, not current pricing. This is why P/S alone is not enough — you must pair it with the growth rate.
Margins and revenue quality matter
Two companies with the same P/S can be wildly different investments if their margins differ. A 10× P/S on 80% gross margin software is very different from a 10× P/S on 5% gross margin distribution. The richer metric is P/S ÷ margin, or its cousin, P/Gross Profit (also called P/GP). Many value investors now use P/GP instead of P/S because it normalises for the cost of the revenue. If you are comparing two P/S ratios, check the margin structure before concluding one is cheaper.
For crypto protocols, revenue is not always protocol revenue
In crypto, the phrase "protocol revenue" is contested. Total fees paid by users (like Uniswap's trading fees) may all go to liquidity providers, with only a slice going to the protocol. Protocol revenue usually means the portion that accrues to the DAO treasury or token holders — from token buybacks, fee switches, or direct treasury fees. Using total fee volume as the denominator inflates revenue and shrinks P/S, making the protocol look cheaper than it is. Always check whether the number you are using is total fees or protocol revenue.
How to Use This Calculator
The P/S relation links three quantities: P/S, MCap, and Revenue. Pick which one you want the tool to solve, then fill in the other two.
1. Choose what to solve for
Pick P/S, MCap, or Revenue from the toggle. The calculator rearranges P/S = MCap / Revenue automatically for whichever you choose.
2. Use realistic presets
Presets cover the range: MCap from $10M (micro-cap) to $1T (mega-cap), Revenue from $100K (early protocol) to $10B (mature mega-cap), and P/S from 0.5× (deep value) to 100× (hyper-growth narrative).
3. Pick the right revenue definition
Use trailing-twelve-month (TTM) revenue or the most recent quarter × 4. For crypto, use protocol revenue (fees that go to the treasury or token holders), not total fees paid by users. The choice of revenue definition can change the P/S by 5–10× for the same protocol.
4. Read the result and verdict
The result card shows the P/S ratio plus the implied market cap per unit of revenue and the years of revenue needed to equal the market cap. A colour-coded verdict classifies the multiple from deep value through mega-cap narrative.
5. Check the schematic and chart
The schematic shows the MCap bar over the Revenue bar, divided into a P/S result card. The fair-value chart plots the implied market cap at different P/S levels, with the current P/S marked.
6. Switch to Advanced for depth
Advanced mode adds a log-log chart showing the revenue needed to justify different P/S levels, a sensitivity check on a +1% change in either input, and companion metrics including implied fair value at peer multiples, revenue multiple at peers, and margin-adjusted metrics.
What This Tool Offers
Built around the classic valuation relation P/S = MCap / Revenue, the fundamental link between market value and revenue generation.
Three-way solving
Solve for P/S ratio, market cap, or annualized revenue. The calculator rearranges the formula for whichever variable you choose.
Clean valuation schematic
A MCap column ÷ Revenue column = P/S result card, with live bar fills that scale to the input magnitudes and a live readout of the exact calculation.
Multiples verdict
Each result is classified from deep value (P/S < 1) through low, fair, high-growth, SaaS/DeFi, narrative, and mega-cap narrative (P/S > 100).
Multi-unit hints
Each field shows related quantities — years of revenue to equal market cap, implied revenue at peer multiples, and margin-adjusted P/S.
Dual comparison charts
A fair-value curve showing implied market cap at different P/S levels, plus an advanced log-log chart of the revenue needed to justify different multiples.
Reference tables
P/S ranges by sector, a P/S lookup grid at $1B market cap, implied fair value at peer multiples, and a full variable reference.
Reference Tables & Conversions
A live P/S solver, a lookup grid, and typical P/S ranges by sector.
Quick P/S solver with peer comparison
P/S Lookup at $1B Market Cap
Computed from Revenue = MCap / P/S with MCap fixed at $1B.
| P/S ratio | Implied revenue | Years of revenue = MCap | Growth needed to reach P/S 10 in 5 yrs | Typical sector |
|---|
Typical P/S Ranges by Sector
Representative P/S multiples across public markets and crypto. Ranges are wide and shift with market regime.
| Sector / asset class | Typical P/S range | Notes |
|---|---|---|
| Utilities / regulated energy | 1 – 3× | Low growth, stable cash flows, often dividend-paying |
| Retail / distribution | 0.3 – 1.5× | Thin margins, high revenue per dollar of capital |
| Consumer staples | 1 – 3× | Steady demand, modest growth |
| Industrial / manufacturing | 1 – 3× | Cyclical, capital-intensive |
| Banks / financials | 2 – 5× | P/S less relevant; P/B or P/E preferred |
| Healthcare / pharma | 3 – 6× | Depends heavily on pipeline and patent cliff |
| Large-cap tech (mature) | 4 – 8× | Apple, Microsoft, Alphabet range |
| High-growth SaaS | 8 – 25× | 80%+ gross margin, 30–50% growth |
| Hyper-growth SaaS | 20 – 50× | 50%+ growth, path to profitability narrative |
| DeFi blue-chips (Uniswap, Aave) | 5 – 30× | Highly variable; protocol revenue definition matters |
| L1 / L2 protocols | 20 – 200× | Often valued on fees not revenue; narratives dominate |
| Memecoins | N/A – ∞ | No revenue to speak of; P/S does not apply |
P/S vs. Other Multiples
Different multiples work better in different contexts. This table compares the major ones.
| Multiple | Formula | Best for | Weakness |
|---|---|---|---|
| P/S | MCap / Revenue | Early-stage companies, cross-sector comparison, unprofitable growth | Ignores margins and profitability |
| P/E | MCap / Net Income | Mature profitable companies | Useless for loss-makers; distorted by one-offs |
| P/GP | MCap / Gross Profit | Software, high-margin businesses | Requires clean gross margin data |
| P/FCF | MCap / Free Cash Flow | Cash-generative mature businesses | Noisy quarter to quarter; capital-intensive distortion |
| P/B | MCap / Book Value | Banks, financials, asset-heavy businesses | Meaningless for asset-light tech |
| EV/EBITDA | Enterprise Value / EBITDA | Cross-capital-structure comparison, M&A | Ignores capex and taxes |
| P/TVL (crypto) | MCap / Total Value Locked | DeFi protocols with deposits | TVL can be double-counted or incentivised |
| P/Fees (crypto) | MCap / Total Fees | L1s and exchanges | Total fees ≠ protocol revenue |
Variable Reference
| Symbol | Meaning | Typical range | Units |
|---|---|---|---|
| P/S | Price-to-sales ratio | 0.1 – 1000 | × |
| MCap | Market capitalisation | 1e5 – 1e13 | USD |
| Rev | Annualized revenue (TTM) | 1e4 – 1e11 | USD |
| Growth | Year-over-year revenue growth | −50 – +200 | % |
| Margin | Gross or net margin | 5 – 95 | % |
| P/GP | Price-to-gross-profit | 1 – 100 | × |
What Does P/S = MCap / Revenue Measure?
The price-to-sales ratio connects three quantities that every investor and analyst works with: the market's valuation of an asset (MCap), the revenue the underlying business or protocol generates each year (Revenue), and the resulting multiple (P/S). It is one of the simplest and most robust valuation metrics — it tells you how many dollars of market value the market assigns per dollar of annual revenue, and by extension roughly how many years of current revenue it would take for the business to "pay back" the current price if nothing changed.
P/S Ratio Formula
The defining relationship is:
Rearranged to solve for the other two unknowns:
Revenue = MCap / P/S
From these, additional metrics follow directly:
Implied fair value at peer P/S = Peer P/S × Revenue
Implied revenue needed to justify current MCap at peer P/S = MCap / Peer P/S
Revenue CAGR needed to reach target P/S in N years = (Target P/S / Current P/S)^(1/N) − 1
P/S Variables
| Symbol | Meaning | Notes |
|---|---|---|
| P/S | Price-to-sales ratio | MCap divided by annual revenue |
| MCap | Market capitalisation | Price × circulating supply (crypto) or shares outstanding (equity) |
| Rev | Annualized revenue | Trailing twelve months, or most recent quarter × 4 |
| Growth | Revenue growth rate | The single largest driver of what P/S is "fair" |
| Margin | Gross or net margin | Normalises P/S across business models with different cost structures |
How Each Variable Affects the Multiple
The P/S ratio is arithmetic, but interpreting it requires context that the formula alone does not supply. Two companies with identical P/S can be drastically different investments: one growing at 40% with 80% margins, the other growing at 2% with 5% margins. The first deserves a high P/S; the second almost certainly does not. This is why analysts use P/S alongside growth, margin, and cash flow metrics, and why P/S is best used as a comparison tool within a sector rather than across sectors.
A useful exercise is to invert the question: instead of asking "is this P/S cheap?", ask "what growth rate would justify this P/S at a mature multiple?" If your peer group trades at P/S 5 when mature, and the target trades at P/S 20 today, then the target must grow revenue 4× to reach mature multiple parity at constant market cap. That is a specific, checkable prediction about the business — much more useful than a vague sense that "20 sounds expensive."
In crypto specifically, P/S is a relatively new metric and the definition of "revenue" is contentious. Some protocols count total fees paid by users as revenue, even though those fees go to liquidity providers rather than the protocol itself. Others count only the slice that accrues to the treasury or token holders via fee switches and buybacks. The difference can be 5–10× for the same protocol, producing wildly different P/S ratios. When comparing two DeFi protocols, always check that both P/S figures use the same revenue definition. Otherwise you are comparing apples to oranges.
P/S Ratio Calculation Examples
P/S = 1,000,000,000 / 100,000,000 = 10.00×
MCap = 5 × 100,000,000 = $500,000,000
Revenue = 1,000,000,000 / 20 = $50,000,000
CAGR = (30 / 10)^(1/5) − 1 = 3^(0.2) − 1 = 24.57% per year
Frequently Asked Questions
There is no universal answer — it depends entirely on the growth rate, margins, and durability of the revenue. A mature utility with 2% growth and stable cash flows is fairly valued at P/S 1–3. A high-growth SaaS company growing 40% with 80% gross margins might justify P/S 15–25. A hyper-growth company growing 60%+ with a large addressable market can support P/S 30–50. The right way to use P/S is to compare within a peer group, adjust for growth and margin, and then ask whether the gap is justified. A P/S of 10 is cheap for a 50% grower and expensive for a 5% grower.
Because P/E does not work for loss-making companies (the denominator is negative or zero), and it can be distorted by one-off items like writedowns, tax credits, or stock compensation. Revenue is reported under more consistent accounting than net income, and is much harder to manipulate in the short term. This makes P/S the standard multiple for early-stage companies, high-growth SaaS, and most DeFi protocols, none of which may have meaningful earnings. The trade-off is that P/S ignores margins entirely, so a low P/S on a low-margin business is not actually cheap.
This is one of the most contested terms in crypto. Total fees paid by users is the gross amount — for a DEX like Uniswap, most of it goes to liquidity providers. Protocol revenue usually means the portion that actually accrues to the protocol or its token holders: buybacks, fee switches, treasury revenue, or direct protocol fees. For some protocols this is zero (Uniswap historically had no fee switch), meaning the P/S is technically infinite. For others (like some DEXs that have turned on fee switches) it is a meaningful fraction of total fees. Always check which definition a P/S source is using before comparing protocols.
For crypto, use circulating market cap (price × circulating supply) to stay consistent with revenue that accrues to current holders. Fully diluted valuation (FDV) uses max supply and produces a much higher number for tokens with large locked or unvested allocations. Both metrics are useful, but they answer different questions: circulating MCap tells you what the market is paying for current float; FDV tells you what the market is paying for the eventual full supply. Many analysts quote both. If you use FDV as the numerator, use it consistently — and consider whether the revenue basis is current or projected.
Trailing twelve months revenue is the sum of the last four quarterly revenue figures, in order, most recent last. For a company reporting quarterly, add Q1 + Q2 + Q3 + Q4 from the last four quarters. For a protocol reporting monthly (common in DeFi), add the last 12 monthly revenue figures. If you only have the most recent quarter, multiply by 4 as a rough annualisation — but this ignores seasonality and can overstate or understate the true trailing figure by 20% or more for businesses with strong seasonal patterns.
Margin-adjusted P/S (sometimes called P/Gross Profit or P/GP) divides market cap by gross profit instead of revenue. This normalises for the cost of producing the revenue, so a 10× P/S on an 80% margin business (equivalent to 12.5× P/GP) is not the same as a 10× P/S on a 10% margin business (equivalent to 100× P/GP). Most value investors now prefer P/GP over P/S for exactly this reason — it lets you compare companies with very different business models on a more like-for-like basis. If you have access to gross margin data, using P/GP alongside P/S gives a much more reliable picture.
No. Market cap is always positive (price and supply are positive) and revenue is normally positive. If revenue is negative — which would require refunds and reversals exceeding sales, an extremely rare situation — P/S is undefined or negative, which means the metric does not apply. The same goes for companies or protocols with zero revenue: dividing by zero gives infinity, and P/S is meaningless. In those cases, valuation has to rely on other metrics — user counts, TVL, volume, or comparable-company analysis on projected future revenue.
Variables
| Symbol | Quantity | Unit |
|---|---|---|
| P/S | Price-to-sales ratio | |
| Market Cap | Protocol token's market capitalization | currency |
| Annualized Protocol Revenue | Protocol's annualized fee/revenue generation | currency |
What it means
The Price‑to‑Sales (P/S) ratio is used to value protocols that generate revenue (e.g., from fees). A lower ratio may indicate undervaluation. This is used in fundamental analysis of DeFi and other revenue‑generating crypto protocols. Understanding this helps investors assess the valuation of protocols relative to their earnings.
Worked example
Price‑to‑Sales Ratio – Two Detailed Examples
Real‑World| Parameter | Value |
|---|---|
| Market Cap | $2,000,000,000 |
| Annualized Revenue | $50,000,000 |
| Parameter | Value |
|---|---|
| Cap | $500,000,000 |
| Revenue | $25,000,000 |
Common mistakes
- Price‑to‑Sales (P/S): Market cap divided by annualised protocol revenue.
- Market cap: The current market capitalisation.
- Annualised protocol revenue: The projected annual revenue of the protocol (e.g., fees).
- Lower P/S: May indicate undervaluation (similar to traditional finance).
Applications
Price‑to‑sales ratio (protocol revenue) compares market cap to annualised protocol revenue, similar to the traditional P/S ratio. This is used to value protocols that generate fees. Investors use it to gauge whether a protocol is overvalued relative to its revenue. A lower P/S may indicate value. Understanding this metric helps in DeFi investment analysis.
- Valuation of revenue‑generating DeFi protocols
- Comparing protocols based on revenue efficiency
- Identifying potential undervaluation opportunities
- Fundamental analysis for protocol investments
- Educational understanding of revenue metrics
Related calculators · Technical & Market Analysis
Recently updated formulas
Suggest an improvement
Found a mistake? Have a better example? Let us know.
You may send up to 3 suggestions per 24 hours.