A surprising number of agency-client disputes trace back to the same root cause: something that should have been in the contract was instead a verbal understanding that the two parties remembered differently three months later.
Every item below is cheap to specify before a campaign starts and expensive to renegotiate after a client is unhappy. A contract signed before infrastructure work begins, covering the items in this guide, is what turns "I thought we agreed..." into a two-minute contract lookup instead of a strained conversation.
Specify exactly what's included: number of campaigns, target send volume, number of sequences, whether copywriting is included or client-supplied, and what counts as a revision versus a new deliverable. Vague scope is the single most common source of "scope creep" friction — a client reasonably assuming something is included that the agency reasonably assumed was extra.
If any part of pricing is performance-based (see our pricing models guide), the contract needs an explicit definition of what counts: minimum company size or revenue band, job title or seniority of the attendee, meeting duration, and what confirms a meeting as "held" versus a no-show. Leaving this undefined is exactly what turns a performance-pricing relationship into a recurring invoice dispute.
This is the section most agency contracts underspecify, and it's directly connected to real legal exposure — see our guide to agency compliance for the full picture on why. At minimum, the contract should cover: which party supplies the physical address and sender identification details required under laws like CAN-SPAM and CASL, who confirms the legal basis for each contact list used, and — for EU/UK-facing campaigns — whether a separate Data Processing Agreement is in place.
A missing compliance clause doesn't make the agency's liability disappear — it just leaves it undocumented. Several of the laws covered in our compliance cluster hold the agency independently responsible regardless of what the client assured you. Get this in writing rather than assuming it's implied.
Specify who owns the lead list and reply data at the end of the engagement — the client, generally, but this should be explicit rather than assumed, along with what happens to that data if the relationship ends: deletion, handoff, or continued agency use for a defined period.
A standard notice period (30 days is common for retainer engagements) protects both sides — the client from being locked in indefinitely, the agency from losing revenue with zero warning. Specify what happens to in-flight campaigns, infrastructure (domains registered under the agency's account versus the client's), and any remaining deliverables at termination.
Scope of work, payment terms, a defined "qualified meeting" if any pricing is performance-based, compliance and liability responsibility, data ownership, and termination/notice terms — all specified in writing before the first send.
Because an undefined qualification standard is one of the most common sources of billing disputes under performance-based pricing — specifying minimum company size, attendee seniority, and no-show handling in writing prevents a recurring argument over what counts.
Yes. Several cold email laws hold both the agency and the client independently responsible for compliance regardless of assurances either side gives verbally — the contract should specify who handles sender identification, list legal basis, and (for EU/UK campaigns) whether a Data Processing Agreement is in place.
This should be specified explicitly in the contract rather than assumed. It's typically the client, but what happens to the data at termination — deletion, handoff, or limited continued agency use — needs its own clause.
Related guides
Written by
Scott Holmes
AI systems consultant based in Barrie, Ontario. Founder of Pinnacle Tech Projects. Has structured agency-client agreements for cold email engagements across multiple pricing models.
Answer four quick questions and get a tool recommendation for your setup.