--- title: "Event outreach framework: the pre-event standard" description: "A free standard for pre-event outreach: the five phases, real outreach copy read line by line, the mailboxes it sends from, and one report per event." canonical: https://www.luminik.io/resources/event-outreach-framework/ source: html generated_at: 2026-08-09T21:22:58.194Z --- 1. [Home](/) 2. [Resources](/resources/) 3. The Event Outreach Framework Free guide, full text on this page # 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](#get-the-pdf)[Book a 20-min walkthrough](/demo/) ## The short version - Launch outreach the same week the attendee list is built, four weeks out. Everything else in this framework depends on that one date. - Run five to seven touches over 30 days across email and LinkedIn, two to three days apart. - Send from dedicated outreach mailboxes on a secondary domain and a dedicated LinkedIn profile owned by marketing, not from individual rep accounts. - Keep the copy under 60 words: the recipient's company first, one peer reference, one specific outcome, one low-commitment question. - Produce one engagement record per event covering every channel, so event performance can be compared rather than recalled. Everything below is the complete framework. Nothing on this page is held back for the download. The problem this solves ## Outreach that works differently at every event A team with a dozen third-party events a year usually runs three different motions across them. 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 six-day one. A ### Centralised, and it works Reviewed copy, sequences in one place, tracking that still holds up when somebody asks about the event three months later. B ### Every AE writes their own No review before it sends and no record after. The messages may be good; nobody outside the rep will ever know either way. C ### 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 as a result Quality varies Copy nobody reviewed is copy nobody improved, so the same mistakes ship 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 one to two flagship events with serious spend and pipeline targets. Printable PDF ## Want 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. Work emailFirst name (optional)Email me the PDF One email with the download link. You are not added to a mailing list. Read the [privacy policy](/privacy/). The copy, annotated ## What bad event outreach looks like, line by line Both examples below were really sent, for real events, by teams with real budget. Company names, people and events are removed. The annotations are the reason they are here: a bad example on its own tells you nothing you can use, and a bad example with the reasoning attached is something you can apply to your own draft tomorrow. 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 fortnight 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 two lines sat a list of six product capabilities: onboarding, booking, boarding, identity verification, biometrics, card scanning. ### What is not working - The opener asks the recipient to supply the reason for the meeting. A partnership is a category. It is not a reason to give up half an hour. - The middle is a capability list. Not one of the six is tied to anything the recipient does on a Tuesday. - The close offers availability without saying what the half hour would cover. - Nothing in it could not have been sent, unchanged, to every other name in the app. Expected reply rate: close to zero, and that is what it got. 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 - Four 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. - 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. - Six pieces of category vocabulary in one email: GenAI, deepfakes, synthetic identity fraud, document manipulation, anomalies, attack patterns. It reads like a press release, and press releases get skimmed. - No personalisation past \[First Name\]. Nothing about their company, their role, or what they are dealing with this year. - The follow-up is 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 short versions that replaced them Same events, same target lists, same week. Both are under 60 words and both open on the recipient rather than the sender. 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 these get replies - Under 60 words. It fits on a phone screen without a scroll, which is where it will be read. - The first clause is about the recipient's company. The sender's company does not appear at all. - One peer reference, unnamed. Social proof without a logo drop that invites a procurement question. - One question, and answering it costs the recipient nothing. - The close removes the pressure. "Either way" is doing real work: it makes a non-reply socially free, which is exactly what makes a reply likely. - Plaintext. No header image, no branded shell. It looks like an email a person sent. ### The one clause you have to write yourself Everything else in those two 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 three capabilities, the problem is upstream in the positioning rather than in the email, and no amount of rewriting the sequence will fix it. ### Copy is only half of it The sequence around it is five to seven steps over 30 days, split across email and LinkedIn, spaced two to three days apart so it reads as natural follow-up. That spacing only exists if outreach launches the same week the attendee list is built. Compress the same seven touches into the last six days and the sequence reads as desperate, which is the tone that costs the most replies. The standard ## Five phases, applied to every event Same steps, same ownership, same quality bar, whether the event is a flagship sponsorship or two people walking a regional show. A process that gets renegotiated per event produces results that cannot be compared across events. T-4 weeks ### Build the list and launch in the same week Phase 1 - 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 is how the 30-day window disappears. T-4 to T-1 ### Run the multi-touch sequence Phase 2 - Email: five to seven 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. - Two to three days between touches. The spacing is what makes the sequence read like follow-up rather than a drip. - 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 Phase 3 - 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, not the evening after. - 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 Phase 4 - Post-event sequences live inside 48 hours, 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 Phase 5 - 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 forever. After four events, that sheet is the strongest event planning argument you have. What it sends from ## Sending infrastructure This is the part teams skip, and it is the part that decides whether the framework survives its second event. Outreach that depends on borrowing an individual rep's mailbox and LinkedIn account is outreach that 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 rather than per event. - Protects the reps' primary mailbox reputation, which is hard to recover once it is damaged. - Centralises tracking. Every event touch is visible in one place rather than in seven inboxes. - 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 rather than borrowing access from whoever happens to be attending. - The network compounds. After a year of events it 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. A profile that behaves like a tool gets restricted, and a restricted profile takes a channel out of the plan mid-campaign. ### The one report per event When it is time to assess an event, the engagement data is normally in four 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 by hand 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 five questions: who was contacted, through which channels, what came back, which meetings were booked, and what pipeline followed. That record is what makes the next event's plan an argument from evidence rather than from memory. Ownership ## Who owns what 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, not during the event | | 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 ## Before the standard, and with it | 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 four systems and reconciled by hand | 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 | Honest footnote ## Where Luminik fits 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. That is the honest version, and it is why the framework is written as a standard rather than as a product tour. The cost is where you would expect. The T-4 week is days of list building, enrichment and deduplication. Copy is a person's week per event once it is segmented by persona. The single engagement record is somebody reconciling four systems by hand after every event, in the same week the team is jet-lagged and behind. 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 stays yours. The enrichment vendor stays yours. The CRM stays the system of record. 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. Work emailFirst name (optional)Email me the PDF One email with the download link. You are not added to a mailing list. Read the [privacy policy](/privacy/). ## Questions about the framework 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. What matters is not the document itself but that the answers stop being renegotiated four weeks before every event. How early should pre-event outreach start? The same week the attendee list is built, which in this framework is four weeks out. That gives a full 30-day window, so a five to seven touch sequence can sit two to three days apart instead of being compressed into the last week. Outreach that launches inside two weeks arrives while the recipient is booking flights, and it reads as urgent for the sender rather than useful for the reader. 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 fortnight 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 the whole record in one place. How many touches should a pre-event sequence have? Five to seven over 30 days, split across email and LinkedIn, spaced two to three days apart. The spacing is the part that gets cut when the launch slips, and it is the part that makes the sequence read like a person following up rather than an automated drip. Who should approve the outreach copy? Product marketing or demand gen, against a dated deadline rather than an open request. Copy review is the dependency that slips most often, and everything downstream waits on it. Give it a name and a date at the point the list is built, not the week the sequence is meant to go live. 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, in one place. Sequence activity, LinkedIn activity, badge data and CRM records normally live in four systems, and reconciling them by hand after each event is where event reporting usually stops. ## Keep going [Two event outreach emails, read line by line](/blog/2026/event-outreach-emails-line-by-line/)[What five event programs taught us about event outbound](/blog/2026/five-event-programs-field-learnings/)[The Event GTM Playbook: the 28-day sprint and post-event triage](/resources/event-gtm-playbook/)[Why event campaigns show zero converted leads](/blog/2026/event-campaigns-zero-converted-leads/)[Generate a sequence for a specific event](/tools/event-outbound/)[How Luminik runs the pre-event weeks](/product/pre-event-intelligence/) ## 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](/demo/)