How to book meetings with conference speakers before the event

You set up meetings before a conference by deciding who you want to meet, finding out enough about each person to give them a real reason to say yes, and asking early enough that their schedule still has room. Speakers are usually the best place to start. They're named publicly on the agenda, their session tells you what they care about right now, and they tend to be senior people at companies that matter in your market.

That visibility cuts both ways. Everyone else at the event can read the same speaker list, so the people on it get a lot of requests, and their time at the event fills up in the weeks before it starts. A request that arrives a few weeks ahead has a far better chance than one sent the night before, and a request that sounds like it came from someone who read their session abstract has a better chance than one that sounds like a mass invite.

A good request does a few specific things:

• It names their session. One sentence that connects their talk to a problem you work on shows you've done the reading.
• It explains why meeting you is worth their time. Say what you'd talk about in terms of their situation, not your product.
• It asks for something small and concrete. A 15- or 20-minute coffee on a named day of the event is easy to agree to. "Let's connect sometime" isn't.
• It's short. A speaker reading email between prep sessions will give it a few seconds.
• It's easy to decline. A line like "If the schedule's too tight, no worries" makes a polite no as easy as a yes, which keeps the door open for after the event.

Most large conferences also run a networking app where registered attendees can browse profiles, send messages, and request meetings in reserved time slots. It's worth using, because some people do book through it, and it handles the logistics of rooms and times well. But the app only shows you who's there. It doesn't decide which speakers fit your business, confirm that their title is current, or write a message they'll want to answer, and not every speaker checks it. That's why a direct email to a work address, sent ahead of time, is still the main route to a speaker's calendar.

So the real work in this job is the research and the writing: choosing the right handful of speakers, learning enough about each one, and writing a request that only they could have received. Kite does that work for you, and it sends the requests once you approve them.

Start by telling Kite which event you're going to and what you want from it, in the Kite web app or in Slack:

"We're going to a big SaaS conference in San Francisco next month. Here's the agenda. Find the speakers worth meeting for us and draft meeting requests for the best ones."

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 existing customers, and your competitors from that research. That means it can judge which speakers matter to you without a long brief. If you haven't said what the meetings are for, such as finding customers, partners, or investors, Kite works it out from what it knows or asks you, because the goal decides who's worth meeting.

Tell Kite which days you'll be at the event and whose name should be on the emails, so each request is signed by a real person on your team. If you use a booking link, share it, and Kite will put it in the requests. You don't need any data accounts of your own, because Kite's built-in sources cover professional profiles and work emails. Kite sends from your team's Kite email address, or from an email account you connect.

Kite starts with the event's own pages, because they're the most reliable record of who's speaking and when. It reads the official site's speaker lineup, keynote list, agenda, tracks, and individual session pages, and it checks that each page belongs to this year's event rather than an earlier one. From those pages, it collects each speaker's name, title, company, session title, track, and time slot. It also notes the sponsors and exhibitors, because their staff can be worth meeting too.

If the event hasn't published its speakers yet, Kite tells you so, with the date it checked and a link to the page. In the meantime, it can work from last year's speakers or the call-for-speakers page, and it can check the lineup again once it's announced.

Kite chooses the speakers who matter most to your business, usually five to ten per event, rather than writing to the whole lineup. It weighs each speaker's role, their company, and their session topic against your ideal customer profile and your goal for the event. A speaker can matter because they're a likely buyer, because they influence buyers, because their company would make a good partner, or because they're an investor in your market.

Kite removes your existing customers, your competitors, and anyone who has asked not to hear from you. It checks for opt-outs in your knowledge base, in earlier replies, and in your connected CRM.

Each speaker who passes gets a fit score from one to five with a one-line reason. A typical reason reads like "VP of revenue operations at a 400-person software company, speaking on cleaning up CRM data before a sales reorg." When the list runs past about fifteen people, Kite splits it into primary and secondary groups so you know whom to approach first.

Kite researches each chosen speaker from public sources so the request can say something true and specific about them. It confirms that the person still holds the title and works at the company the agenda lists, using their professional profile or their company's own pages, because conference bios are often written months before the event. It then reads what the speaker works on, their session abstract, their recent public posts, and recent news at their company, such as a funding round, a launch, or a new hire on their team.

From that research, Kite picks the detail that best explains why this person would want to meet you now. Usually it's the session itself. Sometimes a recent event at their company gives an even stronger reason.

Kite looks up a professional email for each chosen speaker through its built-in data sources, using the person's name, company domain, and professional profile. Each address keeps the verification status the provider returned, such as verified, catch-all, or unverified. When no address turns up, the speaker stays on the list marked as not found, with the sources Kite tried, rather than receiving a guessed address. Kite includes only professional details, so personal email addresses and phone numbers stay out.

For speakers without a work email, Kite can draft a LinkedIn message of under 60 words instead, for you to send from your own account.

Kite writes one email per speaker, and each one makes a single ask: a short meeting at the event. The first two sentences give the reason for writing in terms of the speaker's situation, usually by connecting their session to a problem you work on. Kite then adds a sentence or two about what you'd talk about, written in the brand voice your knowledge base records.

The ask names the length of the meeting and the days you'll be at the event, and it includes your booking link when you've shared one. Each email stays under 120 words, goes out as plain text with at most one link, closes with an easy way to decline, and is signed by the team member you named. Kite then reads each draft as a stranger would and rewrites anything that sounds machine-made, because a request that reads as generated gets deleted.

Kite shows you every request beside the speaker's session, the detail it opens with, and the source for that detail, so you can check the research and the copy together. You can approve the batch, edit individual emails, or drop someone. Sending outreach is one of the things Kite asks about first, until you decide to give it more autonomy.

Once you approve, Kite sends one email per speaker so each message keeps its own personal body. It sends a small first batch of three to five, confirms they were accepted, and then sends the rest. Before each send, it checks opt-outs again. It records an identifier for every email it sends, so it can match each reply and follow-up to the right speaker.

Kite plans up to two follow-ups for each speaker who doesn't reply, spaced days apart and threaded onto the original email, so the speaker sees one conversation. Each follow-up adds something new rather than repeating the first request, such as a short point about their talk's topic or a different time that might suit them better. Because the event date sets a natural deadline, Kite plans the follow-ups so they arrive before the conference starts. After two follow-ups, Kite stops.

As replies come in, Kite tells you who responded and what they said. When a speaker agrees to a time and you've connected your calendar, Kite can put the meeting on it. If you've connected a CRM and asked Kite to record the work, it logs each speaker with their fit score and where the conversation stands.

When the requests are out, Kite reports in the conversation where you asked. It lists the speakers it chose and why, who was emailed, any sends that failed and why, who was skipped because of an opt-out, the copy that went out, and the follow-up plan. It also tells you how many speakers have a work email and which ones need a LinkedIn message from you instead. Kite saves the event research in your knowledge base, so next year's version of the same conference starts from what it learned this time.

When Kite finishes, you have a short list of the speakers worth your time at the event, a personal request in each of their inboxes, and a record of who has agreed to meet.