Sales qualified lead velocity

A consulting firm was generating 20 SQLs monthly with inbound leads only, which wasn't enough to support their sales team. They hired two SDRs to convert outbound meetings into qualified prospects. The SDRs identified companies matching their ICP, conducted outreach campaigns, and qualified interested prospects before passing to sales. SQL velocity immediately jumped from 20 to 55 monthly, allowing the sales team to be fully utilised and grow revenue by 85% within 12 months despite the cost of hiring the SDR team.

A B2B SaaS company's SQL velocity was 45 monthly, and conversion was only 12%, so they were generating lots of marginally-qualified leads. Rather than focusing solely on increasing volume, they tightened SQL qualification: leads now had to show clear product usage intent (filled out a specific product demo request, not just generic interest form) and fit within their ICP (company size, industry, location). This raised their bar for SQL, and velocity dropped to 32 monthly initially. However, conversion rate jumped to 35% because real qualified leads were being prioritised. The company generated fewer deals this way initially but higher quality pipeline, and after they increased marketing generation to hit the 45 target, they were hitting their conversion goals.

An SaaS company's SQL velocity was stagnant at 40 monthly despite strong marketing lead generation of 200+ leads per month. Analysis showed that marketing and sales disagreed on what constituted an SQL: marketing was passing all leads with company info on file, whilst sales expected leads to have demonstrated product interest. They jointly rebuilt their SQL definition and implemented a qualification workflow: marketing leads scoring above threshold were automatically routed to SDRs, who conducted 15-minute qualification calls. SQL velocity increased to 85 monthly within two months as the handoff became clearer and leads stopped falling into black holes.

Sales qualified lead velocity is just the speed at which your sales team gets fresh, ready-to-buy leads. If 50 leads cross your qualification line in a month, your monthly SQL velocity is 50. An SQL (sales qualified lead) is a lead someone has actually looked at and judged ready for a sales conversation: right market, some genuine interest, fits your ideal customer profile. Velocity is the flow through that quality gate, not your total lead count and not your eventual close rate.

This is the number that quietly caps your growth. You can't close deals that were never in the pipeline. If you need 30 new customers a month and one in four SQLs closes, you need 120 SQLs landing every month, roughly 28 to 30 a week. Generate only 80 and you'll miss target no matter how sharp your reps are. So track it weekly, not just at month-end, and the moment it dips you can ask the honest question: is marketing sending fewer leads, are the SDRs qualifying harder, or did everyone quietly drift on what "qualified" even means?

Why it matters

Velocity tells you two things at once: whether you'll hit the number, and where the bottleneck is when you won't. A high bar with low velocity means you're starving the funnel; steady velocity with a poor close rate means those "qualified" leads aren't really qualified. It also sets your hiring ceiling, no point hiring a fourth rep if you only feed three.

How to apply it

First, write the SQL definition down and make everyone use the same one, or the number means nothing. Say you're running outbound prospecting in Apollo: you can encode your ICP filters (company size, industry, intent signals) right into the search so an SDR only ever qualifies leads that already fit, which keeps the gate consistent instead of vibe-based.

Second, watch the flow in real time. Say you're running your pipeline in Close: tag a lead the moment it's qualified and you can pull this-week-vs-last-week SQL counts straight from the activity feed, catching a two-week slide before the month closes rather than discovering it in the monthly deck.

Third, put the trend on a wall. Say you're tracking it in Databox: wire your CRM in and chart SQL velocity against your weekly target so marketing and sales stare at the same line, which is usually what finally kills the argument over what counts as an SQL.

The pattern to expect: tightening your qualification bar drops velocity at first and lifts your close rate, then you scale lead generation back up to refill the now-cleaner funnel.

Establish a clear, consistent definition of an SQL. An SQL typically means a lead that has been manually reviewed and deemed ready for a sales conversation because they meet basic criteria: they're in your target market, they've expressed some interest, and their company fits your ICP (ideal customer profile). Write this definition explicitly and train all team members on it so qualification remains consistent over time.

Measure SQL velocity weekly or bi-weekly rather than waiting until monthly reporting. Weekly velocity tracking reveals trends early: if velocity drops for two weeks, you can diagnose and act before the month ends. Monthly snapshots hide in-month volatility and delay response.

Set targets for SQL velocity and make the entire team responsible for them. If your sales target is 30 closes monthly with a 25% conversion rate, your SQL target is 120, which means 28-30 per week. When marketing and SDRs understand what they need to hit, they prioritise accordingly. Marketing stops chasing vanity metrics like total leads and focuses on qualified leads that convert.

SQL velocity directly determines whether you'll hit growth targets. If you need to close 30 customers monthly at a 25% conversion rate, you need 120 SQLs monthly. If you're generating only 80 SQLs monthly, you won't hit targets regardless of how efficient your sales team is. SQL velocity is the ceiling on growth: you can't close deals that don't exist in your pipeline.

Tracking SQL velocity reveals bottlenecks in your acquisition process. If velocity is declining month-over-month, you know you need to diagnose whether marketing is generating fewer leads, SDRs are qualifying more aggressively (good or bad depending on context), or definition/standards have shifted. This diagnostic clarity is impossible without velocity tracking.

For planning and investment, SQL velocity determines how many reps you can productively employ. If you can generate 100 SQLs monthly but only 3 sales reps can close them, you have a capacity ceiling. Understanding your SQL velocity helps determine whether to hire sales reps (if velocity can support them) or focus on demand generation first.