Free guide

The Event Outreach Framework

One standard for every event on the calendar: when outreach launches, what it says, where it sends from, who owns each step, and what the single per-event report contains.

Get the PDF Book a 20-min walkthrough

The short version

Launch at T-4 from shared mailboxes and keep one record per event

The complete framework is on this page. The PDF has the same content.

Launch at T-4 weeks

The same week the attendee list is built. Everything else in this framework depends on that one date.

Run 5 to 7 touches over 30 days

Across email and LinkedIn, spaced 2 to 3 days apart.

Send from accounts marketing owns

Dedicated outreach mailboxes on a secondary domain and a dedicated LinkedIn profile, so no event depends on a rep's personal account.

Keep the copy under 60 words

The recipient's company first, one peer reference, one specific outcome and one low-commitment question.

Keep one record per event

One engagement record covering every channel, so each event can be compared with the last.

The problem this solves

Per-event renegotiation shrinks a 30-day outreach window to 6 days

12 events a year can end up with 3 different motions. Underneath that is a negotiation repeated every event: app access, sending channels, copy approval and rep participation, all agreed with whoever happens to own each piece. Campaign timelines slip while the approvals wait, which is how a 30-day window becomes a 6-day one.

Centralised, and it works

Reviewed copy, sequences on shared mailboxes, tracking that still holds up when somebody asks about the event 3 months later.

Every AE writes alone

No review before it sends and no record after. Nobody outside the rep knows whether the messages worked.

Nobody outside the rep knows

What went out, to whom, and on what day are all unrecorded. The event gets reported on attendance because that is the only number anyone has.

What breaks when each event runs a different way

Quality varies

Nobody reviews the copy, so the same mistakes go out at every event.

Attribution breaks

Outreach that runs outside the workflow cannot be reported on, so the touches never reach the Opportunity record.

Accountability gets murky

When an event produces thin results there is no baseline, so nobody can say whether it was the targeting, the copy, the timing or the effort.

Written for B2B marketing and RevOps teams using Salesforce or HubSpot, where third-party events carry pipeline targets, sales follow-up, and CRM attribution pressure. Usually a fit for teams with several third-party events a year, or 1 to 2 major events with serious spend and pipeline targets.

Printable PDF

Get it as a PDF to send to your team

Same content, formatted to print and to forward. Work email, one email back, and you are not added to any list.

One email with the download link. You are not added to a mailing list. Read the privacy policy.

The copy, annotated

Real event emails get ignored when they open on the sender

Both examples below were sent ahead of events by teams with budget. Company names, people and events are removed. Each annotation applies to your next draft.

The pattern underneath both is the same. Outreach that leads with the sender's capabilities, reaches for category vocabulary, and reads like marketing material gets ignored. A senior buyer at a large conference receives dozens of these in the 2 weeks before the event starts and can recognise the shape from the first line.

Example ASent through the event app at a travel and cruise trade show.

I'd love to connect to see if there are any opportunities for partnership

I'm open for meetings at the convention center or for dinner Monday to Wednesday

Between those 2 lines sat a list of 6 product capabilities: onboarding, booking, boarding, identity verification, biometrics, card scanning.

What is not working

The opener

It asks the recipient to supply the reason for the meeting. A partnership is a category. It gives nobody a reason to give up half an hour.

The middle

A capability list. None of the 6 is tied to anything the recipient does on a Tuesday.

The close

It offers availability without saying what the half hour would cover.

The whole email

Every line of it could have been sent, unchanged, to every other name in the app.

It got no replies.

Example BHanded to us to send, unchanged, ahead of a banking summit.

Subject: GenAI Fraud Trends Discussion @[Event]

Hi [First Name],

I see you'll be attending the [Event] this week as well. I'm with [Company], where we're helping banks combat the latest fraud challenges using GenAI-powered identity verification and document analysis.

With deepfake attacks, synthetic identity fraud, and increasingly sophisticated document manipulation rising across the industry, fraud and risk teams are re-evaluating their defenses. Our AI models detect subtle anomalies and emerging attack patterns in real time, helping teams reduce losses and improve customer experience without adding friction.

If you're focusing on fraud strategy, synthetic ID mitigation, or smarter detection against deepfakes this year, I'd love to connect for 15 to 20 minutes during the conference to share what we're learning from other financial institutions and explore where we might help.

Are you available for a quick chat on Tuesday?

Subject: Coffee in [city]

Hi [First Name],

I wanted to follow up on connecting while we're both in town.

I'd love to say hello and compare notes on what you're seeing around GenAI-driven fraud, deepfakes, and synthetic IDs. Even a quick coffee between sessions would be great.

Are you around for 15 minutes tomorrow?

What is not working

Length

4 dense paragraphs before the ask. On a phone that is a screen and a half of scrolling before the recipient learns what is being requested.

Focus

The second sentence is about the sender's company, and so is the whole of the third paragraph. The recipient appears twice, both times as a merge field.

Vocabulary

6 pieces of category vocabulary in one email: GenAI, deepfakes, synthetic identity fraud, document manipulation, anomalies, attack patterns. It reads like a press release.

Personalisation

None past [First Name]. Nothing about their company, their role, or what they are dealing with this year.

The follow-up

Lighter in tone, which helps. "Compare notes" still does not say what about, so it asks for 15 minutes in exchange for nothing specific.

The under-60-word versions that replaced them

Same events, same target lists, same week. Both open on the recipient's company, and the sender's company does not appear.

Fintech and payments

Subject: quick q for [Company]

[First Name],

Saw [Company] is heading to [Event]. We have been helping [peer] reduce KYC false positives at onboarding without adding friction for applicants.

Curious if that is on your radar this year? Either way, happy to say hi at the show.

[Name]

Travel and cruise

Subject: quick q for [Company]

[First Name],

Saw [Company] is heading to [Event]. We have been helping [peer cruise line] speed up embarkation with automated ID checks, without adding friction for guests.

Curious if that is something you are looking at? Either way, happy to say hi at the show.

[Name]

Why the short versions get replies

Under 60 words

It fits on a phone screen without a scroll, which is where it will be read.

The recipient's company first

The first clause is about the recipient's company. The sender's company does not appear at all.

One unnamed peer

Social proof without a logo drop that invites a procurement question.

One free question

One question, and answering it costs the recipient nothing.

A close without pressure

"Either way" makes it easy not to reply, which makes a reply more likely.

Plaintext

No header image and no branded shell. It looks like an email a person sent.

Write the value clause yourself

Everything else in those 2 emails is structure and can be copied. The value clause is yours: one unnamed peer, one specific outcome, in the recipient's language. If you cannot fill it in without listing 3 capabilities, the problem is upstream in the positioning, and rewriting the sequence will not fix it.

Space 5 to 7 touches over 30 days

Split across email and LinkedIn, 2 to 3 days apart, so it reads as natural follow-up. That spacing only exists if outreach launches the same week the attendee list is built. Compressed into the last 6 days, the same 7 touches read as pressure and get fewer replies.

The standard

Run the same phases at every event so results are comparable

The steps, the owners and the quality bar stay the same for a large sponsorship and for 2 people walking a regional event.

T-4 weeks

Build the list and launch in the same week

Source the attendee picture from the open web and the event platforms you are entitled to.
Enrich every record through the enrichment vendor you already pay for, then deduplicate against the CRM so no rep cold-opens a live account.
Classify by ICP tier before a rep sees anything.
Sales flags named accounts and must-meet targets, and gets read-only visibility into what is going out.
Product marketing or demand gen approves the copy against a dated deadline.
Sequences go live on the first enriched batch. Waiting for the complete list eats into the 30-day window.

T-4 to T-1

Run the multi-touch sequence

Email: 5 to 7 steps, sent from the dedicated outreach mailboxes.
LinkedIn: connection requests and follow-ups from the dedicated outreach profile.
Event app: meeting requests to priority targets, where the app allows it.
2 to 3 days between touches.
Revise mid-flight on reply data. Early replies tell you which persona and which framing is landing at this event, and there is still time to act on it.

Event days

Support the floor live

One live channel per rep for the duration.
Adjust sequences daily against what is happening on the floor.
Surface hot replies to the owning rep the hour they land.
Sync new contacts to Salesforce or HubSpot the same day, tagged to the pre-event score.

T+1 week

Follow up before the memory fades

Post-event sequences live within 48 hours from event end, segmented by what happened: met, replied, invited and did not come, never engaged.
A per-rep summary of who they spoke to, what was agreed, and what is still open.
Every contact written back with source attribution: event, tier, channel, persona, owner.
Marketing ops routes leads into nurture, validates the CRM data, and updates campaign membership.

Ongoing

Produce one record per event

Combine sequence activity, LinkedIn activity, meetings and pipeline into a single per-event record.
Report who was contacted, through which channel, what the response was, which meetings were booked, and what pipeline was created.
Keep one row per event. After 4 events, that sheet shows which events to repeat.

What it sends from

Send from accounts marketing owns, so outreach survives rep turnover

Outreach that depends on borrowing a rep's mailbox and LinkedIn account stops the first time that rep is busy or leaves.

Dedicated outreach mailboxes

Several mailboxes on a secondary sending domain, under a real sales leader's name, rotated across sequences so volume is distributed and domain health holds. Configuration, warm-up and monitoring belong to whoever runs the program, coordinated with IT once per program.

Protects the reps' primary mailbox reputation, which is hard to recover once it is damaged.
Centralises tracking. Every event touch goes through the same mailboxes.
Keeps sender identity consistent across the calendar.
Scales as event volume grows, without a new negotiation each time.

A dedicated outreach LinkedIn profile

One profile under a real team member's name, from sales or marketing leadership, used only for event outreach. Connection requests and follow-ups run through it, and marketing owns it.

After a year of events the profile is a curated audience of ICP contacts that stays with the company through rep turnover.
It doubles as a distribution channel for event recaps and product updates to a warm audience.
Marketing owns it, so no event depends on an individual agreeing to share their account.
Keep the activity human. LinkedIn can restrict a profile that behaves like a tool, which removes the channel mid-campaign.

One report per event shows who was contacted and what followed

When it is time to assess an event, the engagement data is normally in 4 places. Sequence activity sits in the sequencer. LinkedIn outreach sits in whatever tool sent it. Meetings and pipeline sit in Salesforce or HubSpot. Badge scans and event-specific data arrive separately from marketing ops. Pulling those together manually per event is slow and produces an incomplete picture: some leads have outreach data and no CRM activity, others have meetings logged and no source attribution.

The target is one record per event that answers who was contacted, through which channels, what came back, which meetings were booked, and what pipeline followed. That record lets the next event's plan argue from evidence.

Ownership

Marketing runs pre-event outreach, and reps take the replies

The pre-event motion belongs to the event program and marketing. Reps still see what is going out, flag the accounts that matter to them, and take the replies. They stop writing copy, building sequences and deciding event by event whether to participate.

Activity	Event program	Sales	Marketing and ops
Attendee data	Source, enrich, deduplicate against the CRM, tier by ICP	Flag named accounts and must-meet targets	Confirm which ICP definition is in force
Outreach copy	Write, segment by persona, revise on reply data	Read-only visibility, so what went out is never a surprise	Review and approve before launch, against a dated deadline
Email sequences	Build, launch from the dedicated mailboxes, monitor, adjust	Handle replies and book the meetings	Keep suppression and consent lists current
LinkedIn outreach	Build and run from the dedicated outreach profile	Accept connections and carry the conversation	Own the profile as a marketing asset
Event app meetings	Send requests to priority targets	Take the meetings	Obtain app credentials before T-4
CRM writeback	Upload contacts, tag event, tier, channel, persona and owner	Keep the next step on the record	Validate, route, update campaign membership
Reporting	One engagement record per event, all channels combined	Pipeline and stage updates	Reconcile campaign and revenue reporting

What changes

With one standard, every event launches at T-4 with a 30-day window

Area	Without a standard	With one
Who runs outreach	Renegotiated per event, per rep	The same process every event, owned by the event program and marketing
Copy quality	Varies by event and by whoever wrote it	Reviewed and revised on reply data across events
Timing	Sequences start late and get compressed into the final week	Launch at T-4, full 30-day multi-touch window
Visibility	No record of what was sent or to whom	Opens, replies, meetings and pipeline tracked per event
Engagement data	Scattered across 4 systems and reconciled manually	One engagement record per event, all sources combined
Sending infrastructure	Individual rep mailboxes and personal LinkedIn accounts	Dedicated mailboxes and a dedicated outreach profile owned by marketing
Accountability	Unclear whether thin results were targeting, copy, timing or effort	A named owner at every step and a baseline to compare against
Rep time	Spent on list hygiene, copywriting and sequence admin	Spent on replies, meetings and closing

Where Luminik fits

Run manually, the standard costs a person's week of copy per event

None of this needs software. It has been run with a spreadsheet, a sequencer, a set of mailboxes and one person who held the dates.

The T-4 week is days of list building, enrichment and deduplication, and copy segmented by persona is a person's week per event. After every event, somebody reconciles 4 systems manually to produce the engagement record.

Luminik is the event pipeline platform that runs those steps for teams who do not want to hire for them: source, enrich, sequence, capture, attribute, on the Salesforce, HubSpot, Apollo and enrichment accounts you already pay for. The sequencer, the enrichment vendor and the CRM all stay yours.

Printable PDF

Take the framework with you

The full standard as a formatted PDF, including the annotated copy examples, ready to forward to whoever writes the next sequence.

One email with the download link. You are not added to a mailing list. Read the privacy policy.

What teams ask before adopting the standard

What is an event outreach framework?

A written standard for how pre-event outreach runs, applied the same way to every event on the calendar. It fixes when outreach launches, who builds the list, who writes the copy, who approves it, which mailboxes and profiles it sends from, what gets logged, and what the single per-event report contains. The answers then stop being renegotiated 4 weeks before every event.

How early should pre-event outreach start?

The same week the attendee list is built, which in this framework is 4 weeks out. That gives a full 30-day window, so a 5 to 7 touch sequence can sit 2 to 3 days apart. Outreach that launches in the last 2 weeks arrives while the recipient is booking flights, and it reads as urgent for the sender.

Why does event outreach get ignored?

Because it leads with the sender's capabilities. A recipient at a large conference receives dozens of these in the 2 weeks before the event starts, and the pattern is recognisable from the first line: a vague opener, a paragraph about the vendor, a list of features, then an ask. The messages that get replies open with the recipient's company, name one specific outcome, ask one low-commitment question, and finish under 60 words.

Should event outreach send from an AE's mailbox or a dedicated one?

A dedicated set of mailboxes on a secondary sending domain. Sending from individual rep mailboxes puts their primary deliverability at risk, scatters the tracking across accounts nobody in marketing can see, and makes every event a negotiation with whoever happens to own the mailbox. Dedicated mailboxes keep sender identity consistent across events and keep every reply in the same inboxes.

How many touches should a pre-event sequence have?

5 to 7 over 30 days, split across email and LinkedIn, spaced 2 to 3 days apart. The spacing gets cut when the launch slips.

Who should approve the outreach copy?

Product marketing or demand gen, against a dated deadline. Copy review is the dependency that slips most often, and everything downstream waits on it. Give it a name and a date in the week the list is built.

What should a single event outreach report contain?

Who was contacted, on which channel, what came back, which meetings were booked before and during the event, and what pipeline followed. One record per event. Sequence activity, LinkedIn activity, badge data and CRM records normally live in 4 systems, and reconciling them manually after each event is where event reporting usually stops.

Keep going

Read the full annotations, then build the next sequence

Event outreach emails, read line by line

The full annotation of both examples above.

What 5 event programs taught us

Field learnings on event outbound across 5 programs.

The Event GTM Playbook

The 28-day sprint and post-event triage around this standard.

Why event campaigns show 0 converted leads

The CRM setup that hides event-sourced pipeline.

Outbound sequence generator

A sequence for a specific event and persona.

How Luminik runs the pre-event weeks

Sourcing, ICP scoring and sequences, 6 weeks before the event.

Apply the standard to the next event on your calendar

Pick one event. We walk the sourcing, the ICP cut, the sequence copy and the writeback to Salesforce or HubSpot on that specific event.

Book a 20-min walkthrough

I take every walkthrough myself. Bring the next event on your calendar.

Prasad Subrahmanya, founder