Cold email for marketing agencies without sounding like every other agency
Agencies win cold email by being specific: one segment, one problem you can name from outside, one piece of proof, one question. Send from an authenticated domain, keep volume modest per mailbox, and stop the sequence on reply. The goal is a conversation, not a proposal in the first message.
The first line decides the reply
Agency cold email usually fails because the first line is about the agency. Replace it with something the recipient can verify about their own business: a page that has not been updated, a campaign running to the wrong audience, a channel they have not opened.
You do not need a research report. One observable detail is enough, and it proves a human looked.
One proof, not a portfolio
Link one case study, not six. Six links read as a brochure and give the recipient nothing to decide. One relevant example answers the question they actually have: have you done this for someone like me.
If you have no case study in their vertical, say what you would do first and why. Honesty about the gap is more persuasive than a generic claim.
Protect the domain you send from
Use one mailbox per campaign, authenticate the domain, and keep the first batch small. Agencies often send from the main brand domain, which means a single bad campaign risks the business's own email.
A separate sending domain costs little and keeps the risk where it belongs.
What to do when a prospect is already being pitched
Assume they are. Your first line has to prove you are not the fifth identical agency email that day, which means it cannot be about your services. It has to be about something they can verify about themselves.
If they reply with a polite no, ask what would make it relevant later and record the answer. That answer is the best market research an agency gets.
Keeping client work separate from your outreach
Send agency prospecting from its own domain and its own mailboxes. Mixing it with client sending means a bad campaign can affect deliverability you are responsible for on someone else's behalf.
Keep the reply inbox separate too. A client seeing your prospecting replies is an avoidable awkwardness.
What to do with the replies you get
Answer within the day, in two or three sentences, and ask one question that moves toward a conversation. The reply is not the win; the booked call is.
If someone asks for a proposal immediately, ask what decision the proposal needs to support. It saves you writing a document nobody reads.
Record what the reply said. Five replies in a row saying the same thing is your next campaign brief.
The proposal question
When a prospect asks for a proposal, ask what decision it needs to support and who else reads it. Half the time the answer changes the document you would have written.
Agencies lose deals by answering the wrong question quickly rather than the right one slowly.
What good looks like after a month
You send in small batches, the first line references something specific, and replies are answered the same day by one named person.
The agency's marketing domain never carries campaign risk, and the case study you link is the one relevant to the reader.
What agencies send vs what gets replies
| Common approach | Why it fails | Better |
|---|---|---|
| Portfolio deck attached | Looks like a pitch | One link, one proof |
| We are a full-service agency | Says nothing specific | Name one problem you saw |
| Booking link in message one | Asks before value | Ask one question first |
| Same email to 2,000 | Obvious bulk | 40 at a time, read replies |
No approach guarantees replies. These are structural differences, not tricks.
Agency send checklist
- One segment per campaign
- One observable detail in line one
- One proof link
- One question, no deck
- Separate authenticated sending domain
- Small first batch
- Reply handling assigned to a person
A worked example, hypothetical
An agency targeting ecommerce brands swaps a portfolio email for one line about a product page that lists out-of-stock items, plus a single case study from a similar category.
They send 40 a day from a subdomain, read replies each afternoon, and book three calls in the first week. The change was not volume; it was replacing claims with an observation.
- 1.Pick one segment
- 2.Write the observation
- 3.Attach one proof
- 4.Ask one question
What this will not do
- Observations can be wrong; check before you send.
- Agency referrals still outperform cold email in most markets.
- A separate domain needs its own authentication and warm-up.
Questions people ask about this
Should agencies cold email or rely on referrals?
Both, but they need different systems. Referrals need a habit of asking; cold email needs a list, a message and reply handling. Running one badly is worse than running one well.
How many emails per day for an agency?
Few enough that a person can read the replies. That number is usually tens, not hundreds, per mailbox.
What if we have no case study in their vertical?
Say so, and describe the first thing you would change. Inventing relevance is the fastest way to lose trust in one line.
Should we name the client in the first email?
Only with permission, and only if it is directly relevant. Naming a client without consent is a small break of trust that prospects notice.
How do agencies avoid sounding like agencies?
Write about one observed problem and one question. Remove every adjective that could appear in a competitor's email.