How to run outreach to a qualified prospect list with Resend

You send outreach through Resend by adding your prospects as contacts, grouping them into a segment, and sending from a domain you've verified. Resend imports a CSV file of contacts and maps its columns onto each contact's email address, first name, last name, and any custom contact properties you've defined, such as company or job title. You add the imported contacts to a segment, which is the group a broadcast sends to. Then you write a broadcast in Resend's editor, choose the segment, and send it now or schedule it for later. Resend fills contact details into the email wherever you place them, so each person sees their own first name or company. If you write code, Resend's API also sends individual emails one at a time or in batches of up to 100.

Before any of that, Resend needs a sending domain. You add the domain in Resend, copy the DNS records it gives you into your DNS provider, and wait for Resend to verify them. Until the domain is verified, nothing sends from your address.

That route sends email reliably, but it doesn't decide anything about the email or the people receiving it. A broadcast to 150 prospects is one email with a few details swapped in. The person who just raised a funding round and the person whose company is hiring its first marketer get the same message, because nothing in Resend knows the difference. Sending a separate email to each person through the API solves that only if someone researches every prospect and writes every message first.

That's the real work in this job. A good result is a set of emails that each give one person a specific reason to reply, sent from a verified domain to people who still hold the role you're targeting, with follow-ups that stop as soon as someone answers. Resend's acceptable use policy also requires that everyone you email has explicitly opted in to hear from you, so this route works for prospects who have, such as event attendees, past trial users, or leads who went quiet.

Kite does that work for you. It checks the list, writes each email from research on the prospect's company, sends through your Resend account once you approve, and follows up in the same thread.

Start by telling Kite who you want to reach and why. You can hand it a list you already have:

"Email the people on this list about our new reporting feature. Send from our Resend account and follow up once with anyone who doesn't reply."

Kite is an AI marketer. It researches your business, builds a growth strategy, and ships the work that brings you new customers. By the time you ask, it already knows your positioning, your ideal customer profile, your current customers, and your competitors from that research. That means it can propose who to email, what the email should offer, and what a reply should lead to, such as a short call or a trial, without a long brief. Confirm the plan or adjust it, and Kite starts.

You can work with Kite in your browser or in Slack. You'll need to connect your Resend account through OAuth so Kite can manage contacts, segments, and sends there. If your list is a CSV file, share it in a Slack thread with Kite, or point Kite to the Google Sheet or CRM list where it lives. Kite can also build a list from scratch with its own built-in prospecting sources, so you don't need a separate data subscription, but the people on that list haven't opted in to hear from you, so Kite sends that outreach through another connected email product rather than Resend.

By default, Kite asks before it sends email to anyone outside your team. It shows you the audience, the subject lines, and the emails, and nothing goes out until you approve them with the button in the conversation or with a reply. Once you trust its outreach, you can let Kite send without asking.

Kite checks your sending domain first, because Resend won't send from your address until the domain is verified. It reads the domains on your Resend account and their verification status. If the domain you want to send from isn't there, Kite adds it and gives you the DNS records to place with your DNS provider. Once you've added them, Kite triggers verification and confirms the domain is ready before it schedules anything.

Many teams send outreach from a subdomain of their main domain, so the reputation of the address that sends invoices and password resets stays separate from outreach. Kite can set up that subdomain the same way.

Kite decides who receives an email by checking each person on the list before it writes anything. It confirms that the person still holds the role at that company, using their public professional profile or the company's own pages, and it drops anyone who has moved on. It removes your existing customers, your competitors, and anyone who has asked not to hear from you.

Kite also checks Resend itself. It looks up each address on Resend's suppression list, which holds every address that bounced hard, marked your email as spam, or was blocked by hand, because Resend will never deliver to those addresses. It looks up each address among your existing Resend contacts and skips anyone marked as unsubscribed.

Everyone who passes gets a fit score from one to five with a one-line reason, such as "Runs operations at a 300-person freight company that just opened two new warehouses." When the list is long, Kite splits it into primary and secondary groups so the strongest prospects go first. If fewer people qualify than you expected, Kite tells you how many it kept and why the rest fell out.

Kite adds every qualified prospect to Resend as a contact, so your account holds a record of who was contacted and why. Each contact gets an email address, a first name, and a last name. Kite reads the contact properties your account already has and creates any it needs, then fills them in for each person:

• Company
• Job title
• Fit score
• The reason this person fits
• The source of the information

For a short list, Kite creates the contacts one at a time. For a long one, it imports them in a single CSV upload with the columns mapped to those fields and checks the import's status until Resend finishes. A person who's already a contact gets their details updated instead of a second record, and Kite leaves their unsubscribed setting as it is.

Kite then creates a segment for the campaign, named for what it is, and adds the new contacts to it. The segment keeps the campaign's audience together in Resend, so you can see exactly who it reached and send a later update to the same group.

Kite chooses how to send based on what the email needs to say. A broadcast sends one email to the whole segment, with contact properties such as first name or company filled in for each person and a fallback value for anyone missing one. Kite uses a broadcast when the message really is the same for everyone, such as an invitation to an event your attendees already registered for.

For outreach to prospects, Kite sends each person their own email. The reason one prospect fits is rarely the reason the next one does, and an email that names the real reason earns more replies than one with a name swapped in. Resend sends individual emails as easily as broadcasts, so Kite doesn't have to trade relevance for convenience.

Kite writes each email from its research on that person's company and from what it knows about your business. It reads the company's site, its recent news, and its open roles, and it picks the one detail that makes your offer timely for that person, such as a new location, a recent funding round, or a job posting that describes the problem your product solves.

Each email has a subject line, a short body in your brand's voice, and a single clear request, such as a reply or a 20-minute call. Kite keeps outreach plain and short, because a personal note from one person to another reads better in an inbox than a designed newsletter. It sets the reply-to address to the inbox where you want answers to land.

When Kite asks for your approval, it shows you the full list of emails along with each person's fit score and reason. You can edit any email, drop any person, or ask Kite to change its angle for everyone.

Once you approve, Kite sends the emails through your Resend account from your verified domain. It sends them in batches of up to 100, or it schedules them so each one arrives during the recipient's working morning.

Kite keeps the identifier of every email it sends. Until a scheduled email goes out, Kite can move it to a different time or cancel it, so a change of plan doesn't mean an email you no longer want.

Kite follows up only with people who haven't answered. Before each round, it checks where replies arrive. That's your Resend receiving address if you route replies there, or a Gmail or Outlook inbox you've connected to Kite. It also checks the suppression list again, so anyone who bounced or complained since the first email is skipped.

Kite sends each follow-up as a reply to the original email. It uses the first email's identifier so the follow-up carries the same subject with "Re:" in front and sits under the first message in the prospect's inbox. Each follow-up adds something new instead of asking whether the person saw the last one, and Kite stops after two follow-ups, because silence after three emails is an answer too.

When someone does reply, Kite treats it as a conversation with a lead rather than a reason to send another email. It reads what they said, drafts a response to their actual question, and tells you.

When each round finishes, Kite posts a summary in the conversation where you asked. It says how many emails went out, how many were delivered, how many bounced, and who replied. It lists the people it skipped and why, and it includes the copy it sent so you can read exactly what each prospect saw.

Kite reads the delivery and engagement figures from Resend for the campaign's sends, including opens and clicks when tracking is turned on for your domain. It treats replies as the measure that matters, since opens are unreliable in many inboxes. When the campaign ends, it records which angles and subject lines drew replies in your team's knowledge base, so your next round of outreach starts from those results.

When Kite finishes, your Resend account holds a clean record of the campaign, and the conversation where you asked holds everything that was sent and what came back.