How Many People at One Company Should You Cold Email? Limits That Protect Bounces and Replies

Cap how many people you cold email at one company at the same time. Two or three at once, in different roles, with different messages, is a common working rule. Hold the rest until the first wave has finished or someone has replied. Many contacts at one domain concentrate your risk: if that company's gateway starts rejecting you, or the domain is a catch-all that bounces later, every one of those leads fails together. And colleagues compare notes, so ten copies of the same email reads as a campaign, not outreach.

There is no published limit from any mailbox provider on this. The numbers below are working rules, and you should adjust them to your market.

Why many contacts at one company goes wrong

What happens	Why it hurts
A security gateway sees many messages from one new sender to many internal users	Proofpoint, Mimecast and similar filters look at patterns, and a burst can lead to a block. See cold emailing enterprise companies
The block bounces every remaining lead at that company	A cluster of bounces from one domain raises the whole campaign's rate. See bounces from one domain
The domain is a catch-all and bounces unknown addresses later	Guessed addresses all fail at once, after your tool marked them delivered
People forward the email to each other or to IT	Your email gets reported, and your next one is more likely to be filtered
Two people at the company reply "already talking to your colleague"	Wasted sends and a worse impression

The risk scales with sameness. Five people getting five different, relevant emails over three weeks is normal business. Five people getting the same template on the same morning is a pattern.

A per-company cap by company size

Illustrative defaults to adjust:

Company size	Contacts at once	Total over a quarter
Under 50 people	1-2	2-3
50-500	2-3	4-6
500-5,000	3	6-8, spread across functions
5,000+ with separate divisions or regions	3 per division	Treat each division as its own account

"Contacts at once" means people in active sequences at the same time. "Total over a quarter" is everyone you contact at that company, including later waves.

Pick the first wave by role, not by list order

When a lead list gives you twelve people at one company, choose the first two or three deliberately:

1. The likely owner of the problem. The person whose job your offer changes.
2. Their manager or the budget holder, with a shorter, higher-level message.
3. An adjacent user or influencer, with a message about their part of the problem.

Each gets a reason that fits their role. If two of them would plausibly get the same email, drop one of them.

Stagger the waves

Wave	Who	When
1	2-3 people, different roles	Week 1
2	Next 2-3, only if wave 1 produced no reply and no objection	After wave 1's last step, plus a gap of a couple of weeks
Stop	Everyone at the company	As soon as anyone replies, positive or negative

A reply from anyone at the account should pause everyone else at that account. Most sequencers can do this if you set "stop on reply from same company" or a similar option; check yours. If yours cannot, handle it by hand from your replies inbox.

Catch-all and gateway domains change the answer

Two kinds of company domains warrant a lower cap.

Catch-all domains. When a company's server accepts every address, you cannot confirm which of your twelve guessed addresses exist. Several of them may bounce later, all from the same domain. Send to one or two of the most likely addresses, wait for a reply or a bounce, and use what you learn. Our guide to catch-all leads in a sequence covers the follow-up logic.

Gateway-protected domains. Companies behind Proofpoint, Mimecast and similar filters react to patterns. Keep the first wave small and the copy plain. Our post on verifying emails behind security gateways explains what a verifier can and cannot see at those companies.

You can spot both before sending. The free bulk catch-all checker finds domains that accept everything, and the email stack lookup shows which mail provider or gateway a domain uses.

Enforce the cap in the list

Do not rely on the sequencer to spread contacts out. Fix it before upload.

1. Extract the domain. The free email to domain extractor adds a domain column.
2. Count rows per domain with a pivot table or COUNTIF.
3. Freemail domains are not companies. Exclude gmail.com, outlook.com and similar from the count; see personal emails in a B2B list.
4. Sort by domain and role priority, keep the top two or three per domain in the wave-1 file, and move the rest to a wave-2 file.
5. Watch for related domains. A company can have several (example.com, example.co.uk, example-group.com). Group them if your list has a company name or website column.
6. Check against current campaigns. If anyone at the company is already in a live sequence, the new leads wait. Use compare email lists on domains, not only on full addresses.

The email list segmenter and remove emails by domain tools help with steps 4 and 6.

Bounce maths at one domain

Concentration changes how much one company can hurt a campaign. An illustrative comparison for a 1,000-lead campaign:

Setup	Leads at the largest company	If that company blocks you
No cap	40	40 bounces, 4% of the campaign from one domain
Cap of 3	3	3 bounces, 0.3% of the campaign

The cap does not stop the block. It stops one company's block from pushing your inboxes over their bounce threshold.

Verify before the cap, not after

Run verification first, then apply the cap to the rows that came back valid. Otherwise your chosen two or three might include an invalid address, and the next-best contact at that company sits in wave 2 for no reason. Rows that come back risky (catch-all) should count towards the cap like any other lead, but go into their own campaign.

Mistakes to avoid

• Uploading a raw export. Data tools often return every matching person at a company. A filter on title alone can give you twenty people at one firm.
• Counting by company name, not domain. "Acme" and "Acme Inc." look different in a spreadsheet but share one mail server.
• Letting several reps work the same account. Two reps on two sequencers can each stay under the cap and still double it together. Share one account list across the team.
• Restarting wave 1 after a block. If a company's gateway rejected you, more contacts there will be rejected too. Wait, fix the cause, and try one contact first.
• Ignoring replies from colleagues. "Please stop emailing our team" from one person applies to everyone at that company. Suppress the domain.

Where SimpleVerifier fits

SimpleVerifier checks each address with a live mailbox check and returns valid, risky or invalid with a reason, so you choose each company's first wave from confirmed addresses. Catch-alls come back risky and graded, which helps you decide which guessed address to try first. Upload a list on the verify page; the first 100 checks are free with a Google sign-in. Starter is $9 a month for 2,500 checks, and Pro is $39 a month with the first 100,000 checks a month at full speed, then slower, never cut off. See pricing.