How to send personalized cold emails at scale without a mail merge

To send hundreds of personalized cold emails without a mail merge, write each email for its one recipient from facts about them, then send each one separately from a real mailbox or a cold-email tool, a small batch at a time, with opt-outs checked before every send.

Part of Run personalized outbound email campaigns

Key Takeaways

  1. Sending personalized cold email without a mail merge means writing each email for its one recipient and sending it as its own message, instead of filling a first name and company into one shared template.
  2. The hard part is the writing, not the sending. Each email needs a reason to write that is true of that person only, such as a new hire on their team or a market they just entered, and that takes research on every recipient.
  3. Sending hundreds of separate emails safely comes down to a few habits: send from a real, authenticated mailbox, keep the daily volume modest, start with a small batch, and skip anyone who has asked not to hear from you.
  4. Kite verifies each recipient's role, writes every email from facts about that person, and sends it once you approve, one recipient per message, from your connected Gmail account or through a cold-email tool such as Lemlist or Instantly.
  5. You end up with a separate email in each recipient's inbox, follow-ups threaded under the first message, and a report of who was emailed, what each person received, and who replied.
On this page

How do I send hundreds of personalized emails without using a mail merge template?

You send hundreds of personalized emails without a mail merge by treating each email as its own piece of writing. You decide why you're writing to this particular person, write a short email around that reason, and send it as a separate message from your own address. Then you repeat that for every person on the list, and you send them in batches spread over days rather than all at once.

A mail merge works the other way around. You write one email with blanks in it, such as a first name, a company name, or a job title, and a tool fills in the blanks from a spreadsheet and sends a copy to each row. Gmail offers this on some paid Google Workspace plans, and add-ons such as GMass, Mailmeteor, and Yet Another Mail Merge do the same with more options. Cold-email tools such as Lemlist and Instantly add sequences, sending schedules, and automatic follow-ups on top.

Those tools move email reliably. The trouble is what they send. A merged email reads the same for everyone on the list except for the words in the blanks, and the people receiving cold email have seen thousands of them. "Hi Sarah, I noticed Acme is growing fast" is a template with a name in it, and Sarah can tell. Personalization that works is a fact about the recipient that changes what the email says: the role they just posted, the pricing page they just rebuilt, the market they just opened.

So a good result has three parts:

  • A list where everyone belongs. Each person still holds the role you think they hold, fits the kind of customer you serve, and hasn't asked you to stop writing.
  • An email per person that couldn't go to anyone else. It opens with that person's situation, makes one ask, and stays short.
  • A send that lands in the inbox. The emails go out one at a time from a mailbox that inbox providers trust, at a pace that doesn't look like a blast.

The first two parts are why people reach for a mail merge in the first place. Writing three hundred individual emails by hand takes days. Kite does that research and writing for every recipient, then sends each email as its own message once you approve.

How to get started

Start by telling Kite who you want to reach and why. You can do this in the Kite web app or in Slack. If you already have a list, share it:

"Email the 250 operations leads in this spreadsheet about our new scheduling feature. Send from my Gmail and follow up once if they don't reply."

If you don't have a list yet, ask Kite to build one:

"Find 200 heads of operations at logistics companies with 50 to 500 employees and send each of them a personal email about our route planning product."

Kite is an AI marketer. It researches your business, builds a growth strategy, and ships the work that brings you new customers. From that research, it already knows your ideal customer profile, your positioning, your competitors, and your brand voice. That means it can propose who belongs on the list, the reason to write, and the ask without a long brief. It shows you the plan and sample emails, and you confirm or adjust them.

To send, connect the account the emails should come from. Connect your Gmail account through OAuth, which is Google's sign-in screen where you approve what Kite can access, and Kite sends each email from your address. If your team already runs cold email in Lemlist or Instantly, connect that account instead, and Kite sends through the mailboxes and schedules you've set up there.

Kite asks before it sends email to anyone outside your team. You see the list, the emails, and the sending plan first. Approve them with the button in the conversation or with a reply, and Kite starts sending.

How Kite sends personalized cold emails at scale

Who belongs on the list?

Kite keeps only people it can justify in one sentence. Each recipient either fits your customer profile, did something relevant, or was named by you directly, and anyone Kite can't explain gets cut. When you share a spreadsheet, Kite reads every row. When it builds the list itself, it uses its built-in Apollo connection to find companies by size, industry, location, and funding, then finds the right people at those companies by title and seniority.

Before writing anything, Kite checks that each person still holds the role at that company, using their public professional profile or the company's own pages. A wrong name or an old job title loses the reply before the email is read, and in a list of a few hundred people, some will have moved on since the list was made. Kite tells you who it dropped and why.

Kite also removes anyone who has asked not to hear from you. It checks the email notes in your team's knowledge base, any earlier replies it can see, and the unsubscribe list in your connected cold-email tool, such as Lemlist's list of unsubscribed addresses. A person marked there doesn't get an email, even when their name is on your spreadsheet.

What makes each email personal?

Kite writes each email around a fact that is true of that recipient and nobody else. It looks for a recent, dated reason to write, such as a new hire on the person's team, an expansion into a new region, a funding round, or a change to their website. Kite's research sources supply company news about funding, hiring, and launches, and the person's recent public posts add more. When it finds no recent event, Kite states the benefit in terms of that person's role and company.

The email puts that reason in the first two sentences, framed around the recipient's situation rather than your product. It asks for one thing, such as a short call or a reply. It runs under 120 words, in plain text, with one link at most. It's signed with your name and role and names your company plainly. It closes with an easy way out, such as "If this isn't relevant, tell me and I won't follow up."

Kite writes in your brand voice and checks every draft for phrasing that reads as machine-written, because cold email that sounds generated gets deleted. Each email also gets its own subject line. Two emails on the same list may share an angle, but neither one could be forwarded to the other recipient and still make sense.

How do the emails go out without a mail merge?

Kite sends one email per recipient, so every body stays personal and nobody sees anyone else's address. It never puts a list of names in the BCC field, and a cold email never goes out as one shared body.

From Gmail, each email goes out from your connected account as its own message, with your name in the sender line and its own subject. It sits in your Sent folder like any email you wrote yourself, and replies come back to your inbox. If you'd rather press send yourself, ask Kite to leave the emails as drafts in your Gmail Drafts folder.

From Lemlist or Instantly, Kite works with the tool's campaign. In Lemlist, it adds each recipient to the campaign as a lead, with their email, first name, and company, and it stores the email it wrote for that person in a custom variable on the lead. The campaign's sequence step then sends that variable as the email body, so the tool handles the sending schedule, the mailbox rotation, and the tracking, while every lead still receives a message written only for them. Kite can attach a sending schedule to the campaign, with the days, hours, and time zone the emails should go out in.

How fast should the emails go out?

Kite sends a first small batch, usually three to five emails, and checks that each one was accepted before sending the rest. For every accepted email, it records the message and thread identifiers so later follow-ups land in the right conversation. If a send fails, Kite notes which recipient it was for and why, and it doesn't quietly retry, because the email may already have gone out. If failures repeat, it stops and tells you.

Pace matters as much as the batch. Gmail caps how much one account can send in a day, at about 500 messages for a personal account and 2,000 for a Google Workspace account. Those caps are the ceiling, though, not the target. A mailbox that suddenly sends hundreds of cold emails a day looks like a spammer to Gmail and Outlook, even when every email is personal. So spread a list of a few hundred across several days. Kite can put each day's batch on a schedule so the sends run on their own. In Lemlist or Instantly, the campaign schedule and the tool's own daily limits do the pacing.

A few setup details decide whether these emails land in the inbox at all. Your sending domain needs SPF, DKIM, and DMARC records, which are the settings in your domain's DNS that prove your mail really comes from you. Many teams send cold email from a separate domain, such as one with "try" or "get" in front of the main name, so a bad week doesn't affect the domain their invoices and support email come from.

Who gets a follow-up?

Kite follows up only with people who haven't replied and haven't asked to be left alone. Before each round, it reads each thread in your Gmail, or the lead's activity in Lemlist, and anyone who answered, even with "not for us," gets no further email. In Lemlist, Kite marks a lead who replied positively as interested and a lead who declined as not interested, so the campaign stops writing to them.

Each follow-up adds something the first email didn't have, such as a short customer result, a relevant resource, or a different angle that fits the person's role better. Kite sends at most two follow-ups, spaced days apart, and treats silence after that as an answer. From Gmail, every follow-up goes out as a reply in the original thread, so it keeps the subject line and sits on top of the first email in the recipient's inbox. In Lemlist, Kite writes the follow-ups as later steps in the sequence, with a delay of a few days between them.

When someone replies with interest, Kite treats it as a real conversation. It reads what they asked and drafts an answer that responds to it, with a next step such as two meeting times or your booking link.

What Kite reports back

After each batch, Kite posts a summary in the conversation where you asked. It lists who was emailed, any sends that failed and why, who was dropped from the list and the reason, and when the next batch or follow-up is due. The summary includes the exact copy each person received, so you can read everything that went out under your name. From Lemlist, Kite also reads the campaign's statistics, including sends, opens, clicks, and replies for each step.

When the campaign ends, Kite records what worked in your team's knowledge base, including which subject lines and angles drew replies. Your next campaign starts from those results.

When to use Resend instead

Resend is the right route when the people on your list asked to hear from you. Resend, like most email delivery services, is built for email to people who signed up, and its terms don't allow cold email to people who haven't. That still covers a lot of personalized sending: following up with everyone who registered for your webinar, writing to past trial users, or re-engaging leads who once filled out a form on your site.

For those lists, connect your Resend account and Kite adds the people as contacts, groups them into a segment, and sends each person their own email as an individual or batch send from your verified domain. It checks Resend's suppression list first, so anyone who unsubscribed or bounced is skipped, and it reads delivery, open, and click data after the send. For a first email to a stranger, Kite uses your Gmail or your cold-email tool.

What the finished work contains

When Kite finishes, every recipient has received an email written for them, and you have a complete record of what went out.

One email per recipient

Each person has their own message from your address, with a subject line and opening built on a fact about them, one ask, and your signature.

Follow-ups in the original threads

People who didn't reply have one or two follow-ups under the first email, each adding something new.

Draft answers to replies

Anyone who wrote back has a drafted response to what they actually asked, waiting for you to approve.

The checked list

The list Kite worked from shows each person's current role, the reason they're on it, and everyone dropped because they moved on or opted out.

The campaign summary

The conversation in Kite shows who received what, the exact copy, any failures, the reply count, and the dates of the next sends.

Common questions

Is it legal to send cold emails without a mail merge?

Yes, in the US cold email to business contacts is legal under the CAN-SPAM Act, as long as the sender and subject are honest, the email is clearly identified as a sales message, it includes your physical address and a clear way to opt out, and you honor requests to stop. Rules are stricter elsewhere. Under the GDPR in Europe and in Canada, you need a legitimate reason that relates to the person's job, and some countries require consent. Kite honors opt-outs on every send and closes each cold email with a line inviting the recipient to say no, but check the rules for the countries you're emailing.

How many cold emails can I send per day from one Gmail account?

Most teams send between 30 and 50 cold emails a day from each mailbox, well below Gmail's caps of about 500 for a personal account and 2,000 for Google Workspace. A new mailbox should start lower and build up over a few weeks. To reach a few hundred people a day, teams usually spread the sending across several mailboxes, which is what tools like Lemlist and Instantly are built to manage.

Can I review every email before it goes out?

Yes. Kite shows you the list and the emails before anything sends, and you approve them in the conversation. For a long list, you can read a sample, ask Kite to change the angle or the ask, and approve the rest once the emails read right. You can also have Kite leave every email as a draft in your Gmail and send them yourself.

Questions this page answers

  • How do I send hundreds of personalized emails without using a mail merge template?
  • How can I use an AI marketing agent to send personalized cold emails at scale without a mail merge?

About the author

Devon Wells leads product marketing at Kite, the AI marketer. He spent a decade marketing industrial AI, from self-driving trucks to computer vision, but now Kite handles most of the work itself.

Tell me your goal and I’ll get to work.

Get started for free