Lead Velocity Rate (LVR): Formula and Why It Matters

Revenue tells you what already happened. By the time a deal closes, the outcome was mostly decided weeks or months earlier: a rep's first call, a shifted campaign, a competitor entering the deal. Lead velocity rate (LVR) exists because sales and marketing leaders got tired of finding out about a demand problem after it had already cost them a quarter.

LVR measures how fast your pool of qualified leads is growing, month over month. It is not a stand-in for "more leads." It is specifically about qualified leads, and specifically about the rate of change, not the raw count. That distinction is why LVR built a reputation as one of the few metrics that tells you where revenue is headed before revenue actually gets there.

This guide covers the formula, a full worked example across several months, how LVR differs from lead conversion rate, pipeline velocity, and sales velocity, how to set your own target from your revenue plan instead of chasing a made-up industry benchmark, and how to diagnose a drop before it shows up in your pipeline review.

Key Facts: Lead Velocity Rate

• LVR was popularized by SaaStr founder Jason Lemkin, who calls it "the number one most important metric for SaaS and B2B companies" because it moves in real time instead of on a reporting lag (SaaStr).
• Sales reps spend just 40% of their time actually selling; the rest goes to admin, internal meetings, and non-selling work, the same hours that would otherwise go toward qualifying and acting on new leads (Salesforce, State of Sales, Seventh Edition).
• Only 27% of B2B leads are sales-ready the moment they first raise their hand; the other 73% need nurturing before "qualified" honestly applies to them (MarketingSherpa, 2012 B2B Benchmark Report).
• SaaStr's own public guidance points to roughly 10% monthly LVR growth at $1M ARR and 8% monthly at $3M ARR for companies aiming at close to 100% year-over-year growth (SaaStr).

What is lead velocity rate?

Lead velocity rate is the percentage growth in your qualified leads from one month to the next. That's the whole idea. It doesn't measure how many leads you generated in total, how many converted, or how much revenue closed. It measures one thing: is the qualified pipeline you're feeding into sales growing, shrinking, or flat, right now.

The "right now" part is what makes LVR different from almost every other metric your team tracks. Revenue, closed-won deals, even lead conversion rate, all describe things that already happened, often things that started forming months ago. LVR skips that lag. It looks at leads entering the funnel today and tells you whether the engine feeding your business is speeding up or slowing down before that shows up anywhere else.

That's why LVR sits alongside the lead management process as an operating metric, not a scorecard metric. A scorecard metric tells your board how last quarter went; an operating metric tells your team what to do this week. It only works if your lead management process is consistent enough to trust the number it produces.

The lead velocity rate formula

The formula is:

Lead Velocity Rate (%) = ((Qualified Leads This Month - Qualified Leads Last Month) / Qualified Leads Last Month) x 100

Say your team generated 150 qualified leads last month and 180 qualified leads this month. Your LVR is:

((180 - 150) / 150) x 100 = 20%

That's a 20% month-over-month growth rate in qualified pipeline. If you sustain that pace and conversion rates hold steady, closed revenue should follow the same curve on a delay. That delay is the part most teams miss when they first start tracking LVR: a strong LVR this month is a signal about a future quarter, not this one.

Two things make or break whether that number means anything.

Only count leads that meet your qualification bar. Divide by total inquiries or raw contacts instead of qualified leads, and you're measuring top-of-funnel traffic, not pipeline health. A spike in raw leads from a viral post can inflate the number without telling you anything about revenue.

Use a consistent time window. LVR is a month-over-month calculation. Comparing this week to last week introduces too much noise (weekday mix, holidays, one big event). Comparing this year to last year hides the exact thing LVR exists to catch: a change that started three weeks ago.

Why LVR is a leading indicator, not a lagging one

Most of the metrics on a sales dashboard are lagging. Closed revenue, win rate, average deal size all describe outcomes from deals that started their journey through the funnel weeks or months earlier. By the time a lagging metric moves, the cause is already old news, and there's often nothing left to do about the cohort that produced it.

LVR is built to solve that problem. According to SaaStr's Jason Lemkin, the executive most closely associated with popularizing the metric, "your monthly sales tell you about the past," while lead velocity rate is "real-time, not lagging," and it "clearly predicts your future revenues and growth" (SaaStr). His framing is blunt: if qualified pipeline is growing today, revenue growth tends to follow on a lag of roughly one to two sales cycles, commonly cited as 90 to 120 days for many B2B SaaS businesses, though the exact lag depends on your own sales cycle length.

That lag is why LVR matters operationally. A CRO watching only closed revenue is looking at decisions made two or three quarters ago. A CRO watching LVR is looking at decisions being made this week, while there's still time to change course: shift budget to a working channel, fix a scoring rule that overcorrected, or catch a channel that quietly stopped converting before the pipeline review makes it obvious.

The "qualified" definition is what makes or breaks LVR

LVR is only as trustworthy as your definition of "qualified." Change that definition, even slightly, and the number moves for reasons that have nothing to do with demand.

Say your team tightens MQL criteria this month, maybe you raise the minimum company size, or add a new behavioral signal requirement. Qualified lead volume drops 15%. Your LVR reports a scary decline. But nothing about actual buyer interest changed; you just moved the goalposts. The inverse is just as dangerous: loosen the definition, and LVR looks like it's accelerating even though the leads coming through are worse fits than the ones you were counting last month.

This is why a clear, stable lead qualification framework has to exist before LVR is worth reporting on. Whatever separates a raw contact from a qualified lead, whether that's a lead score threshold, a fit-and-intent combination, or a formal MQL-to-SQL handoff rule, needs to stay consistent month over month, or at minimum, any change needs to be logged and flagged the month it happens. Sales and marketing leadership should be able to look at an LVR swing and immediately answer one question: did demand change, or did our definition change? If you can't answer that quickly, the number isn't ready to drive decisions yet.

A practical habit: whenever you adjust scoring rules or the fields that count toward "qualified," annotate the month on your LVR chart. Months later, when someone asks why LVR dipped, you want an answer on file, not a guessing exercise.

Monthly vs. quarterly measurement: why smoothing matters

LVR is designed as a monthly metric, but any single month can be misleading on its own, especially for businesses with lumpy pipelines: a big conference, a product launch, a slow holiday month, or one large account skewing the count. A single bad month doesn't mean your engine is broken, and a single great month doesn't mean you've solved growth.

The fix isn't to abandon monthly measurement and switch to quarterly. It's to track monthly LVR alongside a rolling average that smooths out the noise while still catching real trend changes fast. A three-month rolling average is the most common approach: it's slow enough to ignore a single odd month, fast enough to catch a genuine multi-month slide.

Here's what that looks like across six months for a mid-market B2B company with a naturally lumpy lead flow:

Look at the spread. Month-over-month LVR swings from -11.4% to +33.3%, a 44.7-point range that would set off alarm bells (or false celebrations) if you reacted to every single reading. The rolling average stays in a much tighter band, 4.8% to 13.4%, and tells a calmer, more accurate story: this company is growing qualified pipeline at a healthy, if uneven, pace. Neither view alone is complete. Monthly LVR catches sudden shocks fast; the rolling average tells you whether the underlying trend is actually intact. Track both, and read big single-month moves against the lead lifecycle stages your leads are actually sitting in before you react to them.

LVR vs. lead conversion rate vs. pipeline velocity vs. sales velocity

These four metrics get conflated constantly, partly because they all sound like "how fast are we growing." They measure genuinely different things, and mixing them up leads to the wrong fix for the wrong problem.

The practical distinction: LVR looks upstream of your pipeline, at whether new qualified demand is showing up at all. Pipeline velocity and sales velocity look inside the pipeline, at how efficiently existing opportunities move toward closed-won. Lead conversion rate sits in between, describing how well you turn one into the other. A team with rising LVR but flat pipeline velocity has a demand problem solved and an execution problem still open; the reverse team is efficiently working through pipeline that's about to run dry.

Cost per lead is worth pairing with LVR too, for a different reason: LVR alone can't tell you whether growing qualified volume is coming at a sustainable acquisition cost. Fast-growing LVR funded by rapidly rising cost per lead is a trend that runs out of budget before it runs out of momentum.

What "good" LVR looks like

There's no single, reliable, universally cited "good LVR" benchmark you can pull off a research report and apply to your business, and any article that hands you one flat number (say, "aim for 15%") without naming a source and a company stage is guessing. LVR is too dependent on your growth stage, your sales cycle, your average deal size, and your current base of qualified leads for one number to travel across all of that.

What does exist is public guidance from the person most associated with popularizing the metric. SaaStr's Jason Lemkin has published rough monthly LVR targets tied to ARR stage, aimed at SaaS companies pursuing close to 100% year-over-year growth:

Treat this table as one credible, sourced reference point, not as a universal law. It's specific to venture-backed SaaS companies chasing roughly 100% annual growth, which describes a narrow slice of B2B businesses. If your growth target is 30% a year, or you sell services with a 9-month sales cycle, or your ACV is ten times a typical SaaS deal, this range won't transfer cleanly. Rather than force-fitting someone else's target, work backward from your own revenue plan, the same way the next section does.

Setting your own LVR target from your revenue plan

The most useful LVR target is one you build yourself, working backward from the revenue number you actually need to hit, through your own conversion rates and sales cycle. Here's the math laid out step by step, using an example company as a worked illustration:

Only the "(input)" rows are assumptions; everything else is calculated, so swap in your own numbers and the arithmetic follows. In this illustration, a company generating 130 qualified leads a month today needs roughly 167 a month within a year to hit its revenue target, given its own win rate and SQL conversion rate. A steady 2.1% monthly LVR closes that gap by year-end, a very different number from the 8 to 10% SaaStr range above, because this company simply needs less growth to hit its specific goal.

This exercise also exposes which lever matters most. If the required LVR looks unrealistic given your historical growth rate, you have three places to intervene: improve SQL conversion, improve win rate, or accept a lower revenue target, rather than willing a higher LVR into existence through effort alone.

What a falling LVR predicts, and how far ahead

A sustained decline in LVR, not a single bad month but a multi-month rolling average trending down, is one of the earliest reliable signals that revenue growth is about to slow. The lag between the signal and the revenue impact roughly tracks your sales cycle length, plus whatever time your team spends nurturing a lead from qualified to sales-ready. For many B2B SaaS companies, that lands in the 90 to 120 day range cited around the metric's origin, though a company with a 9-month enterprise sales cycle should expect a much longer gap.

That lag is an advantage if you use it. A CRO who spots declining LVR in month one has, roughly, one to three months before it shows up in closed revenue to fix the cause: shift budget between channels, adjust a rule that overcorrected, or pull forward a campaign planned for later in the quarter. A CRO who only watches revenue finds out about the same problem after that window has already closed.

The size of a decline matters less than its direction and duration. A single month down 10% inside an otherwise healthy rolling average is noise. A rolling average that's declined for three straight months is a trend worth escalating before the next quarterly business review, not after it.

Diagnosing a drop in LVR

When LVR falls, the instinct is often to assume demand dried up. That's one possible cause, and often not the most common one. Work through these in order before concluding anything about market demand:

The fastest way to misdiagnose a drop is to skip straight to "we need more marketing spend." More spend on the same channel, targeting the same audience, with the same qualification bar, usually just reproduces whatever caused the drop, at a higher cost. Look upstream at the demand generation mix first, because a fall in qualified volume is more often a creation problem, too few people entering the market already aware of you, than a capture problem you can buy your way out of.

Failure modes: how teams game or misread LVR

LVR is simple enough that it's also easy to accidentally (or deliberately) distort. Three patterns show up often enough to name directly.

Gaming the number by loosening qualification. The fastest way to post a great LVR this month is to lower the bar for what counts as "qualified." It works exactly once. The SQL and close rates that follow a few weeks later expose the trick, because a flood of lower-fit leads converts worse than the leads it replaced. If LVR and downstream conversion move in opposite directions for more than a month, check the qualification rules before anything else, and check whether lead grading criteria shifted alongside the scoring model.

Tracking raw lead volume instead of qualified leads. This is the most common mistake, and usually not a deliberate one. A dashboard gets built off "total leads created" because that field is easier to pull, and the metric quietly stops being LVR at all. It becomes a traffic metric wearing an LVR label. The two can diverge sharply: a viral piece of content can double raw leads while qualified leads stay flat, because the audience it reached wasn't your ICP.

Reading one month as a trend. A single strong month doesn't mean the growth engine is fixed, and a single weak month doesn't mean it's broken; both move the rolling average only gradually. Treat any one-month reading as a data point, not a verdict, and give it two more months of confirmation before changing strategy or headcount based on it.

None of these failure modes are exotic. They're the predictable result of treating a leading indicator like a lagging one, checking it once a quarter, and letting the definition of "qualified" drift until the numbers stop making sense.