Skip to main content
Back to Glossary

Metrics

Lead Velocity Rate

Lead velocity rate (LVR) measures the month-over-month percentage growth in qualified leads, used by SaaS leaders as a real-time leading indicator of future revenue growth before any deal closes.

Lead velocity rate (LVR) measures the month-over-month percentage growth in qualified leads. It is a leading indicator: this month's LVR predicts next quarter's bookings before any deal has closed. Jason Lemkin popularized the metric in SaaS circles as the single most useful real-time signal for whether a growth-stage company is accelerating or decelerating, because it shows up in the funnel weeks before revenue catches up to the change.

How Lead Velocity Rate Is Calculated

The formula is straightforward:

LVR = ((Qualified Leads This Month − Qualified Leads Last Month) / Qualified Leads Last Month) × 100

"Qualified leads" usually means SQLs — leads that have been accepted by sales — but some teams measure on MQLs or SQOs. The choice matters. Calculating LVR off MQLs measures marketing effort. Calculating off SQLs measures pipeline that will actually be worked. Most CFO-grade reporting standardizes on SQL or SQO for that reason.

Month Qualified Leads LVR
January 200
February 230 +15%
March 264 +14.8%
April 290 +9.8%

A consistent 10-15% monthly LVR compounds to roughly 3x annual lead growth. A 20% monthly LVR is venture-scale growth. Anything under 5% sustained means the funnel is filling slower than the team is hiring.

A Worked Lead Velocity Rate Example

A Series B SaaS company hits 180 SQLs in April and 216 in May. LVR is (216 − 180) / 180 × 100 = 20%. If average deal size is $40K and SQL-to-close conversion is 25%, the May cohort represents roughly $2.16M of forward bookings, up from $1.8M in April. The board sees the LVR number in the monthly investor update because it forecasts the Q3 number before Q2 even closes.

When Sales Teams Use Lead Velocity Rate

Founders and CEOs at growth-stage SaaS companies watch LVR more closely than ARR growth because LVR moves first. CFOs include it in board decks. Demand gen leaders use it to defend marketing budget — if LVR is climbing, ad spend is working before the closed-won data confirms it. VPs of Sales use it to argue for AE headcount: rising LVR with flat capacity means the next quarter's bottleneck is going to be reps, not leads.

It is especially useful as an early-warning system. Bookings can stay flat for a quarter because of long sales cycles, but LVR will show the deterioration two months earlier. Companies that miss their number rarely missed the LVR signal — they ignored it.

Common Lead Velocity Rate Gaming Patterns

The single biggest LVR exploit is loosening the qualification bar. Marketing wants to show 20% LVR this month, so the MQL threshold drops from "form fill plus title match" to "form fill, any title." The number prints; sales rejects 40% of the new leads as unworkable. Net SQL volume is flat, but the headline LVR looks great until the bookings number lands.

A second pattern is timing manipulation. Leads get held back at month-end and released on the 1st to make the new month's start look strong. Reverse engineering shows up in the day-by-day SQL creation curve: a healthy funnel produces leads on Tuesdays through Thursdays; a manipulated one shows a suspicious spike between days 1-3.

LVR also tells you nothing about lead quality or deal size. A team can post 25% LVR by buying a list and dumping it into SDR cadences, then watch the SQL-to-opp rate collapse from 30% to 8%. The number that matters is qualified pipeline dollars, not lead count. LVR is a useful leading indicator only when the qualification definition is held constant — the moment it floats, the metric becomes self-congratulatory noise.

Related terms

Ready to see your numbers?

Get your verified Alpha Score. Read-only CRM, score within minutes.

Get my Alpha Score