Run Rate: Definition, Formula + ARR vs MRR Comparison (2026)

Last reviewed by Igor Shaverskyi on April 29, 2026

Run rate annualizes a recent revenue period to project a full-year figure. The formula: Run rate = Revenue in period × Number of periods per year (monthly × 12, quarterly × 4, daily × 365). It works as a snapshot, not a forecast — seasonality, one-off deals, and churn break it instantly. In our work across 600+ startups, run rate is the single most-misused number in early-stage decks.

Say "we're at a $1M run rate" to an investor, and the first thing they'll ask is: "…based on what?"

Run Rate: Definition, Formula + ARR vs MRR Comparison (2026)

That's the problem with run rate. It's simple to calculate, tempting to show, and incredibly easy to misinterpret. One strong month becomes a year-long projection, and suddenly your metrics look better on paper than they are in reality.

This guide covers what run rate actually means, the formula across monthly / quarterly / daily timeframes, how it differs from ARR and MRR, what "run rate EBITDA" means in M&A diligence, and the five mistakes investors spot in 30 seconds. Everything below is the same playbook we use across the 600+ startups we've helped raise $3B+.

What is run rate?

Run rate is a method of projecting full-year revenue (or any other metric) by extrapolating recent performance forward. You take what the business earned in a recent period and assume that pace continues. It's a snapshot, not a forecast — useful when you have limited history, dangerous when seasonality, churn, or one-off deals enter the picture.

Run rate is a quick way to project future revenue by extrapolating what you earned in a recent period and assuming that pace continues (Investopedia's run rate definition frames it the same way). You take your latest revenue and extend it forward, as if nothing changed — no forecasting model, no complex math. Just a straight line drawn from today, typically into the next 12 months.

If your startup made $20,000 last month, your annual run rate (often called revenue run rate) is $20,000 × 12 = $240,000. That's it. It's popular with early-stage teams because it gives a fast sense of scale even when historical data is thin.

There's a catch. Run rate assumes the next 12 months will look exactly like the most recent period — and real businesses rarely behave that neatly. When a founder says "we're at a $1M run rate," an investor mentally translates: "based on what period? Repeatable? One-off? Seasonal? Lucky month?" That's why run rate without context is worse than no number at all.

How to calculate run rate

The run rate formula is Run rate = Revenue in period × Number of periods per year. Monthly revenue × 12, quarterly revenue × 4, weekly revenue × 52. For irregular timeframes (45 or 75 days), use (Revenue ÷ Days in period) × 365. The output is always annual; the input period is whatever fits the data.

The run rate formula is intentionally simple:

Run rate formula
Run rate = Revenue in period × Number of periods in a year - Monthly → multiply by 12 - Quarterly → multiply by 4 - Weekly → multiply by 52 - Daily / irregular → (Revenue ÷ Days in period) × 365

The output is always the same — an annual projection — but the input period can differ. To make the math comparable across timeframes, assume your startup made $40,000 in revenue in November 2025 and we'll annualize it three different ways.

Monthly-based annual run rate

Run rate = $40,000 × 12 = $480,000

Based on November 2025 alone, your annual run rate is $480K. This is the most common method — take one month and annualize it. It's also the most fragile, because a single month rarely reflects a full-year pattern.

Quarterly-based annual run rate

Some businesses don't behave on a steady monthly rhythm. B2B especially has weird timing — invoices land late, clients batch purchases, sales cycles slip. A quarterly base smooths the noise.

  • July 2025 → $25,000
  • August 2025 → $28,000
  • September 2025 → $30,000

Q3 total = $83,000. Quarterly-based annual run rate = $83,000 × 4 = $332,000. Notice how this number is meaningfully lower than the November-only $480K calculation — that's the seasonality the monthly view hides.

Daily / irregular-period run rate

Sometimes your "month" isn't a calendar month — it's 45 or 75 days. Daily revenue smooths it out:

Irregular-period formula
Run rate = (Revenue ÷ Days in period) × 365

Example: new pricing went live on September 17, and you only want to measure revenue under the new model. From September 17 to November 30 (75 days) you made $60,000. Daily revenue = $60,000 ÷ 75 = $800/day. Daily-based annual run rate = $800 × 365 = $292,000. This is the right method when measuring post-launch traction, post-pricing-change performance, or any window that doesn't snap to a calendar.

Run rate vs ARR vs MRR

Run rate annualizes all recent revenue — recurring and one-off — across any business model. ARR (annual recurring revenue) is SaaS-only and counts subscription revenue alone. MRR (monthly recurring revenue) is the same on a monthly view (ARR = MRR × 12). Confusingly, ARR sometimes also means annual run rate — outside SaaS, it usually does. Rule: if it's recurring, call it ARR; if it's everything, call it run rate.

You've probably seen the acronym ARR used two ways — sometimes meaning annual run rate, sometimes annual recurring revenue. They're not the same metric, and that one acronym collision causes more diligence confusion than any other line in early-stage models. Here's how the three actually compare:

Run rate vs ARR vs MRR — what each metric measures, when to use it, who watches it

DimensionRun rateARR (annual recurring revenue)MRR (monthly recurring revenue)
What it measuresAll revenue from a recent period × periods/yearRecurring subscription revenue only, annualizedRecurring subscription revenue, monthly view
Includes one-off deals?Yes (often inflates the number)NoNo
FormulaPeriod revenue × periods per yearMRR × 12 or sum of contracted recurringSum of monthly recurring contracts
Best forAny business model — early-stage snapshotSaaS / subscription, year-over-year comparisonSaaS, month-over-month tracking
Manipulation riskHigh — timeframe + one-offs distort itMedium — multi-year contracts can inflate itLow — granular, hard to fake
Who watches it mostEarly-stage founders, internal planningSaaS investors, board reportsSaaS founders, growth teams
What investors actually want next to itPair with MRR or recurring revenue to triangulateNet new ARR, NRR, gross retentionMRR growth %, expansion, churn

Two-line rule we give every founder during model reviews: if it's recurring, call it ARR. If it's everything, call it run rate. Mixing the two — especially in a SaaS pitch — reads as either sloppy modeling or quiet inflation, and investors flag both the same way.

Related read: Key SaaS metrics founders should track.

Sales run rate

Sales run rate annualizes recent sales bookings or quota attainment to project full-year sales performance — typically monthly bookings × 12 or weekly bookings × 52. It differs from revenue run rate because bookings are not recognized revenue: a $120K annual contract signed today is $120K in bookings but only $10K in MRR. Sales teams use it for quota planning; finance teams use it for capacity, not forecasting.

Sales run rate is the same formula applied to sales output instead of revenue. A team booking $200K of new ACV per month is on a $2.4M annual sales run rate. It's a rough capacity check — if our team keeps closing at this pace, what does the year look like?

The trap: bookings and revenue aren't the same thing. A $120K annual contract signed today shows up as $120K in bookings (sales run rate) but only $10K in MRR (revenue run rate). Conflate them and you'll either look like you're sandbagging or — more often — overstating revenue by 12x. When investors ask for run rate during diligence, default to revenue run rate unless they explicitly ask about bookings; sales run rate belongs in the GTM section, not the financial summary.

Run rate EBITDA

Run rate EBITDA (sometimes called annualized EBITDA or ARR EBITDA) extrapolates recent operating profit forward — typically last quarter's EBITDA × 4 or last month × 12. PE buyers and lenders prefer LTM EBITDA (last twelve months), but for fast-moving SaaS or post-cost-cut targets they'll accept run rate EBITDA when LTM understates current performance. Adjusted-EBITDA scrubbing happens in the data room — investors will challenge every add-back.

Run rate EBITDA shows up most often in M&A and PE diligence. The buyer's question is straightforward: "What's the earnings power of this business right now, not the trailing twelve months?" For a target that just closed a major restructuring, repriced its product, or shed unprofitable customers, LTM EBITDA looks worse than current run-rate EBITDA — sometimes materially. The buyer wants both.

Mechanically it's the same arithmetic as revenue run rate, applied to operating profit. Q4 2025 EBITDA of $1.2M annualizes to a $4.8M run rate EBITDA. The catch: EBITDA is non-GAAP, so the adjustments are where deals fall apart. Buyers scrub one-time gains, owner add-backs, capitalized R&D, and "normalized" comp during quality-of-earnings work — see Aswath Damodaran's NYU Stern dataset for sector EBITDA benchmarks. If the run-rate EBITDA depends on three add-backs that survived the seller's spreadsheet but won't survive a data room, the valuation moves with them.

Related read: EBITDA vs revenue — what startups should track in 2026.

When run rate works (and when it breaks)

Run rate works as an internal snapshot for early-stage teams with limited history, stable pricing, and no seasonality — useful for sales targets, budgeting, and quick board updates. It breaks the moment seasonality, one-off deals, churn, discounts, or large enterprise contracts enter the picture. As a forecasting tool, it almost always overstates next-year revenue.

When run rate works vs when it breaks

When run rate is usefulWhen run rate breaks
You're an early-stage startup with only a few months of dataYou're calculating it off your best month ever
Your recent growth inflection says more than your last 12 monthsYou're in a seasonal industry (tax tools, holidays, tourism, Black Friday)
You need a simple internal benchmark for sales targetsRevenue includes large one-off deals or depends on discounts and promotions
You want a quick snapshot for planning or budgeting (kept conservative)You haven't accounted for churn, downgrades, or short-term promos
Pricing and cost structure have been stable for 90+ daysYou're trying to forecast 2–3 years out — run rate is a snapshot, not a forecast

The pattern across the 800+ models we've reviewed is consistent: founders use run rate well as an internal tool and badly as an external one. Investors don't reject run rate — they reject undisclosed assumptions behind it.

3 scenarios where founders inflate their run rate

Investors see the same three scenarios over and over: seasonal businesses annualizing their peak month, B2B companies treating a one-off enterprise contract as recurring, and SaaS founders ignoring churn that compounds against the run-rate projection. Each one inflates the number by 2–6x. Each one gets caught in the first 10 minutes of diligence.

Scenario 1: Seasonal businesses
You run a tax-productivity tool. April is your big month — $40K, your best of the year. Annualize it: $40,000 × 12 = $480,000 run rate. On paper you're a half-million-dollar business. But your typical off-season month (August) brings barely $8K. April doesn't represent your business; it represents a moment in your business. As soon as investors spot seasonality, they mentally adjust the number down — usually way down.
Scenario 2: One large enterprise contract
You're building a B2B tool. Most months you bring in around $10K in recurring revenue. In July you land your first big enterprise customer — a $50K one-off implementation project. July total: $60K. Annualized run rate: $60,000 × 12 = $720,000. Suddenly you look on track to clear three-quarters of a million. You aren't. The $50K isn't a repeatable pattern; it's a milestone. The honest split: $10K × 12 = $120K recurring run rate, plus a one-time $50K project disclosed separately.
Scenario 3: SaaS startup with churn
You run SaaS at $20K MRR with early traction, paying customers, and stable onboarding. Run rate: $20,000 × 12 = $240,000. Except last month churn was 9% and you barely replaced what you lost. Run rate assumes the next 12 months look exactly like the last one — but churn compounds, it doesn't repeat. This is why SaaS investors barely look at run rate. They look at MRR stability, net revenue retention, expansion vs contraction, and cohort retention curves. A SaaS business with 9% monthly churn never sees the run-rate number the formula projects.

5 mistakes founders make with run rate

Five recurring mistakes we see during pitch-deck and model reviews: using your best month as the baseline, ignoring discounts or promotions, treating one-off deals as recurring, citing a run rate without naming the period, and using run rate to justify hiring or spending. Each one is visible in 30 seconds — and once an investor spots one, they assume the rest of the model has the same problem.

  1. Using your best month ever as the baseline. Every startup has a hero month — a big customer signs, a promo lands, a launch hits. Annualizing $40K when your normal months sit at $12–15K isn't a $480K run rate; it's a great November. Investors spot the gap immediately by asking for the trailing-six-month chart.
  2. Ignoring discounts or promotions. Revenue from a 50%-off month doesn't reflect sustainable earning power. Run rate built on discounted revenue overstates what the business can charge at full price.
  3. Treating one-off deals as recurring. The classic trap. A $50K implementation project drops into the recurring revenue line, gets multiplied by 12, and the run rate balloons overnight. Strip non-recurring revenue before annualizing, every time.
  4. Citing run rate without saying what period it's based on. "We're at a $1M run rate" tells an investor nothing — they need to know whether you annualized last month, last quarter, or a promo-driven spike. Without the period, the number is a vibe.
  5. Using run rate to justify hiring or spending. This one is dangerous internally, not just externally. Scaling the team based on a run-rate projection assumes the run rate will hold — almost no early-stage business actually does. Plan headcount against trailing revenue, not extrapolated revenue.

Related read: What's the difference between a forecast and a projection.

Want to know if your startup is actually ready to fundraise? Take our 5-minute VC readiness quiz — built from the same diligence checks investors run on Waveup decks.
Take the quiz

How to use run rate without misleading investors

Five rules from reviewing 800+ pitch decks: state the period explicitly, strip one-time revenue, calculate from at least three months of data, pair run rate with a recurring metric (MRR or NRR) so investors can triangulate, and use it as one data point — not the headline. Founders who follow these rules don't get challenged on run rate; the ones who skip them lose 20% of the meeting to it.

  1. State the period explicitly. "$480K annual run rate based on November 2025 monthly revenue" is defensible. "$480K run rate" isn't.
  2. Strip out one-time revenue. Implementation fees, setup charges, hardware sales, and one-off enterprise deals get reported separately — never multiplied by 12.
  3. Calculate from at least 3 months of data when possible. A trailing-three-month average × 4 (for quarterly view) smooths the noise and removes the "hero month" objection in one move.
  4. Pair with a recurring metric. Show run rate next to MRR, ARR, or NRR so investors can see how much of the run rate is recurring vs one-off. Pairing pre-empts the "based on what?" question.
  5. Use it as one data point, not the headline. Run rate sits next to growth rate, gross margin, and cash burn — not above them. The headline number in any pitch should be either ARR (SaaS) or trailing-12-month revenue (everything else).

Across the 600+ startups we've helped raise $3B+ since 2018, the founders who land term sheets follow these five rules. The ones who don't spend half of every meeting defending the number.

Run rate FAQ

Below — the run rate questions we hear most often during financial-model reviews and pitch-deck prep, including the ARR / MRR / EBITDA crossovers that trip up every first-time founder. If yours isn't here, the answer is almost always "it depends on what you're annualizing and what you're not stripping out."

Frequently asked questions

What is the revenue run rate?
Revenue run rate is a quick way to estimate full-year revenue based on a recent period — typically last month × 12 or last quarter × 4. It only works when the period reflects normal, repeatable performance. As a forecasting tool, it almost always overstates next-year revenue.
How do I calculate a run rate?
Take revenue from a recent period and multiply by the number of periods in a year: monthly × 12, quarterly × 4, weekly × 52. For irregular timeframes (45 or 75 days), use (Revenue ÷ Days in period) × 365.
Is run rate the same as ARR?
Sometimes — and that's the confusion. ARR can mean annual run rate (any business, all revenue annualized) or annual recurring revenue (SaaS, subscription revenue only). In SaaS conversations ARR almost always means recurring; outside SaaS it usually means run rate. Always disambiguate before quoting the number.
What is run rate EBITDA?
Run rate EBITDA annualizes recent operating profit — typically last quarter's EBITDA × 4. PE buyers and lenders use it alongside LTM (last-twelve-months) EBITDA when current performance differs sharply from the trailing year, often after restructuring, pricing changes, or cost cuts. Adjusted-EBITDA scrubbing happens in diligence — every add-back gets challenged.
What's a good run rate for a startup?
There's no universal benchmark — "good" depends on stage, sector, and capital raised. For seed-stage SaaS, a $1M+ ARR run rate is typically the bar to credibly raise a Series A. For non-SaaS, investors care more about growth rate (3x+ year-over-year at early stage) and gross margin than the absolute run-rate number.
What's the difference between run rate and burn rate?
Run rate annualizes revenue; burn rate measures cash going out. Run rate is a top-line forward projection; burn rate is the cash you're spending each month to operate. Both matter at the early stage — pair them with cash on hand to derive runway. See our deeper take in capital efficiency.
Can I use run rate to forecast 2 or 3 years out?
No. Run rate is a snapshot, not a forecast. A real multi-year forecast accounts for growth rate, churn, sales-cycle dynamics, hiring plans, and CAC payback — none of which run rate captures. Annualizing one month and projecting it across 36 months is one of the fastest ways to lose investor credibility. See the difference between a projection and a forecast.
Is daily run rate a real metric?
Yes — it's the right method when the period you want to measure isn't a clean calendar month. Calculate (Revenue ÷ Days in period) × 365. It's especially useful after a pricing change, post-launch, or when you want to normalize across uneven months.
Why don't SaaS investors care about run rate?
Because SaaS economics depend on recurring subscription dynamics — MRR, churn, expansion, cohort retention — that run rate can't capture. Run rate treats next month like last month; SaaS revenue compounds or contracts based on retention curves. SaaS investors look at ARR, NRR, and the burn-multiple instead.

Run rate in your investor conversations

Investors don't reject run rate — they reject undisclosed assumptions. A clearly-labeled, conservatively-calculated run rate paired with MRR and growth rate is fine. A bare "$1M run rate" with no period and no recurring breakout reads as either sloppy or evasive. Either way, the founder loses 10–20 minutes of the meeting defending the number instead of selling the business.

Run rate is a useful internal metric and a hazardous external one. Used well, it gives you and your team a quick read on momentum. Used badly — annualizing a hero month, ignoring churn, treating one-off deals as recurring — it creates a number that breaks under the first 30 seconds of investor scrutiny.

If you're working on your pitch deck, preparing for a raise, or building a defensible financial model, our team can help. Across 800+ financial models and 600+ startups raising $3B+, we've seen exactly which run-rate framings clear diligence and which ones blow up in it.

Building a model that holds up under investor scrutiny? The team behind 800+ startup financial models can help — from seed-stage run-rate framing to PE-ready EBITDA reconciliation.
Talk to Waveup

Or, if you prefer something flexible and on-demand, check out our subscription service Waves by Waveup.

102 posts

Igor Shaverskyi

Founder, Waveup

Igor Shaverskyi is the founder of Waveup, which he launched in 2015. Over the past decade he has helped 500+ startups navigate both dilutive and non-dilutive funding paths, with founders raising more than $3B in capital. His perspectives on startup fundraising have been featured in TechCrunch, Forbes, and The Next Web.

120 posts

Ruslana

Senior Content Writer, Waveup

Hi, I’m Ruslana—Waveup’s senior content writer with six years of professional writing under my belt and two years laser-focused on venture funding, pitch decks, and startup strategy. I pair content writing with ongoing training in SEO, market research, and investment analysis to turn complex business data into clear, founder-friendly guides.