SaaS magic number
The SaaS magic number relates new recurring revenue to the sales-and-marketing spend that produced it. A common form divides the annualized increase in recurring revenue in a quarter by the prior quarter's sales-and-marketing cost. It estimates how much new annual recurring revenue each dollar of go-to-market spend generates. It is a venture-finance convention with several formula variants.
What this means
A common SaaS magic number formula is: (current-quarter recurring revenue − prior-quarter recurring revenue) × 4 ÷ prior-quarter sales-and-marketing spend. Multiplying the quarterly revenue gain by four annualizes it, so the result estimates new annual recurring revenue produced per dollar of the previous quarter's go-to-market spend. The one-quarter lag reflects that spend takes time to convert.
Variants and limits
There is no single canonical formula — some versions use gross margin-adjusted revenue, different lags, or net-new ARR directly. Because of that, magic numbers are comparable only when the same construction is used. The metric also assumes a stable lag between spend and revenue, which breaks for long or lumpy sales cycles, and it says nothing about retention after acquisition. Read it together with payback period and net revenue retention rather than alone.
This page is educational and not financial advice.
- (ΔQuarterly recurring revenue × 4) ÷ prior-quarter S&M spend
- Annualizes the quarterly revenue gain against go-to-market cost
- Multiple formula variants exist — match before comparing
How it appears in analytics and logs
A higher magic number means each dollar of prior-period S&M spend produced more new annualized recurring revenue. A low number suggests go-to-market is inefficient and scaling spend may not pay back.
Diagnostic use case
Gauge how efficiently sales and marketing spend converts into new recurring revenue, to decide whether to accelerate or pull back go-to-market investment.
What WebmasterID can help detect
WebmasterID measures marketing-driven acquisition and conversion first-party, helping attribute the revenue side of go-to-market efficiency without third-party tracking.
Common mistakes
- Assuming a single canonical magic-number formula.
- Ignoring the spend-to-revenue lag for long sales cycles.
- Reading it without retention or payback context.
Privacy and accuracy notes
The magic number combines aggregate revenue and spend figures and uses no personal data. This page is educational and not financial advice.
Related pages
- Burn multiple
The burn multiple divides net cash burned in a period by the net new annual recurring revenue (ARR) added in the same period. It answers: how many dollars of cash did the company spend to add one dollar of new recurring revenue? A lower multiple means more efficient growth. It is a startup-finance convention popularized as a capital-efficiency gauge, not an accounting standard.
- Blended customer acquisition cost (CAC)
Blended customer acquisition cost (CAC) divides total acquisition spend over a period by the total number of new customers acquired, mixing paid and organic together. It differs from paid CAC, which divides only paid spend by only paid-acquired customers. Blended CAC answers 'what did each new customer cost on average overall,' while paid CAC isolates channel efficiency — both are valid, for different questions.
- CAC payback period
The CAC payback period is the time required for the gross margin a customer generates to repay their acquisition cost. It complements the LTV-to-CAC ratio by adding the dimension of time: two businesses with the same ratio can have very different cash dynamics if one recovers its spend in months and the other in years.
- Attribution analytics
Attribute the revenue side of go-to-market spend.
Sources and verification notes
- U.S. SEC — investor guide to financial statementsBackground on revenue and expense concepts; the SaaS magic number is a venture-finance convention with several variants.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.