Evaluation RuleDecision layer

Lead Gen Rule: Price the Targeting Hypothesis Before You Price the Seats

When a client asks for more leads, should the agency buy more contact volume or sell a sharper targeting hypothesis? Sell the targeting hypothesis and the qualification score as the deliverable, and treat contact data as the pass-through input it is.

By InnovaAI ResearchPublished

“When a client asks for more leads, should the agency buy more contact volume or sell a sharper targeting hypothesis?”

Sell the targeting hypothesis and the qualification score as the deliverable, and treat contact data as the pass-through input it is.

Common Mistake

Operators resell seats and list volume, then discover the client can price the same records elsewhere in an afternoon; the agency ends up defending a per-contact rate instead of a targeting framework, and the retainer gets renegotiated as a software line item.

Why This Works

Contact databases have converged: AnyBiz ships a 450M-record B2B file, Leadinfo surfaces decision-makers from 300M+ contacts, and Origami assembles lists from 50+ live sources on a natural language prompt, so record count is no longer a differentiator an agency can charge for. The margin sits in the judgment layer, and that layer fails on inputs: dirty contact data is the most common root cause of automation breakdowns, with duplicates and unvalidated emails producing bad outputs at scale. Buyers are also asking harder ROI questions of automated outreach, and an agency that cannot show which trigger produced which meeting has no answer.

Apply When
  • •A client retainer is being renewed and the conversation drifts toward adding seats or contact credits
  • •Prospect lists are being built from a broad firmographic filter with no named trigger event
  • •The agency is quoting a lead-gen engagement and the scope is written as tool access plus list volume
  • •Reply rates have flattened while list volume has grown month over month
  • •A client is comparing the agency's quote against a per-contact price from a self-serve database