Most SDRs already know they should email prospects before a show. Where they lose the reply is in the copy: a generic "will you be at [event]?" note reads exactly like the other forty emails already sitting in that inbox. The fix isn't a cleverer subject line – it's a small set of templates built around what actually earns a reply, used at the right point in the countdown to the event.
Why event context should outperform a generic blast
Cold email as a category has gotten harder to land. Instantly's 2026 Cold Email Benchmark Report – built from billions of cold email interactions across more than 700,000 businesses – puts the average reply rate at 3.43%, with top-quartile senders at 5.5%+ and elite campaigns clearing 10.7%. The report also found that 58% of replies land on the first email, with the remaining 42% coming from follow-ups – which is the whole case for running a short sequence instead of a single send.
An event gives you something most cold email doesn't have: a real, dated, shared reason to talk. "Will you be at [event] next month?" isn't a pitch, it's a question a normal person would ask a peer – which is exactly why it should outperform "quick question about your stack" in a prospect's inbox. The templates below are built to keep that advantage instead of accidentally writing it back into a generic pitch.
Three templates, timed to the countdown
Run these as a sequence rather than picking one. Each does a different job, and skipping straight to the urgency email without the earlier touches reads as presumptuous instead of familiar.
1. The first touch (4–6 weeks out)
Subject: [Event] – worth 15 minutes?
Hi [First name],
Saw [Company] is on the attendee list for [Event] next month. We work with
[peer company type] on [specific, narrow problem – not your whole platform],
and I'd guess it's relevant given [specific trigger: a recent hire, a product
launch, a job posting you saw].
Would you be up for a 15-minute coffee or meeting slot while we're both there?
[Your name]
Why it works: it opens with the event, not the pitch, so the ask feels proportionate to the relationship. Naming a specific trigger instead of a generic pain point signals you actually looked at their company rather than merging a mail list. Keeping it under 80 words matters too – Instantly's benchmark data ties first-touch emails under that length to stronger reply rates than longer, feature-heavy intros.
2. The value-add follow-up (2 weeks out)
Subject: Re: [Event] – worth 15 minutes?
Hi [First name],
Following up ahead of [Event]. One thing that might be useful before the
show: [a specific data point, a session worth attending, or a one-line
insight tied to their industry].
I've got a few slots open on [Day 1] and [Day 2] if you want to grab 15
minutes – happy to work around your schedule.
[Your name]
Why it works: the first email asked for time; this one gives something back before asking again. A concrete piece of value – not "just checking in" – is what earns the second reply from someone who skimmed and forgot the first note. Naming specific days also turns an open-ended "let's meet" into a decision the reader can make in one line.
3. The urgency touch (about a week out)
Subject: [Event] is next week – still have room
Hi [First name],
[Event] is next week and my calendar's filling in. I've still got [specific
time, e.g. "10am Tuesday" or "a slot Wednesday afternoon"] open if you'd
like to grab it – otherwise no worries, hope the show goes well.
[Your name]
Why it works: real scarcity, stated plainly, without pressure tactics. Naming an exact slot instead of "let me know when works" removes the back-and-forth that kills meetings in the final week, when both calendars are getting busy. The low-pressure close ("otherwise no worries") keeps the door open for an on-site conversation even if they don't book.
Keep every touch short, specific, and single-threaded
A few rules apply across all three templates. Cap each email at one ask – a meeting, not a meeting plus a demo plus a resource link. Reference exactly one specific, real detail about the recipient or their company rather than three generic ones; a single well-chosen trigger reads as researched, while three vague ones read as a template with merge fields. And send from whoever owns the relationship – an SDR sequence for cold accounts, a rep's own address for anything with existing pipeline – since reply rates on outreach that already has a name attached consistently beat anonymous sequences.
None of this replaces good targeting. A well-written email to the wrong account still gets ignored, and a mediocre one to a high-fit account with a real trigger still tends to land. Get your pre-event target list built and prioritized first, then point these templates at it – that order is what turns a sequence into booked meetings instead of just sent emails.
Copy the three templates above into your sequencer, swap in your own trigger details, and start the first touch four to six weeks before your next show. If you want the target list and triggers ready before you write a single email, try Scryon free to see how Scryon surfaces them for SDR teams ahead of an event.