Qualified Lead Definition — Revenue Threshold Model

Overview

When structuring performance-based marketing agreements, a clear, contractual definition of what constitutes a "qualified lead" is essential. Without it, attribution disputes arise — the client questions whether a lead was truly generated by the agency's work, and the agency questions whether it's being fairly compensated. A minimum revenue threshold model resolves this by anchoring lead qualification to a measurable client outcome rather than a channel or activity.

The core principle: a lead only counts if the prospective customer represents revenue potential above a defined floor (e.g., $100k+ annual spend). Everything below that threshold is excluded from performance fee calculations, regardless of source.

The Problem This Solves

B2B clients often already receive a mix of inbound leads — some high-value, some low-value — through existing paid search, paid social, or organic channels. When an agency takes over or augments marketing, several tensions emerge:

Attribution gray zones: Did that lead come from the agency's ABM campaign or the client's existing Google Ads?
Misaligned incentives: An agency paid per lead has an incentive to count every inquiry; the client wants to pay only for leads that actually move the business forward.
Volume vs. quality: Raw lead volume can increase while lead quality declines, wasting the client's sales team's time.

A revenue threshold cuts through all of this. If the prospective customer can't plausibly spend above the floor, the lead simply doesn't count — no debate required.

How the Model Works

Define the threshold contractually. Agree on a minimum annual revenue potential (or order value) that a prospect must represent to qualify. This number should reflect the client's strategic target segment, not just an arbitrary cutoff.
Scope attribution to specific channels. Pair the revenue threshold with a channel scope. For example: the performance fee applies only to leads generated through ABM outreach, LinkedIn, email campaigns, and content marketing — explicitly excluding paid search and paid social channels the client already operates independently.
Exclude pre-existing accounts. Leads already in the client's CRM (e.g., Salesforce) at contract start are excluded. This prevents the agency from being credited for pipeline that existed before engagement.
Set a post-contract attribution window. B2B sales cycles are long. Agree on a window (e.g., 12 months post-contract) during which closed revenue from qualified leads introduced during the engagement still triggers the performance fee.
Reverse-engineer funnel KPIs. Because revenue takes time to materialize, define leading indicators — meetings generated, presentations made, proposals sent — that demonstrate the funnel is working before deals close. These serve as interim performance benchmarks.

Example: Paper Tube

^[1] applied this model when finalizing their marketing services agreement with Asymmetric. Key parameters:

Revenue threshold: $100k+ annual spend potential per prospect (exact figure to be confirmed by Parag Agrawal)
Attribution scope: ABM outreach, LinkedIn, email, and content marketing only — paid search and paid social explicitly excluded, as Paper Tube already runs those independently
Performance fee: 8% flat on revenue from new qualified leads
Post-contract window: 12 months
Rationale: Paper Tube's strategic priority is shifting away from small startup/indie brands (high volume, low value, high churn) toward established brands with reliable, growing spend. The threshold enforces that strategic focus at the contract level.

Parag's framing was direct: "I don't need more garbage that we have to cull through. What I really need are companies that have the ability to spend." The revenue threshold translates that business priority into a contractual mechanism.

Why This Prevents Attribution Disputes

The alternative — benchmarking against a baseline index and crediting the agency for incremental lift — is conceptually sound but operationally messy. As Parag noted, it creates ongoing debates: "Well, that doesn't count. Well, this counts." Those debates are unproductive for both parties and erode trust.

A binary threshold is clean: either the prospect meets the revenue floor and was introduced through an in-scope channel, or they don't count. There's no index to argue about, no baseline to recalculate.

Considerations When Setting the Threshold

Set it at the client's real target, not a stretch goal. If the client genuinely wants $100k+ accounts, that's the threshold. Setting it too high means the agency can never qualify leads; too low recreates the volume-vs-quality problem.
Align with the client's existing sales qualification criteria. If the client's sales team already uses a minimum deal size to prioritize outreach, the contract threshold should match.
Revisit as the engagement matures. Early in an engagement, the threshold may need adjustment as both parties learn what the market actually yields.
Document how revenue potential is assessed. For prospects that haven't yet placed an order, agree on how potential is estimated (e.g., company size, industry benchmarks, stated intent).

^[2] — Leading indicators to track before revenue closes
^[3] — How to structure performance fees alongside retainers
^[4] — Setting post-contract attribution windows for long B2B sales cycles
^[5] — Source meeting where this model was negotiated