5 things to check in a UK lead generation agency contract

What to take away

Why a UK lead generation agency contract needs a defined lead record

A lead generation contract is not a supply agreement for goods. It is a set of promises about data, timing and money, and each promise needs a record behind it.

Most disputes we see between buyers and networks in Greater London, the South East and the North West start in the same place. The contract says "valid lead" or "qualified enquiry" and neither side can point to the clause that decides the argument.

A defined lead record fixes that. It states what an accepted lead looks like, who decides, how long the decision takes and what happens when the answer is no.

The record matters commercially as well as legally. Sales teams forecast on accepted leads, finance teams pay on invoices, and both need the same number. If the contract does not define the unit, the invoice and the forecast will disagree.

This is why we point buyers towards contract records that define a lead before they argue about price. Price per lead is meaningless until the lead is defined.

What the five checks cover

Check one: the definition of a lead and the acceptance test

Start with the unit. A lead definition should name the data fields, the source, the geography and the sector, and it should be narrow enough to test.

"A consumer who has expressed interest in a product" is not a definition. "A named individual, resident in the UK, who has submitted a form on a named site, with the fields listed in Schedule 1, and who has not previously been sold to the buyer" is a definition.

The acceptance test is the second half. It sets the window in which the buyer must accept or reject, the grounds for rejection and the evidence required.

Common grounds include a duplicate already held by the buyer, a disconnected number, a mismatch with the agreed sector or a missing consent record. Each ground should be listed, not left to "reasonable rejection".

The window matters. A 48 hour window suits high volume, low value enquiries. A five working day window suits regulated sectors where a callback is part of the sale.

Worked example: a rejected lead

A network supplies 400 enquiries a month to a home improvements firm in the West Midlands. The contract defines a lead as a homeowner in a named postcode area who has requested a quote.

One enquiry arrives with a postcode outside the agreed area and a consent record that names a different brand. The buyer rejects it on day two, inside the window, citing two listed grounds.

The contract says rejected leads are credited in the next invoice period if the rejection is inside the window and the ground is listed. The credit is applied. No argument, no lost goodwill.

Without the definition, the acceptance test and the listed grounds, that same enquiry becomes a phone call, then a dispute, then a deduction taken without agreement.

The acceptance test in practice

Check two: data handling, consent evidence and lawful basis

Data handling clauses describe what the network does with personal data, who else touches it and on what basis. In the UK that means UK GDPR and the Data Protection Act 2018.

The contract should name the lawful basis for each processing activity. Consent is the usual basis for consumer lead generation, but legitimate interests can apply in some B2B contexts. The basis must match what the privacy notice says.

Where consent is the basis, the standard is specific and informed. The ICO's guidance on Consent | ICO sets out what a valid consent record needs, including the name of the organisation relying on it.

Consent evidence is the practical test. For each lead, you should be able to produce the time, source, wording shown and the brands named. A monthly summary is not evidence.

Data sharing between a network and its buyers is a controller to controller arrangement in most cases. The ICO's Data sharing | ICO guidance covers the information sharing agreements and the transparency expectations that follow.

What to ask for in the data handling clause

On breach notification, the clock is short. The ICO's Personal data breaches: a guide | ICO explains the 72 hour reporting duty where a breach is likely to risk people's rights.

Accountability is the wider duty. The ICO's Guide to accountability and governance | ICO expects records of processing, contracts that set responsibilities and evidence that the arrangements are reviewed.

PECR sits alongside this for electronic marketing. Cold calling and unsolicited electronic mail have their own rules, and a lead contract should say which party is responsible for compliance on each channel.

Consent evidence in a form you can use

Ask for a specimen record, not a description. You want to see the timestamp, the URL, the exact wording, the brands named and the IP or device data held.

Then test it. Pick five leads at random and ask for the consent record for each. If the network cannot produce them within a working day, the clause is decorative.

Check three: delivery, replacement and refund terms

Delivery terms set volume, cadence and the delivery method. A monthly cap with a daily flow is different from a monthly dump, and the difference shows up in contact rates.

Replacement and refund terms are the commercial heart of the contract. They should follow the acceptance test rather than sitting in a separate schedule with different wording.

A common structure is a replacement window: rejected leads are replaced within a set period, and if no replacement is available, a credit is issued. Refunds are rarer and usually reserved for termination or persistent failure.

The refund route should name the trigger, the calculation and the payment period. "Refund at our discretion" is not a term a buyer can plan around, and it invites argument.

Ask how credits are applied. Credits against future invoices are common, but they tie you to the supplier. Cash repayment is stronger if the relationship is likely to end.

Replacement and refund comparison

Service levels sit alongside these terms. Uptime, delivery windows and contact data accuracy should be measured, and the measurement method should be the same one used for credits. Our note on service standards covers how to measure transitions rather than vague quality.

Check four: exit, data return and deletion on termination

Exit terms are where most lead contracts are thinnest. Buyers focus on price and volume, then discover at termination that data return was never agreed.

A workable exit clause covers notice, run off, data return, deletion, suppression and outstanding credits. Each has a date attached.

Data return should be specific: which records, in what format, within how many days. Deletion should cover the network's copies, backups and sub processors, with a certificate or written confirmation.

Suppression lists are the exception to deletion. Both parties usually need to keep a suppression list to honour opt outs, and the contract should say so, with the retention period named.

Run off matters where leads are in flight at termination. The contract should say whether leads already supplied but not yet accepted are still tested against the acceptance test.

Outstanding credits and refunds should survive termination. If they do not, the exit clause hands the supplier a free option.

This is why we advise buyers to have exit proven before signature. Exit terms negotiated after a dispute are rarely favourable.

Exit checklist

Check five: liability, consumer terms and dispute route

Liability clauses decide who carries the cost when something goes wrong. The usual structure is a cap, a set of exclusions and a carve out for the things that cannot be capped.

Data protection breaches, regulatory fines and fraud are common carve outs. Expect resistance, and expect the cap to be expressed as a multiple of fees paid.

Consumer law enters the picture in two ways. If the buyer is a consumer, or if consumer terms are embedded in the lead flow, the Consumer Rights Act 2015 governs fairness and remedies. The Act is set out in full at Consumer Rights Act 2015.

Even in business to business contracts, terms that are unfair can be challenged. The Act's fairness provisions matter where a network imposes wide discretion on itself.

Regulated sectors add their own layer. FCA rules apply to credit, insurance and claims leads, and the ASA polices advertising claims in the lead creative. The contract should say who owns the creative and who checks it.

Dispute routes should be staged: a named contact, a review period, then mediation or arbitration, then court. A named governing law and jurisdiction clause avoids a fight about where to sue.

Pricing disputes deserve their own route. Volume tiers, credits and reconciliation are frequent sources of disagreement, and our comparison of dispute rights sets out how pricing models change the argument you end up having.

Dispute route in order

Turning the five checks into a contract review record

The five checks are only useful if they produce a record someone can act on. Build one document that mirrors the contract structure and records your position on each point.

Start with the lead definition and the acceptance test, because every other term depends on them. Then work through data handling, refunds, exit and liability in that order.

For each item, record the clause reference, the position agreed and the gap. Gaps are the useful part. A review that lists what is missing is worth more than one that confirms what is present.

Use a control log to track gaps to signature. Our lead specification to control log template shows how the specification, the acceptance test and the control log connect.

Once signed, the review record becomes an operational document. The acceptance test, the rejection grounds and the credit rules are what your sales and finance teams use every month.

Review it at renewal and after any material change in the lead source, the lawful basis or the delivery method. Contracts drift, and the record should drift with them.

Common questions