Any Agency That Guarantees You 30 SQLs a Month Is Lying to Someone

SQL volume is a function of your ICP size, your price point, your sales cycle, your existing brand presence, and the maturity of your product-market fit. An agency that promises a fixed number before understanding those variables is not guaranteeing an outcome. It is guaranteeing that something will be labelled an SQL.

Why the guarantee sells anyway

The pitch works because it converts an uncertain investment into what sounds like a purchase order: pay X, receive 30 SQLs. Buyers under pipeline pressure want that certainty, and finance teams approve line items with deliverables attached. But lead generation is not procurement. The honest version of the sentence is 'we will label 30 things SQLs', and the difference between those two sentences is where the entire trick lives. When a vendor prices certainty in a system they have not examined, they are not pricing your outcome. They are pricing your urgency. The same pressure that makes the guarantee attractive is the pressure that should make you slow down and look at what actually determines volume in your specific market.

How the trick works

Guaranteed-volume agencies hit their number by degrading the definition: booked calls counted as qualified, curiosity meetings dressed up as intent, prospects bribed with gift cards. You get the SQLs. Your sales team gets a quarter of no-shows and your CAC quietly doubles.

The second-order damage

The wasted retainer is the cheap part. The expensive part compounds over the following two quarters. Your AEs learn that marketing-sourced meetings are junk, so they stop preparing for them, and the occasional genuine buyer gets a flat first call. Your forecast inflates and then collapses, which costs credibility with the board. Your ICP data gets polluted, because a quarter of gift-card meetings teaches your systems that the wrong companies are your buyers. And churn arrives early, because deals pushed through a degraded definition were never qualified to succeed. Cleaning this up costs more than the original programme, which is why the cheapest moment to be sceptical is before signature.

What honest looks like

At mid-market deal values ($30K to $200K ACV), realistic SQL targets after a 60-day ramp typically land between 4 and 15 per month, depending on ICP size, outbound capacity, and market maturity. The honest sequence is: diagnose first, baseline within 60 days, set quarterly targets collaboratively, review them openly, and own the misses.

The arithmetic behind those numbers

The range is not modesty. It is multiplication. Suppose your true ICP contains 2,000 accounts, your team can properly work 150 of them a month, a well-run motion gets responses from a tenth, and half of those conversations qualify. That is seven or eight genuine SQLs a month, and every input in that chain is visible and improvable. Now run the same arithmetic for a promise of 30: it requires either an ICP several times larger than yours, a response rate no cold channel reliably produces, or a qualification bar low enough to admit anyone. When a vendor shows you their assumptions, you can argue with the inputs. When they only show you the output, the inputs do not exist. This is the same reasoning we apply to outbound programme design: pipeline math you can audit beats pipeline math you have to trust.

The question to ask any agency

'Show me the definition of SQL you will report against, and show me a client where you missed target. What happened next?' The first answer tells you what you are buying. The second tells you who you are buying it from.

Red flags in the first sales call

The tells show up before any contract does. A vendor who quotes a volume before asking about your ACV, sales cycle, and ICP size is pricing a template, not your market. A definition of 'qualified' they cannot produce in writing on request, or one that quietly means 'accepted a meeting'. Case studies with impressive numbers and no context: no deal size, no market, no timeframe, nothing you could check. Pricing anchored per lead rather than per outcome, which pays them for labels. Pressure to sign inside the week because 'onboarding slots are closing'. And the subtlest one: no curiosity. An honest operator interrogates your funnel before promising anything, because their forecast depends on it. A dishonest one already knows the number they will promise you, because it is the same number they promised the last three prospects.

If you already signed one

If you are mid-contract with a volume guarantee, salvage rather than sulk. First, audit the last two months of delivered SQLs against your own definition of qualified, deal by deal, and put the acceptance rate in writing; that number is your negotiating position. Second, renegotiate the remaining term onto evidence-based quarterly targets with the definition attached, which honest vendors will accept and volume shops will refuse, telling you which one you have. Third, keep the by-products: account research, response data, and the message variants that produced genuine conversations all transfer to whatever you run next. And bring the acceptance-rate audit into your regular pipeline review so the CRM record reflects what the programme actually produced. The retainer may be sunk; the data does not have to be.

A contract structure that keeps everyone honest

If you want accountability without fiction, structure the engagement in three parts. A fixed diagnostic phase that produces the baseline and the assumptions, in writing. A quarterly target set from those assumptions, with the definition of qualified attached as a contract exhibit, not a slide. And a review clause both sides can invoke: if the number misses for two consecutive months, the response is a documented change of approach, not a redefinition of the metric. Vendors who do honest work accept this structure readily, because it protects them too. Vendors who sell certainty resist it, which is itself the answer. This is exactly how we scope our own engagements: baseline first, targets from evidence, misses owned in the open.