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.
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:
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.
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.
[1] applied this model when finalizing their marketing services agreement with Asymmetric. Key parameters:
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.
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.