The infrastructure question should come before campaign one
A cold email campaign has more moving parts than a list and a few sequences.
There are sender domains. Mailboxes. DNS records. SPF, DKIM and DMARC. Warm-up settings. Reply routing. Suppression lists. Campaign data. Admin access.
None of this is exciting. It is still where a lot of the risk sits.
A founder sees positive replies and booked calls, so the setup feels fine. Then the agency relationship changes. Maybe the company brings outbound in-house. Maybe the offer changes. Maybe the agency simply is not delivering.
Now someone has to answer basic questions:
- Who can log into the domain registrar?
- Who controls the DNS records?
- Are the mailboxes in the client's Microsoft 365 or Google Workspace account?
- Where are the prospect lists and suppression lists stored?
- What happens to sender reputation if the team changes tools or providers?
Those should not be difficult questions. They often are.
Agency-owned infrastructure creates an expensive handover
The issue is not that an agency helps set up cold email infrastructure. That can be useful, especially for a small team without someone technical in-house.
The issue is control.
If the agency owns the domains, creates the inboxes under its own accounts and keeps the data in tools the client cannot access, the client has a problem the moment they leave. They may have to rebuild sending infrastructure, recreate lists, reconnect reply workflows and wait for new mailboxes to establish a sending history.
That is not a minor admin job. It can stop outreach while sales still needs pipeline.
Here is a simple illustrative example. A company has six active sending inboxes, two domains and several months of campaign history. It decides to switch providers because it needs a different targeting approach. If it cannot take those assets with it, it may be starting again with new domains, new inboxes and a new warm-up period.
The cost is not only software or setup time. The cost is the gap between deciding to change and being able to send responsibly again.
Ownership does not mean the client has to run it
Some teams hear "you should own the infrastructure" and assume that means they need to manage every DNS record themselves.
It does not.
A client can own the accounts and still give an agency the access needed to run the work. That is usually the better arrangement.
The agency can set up domains, configure authentication, manage inbox health and make changes. The client keeps admin access and knows where everything lives. If the engagement ends, there is a handover instead of a scramble.
Think of it like a website or CRM. You would not want to discover that your agency owns the account holding all of your customer data. Outbound infrastructure deserves the same basic standard.
The operating rule is straightforward: the client should be able to access the assets that keep their outbound running without asking permission from the agency they are leaving.
Put the handover terms in writing
This does not need a 20-page legal document. A one-page infrastructure ownership appendix is usually enough.
Before launch, document:
- Domain registrar and account owner
- DNS access and who can change records
- Mailbox provider, admin access and recovery details
- SPF, DKIM and DMARC status
- Sending tools and which account holds the subscription
- Prospect data, suppression lists and export process
- Reply routing and CRM connections
- Who handles offboarding and what gets handed over
The point is not to create friction. It is to remove ambiguity while everyone is still on good terms.
A good agency should be comfortable with this. Clear ownership makes the relationship easier to manage because both sides know what they are responsible for.
Sender reputation needs the same clarity
Sender reputation is where this gets a bit more practical.
A domain can be technically owned by the client but still be poorly managed. If sending volume spikes, authentication breaks or inboxes are used carelessly, the client carries the consequence after the agency leaves.
So ownership and responsibility need to sit together.
Ask the agency how it decides:
- How many emails each inbox sends per day
- When an inbox should be paused
- How it monitors bounces and reply quality
- What happens if a domain starts underperforming
- Whether the client can see the sending setup and campaign history
There is no universal daily send number that works for every company. The right volume depends on mailbox age, list quality, copy, domain setup and how recipients respond. Anyone promising a fixed number without looking at those things is skipping the part that matters.
The useful question is not "How much volume can we send?"
It is "What tells us this sender is healthy, and who can act when it is not?"
Do not confuse access with accountability
Giving a client logins does not automatically mean the outbound system is well run.
Someone still needs to own the work. That includes checking inbox placement, reviewing reply quality, keeping the list current, handling interested prospects properly and reporting whether meetings become real opportunities.
This is where agencies should earn their fee.
Tools can send messages. They do not decide whether a reply is worth pursuing. They do not tell you whether the issue is targeting, deliverability, the offer or follow-up after a meeting is booked. They definitely do not protect the client from a vague handover process.
The agency should own the operating decisions. The client should own the underlying assets.
That split is fair to both sides.
A practical check before you sign
Before you approve an outbound engagement, ask for a plain-English answer to this:
"If we stop working together in six months, what do we keep, what access do we have, and what needs to be moved?"
A good answer should cover domains, DNS, inboxes, data, campaign history and offboarding. It should not depend on a verbal assurance that "we can sort that out later."
Later is when it becomes expensive.
Outbound works better when the commercial arrangement is simple. The client owns the infrastructure. The agency runs the operating work. Both sides can see what is happening. If the relationship ends, the pipeline does not disappear with it.
Frequently asked questions
Should a cold email agency own the sending domains?
Usually, no. The client should own the domains and give the agency the access needed to manage them. That keeps the client in control if the engagement changes or ends.
Can an agency set up cold email infrastructure in the client's account?
Yes. This is often the sensible approach. The agency can handle the setup and day-to-day management while the client retains administrator access to the registrar, mailbox provider and campaign data.
What should be included in an outbound offboarding handover?
The handover should include domain and DNS access, mailbox credentials or admin access, authentication records, campaign data, suppression lists, reply-routing rules and a record of active tools. The client should also know which inboxes are active, paused or no longer suitable for sending.
Does client-owned infrastructure reduce deliverability risk?
Client ownership does not guarantee deliverability. Good sending habits, authentication, list quality and ongoing monitoring still matter. It does reduce the risk of losing access to the assets and history needed to manage deliverability properly after an agency relationship ends.
Keep control before you need it
If you are reviewing an outbound agency or rebuilding a campaign that has gone quiet, start with the infrastructure and work forward from there. A free outbound review can help identify whether the first problem is sender health, targeting, messaging or follow-up.