# How Many People at One Company Should You Cold Email, and Who First?

> Email 2-3 people when the account matters, 1 when it doesn't. In Ken data, same-day colleagues weren't blocked more, and middle managers answered least.

Oct 28, 2026 · Cristian Frunze · 13 min · Guide

Tags: how many people at the same company should I cold email, multithreading cold email, contacts per company, cold email multiple people same company, who to email first, cold email sequence timing

![A founder on a step ladder picks two ripe fruits from one tree while a man shakes the whole next tree, raining every fruit down.](/images/blog/how-many-contacts-per-company-cold-email-cover.webp)

Hunter has given two answers to this question. Its blog found that emailing two or more people at a company roughly doubles the odds the company replies. Its 2026 report says to pick one well-matched person, partly because similar emails to one domain "can look spammy to the recipient's email server."

**Email two or three people at a company when the account is worth it, and one person when it isn't.** Pick them by who's likely to answer, not by rank. That usually means the founder at a small company and the person doing the work at a bigger one. Emailing them on the same day didn't get anyone blocked in our data. Give each one a different email, and stop the whole company only when a human replies.

We tested both of Hunter's answers on our own sending data: contacts across 17 sending workspaces, with first emails sent February 25 to August 3, 2026 and replies tracked to August 24. Ken runs cold email and LinkedIn outreach for B2B companies, done for you, on infrastructure we own. Plenty of companies in that data got emails to more than one person, which sales teams call multithreading.

**The second person you email at a company doesn't make anyone less likely to reply. They're usually just a worse lead than the first.**

## Does emailing a second person at the same company lower your reply rate?

On the raw numbers, yes. When we emailed two people at a company, each one replied at 0.74x the rate of someone who was the only person emailed there. With three people it was 0.73x. With four or more, 0.35x.

Then we compared like with like. We matched each person with people in the same campaign, at a similar-size company, at a similar job level. The drop mostly went away, to 0.93x, 0.99x and 0.81x. Each of those has a 95% range, the span the true number most likely sits in, and all three ranges include 1.0. No penalty we can measure.

The reason is who gets added. Only 8% of lone contacts worked at companies with more than 200 employees, against 70% of people at companies where we emailed four or more. Founders, owners and C-level fell from 47% of contacts to 13%. Middle managers rose from 25% to 53%. Big companies and middle managers reply less no matter how many of their colleagues you email.

![Raw reply odds fall as colleagues are added, but compared like for like the drop mostly disappears](/images/blog/how-many-contacts-per-company-cold-email-1.svg)
*Source: Ken sending data, first emails Feb 25 to Aug 3, 2026, replies to Aug 24, across 17 sending workspaces. Lines show 95% confidence intervals.*

So each extra person adds roughly their own chance. Companies where we emailed two people sent a human reply 1.45x as often as companies where we emailed one, with a 95% range of 1.15x to 1.83x. That's 0.98x what you'd predict if the two colleagues never talked to each other. In our data, colleagues behaved like strangers who happen to share an email domain.

The published numbers look like they disagree, but they measure different things:

| Source | Data | What it compared | Finding |
|---|---|---|---|
| [Hunter blog](https://hunter.io/blog/should-you-email-more-than-one-person-per-company), updated Sep 2026 | 25,138 campaigns, 12 months | Companies, inside the same campaign | 3.35% of companies replied with 2+ people emailed, 1.61% with one |
| [Hunter, State of Email Outreach 2026](https://hunter.io/the-state-of-cold-email) | 31M emails sent in 2025 | Reply rate, 1-2 people per company vs 3+ | 5.1% vs 3.5% |
| [Backlinko and Pitchbox](https://backlinko.com/email-outreach-study), 2019 | 12M outreach emails to bloggers and publishers | Response rate, several contacts vs one | 93% higher, fading at 5+ contacts |
| Ken, 2026 | Contacts first emailed Feb to Aug 2026, 17 workspaces | Companies raw, people matched on campaign, company size and seniority | Company 1.45x as likely to reply with two people, no per-person drop like for like |

## So how many people should you email at one company?

The right number depends on what's scarce for you, companies or contacts. Per contact you spend, putting two people at each company found 0.73x as many replying companies as putting one person at each of twice as many companies.

| Your situation | People per company | Why |
|---|---|---|
| More good-fit companies than you can email this quarter | 1, the best fit | A contact spent on a new company finds more replies |
| A few hundred target accounts, or accounts you really want | 2-3, in different roles | The company's odds add up, about 1.45x with two |
| Large companies where many people sign off | 3-4, across departments | [Forrester](https://www.forrester.com/press-newsroom/forrester-the-state-of-business-buying-2024/) counts 13 people in the average buying decision |
| More than 4 | Rarely worth it | The extra names are mostly middle managers, and auto-replies pile up |

Past the first reply, Gong [found](https://www.gong.io/resources/guides/the-data-backed-guide-to-multi-threading-and-team-selling) that closed-won deals include 67% more contacts than closed-lost deals. That's a correlation, but it's a good reason to have more than one name in any real deal.

## Who should you email first at a company?

Start with the person you most want to talk to. The order itself doesn't buy you replies. At companies where we emailed several people, the first one emailed replied at 1.03x what similar colleagues got, and everyone after at 0.98x.

Who's on the list matters much more, and that's where multithreading usually goes wrong. VPs, directors and managers made up 25% of lone contacts but 46% of people emailed alongside a colleague. Inside those multithreaded companies, they replied at 0.66x what an average contact in the same campaign and company size got, with a 95% range of 0.48x to 0.88x. Founders and C-level came in at 0.86x and other individual contributors at 1.03x, both within the noise.

![Middle managers are 46% of people emailed alongside colleagues and replied at 0.66x similar contacts](/images/blog/how-many-contacts-per-company-cold-email-2.svg)
*Source: Ken sending data, first emails Feb 25 to Aug 3, 2026, replies to Aug 24, across 17 sending workspaces. Lines show 95% confidence intervals.*

The middle managers' inboxes weren't silent. They were automated. In the June to August part of our data, VPs, directors and managers were about 1.2x as likely as the average contact in their campaign to send an auto-reply, and 0.6x to 0.8x as likely to send a human one.

Hunter's blog says going down the org chart doubles your reply rate compared with going straight to the top. Our data adds a catch. Inside the same campaigns, the people who do the work replied about as often as founders and C-level. The middle is where the replies went missing.

Here's the order I'd use:

1. **At a small company,** the founder or CEO. In our data, the founder's edge was mostly a small-company edge.
2. **At a bigger company,** the person whose work your product changes, then the executive who owns the budget.
3. **A middle manager** only when they clearly own the problem, never as the default third name.

That choice gets made when you [build the lead list around your ICP](https://ken.so/blog/build-cold-email-lead-list-icp), long before anyone writes an email.

## Will emailing several people at one company the same day get you flagged as spam?

Not in our data. The worry is common. Instantly [added a daily cap](https://feedback.instantly.ai/en/changelog/weve-just-launched-domain-send-limits-tada) on how many people at one company you can email in October 2025, and Hunter's report warns about similar emails to one domain. If a company's mail server punished a pile of similar emails in one day, the fourth person you email would get blocked more often than the first. They weren't.

We looked at every person who got a first email on the same day as at least one colleague, from the same campaign, between February 25 and August 24, 2026. Compared with the first person emailed that day at the same companies, the second was blocked 1.02x as often, with a 95% range of 0.90x to 1.16x. The third came in at 0.91x and the fourth or later at 0.79x. Even where one campaign emailed ten or more people at a company in a day, the tenth and later were blocked 0.83x as often as the first nine. That sample is small, with a range of 0.56x to 1.25x, but it points the wrong way for the theory.

We split companies by where their mail lives, too: Google, Microsoft, or behind a security gateway, which is a filter that screens mail before it reaches the inbox. In none of the three was the second person blocked measurably more than the first.

Blocks only show mail a server refuses. Mail quietly filed in spam is harder to see, but auto-replies give you a way in. Gmail [doesn't send](https://support.google.com/mail/answer/25922) a vacation reply to mail in the spam folder, and Microsoft 365 [doesn't generate](https://learn.microsoft.com/en-us/troubleshoot/exchange/email-delivery/understand-troubleshoot-oof-replies) an automatic reply for mail sent to Junk. Both pages were checked October 2026. So if later colleagues were landing in spam, their out-of-office replies would dry up. They didn't. Later colleagues sent auto-replies at 0.91x the rate of the first person emailed that day, with a 95% range of 0.76x to 1.09x.

![Colleagues emailed the same day were not blocked or filtered more, and no gap between colleagues won](/images/blog/how-many-contacts-per-company-cold-email-3.svg)
*Source: Ken sending data, 17 sending workspaces. Panel 1: contacts in same-day colleague groups, first emails Feb 25 to Aug 24, 2026. Panel 2: the same kind of groups, first emails Feb 25 to Aug 3, replies to Aug 24. Panel 3: contacts at companies with 2+ people emailed, same period. Labels in panels 2 and 3 give reply counts. Lines show 95% confidence intervals.*

**The fourth colleague you email on the same day is no more likely to be blocked than the first.**

The test has limits. We can't see spam complaints, which is what Instantly's note says can get a sending domain blocked. Most of our same-day groups were two to four people, not dozens. The closest complaint signal we have points the same way. The share of human replies saying "no" or "remove me" was no higher at two or three people per company than at one.

## How long should you wait before emailing the next person?

Long enough to stop if the first person replies. The exact gap didn't matter in our data.

The guides each pick a different number. [FirstSales](https://firstsales.io/blog/contacts-per-company-cold-email) says two to five days. [Octave](https://www.octavehq.com/post/gtm-engineers-guide-to-multi-threading) describes one to two weeks after the champion. Hunter's 2026 report says to move on only once your main buyer ignores you. None of them shows data for its gap.

We sorted people at multithreaded companies by how long after the previous colleague they got their first email. People emailed the same day replied at 0.96x what similar people got. One to three days later, 1.23x. Four or more days later, a median of 9 days, 0.85x. All of these ranges cross 1.0. If one to three days really is better, the edge is too small to see in our data.

So pick the gap for practical reasons. I'd use two to three days. In our data, 35% of first human replies came within a day of the first email, and half within about 3.3 days. A short gap catches many of them before the next colleague hears from you, without dragging one account across a month.

## How should the email change for each person?

Give each person a different reason to reply, based on their job. Our own data can't compare identical and varied copy, because almost nobody in it got an identical email. Only 7% of people at multithreaded companies were in a group where everyone got the same first subject line.

Hunter measured something close. Pairs from different departments got more replies than pairs from the same department, 2.30% against 1.65%. Different departments care about different things, so they should read different emails.

- **The founder or CEO.** Lead with the business outcome and one piece of proof.
- **The person doing the work.** Name the specific task you take off their week.
- **The budget owner.** Show the cost and the time saved, in numbers.

Never send the same email with the name swapped. If two colleagues compare notes, it reads as a mail merge. At Ken, human copywriters write a framework for each role, AI fills it with real facts about each person, an AI check reviews every email, and a human approves before anything sends. More on [how AI email personalization works](https://ken.so/blog/ai-email-personalization).

## What should happen when someone at the company replies?

Stop emailing everyone else at that company, but only when a human replies. Instantly, Smartlead, lemlist and GMass all have a setting for the first part. The second part is where it breaks.

Auto-replies pile up much faster than real ones as you add people. Companies where we emailed four or more people were 5.3x as likely to send some kind of reply as single-contact companies, mostly out-of-office messages. With one person emailed, companies that sent only an auto-reply outnumbered companies with a human reply 2.9 to 1. With two people, 4.7 to 1.

That matters if your company-wide stop fires on any reply. At companies where we emailed two or more people, about 1 in 12 human replies answered an email that went out after someone at that company had already sent an auto-reply. Where we emailed four or more people, it was about 1 in 5. A stop rule that treats an out-of-office as a reply would never have sent those emails.

| Tool | Company-level setting | Matches a company by | Worth knowing, checked October 2026 |
|---|---|---|---|
| Instantly | `stop_for_company` in the [API reference](https://developer.instantly.ai/api-reference/campaign/create-campaign) | Domain | A separate `stop_on_auto_reply` flag covers auto-replies |
| Smartlead | [Company Level Auto-Pause](https://helpcenter.smartlead.ai/en/articles/199-how-to-set-up-company-level-auto-pause) | Not spelled out; gmail.com, outlook.com and other free domains are ignored | Only applies on the first upload of a lead list |
| lemlist | ["Also pause contacts from the same company"](https://help.lemlist.com/en/articles/13338246-pause-a-campaign-when-one-lead-from-a-company-engages), set per rule | Exact Company Name field | Small spelling differences stop it working |
| GMass | [Auto Follow-up Domain Match](https://www.gmass.co/blog/auto-followup-stop-email-anybody-at-company-replies/) | Domain | Account-wide and off by default |

None of these pages says plainly whether an out-of-office triggers the company stop. So test it. Reply to your own campaign from a test address with an auto-reply and see what pauses. Then re-time out-of-office contacts to their return date instead of dropping them. More on [why out-of-office replies need their own handling](https://ken.so/blog/out-of-office-replies-are-quietly-killing-your-cold-email-deliverability) and [sorting every reply the day it lands](https://ken.so/blog/how-to-handle-cold-email-replies).

## Frequently asked questions

### Should I put several people at one company in the same email?

Not named people. Separate emails let each person answer for themselves. Hunter found one exception worth testing. Copying the company's general inbox, like info@, lifted the named person's replies to 2.09%, against 1.30% when paired with another named colleague, though general inboxes unsubscribed almost twice as often.

### What if one person at the company says no?

Treat a clear no from the person who owns the problem as a no for the team. If they say "wrong person," ask who, and mention that referral when you email the new person. An unsubscribe means never emailing that address again, and the FTC's [CAN-SPAM guide](https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business) gives you 10 business days to honor it, B2B email included (checked October 2026).

### What if a company uses more than one email domain?

Plan by company, not by domain. Tools usually match on domain, so in GMass's own example a reply from uber.com doesn't stop emails to uber.net. In our data, grouping by company and by email domain gave the same group size 92% of the time.

### How many people should I email at a 10-person company?

Usually one, the founder or owner. In the June to August part of our data, founders and C-level contacts were about 1.9x as likely to reply as VPs, directors and managers in the same campaigns. Holding company size fixed, that shrank to about 1.4x, so a good part of the edge comes from small companies.

## The short version

Multithreading works when you treat it as picking people, not adding names. Choose two or three people likely to answer, give each a reason that fits their job, and let a human reply close the account, not an out-of-office. If you'd rather have us find the right people at your target accounts and write their emails, [the first campaign is free](https://ken.so/free-campaign).