Cold email software for agencies

Separation is the first requirement

If two clients share a sending domain, a complaint about one offer lands on both. If they share a mailbox, the volume looks twice as high and the audiences mix. Neither problem is visible until something goes wrong.

At minimum, each client needs its own sending mailboxes and its own recipient lists. Separate domains are stronger but not always practical; separate mailboxes are the non-negotiable part.

• One client, one set of mailboxes, one campaign at a time per mailbox.
• Separate lists with no cross-client deduplication surprises.
• A naming convention that identifies the client in every campaign.

Reporting you can hand to a client

Clients ask three questions: how many were sent, how many replied, and what happens next. A tool that reports opens as the headline answers none of them, because open tracking is unreliable. Replies per delivered message, per campaign and per step, is the report that survives scrutiny.

Keep the raw evidence too: bounce reasons, complaint counts and the date of each batch. When a client asks why a campaign stopped, the answer should be a response code, not an opinion.

The calculation that holds up in a client review is in reply rate measurement.

Capacity planning across clients

Each mailbox sends at a human interval, so total capacity is the sum of mailboxes, not the sum of campaigns. An agency with twelve campaigns and twelve mailboxes has twelve streams at 30 to 60 seconds; an agency with twelve campaigns and three mailboxes has a scheduling problem disguised as a software problem.

Plan by client and by month. If a client's list needs 20,000 sends and one mailbox sustains 600 a day, the math decides whether the timeline is realistic before the campaign starts.

• Capacity = mailboxes × interval ceiling.
• Plan per client, not as one pool.
• Keep headroom for follow-ups in the same cap.

Additional mailboxes are the capacity lever; SMTP accounts supplies them on your own domains.

A worked agency setup

Two clients, three campaigns each. Client A has three mailboxes on its own subdomain; client B has three on a different domain. Each campaign has its own list and its own template, and the agency reports replies per campaign weekly.

When client B's second campaign produced two complaints, the agency stopped that campaign only. Client A's sending continued untouched because nothing was shared. The incident cost one campaign, not the accounts.

Running that structure in one place is what AI cold email with per-client workspaces is built for.

When a client asks to send faster

The request is reasonable and the answer is arithmetic. One mailbox at a sixty-second interval has a ceiling of about 1,440 messages a day; at thirty seconds it is about 2,880. Nothing in the software can exceed the interval without changing how the mailbox behaves to receiving servers.

So the conversation is about capacity: more mailboxes, each on its own domain or subdomain, with its own warm-up and its own campaign. That costs more and takes time, and saying so is better than quietly raising the pace until a domain is blocked.

Put the number in the proposal. “Two thousand sends a month, one mailbox, sixty-second spacing” is a commitment the infrastructure can keep. “As fast as you need” is not.

• Show the interval arithmetic before discussing price.
• More volume means more mailboxes, not a faster one.
• Write the capacity figure into the proposal.
• Give each client a named operator and a written escalation path. When a campaign stops, the client should know who is looking and by when, which is a service commitment rather than a software feature.
• Charge for list preparation separately from sending. Verification, deduplication and segmentation are the work that decides whether a campaign is any good, and bundling them into a per-email price hides the effort behind the number the client actually compares against a cheaper tool.
• Agree response ownership in the contract. Whether the agency answers replies or the client does changes the staffing and the reporting, and leaving it vague is how a campaign with good reply numbers still produces no meetings for anyone involved, which is the outcome clients remember.
• Review the capacity plan with the client before the first send, not after the first stall. A two-line table listing mailboxes, interval, daily ceiling and monthly total prevents the conversation where a client expects ten thousand sends in a week from one account and blames the tool when it cannot happen.

Agency requirement, why it matters and what failure looks like

Features are secondary to this structure. A richer tool with shared senders is still unsafe.

Frequently asked questions