Before you trust a 4× slide
SaaS Quick Ratio: a growth-efficiency tripwire that churn can hide
A board slide that prints “Quick Ratio is 4.2” without the four dollars underneath, the period, or what you will do if it misses is not validation. SaaS Quick Ratio asks a smaller, honester question: in this same period, did new plus expansion recurring revenue outrun churned plus contraction — against a bar you wrote first? Matching it is a decision signal — not a forecast that you will succeed, and not a substitute for naming the weakest retention or acquisition assumption first. This is not the accounting acid-test (current assets ÷ current liabilities).
Last updated: October 19, 2026
Direct answer
What is SaaS Quick Ratio — and why write the tripwire first?
SaaS Quick Ratio = (New MRR + Expansion MRR) ÷ (Churned MRR + Contraction MRR). It asks how many dollars of recurring revenue you add for every dollar you lose in the same period. Matching or missing a pre-written tripwire is a decision signal — not a prediction that you will succeed. This is not the accounting “acid-test” quick ratio of current assets ÷ current liabilities, and it is not NRR%.
Key takeaways
What to remember
- SaaS Quick Ratio = (New MRR + Expansion MRR) ÷ (Churned MRR + Contraction MRR). Prefer same-period growth accounting over inventing a proprietary Yibud formula. Use MRR or ARR consistently; do not mix windows. Always report the four components, not only the multiple. Logo/customer churn % is not dollar outflow.
- Mamoon Hamid (SaaStr Annual talk, Social Capital) coined and popularized the SaaS Quick Ratio at SaaStr: brand-new plus expansion, divided by lost plus contracted. A bunch of data, in his wording, suggests four or above is quite desirable — “for every four dollars of revenue that we’re adding, we’re losing about a dollar.” When the ratio drifts toward ~2, “for every two dollars… losing a dollar” — a lot of work just to offset churn. When it approaches ~1, you are on a treadmill: the leaky-bucket nightmare. Top-line ARR can look fundable while the underlying metrics fail.
- Jonathan Hsu (Social Capital, Diligence Part 2): growth accounting splits new, retained, resurrected, expansion, churned, and contraction. For enterprise SaaS, they prefer to invest when Quick Ratio is greater than 4. If it is <2, “your churn is probably too high and you have something to fix.” Subscription revenue is default-retained; visitation businesses are default-not-retained — so subscription Quick Ratios should sit higher. Company A can look like “tons of expansion” while contraction eats it.
- Tomasz Tunguz (3 November 2015): Quick Ratio ≈ (Monthly Growth Rate + Churn Rate) / Churn Rate. A Quick Ratio of 4 can still allow ~5% monthly churn at ~15% monthly growth — about 46% annual revenue loss. His table at QR = 4: 10% / 15% / 20% monthly growth → 3.3% / 5.0% / 6.7% monthly churn possible, and 33% / 46% / 56% annual revenue loss. “Greater Quick Ratios are always better.” High growth can mask high dollar churn. Pair the multiple with an explicit churn / GRR check. Never treat ≥4 alone as proof of health.
- Write the tripwire before you measure: signal (Quick Ratio) + threshold (e.g. ≥4, or “never below 2”) + definition (include/exclude resurrection; MRR vs ARR; monthly vs quarterly) + period + named action (fix retention first / keep experimenting / scale spend / cut leaky channels). A Yibud score is not Quick Ratio and not a success prediction. First Round Levels of PMF do not list Quick Ratio — do not invent bands.
Why it matters
Why a 4× slide can still be a leaky bucket
Founders treat “we are growing” as a feeling that arrives after a good month of new logos. Feelings do not name whether this period’s inflows outran this period’s outflows. Three published sittings are useful here as instruments, not as personal odds: Hamid on the leaky bucket, Hsu on growth accounting, and Tunguz on the churn a 4× can hide.
Hamid: the top line can look fundable while the bucket leaks
Hamid’s SaaStr talk walks a “Not So Fictional” SaaS company whose ARR chart goes up and to the right — the slide everyone wants to raise on — while Quick Ratio drifts from around 4 toward ~2, then toward ~1. At ~2 you are doing a lot of work just to offset churn. At ~1, new dollars barely replace lost dollars: a treadmill. He treats churn, expansion, and contraction of MRR as lagging. The lesson for this page is narrower than his North Star section: do not let a pretty cumulative ARR chart stand in for the four components.
Hsu: same-period growth accounting, not a slogan
Hsu writes the identity: this period’s MRR is new + retained + resurrected + expansion; last period’s MRR is retained + churned + contraction. The change is inflows minus outflows. Quick Ratio compresses that motion into one efficiency number. Enterprise SaaS, in their diligence sitting, is a >4 preference — and <2 is “probably too high” churn you have to fix. That is an investment screen they named, not a proof you will succeed.
Tunguz: a Quick Ratio of 4 can hide unsustainable churn
Tunguz reformulates Quick Ratio as (monthly growth + churn) / churn. Aim at 4, grow 15% in a month, and you can still be losing about 5% of revenue to churn and contraction that month — about 46% annualized. He calls that unsustainably high. “Greater Quick Ratios are always better,” and you still have to watch the underlying churn. A ≥4 tripwire without a churn / GRR column is how a leaky bucket gets a passing grade.
The six terms
Quick Ratio, New, Expansion, Churned, Contraction, tripwire
These six fields are the instrument. If any one is fuzzy, the number is a slide, not a tripwire. This page does not publish a grade table beyond Hamid’s 4-or-above / ~2 / ~1 narrative, Hsu’s >4 and <2 enterprise sitting, and Tunguz’s QR = 4 masking table. Use those, then write your own bar. This is not the accounting acid-test ratio.
SaaS Quick Ratio — same-period inflows ÷ outflows, not the acid-test
Hamid: brand-new revenue from new customers, plus expansion from existing customers, divided by customers you lost or who contracted. Tunguz writes the same sitting as (New MRR + Expansion MRR) / (Churned MRR + Contraction MRR). It is a multiple, usually greater than one if you are adding more than you lose. It is not current assets ÷ current liabilities (the accounting “acid-test” / liquidity quick ratio). It is not NRR%, which is cohort retention of a starting base.
New MRR — newly acquired customers in the period
Recurring revenue from customers who were not paying at the start of this period and are paying now. Hsu counts new separately from resurrection (a previously churned customer who comes back). Write whether resurrection sits inside “new” or gets its own line before you measure. Do not mix a quarterly new-logo dump into a monthly Quick Ratio after the close.
Expansion MRR — incremental spend from customers who already paid
Upsell, cross-sell, or seat growth on accounts that stayed. Hsu: if a customer spent $10 last month and $12 this month, $10 is retained and $2 is expansion. Expansion can make the ratio look kind while contraction on other accounts — or the same account later — eats it. Hsu’s Company A vignette is this sitting in prose: “tons of expansion” largely eaten by contraction.
Churned MRR — accounts that went to zero
Recurring revenue lost when a customer cancels or goes to zero spend. Hsu: dollars are churned only if the customer went to zero. That is not logo count. Ten $200 accounts leaving is a different dollar outflow from two $8,000 accounts leaving. Do not call a logo-churn percentage Quick Ratio.
Contraction MRR — downgrades that did not fully cancel
Recurring revenue lost when an existing customer stays and pays less — seats dropped, plan downgraded, usage shrunk. Tunguz: contractions are customers who decreased their payments. If you fold contraction into “churn” after the close, you changed the definition. Keep it as its own component so the ratio cannot hide a shrinking base that has not fully cancelled.
The tripwire — written before you measure
Signal + threshold + definition (include/exclude resurrection; MRR vs ARR; monthly vs quarterly) + period + named action (fix retention first / keep experimenting / scale spend / cut leaky channels). Write it on a dated page before the first report. A kinder bar after the results is a recap, not a tripwire. Matching the bar is a decision aid. It does not prove you will succeed.
The arithmetic
Growth-accounting math — not a proprietary Yibud formula
There is no Yibud Quick Ratio formula. Use the same-period sitting Hamid and Tunguz actually wrote, name whether resurrection is in or out, and do not swap MRR for ARR after the report. The fictional worked example later on this page is invented so you can see the crossing; it is not a benchmark.
SaaS Quick Ratio (Hamid / Tunguz)
Quick Ratio = (New MRR + Expansion MRR) / (Churned MRR + Contraction MRR)
Same period on every term. Hamid’s wording: new + expansion, divided by lost + contracted. If the denominator is zero (no churn, no contraction), Tunguz notes the ratio is infinite — a startup without churn. Do not invent a “Yibud adjusted Quick Ratio” that quietly drops contraction or adds this quarter’s annualized new logos.
Tunguz restatement — why 4× can hide churn
Quick Ratio ≈ (Monthly Growth Rate + Churn Rate) / Churn Rate. At QR = 4 and 15% monthly growth, monthly churn can be 5.0% (~46% annual revenue loss).
This is Tunguz’s reformulation, 3 November 2015, not a Yibud identity. It is why a ≥4 gate without a churn column is incomplete. His published table at QR = 4: 10% / 15% / 20% monthly growth → 3.3% / 5.0% / 6.7% monthly churn possible, and 33% / 46% / 56% annual revenue loss. He calls those churn numbers unsustainably high.
Same-period crossing (fictional inputs)
Beginning MRR $60,000. New $9,000. Expansion $3,000. Churned $2,400. Contraction $600. Quick Ratio = (9,000 + 3,000) / (2,400 + 600) = 4.0. Net new = $9,000 → 15% monthly growth. Dollar outflow = $3,000 → 5% of beginning.
These dollars are invented so the arithmetic is visible — and so you can see Tunguz’s 15% / 5% / QR = 4 sitting on a page. They are not Hamid’s “bunch of data,” not Hsu’s diligence screen, and not a Yibud report. The 4.0 would clear a ≥4 bar you wrote. The 5% monthly dollar outflow would still be the churn Tunguz called unsustainable. Keep both.
Do not mix a monthly numerator with a quarterly denominator. Do not annualize a 30-day Quick Ratio by multiplying. Do not mix logo counts into the dollar ratio. Hsu’s identity also names resurrection; write whether it sits in the numerator before the first report. The tripwire names the period and the four components first.
Published thresholds
Hamid, Hsu, and Tunguz — labeled, not a grade table
The rows below are what the sources actually named. They are not a Yibud letter-grade chart, not a personal odds table, and not First Round Levels — Levels of PMF do not list Quick Ratio. Use them as vocabulary, then write your own tripwire for the period you can actually measure.
| Source | What they name | How to label it |
|---|---|---|
| Hamid / SaaStr — desirable 4 or above | Coined / popularized at SaaStr. “A bunch of data suggests that a quick ratio of four, is quite desirable, four or above.” In his wording: for every four dollars added, you lose about a dollar that month. | Hamid’s desirable sitting, not a seed law, and not proof you will succeed. |
| Hamid / SaaStr — ~2 then ~1 leaky-bucket narrative | When the ratio hovers close to two: for every two dollars added, you lose a dollar — a lot of work just to offset churn. When it comes down to one: for every dollar added, you lose a dollar — treadmill / leaky-bucket nightmare. Top-line can still look fundable. | Narrative from the Not So Fictional walk-through. Not a deck-slide median. Not a Yibud grade. |
| Hsu / Social Capital — enterprise SaaS screen | “For enterprise SaaS companies, we prefer to invest in companies with a quick ratio greater than 4. If you have a quick ratio of <2 then your churn is probably too high and you have something to fix.” | Their diligence preference, attributed. Not a consumer-app law, and not a success forecast. |
| Hsu — subscription vs visitation; Company A | Subscription is default-retained; visitation is default-not-retained — subscription Quick Ratios should sit higher. Company A (qualitative): lots of expansion, largely eaten by contraction, so they generate expansion just to outrun contraction. | Intuition plus a vignette. No chart numbers copied from his sample. Not an industry median. |
| Tunguz, 3 November 2015 — QR = 4 can hide churn | Reformulation: QR ≈ (monthly growth + churn) / churn. At QR = 4 and ~15% monthly growth, monthly churn can be 5.0%, about 46% annual revenue loss. “Greater Quick Ratios are always better.” High growth can mask high dollar churn. | Required caveat. A ≥4 pass is not a health certificate. |
| Tunguz — published table at Quick Ratio = 4 | Monthly growth 10% / 15% / 20% → monthly churn possible 3.3% / 5.0% / 6.7%; annual revenue loss 33% / 46% / 56%. He calls those churn numbers unsustainably high. | His table, attributed. Not a Yibud “good churn” band, and not a median. |
Tunguz credits Hamid as the creator of the metric in the SaaS context. This page does not invent First Round Quick Ratio bands (Levels do not list it), does not invent industry medians, and does not treat ≥4 as proof you will succeed. Pair every Quick Ratio with an explicit churn / GRR check.
Scope notes, still the sources: Hamid is a SaaStr Annual talk with a worked fictional company, not a census. Hsu is Social Capital’s enterprise-SaaS diligence sitting. Tunguz is a 2015 reformulation plus one table. Do not flatten all three into one homemade “good Quick Ratio” letter grade.
How to run it
How to run a Quick Ratio tripwire without faking scale
This is Yibud’s suggested sequence, not a Hamid checklist, not a Hsu mandate, and not a Tunguz law. Honor the tripwire you wrote before the first period report. If you cannot name the decision the number would change, you are building a slide.
- 1
Write the tripwire before you look
Signal is Quick Ratio for a named period, plus the four components. Threshold is the miss / pass line you will honor — Hamid’s 4-or-above and Hsu’s >4 / <2 are classic gates, not a seed law, and not proof you will succeed. Name MRR vs ARR, monthly vs quarterly, and whether resurrection is in the numerator. Action is fix retention first, keep experimenting, scale spend, or cut leaky channels. Do not rewrite the bar after the report.
- 2
Lock the period and the four components
Same window on new, expansion, churned, and contraction. If you only have 30 days, report a 30-day Quick Ratio and say so — do not multiply by twelve and call it annual. Hsu’s identity is period-over-period. Mixing a quarterly new-logo dump into a monthly denominator is how a leak prints 5.1×.
- 3
Compute the ratio. Put the four dollars on the dated page.
Add new and expansion. Add churned and contraction. Divide. If the denominator is zero, say so (Tunguz: no churn → infinite). Do not publish 4.2 and hide $8,000 of contraction behind $32,000 of new. The components are the sitting; the multiple is the compression.
- 4
Pair Quick Ratio with an explicit churn / GRR check. Then look at neighbors as separate sittings.
Tunguz: a 4× can hide ~5% monthly churn at ~15% growth. Report dollar churn (and, if you have a starting base, GRR on the NRR page) next to the multiple. Do not average Quick Ratio with NRR%, Magic Number, burn multiple, LTV:CAC, CAC payback, or Rule of 40. Those are different decisions on different pages.
- 5
Honor the action. If you are pre-revenue, use a different instrument.
If the period closes and you missed the bar you wrote, do the thing you named — fix retention first, keep experimenting, or do not scale spend. Do not invent next month’s expansion so the ratio clears 4. Pre-revenue, no recurring base, or pure services without recurring: use willingness-to-pay, smoke, interviews, or the Ellis PMF survey first. A Yibud score is not Quick Ratio.
What you leave with
The Quick Ratio tripwire (copy this)
If the sitting produced a multiple and no dated action, you did not finish. Fill the brackets. Leave nothing as “growth is fine,” “soon,” or “we’ll know it when the round happens.”
The fill-in contract
Product: [name]. Period: [month or quarter — books close date], written before the first report. Hypothesis this number can falsify: [same-period new + expansion outruns churned + contraction, so we can scale spend]. Definition: dollar Quick Ratio (not logo churn); MRR [or ARR]; resurrection [in / out] of the numerator. New: [ ]. Expansion: [ ]. Churned: [ ]. Contraction: [ ]. Quick Ratio: [ ]. Dollar churn this period: [ ]% of beginning recurring. Signal: [Quick Ratio and the four components, and/or change vs last period]. Threshold: [e.g. honor a miss if monthly dollar Quick Ratio is below 4, or if it falls below 2 — Yibud template using Hamid’s 4-or-above and Hsu’s <2, not a homemade letter grade, and not Tunguz’s table treated as a target]. Action if miss: [fix retention first / keep experimenting / do not 3× spend / cut leaky channels]. Also honor a miss if Quick Ratio ≥4 while monthly dollar churn is at or above the Tunguz QR=4 band we refuse to ignore (5.0% at ~15% monthly growth). Compare the next period on the same definitions. A Yibud score does not fire this line.
The “below 4 / below 2” line is Yibud’s suggested template from Hamid’s 4-or-above and Hsu’s enterprise <2 sitting — not a census, not permission to skip the four components, and not permission to skip Tunguz’s churn caveat. Rewrite the threshold before you measure if you have a reason. Do not rewrite it after.
Example tripwire (Yibud’s suggested template, not a law)
If, for the calendar month that closes on the last day, dollar Quick Ratio (new + expansion) / (churned + contraction), resurrection out, is below 4, or if it is below 2, or if Quick Ratio is ≥4 while monthly dollar churn (churned + contraction) / beginning MRR is at or above 5% at ~15% monthly growth (Tunguz’s QR=4 / 15% sitting) → we do not 3× paid acquisition next month; we fix retention first and name the weakest churn or acquisition assumption. Do not annualize a 30-day ratio. Do not drop contraction after the close. Report the four components next to the multiple.
A 4.0 Quick Ratio on one month is still one period. A Yibud report score does not fire this tripwire. If you have no recurring revenue yet, this template is the wrong first instrument — use willingness-to-pay, a smoke test, interviews, or the Ellis PMF survey instead.
The fork
When to use a Quick Ratio tripwire — and when not to
Quick Ratio is the wrong first instrument when there is no recurring revenue yet, no period that can close, or a pure services book without a retained base. It is the right instrument when MRR or ARR already moves, a period can close, and you are deciding whether same-period inflows outrun outflows before you scale spend.
Use it when you have recurring motion, a period, and a spend-or-fix decision
You can name new, expansion, churned, and contraction for the same window. You are about to 3× a channel, tell yourself “Quick Ratio is 4 so we are fine,” or skip the churn column because new logos look kind. That is when a dated multiple plus four components earns its keep. Optional: run NRR/GRR, Magic Number, burn multiple, LTV:CAC, CAC payback, or Rule of 40 as separate sittings — do not average them into a homemade “efficiency score.”
Do not start here when you are pre-revenue, have no recurring base, or still need first money, reach, or a who-filter
No paying customers yet? There is no honest New MRR. Do not invent a forecast numerator. Pure services without recurring, or a one-off project book? This ratio does not apply — you do not have a retained base to contract. Still writing a deposit / pre-order / priced checkout? That is willingness to pay. Still testing whether anyone clicks? Smoke, fake-door, or landing-page tests. Still asking whether current users would be very disappointed? Ellis PMF survey. Still writing Stop / Pivot / Continue? Those are the decision contracts. This page supplies one efficiency instrument those contracts can later read. It does not replace them. A Yibud score is not Quick Ratio.
Worked example
One month you can copy (illustrative — fictional)
The month below is illustrative. Names, product, and dollars are invented so you can see the arithmetic — including Tunguz’s QR = 4 sitting that still hides 5% monthly churn at 15% growth. It is not a study, not an industry benchmark, and not a Yibud report. Copy the method, not the numbers.
The promise, written before the month closes
Illustrative names: founder Kenji Mori at Ledgerbay, invoicing software for independent accountants. Recurring MRR exists. A period can close. The tempting trophy is a board slide that prints Quick Ratio = 4.2 from a quarter of new logos, no contraction line, and no churn %. The tripwire is written first, on 2 March: honor a miss if March dollar Quick Ratio (resurrection out) is below 4, or below 2, or if the multiple clears 4 while monthly dollar churn is at or above 5% at ~15% growth — Yibud’s suggested template from Hamid’s 4-or-above, Hsu’s <2, and Tunguz’s QR = 4 / 15% table, not a homemade letter grade, and not permission to skip the four components.
The inputs, kept honest
Beginning MRR 1 March: $60,000. During March: new $9,000; expansion $3,000; churned $2,400; contraction $600. Resurrection $0 (written out of the numerator). Quick Ratio = (9,000 + 3,000) / (2,400 + 600) = 4.0. Net new $9,000 = 15% monthly growth. Dollar outflow $3,000 = 5% of beginning. A quarterly sketch that dropped contraction and annualized two large new logos could have printed something like 5.1×. Same company. Different definition. Different decision.
The tripwire, written 2 March
Signal: March dollar Quick Ratio and the four components, plus monthly dollar churn. Threshold: honor a miss if Quick Ratio is below 4 or below 2, or if Quick Ratio ≥4 while monthly dollar churn is at or above 5% at ~15% growth, before we 3× paid acquisition. Window: books close 31 March. Action if miss: do not 3× paid in April; fix retention first; name the weakest churn or acquisition assumption. A Yibud score does not fire this line. The 4 / 2 / 5% triple is Yibud’s suggested template from Hamid, Hsu, and Tunguz — not a census.
What a miss looks like — and what must not happen
Illustrative close: Quick Ratio 4.0 clears the ≥4 bar they wrote. Monthly dollar churn 5% at 15% growth hits Tunguz’s QR = 4 hiding band. That is a miss on the dated page — even though the multiple “looks like four.” Had Quick Ratio printed 2.0 with the same $3,000 outflow and only $6,000 of new+expansion, that would have been Hamid’s ~2 sitting and Hsu’s <2 “something to fix.” Do not swap the 5.1× quarterly sketch in after the close and call the debate settled. Do not swap logo churn (3 of 80 firms left = 3.75%) in and call it Quick Ratio. Do not treat 4.0 as proof the startup will succeed. Keep the next month on the same four components.
Write the tripwire before the first report. If the period closes and Quick Ratio misses the bar you wrote — or clears 4 while the Tunguz churn band you refused to ignore fires — honor the action. If the multiple and the churn check both cleared the bar, continue to the next cheapest test — usually the next period on the same definitions, or a kill/pivot contract that now has a number to read. The method is the dated page, not the 4.2 slide. Neither 4.0 nor a Yibud score predicts success.
Not the same page
Quick Ratio vs NRR, Magic Number, burn multiple, LTV:CAC, CAC payback, Rule of 40, vanity metrics, WTP, Ellis, NPS, failure rates, Yibud scores, and decision contracts
Several Yibud pages sit next to this one. Mixing them up turns a cohort retention %, a sales-efficiency ratio, a company cash multiple, a lifetime unit-economics ratio, months-to-recover-CAC, a growth-plus-profit sum, a waitlist, a recommend score, or a mid-band engine number into “Quick Ratio is 4, so scale.”
NRR — cohort retention of a starting base, not same-period inflow ÷ outflow
That page asks whether customers live at period start paid you more or less after churn, downsell, and expansion (NRR% / GRR%). This page asks whether this period’s new + expansion outran this period’s churned + contraction (a multiple). A 110% NRR does not tell you Quick Ratio is 4. A 4× Quick Ratio does not tell you the starting cohort retained 110%. NRR can exceed 100% with expansion; Quick Ratio is typically a multiple, not a percent. Keep the instruments on separate pages.
SaaS NRR →SaaS Magic Number — S&M → incremental revenue, not this period’s inflows vs outflows
That page asks how efficiently prior-period sales and marketing spend turned into incremental subscription revenue (often with a one-quarter lag). This page is same-period recurring inflows ÷ outflows. A 1.2 Magic Number does not tell you Quick Ratio. A 4× Quick Ratio does not tell you last quarter’s S&M paid for itself in new ARR.
SaaS Magic Number →Burn multiple — company cash vs net new ARR, not this ratio
That page asks how much company cash you burned, in a period, per dollar of net new ARR (Net Burn ÷ Net New ARR). This page is not cash. A 2× burn multiple does not tell you Quick Ratio. A 4× Quick Ratio does not tell you the company is burning too much cash per new ARR.
Burn multiple for startups →LTV:CAC — lifetime value ÷ CAC, not period growth efficiency
That page asks whether a cohort’s lifetime (or 12/24-month) contribution cleared a multiple of what it cost to acquire them. This page is one period’s MRR motion. A 3.2 LTV:CAC does not tell you Quick Ratio. A 4× Quick Ratio does not tell you lifetime value is three times CAC.
LTV:CAC for startups →CAC payback — months to recover CAC, not this multiple
That page asks how many months of contribution recover fully-loaded CAC for a named cohort or channel. This page is a same-period ratio. A 7-month payback does not tell you Quick Ratio is 4. A 4× Quick Ratio does not tell you LinkedIn ads pay back in months.
CAC payback for startups →Rule of 40 — company growth plus profit, not this ratio
That page asks whether revenue growth rate plus profit margin cleared a ≥40 bar at the company level. This page is one period’s inflow ÷ outflow. A 42 Rule of 40 does not tell you Quick Ratio is 4. A 4× Quick Ratio does not tell you growth plus EBITDA is healthy.
SaaS Rule of 40 →Vanity metrics — hygiene class, not this efficiency tripwire
That page is the sorting hat: hits, cumulative signups, and waitlist size feel like progress and do not tell you what to do next. This page is one specific actionable multiple. A pretty Quick Ratio chart with contraction dropped and no tripwire can still be vanity. A waitlist is not New MRR.
Vanity metrics for startups →Willingness to pay — first money on a deal, not period efficiency
That page is a deposit, pre-order, paid concierge, or priced checkout as proof that money moved once. Quick Ratio needs a recurring base and a period with inflows and outflows. A paid first month with no recurring book should not be running this page yet.
Willingness-to-pay test →Sean Ellis PMF survey — disappointment among current users
That page’s signal is the percent of recent real users who would be very disappointed if the product disappeared. Hamid’s 4-or-above gate is a dollar-efficiency sitting, not Ellis’s question. Do not treat “very disappointed” as Quick Ratio, and do not treat a 4× as Ellis’s bar.
Product-market fit survey →NPS — one recommend-intent score
That page is stated recommendation intent among people who already used you. A high NPS does not raise Quick Ratio. A 4× Quick Ratio does not mean people would recommend you. Keep the instruments on separate pages.
NPS for early-stage startups →Startup failure rate — population frequencies, not the math
That page is what the failure data says at population level — BLS establishment survival, venture-backed “failure” as reported, and why a base rate is not your fate. This page teaches one efficiency instrument those tables do not compute. It does not invent a “percent of startups that die from a sub-4 Quick Ratio.”
What percentage of startups fail →Yibud scores — not Quick Ratio, and not a success prediction
The validation-score and score-calculator pages explain Startup MRI numbers from a deterministic rule engine on a one-line idea plus five questions. Those scores point at the weakest assumption to test next. They are not Quick Ratio. They are not NRR, Magic Number, burn multiple, LTV:CAC, CAC payback, or Rule of 40. Do not read a mid-band monetization score as “Quick Ratio is 4,” and do not read a 4× as a Yibud GO.
Kill, pivot, critical assumption, decision — contracts that can read this number
Those pages write Stop, rewrite one dimension, name the one claim that would kill the idea if false, or decide after evidence. This page can supply the efficiency instrument those contracts later read: a dated Quick Ratio and four components against a bar you wrote first. A 4.2 slide with no contraction line and no churn check cannot fire a kill line honestly.
Where Yibud fits
Neither Quick Ratio nor a Yibud score predicts success
Yibud is a free, no-signup startup idea validator. Scores come from a deterministic rule engine, not from a language model guessing success. Optional AI text, when it is used, only polishes prose. It does not invent the number. A Startup MRI report can name a weak monetization or distribution assumption, then a Day-7 Continue / Refine / Re-test / Stop signal. The score is a flashlight on the weakest assumption to test next — not Quick Ratio, not NRR, not Magic Number, not burn multiple, not LTV:CAC, not CAC payback, not Rule of 40, not a forecast. Quick Ratio work sits next to that assumption: write the tripwire, do not hope a 4.2 slide means the bucket does not leak. If you already have a report, start with the named assumption, not the overall score. Then run the period yourself. The method on this page stands alone if you never open the analyzer.
Analyze my idea →Common mistakes
What usually wastes a Quick Ratio week
Reporting the multiple without the four components
Hamid’s definition is new + expansion over lost + contracted. Hsu’s Company A looks like “tons of expansion” until you see contraction eating it. A 4.2 with $8,000 of hidden contraction is a different company from a 4.2 with $800. Put the four dollars on the dated page.
Letting growth mask churn — treating ≥4 as a health certificate
Tunguz: at QR = 4 and 15% monthly growth, monthly churn can be 5.0% (~46% annual). His table at 10% / 15% / 20% growth → 3.3% / 5.0% / 6.7% monthly churn and 33% / 46% / 56% annual loss. He calls that unsustainable. Pair the multiple with dollar churn / GRR. Never treat ≥4 alone as proof of health, and never treat it as proof you will succeed.
Calling logo churn Quick Ratio — or mixing windows
Logo / customer churn % counts accounts. Dollar outflow weights by MRR. Ten small logos leaving can print a kinder logo number than two large ones. A monthly numerator over a quarterly denominator is a slogan. Write the period. Keep it.
Treating ≥4 as proof you will succeed
Hamid’s desirable sitting is 4 or above. Hsu’s enterprise preference is >4. Clearing the bar you wrote means that period cleared a gate — not that the startup will succeed. It is not Ellis’s very-disappointed question, not a deposit, and not a Yibud GO. Neither Quick Ratio nor a Yibud report score predicts success.
Confusing SaaS Quick Ratio with the accounting acid-test
The accounting quick ratio (acid-test) is (cash + marketable securities + receivables) / current liabilities, or current assets minus inventory over current liabilities — a liquidity sitting. SaaS Quick Ratio is growth-accounting inflows ÷ outflows. Using the balance-sheet version on a SaaS metrics slide is a different instrument with the same English name. Say which one you mean.
Scaling spend before the tripwire — or inventing First Round bands
Hamid: the top line can look fundable while you refill a leaky bucket. Write the bar before the first period. First Round Levels of PMF do not list Quick Ratio; this page does not invent those bands. Do not 3× a channel because the slide looks like 4.2. Do not paste Bessemer NRR tables or Magic Number bands onto this page — those belong next door.
Sources
Where these ideas come from
- Mamoon Hamid / SaaStr, “Numbers that Actually Matter for Founders” (SaaStr Annual talk, Social Capital; video transcript) — Used for coining / popularizing SaaS Quick Ratio at SaaStr; definition (new + expansion) / (lost + contracted); desirable four or above; ~2 as “a lot of work just to offset churn”; ~1 as treadmill / leaky-bucket; top-line can look fundable while underlying metrics fail. Do not invent deck-slide numbers not in the transcript.
- Jonathan Hsu / Social Capital, “Diligence at Social Capital Part 2: Accounting for Revenue Growth” — Used for the growth-accounting identity (new, retained, resurrected, expansion, churned, contraction); enterprise SaaS prefer Quick Ratio >4; <2 → churn probably too high; subscription default-retained vs visitation default-not-retained; Company A expansion-eaten-by-contraction vignette (qualitative only). No sample-chart numbers copied as benchmarks.
- Tomasz Tunguz, “What is the Optimal Quick Ratio for Your SaaS Startup?,” 3 November 2015 — Used for the formula restatement; QR ≈ (monthly growth + churn) / churn; QR = 4 hiding table (10% / 15% / 20% monthly growth → 3.3% / 5.0% / 6.7% monthly churn; 33% / 46% / 56% annual revenue loss); “Greater Quick Ratios are always better”; high growth can mask high dollar churn; credits Hamid as creator of the metric in the SaaS context.
- InsightSquared, Quick Ratio one-pager (PDF) — Optional, formula wording only: (New MRR + Expansion MRR) / (Churned MRR + Contraction MRR). This page does not invent extra benchmarks from that one-pager.
In one paragraph
Summary you can quote
SaaS Quick Ratio = (New MRR + Expansion MRR) ÷ (Churned MRR + Contraction MRR). It is same-period growth efficiency — how many recurring dollars you add for each dollar you lose — not the accounting acid-test, and not NRR%. Hamid (SaaStr Annual, Social Capital): coined at SaaStr; 4 or above desirable; ~2 is a lot of work to offset churn; ~1 is a treadmill / leaky bucket; top-line can look fundable while the bucket leaks. Hsu (Social Capital Part 2): growth accounting; enterprise SaaS prefer >4; <2 → churn probably too high; subscription vs visitation; Company A expansion eaten by contraction. Tunguz (3 November 2015): QR ≈ (growth + churn) / churn; a QR of 4 at 15% monthly growth can hide 5.0% monthly churn (~46% annual); table 10/15/20% growth → 3.3/5.0/6.7% monthly churn and 33/46/56% annual loss; greater is always better — watch underlying churn. Write signal + threshold + definition + period + action before you measure; report the four components; pair with a churn / GRR check. Matching the gate is a decision signal. Neither Quick Ratio nor a Yibud score predicts success.
FAQ
Questions founders actually ask
What is SaaS Quick Ratio?
Same-period (New MRR + Expansion MRR) ÷ (Churned MRR + Contraction MRR). Hamid: new plus expansion, divided by lost plus contracted. It asks how many recurring dollars you add for each dollar you lose. It is a growth-efficiency tripwire, not a success score, not NRR%, and not the accounting acid-test (current assets ÷ current liabilities). Write the bar before you measure.
What is a good Quick Ratio for a SaaS startup?
This page does not publish a universal “good” grade table beyond the sources. Hamid: 4 or above is quite desirable; ~2 is a lot of work to offset churn; ~1 is a treadmill. Hsu, enterprise SaaS: prefer >4; <2 → churn probably too high. Tunguz: a 4 can hide 5.0% monthly churn at 15% monthly growth (~46% annual); his QR=4 table is 10/15/20% growth → 3.3/5.0/6.7% monthly churn. Write your own tripwire. First Round Levels do not list Quick Ratio — do not invent those bands. Do not invent industry medians.
How is Quick Ratio different from NRR?
NRR / GRR is cohort retention of a starting ARR base over a window, as a percent (GRR cannot exceed 100%; NRR can). Quick Ratio is same-period inflow ÷ outflow, as a multiple. A 110% NRR does not tell you Quick Ratio is 4. A 4× does not tell you the starting cohort retained 110%. Use the NRR page for the cohort pair; use this page for the period efficiency sitting.
How is Quick Ratio different from Magic Number, burn multiple, LTV:CAC, CAC payback, and Rule of 40?
Magic Number is how efficiently prior-period S&M turned into incremental subscription revenue. Burn multiple is company-level Net Burn ÷ Net New ARR. LTV:CAC is lifetime (or 12/24-month) value ÷ CAC. CAC payback is months of contribution to recover CAC. Rule of 40 is growth % + profit %. Quick Ratio is same-period (new + expansion) ÷ (churned + contraction). They answer different decisions. Use this page for the growth-efficiency multiple.
Is a Yibud score the same as Quick Ratio? Does it predict success?
No and no. Yibud scores come from a deterministic rule engine on your idea inputs. They point at the weakest assumption to test next. They are not Quick Ratio, not NRR, not Magic Number, not burn multiple, not LTV:CAC, not CAC payback, not Rule of 40, and not a forecast. Neither a Quick Ratio pass nor a Yibud report score predicts success. You do not need an account to use this page.
Write the Quick Ratio tripwire before you scale spend
Yibud scores weak assumptions with a deterministic engine. You write signal, threshold, definition, period, and action while you are still honest — then a month of new + expansion vs churned + contraction is a tripwire, not a 4.2 slide.
Generate a Yibud report →