How many cold emails per day: work out the volume you need

The wrong way to decide how many cold emails per day to send is to pick a round number that feels busy. The right way starts with the result you want and works backwards. You end up with a daily volume, a per-inbox cap and a count of inboxes and domains. This post gives you the formula, a clearly labelled example, and the reasoning for choosing a cap without pretending there's a universal one.

How many cold emails per day: start from the meetings you want

Volume is a means. Start with the end of the funnel:

1. Meetings goal (M): how many booked meetings you want per month.

2. Meeting rate (m): of the positive replies you get, what share turns into a booked meeting.

3. Positive reply rate (p): of the people you email, what share replies with interest.

Contacts you need to reach in the month = M / (p × m).

You supply p and m from your own campaigns. There is no honest benchmark to borrow, because both depend on your offer, audience and list. If you have no data yet, run a small test first: how many cold emails to send before you know if it works covers that, and you can come back with real numbers.

A worked example (placeholder numbers)

This is an example with round placeholder numbers. It is not a typical result.

Say you want 10 meetings a month. Say, from earlier campaigns, 1 in 100 people you email sends a positive reply (p = 0.01), and 1 in 2 of those positive replies turns into a meeting (m = 0.5).

• Contacts needed = 10 / (0.01 × 0.5) = 2,000 contacts.

Now count emails, not contacts. If each contact gets a 3-email sequence, that is up to 6,000 emails across the month. Spread over about 20 sending days, that is 300 emails a day. Replace every number above with your own before you plan anything.

Two adjustments to make to your own version:

• Add a margin for list loss. Some addresses will bounce or be removed. Verify the list first so the loss is small. In SendingOS, email verification is free.

• Count follow-ups honestly. Follow-ups are real sends that count against daily caps. Cold email follow-up covers how many to use and how to space them.

From daily volume to per-inbox caps

Once you know the daily total, divide it across inboxes. The question is what each inbox should send.

Google and Microsoft publish their own limits:

• Google Workspace documents its sending limits, including a daily message cap per user.

• Microsoft documents Exchange Online limits, including a daily recipient limit per mailbox.

Read those pages for the current numbers. They are hard ceilings: the point at which the provider stops accepting your mail. They are not cold-email targets. Staying under the ceiling says nothing about whether your mail lands in the inbox, and a cold sender who sends near the ceiling from a young domain is asking for trouble.

How to choose a cap

We won't name a "safe" number, because no one outside the mailbox providers can know it for your domain. What you can do is choose by evidence:

1. Start low on anything new. A new inbox or domain has no history. Begin with a small number and keep it small through warmup. Email warmup explains the process.

2. Raise in steps, and only while the signals stay healthy. Healthy means bounces stay low, the spam rate in Postmaster Tools stays far under Google's 0.1% guideline, and replies from every provider keep arriving.

3. Back off at the first drift. If bounces or complaints rise after a step up, go back down. A rising send count with a falling reply rate is a warning, not growth.

4. Treat each inbox separately. One inbox with a rough week shouldn't set the cap for the rest.

The cap that works for one sender, one list and one offer won't transfer cleanly to the next, so the number you land on is yours to measure. Email spam test describes how to check placement while you ramp.

How many inboxes and domains that implies

Inboxes needed = daily send target / per-inbox cap.

Continuing the placeholder example: 300 emails a day with a chosen cap of, say, 30 a day per inbox means 10 inboxes. That cap of 30 is a placeholder too; pick yours using the steps above.

Then spread the inboxes across domains. A few inboxes per domain, over several separate sending domains, means no single domain carries all the risk. Keep cold email off your main domain entirely. Cold email infrastructure covers the full build.

Two practical notes:

• Plan capacity ahead. Inboxes need warmup before they carry full volume, so order them weeks before you need them.

• Keep spare inboxes. Some will pause or burn, and you want to rotate in a replacement without cutting your volume.

In SendingOS, domain health rules can pause a drifting domain's inboxes on their own, and every inbox's connection is checked every few minutes, so a failing inbox stops sending until it passes again. That keeps a bad inbox from quietly eating its share of your daily volume.

Put it together

1. Set the meeting goal and fill in your own p and m.

2. Compute contacts, then emails including follow-ups.

3. Divide by sending days for the daily total.

4. Choose a per-inbox cap using the steps above, starting low.

5. Divide to get inboxes, spread them over several domains, and add spares.

6. Re-check every week: if reply rate or bounce rate moves, volume isn't the only thing to adjust. The whole deliverability picture shows what to look at.