Most SaaS RevOps leaders have sat through the same agency pitch: a promise of thousands of leads inside a few weeks, delivered against a headline cost per lead that looks unbeatable on a spreadsheet. The problem shows up later, once those contacts hit the CRM and sales starts working them. This piece sets out what actually distinguishes a lead worth chasing from one that only pads a report, how to measure pipeline health without being fooled by volume, and how to build a qualification framework that sales will actually trust.
Why Lead Volume Numbers Mislead RevOps Teams
Agencies that bill per lead delivered are structurally incentivised to maximise the count of contacts handed over, not the proportion that ever buy. That incentive shapes how “lead” gets defined in the contract. A form fill on a low intent gated asset, an email address scraped from a public directory, and a genuine budget holder who booked a demo can all get reported under the same word. When the definition is loose enough, the number climbs, and the report looks good even though almost none of those records are ready for a sales conversation.
The distortion compounds through cost per acquisition. A low cost per lead figure looks attractive in isolation, but once you divide total spend by the number of contacts that actually convert to a qualified opportunity, the real cost per SQL can be several times higher than what a smaller, better targeted campaign would have produced. Teams that only track cost per lead never see this, because the metric hides the collapse in conversion rate downstream.
There is also a quieter mechanical problem: recycled and repurposed contact databases. The same person can reappear as a “new lead” across two or three campaigns run months apart, particularly when a vendor is drawing from the same scraped list each time. Reported pipeline volume grows even though no new demand has entered the funnel, and forecasting built on that number will consistently overstate what sales can realistically close.
What Makes a SaaS Lead Genuinely High Quality
A high quality SaaS lead sits at the intersection of three separate conditions, and the relationship between them is closer to multiplication than addition. Firmographic fit covers company size, industry, and technical stack compatibility with the product. Role authority covers whether the person can actually approve a purchase or is one step removed from someone who can. Buying stage signals cover behaviour that indicates active evaluation, such as depth of trial usage, repeated visits to a pricing page, or engagement with implementation documentation rather than only top of funnel content.
A contact can score perfectly on firmographic fit and still be worthless to sales if there is no engagement signal attached to them; an account with a large deployment and no economic buyer identified is not yet sales ready either. Treating these three conditions as independent checkboxes, where a lead only needs to clear one or two, is how teams end up with a CRM full of records that look qualified on paper but go nowhere in a pipeline review.
The Compounding Cost of Chasing Low Quality Leads
The most direct cost sits with SDRs, who spend hours dialling and emailing contacts that were never going to respond, time that could have gone into a smaller number of accounts with a real chance of converting. That cost is visible on an activity report but rarely gets traced back to the source campaign that generated the bad list.
A second, less visible cost is forecasting distortion. When leadership builds quarterly plans against an inflated pipeline that includes large numbers of low intent contacts, the plan is wrong from the day it is written. The gap only becomes obvious when the quarter closes and win rate against forecast comes in far below expectation, by which point the damage to hiring plans and board reporting has already been done.
A third cost is trust between marketing and sales. When marketing hands over MQLs defined loosely as any form fill, and sales rejects most of them at the first call, sales stops trusting marketing sourced pipeline entirely and starts self sourcing instead. That breaks the funnel model both teams are supposed to be operating against, and it is difficult to repair once reps have decided marketing leads are not worth their time.
Metrics That Reveal Real Pipeline Health
Raw lead count answers a question nobody in a revenue review actually needs answered. The metrics that matter are the ones that trace a contact through to a closed outcome, and they require the CRM’s stage history to be reasonably clean before they mean anything.
SQL to Win Rate and Deal Velocity
SQL to win rate tells you what proportion of qualified opportunities actually close, which is the number that should drive budget decisions far more than top of funnel volume. Deal velocity, the average number of days a deal spends in each stage, points to exactly where a pipeline is getting stuck. A falling SQL to win rate combined with lengthening time in a specific stage, such as proposal to close, usually points at a qualification gap rather than a sales execution problem, since deals that were never truly ready to buy tend to stall at the same point regardless of who is working them. Salesforce’s opportunity stage and reporting documentation covers how these stage transitions are tracked natively (help.salesforce.com).
Multi Touch Attribution by Channel
First touch attribution credits whichever channel introduced a contact and last touch credits whichever channel was active right before a deal closed; both routinely overstate the channel that happens to sit at the edge of the funnel and understate everything in the middle. A multi touch model that distributes credit across every touchpoint in a deal’s history gives a fairer read on which channels are actually contributing to revenue, and it is the only reliable way to compare an outbound agency’s contribution against inbound or partner sourced pipeline on equal terms. HubSpot’s reporting and property documentation is a reasonable starting point for setting this up inside a CRM (developers.hubspot.com).
Agency, In House or Hybrid: Choosing a Lead Generation Model
Agencies bring reach and speed that most in house teams cannot match in the short term, particularly for a company entering a new segment or region. Their weakness is accountability: an agency paid on volume has little reason to tighten its own targeting criteria once the contract is signed, and hidden management fees can obscure how much is actually being spent per qualified opportunity rather than per raw contact.
An in house team gives tighter control over how a lead gets defined and scored, because qualification criteria live inside the same systems sales uses to run its process, rather than inside a vendor’s separate reporting dashboard. The tradeoff is speed to scale: hiring and training an in house team to match an agency’s short term volume takes months, not weeks.
A hybrid model, where an external partner handles top of funnel outbound reach at scale while an internal RevOps function owns scoring, routing, and disqualification, tends to combine the strengths of both without inheriting either weakness outright. Every contact the agency sources gets filtered through the same criteria as internally generated leads before it ever reaches an SDR’s queue, which removes the agency’s incentive to inflate volume since it no longer controls what counts as qualified. Equanax’s own RevOps builds for clients have included setups spanning 6 pipeline stages, 13 automation workflows and 3 dashboards, which gives a rough sense of the scale of internal scaffolding a hybrid model of this kind typically needs to run properly.
Building a Lead Qualification Framework Sales Teams Trust
Classical frameworks such as BANT and MEDDIC were built for longer, more deliberate B2B sales cycles and need adjustment for SaaS, where product usage itself generates a rich stream of buying signals that neither framework was designed to capture. The adjustment is usually to keep the underlying logic (qualifying on need, authority, and timing) while adding a scoring layer built from product and web behaviour rather than only from what a prospect says on a discovery call.
Fit, Intent and Engagement Signals
Turning the three conditions from the framework above into a working score means assigning each one a data source and a point value rather than leaving it as a qualitative judgement call. Fit typically pulls from a firmographic enrichment provider and gets scored on a fixed scale, for example zero to twenty points, based on how closely a company matches the ICP definition. Intent and engagement scores usually live inside the CRM or marketing automation platform itself, tracked as event based triggers, where a pricing page visit might add five points and a second trial login within a week might add ten. The three subtotals are then summed into a single composite figure, and it is that threshold, not the presence of any one strong signal, that determines whether a contact gets routed to a sales queue. A model that lets a very high score in one category compensate entirely for near zero scores in the other two reproduces the exact problem the framework was built to solve, just with a number attached to it instead of a gut feeling.
Setting Score Thresholds and Routing Rules
Thresholds should never be set once and left alone. Sales messaging, product positioning, and the ICP itself all shift over time, and a threshold calibrated against last year’s win data will drift out of alignment with reality without anyone noticing until win rate quietly declines. A working routine reviews closed won and closed lost deals against their original scores on a regular cadence, most commonly monthly or quarterly, and adjusts weightings where the data shows a mismatch, for example if a signal that used to predict a win no longer does after a product change.
Rolling Out Lead Scoring Without Breaking Sales and Marketing Alignment
A scoring model only works if marketing and sales agree, in writing, on what an MQL and an SQL actually mean, and on the service level agreement that governs how fast sales responds once a contact crosses the qualifying threshold. Without that agreement, sales will keep applying its own informal filter on top of whatever marketing hands over, which defeats the purpose of building a formal model in the first place.
Automation should tighten this process rather than replace human judgement in it entirely. Over automating disqualification, for example auto rejecting any contact that does not match a narrow set of firmographic rules, risks silently filtering out good accounts that simply do not fit the existing pattern, such as a new market segment the model was never trained to recognise. A periodic manual audit of a sample of disqualified records, alongside the win and loss review used to recalibrate thresholds, catches this kind of false negative before it costs the company a segment it could otherwise have won.
Data protection also sits underneath all of this. Purchased or scraped contact lists used for B2B outreach in the UK still need to satisfy the legitimate interest and direct marketing conditions set out under UK GDPR and the Privacy and Electronic Communications Regulations, and the ICO’s guidance for organisations is the primary reference point for getting that assessment right before a list ever gets loaded into an outbound sequence (ico.org.uk).
Related Reading
For more on this, see more on lead generation and outreach, including LinkedIn Prospect Export Guide: Compliant Strategies for Scalable B2B Lead Generation, Scaling SaaS Growth with LinkedIn Signals and AI-driven RevOps, and Lead Generation: Essential Tips and Strategies for 2024.
How can we tell if an agency is inflating its reported lead numbers?
Compare the delivered lead count against SQL conversion and sales accepted rate over a rolling period rather than looking at the lead count alone. A sudden spike in delivered volume with no matching increase in SQLs or accepted opportunities is the clearest sign that the list is being padded rather than genuinely qualified.
How should fit, intent and engagement signals be weighted against each other in a scoring model?
None of the three should be allowed to qualify a lead on its own. A practical approach scores each group separately and only routes a contact to a sales queue once it clears a minimum bar across all three, since strong fit with no intent or engagement, or strong engagement from someone with no authority, both fail to indicate a genuine buying opportunity.
What is deal velocity and why does it matter more than raw lead volume?
Deal velocity is the average number of days an opportunity spends in each pipeline stage. It matters more than lead volume because it shows exactly where deals are stalling, which points at a specific qualification or process gap rather than a generic call for more top of funnel activity.
Should a SaaS company build lead qualification in house or use an agency?
Agencies offer faster reach for a company entering a new segment, but a hybrid model where an agency handles outbound volume while an internal RevOps function owns scoring and routing tends to combine the reach of an agency with the accountability of an in house team.
How often should lead scoring thresholds be recalibrated?
Most teams review closed won and closed lost deals against their original scores monthly or quarterly and adjust weightings where the data shows a mismatch, since product changes and shifting ICPs will drift a static threshold out of alignment with actual win data over time.
Leave a Reply