Event Follow-Up Playbook
Purpose: Hyper-personalized event follow-up sequences for conferences, dinners, demo days Model: 11x’s Alice event follow-up system Format: Structured for agent generation with human-in-the-loop review Last Updated: 2025-01-16
Overview
Use Case: Follow up on warm leads from events (conferences, booths, VIP dinners, demo days, panel discussions)
Goal: Turn warm event connections into qualified pipeline through hyper-personalized, multi-touch follow-up sequences
Key Principle: Not generic “Great to meet you!” emails—narrative-based messaging that incorporates specific event context and engagement details
Segmentation Strategy
Contact Types
1. Booth Visitor
- Context: Walked by booth, scanned badge, asked questions, took materials
- Engagement Level: Light to moderate
- Personalization Angle: What they asked about, what they engaged with at booth
- Example Context: “Great chat about AI ops at Booth #118”
2. Panelist / Speaker
- Context: Presented at event, spoke on panel, gave talk
- Engagement Level: High visibility
- Personalization Angle: Their topic, their insights, mutual respect
- Example Context: “Loved your talk on data infrastructure at the [Event Name] panel”
3. VIP Dinner / Private Event
- Context: Attended exclusive dinner, private meeting, curated event
- Engagement Level: Very high (curated audience)
- Personalization Angle: Intimate setting, deeper conversation topics
- Example Context: “Enjoyed our conversation about [Topic] at the VIP dinner last night”
4. Meeting Logs (Scheduled Meetings)
- Context: Had a scheduled meeting, 1:1 conversation, formal intro
- Engagement Level: Highest (intentional meeting)
- Personalization Angle: Specific topics discussed, commitments made, next steps mentioned
- Example Context: “Following up on our conversation about [Specific Topic] and [Next Step Mentioned]”
5. General Attendee
- Context: Was at event, mentioned in attendee list, no specific interaction noted
- Engagement Level: Unknown/Light
- Personalization Angle: Event context, mutual attendance, potential mutual connections
- Example Context: “Saw you were at [Event Name]—would love to connect on [Relevant Topic]“
Persona-Based Messaging
Persona 1: Executives (C-level, VPs, Directors)
Tone & Style:
- Concise and ROI-driven
- Focus on outcomes, not process
- High-level strategic value
- Respect for their time (short emails, clear ask)
Key Messages:
- Business impact and ROI
- Strategic value (scaling, growth, efficiency)
- Executive-level case studies
- Quick wins and fast time-to-value
What to Avoid:
- Technical jargon
- Long emails
- Process details
- Feature lists
Example Opening:
"Great connecting at [Event]—appreciated your perspective on [Executive Topic]."
Example Value Prop:
"We help [Company Type] leaders like you scale data operations 3x faster while reducing costs by 40%. Our embedded model means you get senior operator expertise without the FTE overhead."
Example CTA:
"Would love 15 minutes to show how [Similar Company] achieved [Outcome] in 30 days. Available this week?"
Persona 2: Practitioners (Engineers, Analysts, ICs)
Tone & Style:
- Tactical and use-case focused
- Technical depth (they appreciate it)
- Specific examples and case studies
- Problem-solving approach
Key Messages:
- Technical solutions to specific problems
- Tools and methodologies
- Implementation details (how it works)
- Peer examples (similar companies/situations)
What to Avoid:
- Vague business value
- Oversimplifying technical challenges
- Sales-y language
- Ignoring technical depth
Example Opening:
"Enjoyed our chat about [Technical Topic] at [Event]—especially your insights on [Technical Detail]."
Example Value Prop:
"We specialize in standing up data stacks for fast-growing companies. We handle everything from dbt transformations to Looker dashboards, with a focus on clean architecture and maintainable code."
Example CTA:
"Would be great to walk through how we'd approach [Specific Technical Challenge] at [Their Company]. Happy to share architecture diagrams and code samples."
Persona 3: VCs / Investors
Tone & Style:
- Vision-led and hype-calibrated
- Portfolio company focus
- Strategic partnerships
- Growth potential
Key Messages:
- Portfolio company benefits
- Strategic value to their investments
- Growth enablement stories
- Partnership opportunities
What to Avoid:
- Direct sales pitches
- Ignoring portfolio angle
- Being too transactional
- Missing strategic vision
Example Opening:
"Great meeting you at [Event]—loved hearing about [Portfolio Company] and their [Challenge]."
Example Value Prop:
"We work with many of your portfolio companies (including [Company 1] and [Company 2]) to accelerate their data maturity. We move fast, build cleanly, and scale as they grow—perfect for growth-stage teams."
Example CTA:
"Would love to chat about how we can support [Portfolio Company]'s data strategy. Happy to provide intro to [Similar Portfolio Company] who's been a great partner."
Follow-Up Sequence Structure
Sequence: Event Follow-Up (Multi-Touch)
Touch 1: Immediate Follow-Up
- Timing: 24-48 hours after event
- Channel: Email (primary)
- Purpose: Reconnect while event is fresh, reference specific interaction
- Tone: Warm, contextual, value-forward
Touch 2: Value Add (If No Response)
- Timing: 3-5 business days after Touch 1
- Channel: Email (or LinkedIn if email bounced)
- Purpose: Provide value (resource, insight, case study), re-engage
- Tone: Helpful, not pushy
Touch 3: Re-engagement (If No Response)
- Timing: 7-10 business days after Touch 2
- Channel: LinkedIn (if email no response) or different angle
- Purpose: Alternative approach, different angle, try to re-engage
- Tone: Casual, relationship-building
Touch 4: Long-Tail Follow-Up (If Engaged but No Meeting)
- Timing: 3+ weeks after event
- Channel: Email or LinkedIn
- Purpose: Re-engage “cool conversation,” keep pipeline alive
- Tone: Friendly reminder, low pressure
Touch 5: Final Attempt (If Still No Response)
- Timing: 4-6 weeks after event
- Channel: Email
- Purpose: One last touch, offer value, leave door open
- Tone: Respectful, final attempt, no hard feelings
Message Templates by Segment & Persona
Template Set 1: Booth Visitor → Executive
Touch 1: Immediate Follow-Up
Subject: Great connecting at [Event Name] — [Their Company]'s data strategy
Hi [Name],
Great chatting with you at our booth about [Specific Topic Discussed]. I appreciated your perspective on [Their Insight/Question].
[1-2 sentences about what Brainforge does that's relevant to their question/need]
I noticed [Their Company] is [Specific Context: e.g., scaling quickly, building data team, etc.]. We work with similar companies like [Relevant Case Study] to [Specific Outcome].
Would love 15 minutes to show you how we approach [Specific Challenge] for companies like yours. Available this week?
Best,
[Your Name]
P.S. [Optional: Link to relevant resource, case study, or event photo]
Personalization Placeholders:
[Event Name]- Name of event[Specific Topic Discussed]- What they asked about at booth[Their Insight/Question]- Specific thing they said[Their Company]- Their company name[Specific Context]- Company-specific detail (from research or conversation)[Relevant Case Study]- Similar company example[Specific Outcome]- Business outcome relevant to them[Specific Challenge]- Challenge that fits their situation
Template Set 2: Panelist/Speaker → Practitioner
Touch 1: Immediate Follow-Up
Subject: Loved your talk at [Event Name]
Hi [Name],
Really enjoyed your presentation on [Their Topic] at [Event Name]—especially your point about [Specific Insight]. I've been thinking about [Related Technical Challenge] and your approach resonated.
We're Brainforge AI, and we help teams like yours tackle [Specific Technical Problem]. We work with companies using [Relevant Tech Stack] to [Specific Outcome].
Given [Their Company]'s focus on [Technical Area], I thought you might find our approach interesting—especially how we handle [Specific Technical Detail].
Would be great to walk through how we'd approach [Specific Challenge] at [Their Company]. Happy to share architecture diagrams and code samples.
Best,
[Your Name]
P.S. Here's a case study of how we solved a similar challenge: [Link]
Template Set 3: VIP Dinner → Executive
Touch 1: Immediate Follow-Up
Subject: [Event Name] dinner follow-up
Hi [Name],
Enjoyed our conversation about [Topic Discussed] at the VIP dinner last night—your insights on [Their Insight] were spot on.
I mentioned how Brainforge helps companies like [Their Company] accelerate data maturity. Given your focus on [Strategic Priority], I thought you might find our approach valuable.
[1-2 sentences on relevant strategic value]
Would love 15 minutes to discuss how we could support [Their Company]'s goals. I'm available [Timeframe]—what works for you?
Best,
[Your Name]
Template Set 4: Meeting Logs → Practitioner
Touch 1: Immediate Follow-Up
Subject: Following up on our [Event Name] conversation
Hi [Name],
Great connecting at [Event Name]—appreciated our discussion about [Specific Topic] and [Next Step Mentioned].
As discussed, I'm following up with:
- [Resource 1: e.g., Architecture diagram for your use case]
- [Resource 2: e.g., Case study of similar implementation]
- [Resource 3: e.g., Pricing overview]
[1-2 sentences summarizing what we discussed and how Brainforge fits]
Would love to continue the conversation. [Next Step Suggestion: e.g., Technical deep dive, intro to similar company, etc.]
When works best for you?
Best,
[Your Name]
Personalization Rules
What to Always Include
Event Context:
- Specific event name
- When it happened (relative: “last week”, “at [Event Name]”)
- Where you interacted (booth, panel, dinner, etc.)
Engagement Details:
- What they said/asked about
- Their insight or perspective
- Specific topic discussed
- Any next steps mentioned
Company-Specific Research:
- Company size, stage, industry
- Recent news, funding, growth
- Tech stack (if visible)
- Team size/structure (if known)
Relevant Case Studies:
- Similar company examples
- Similar industry/situation
- Similar challenge solved
- Similar outcome achieved
What to Never Include
Generic Phrases:
- ❌ “Great to meet you!” (too generic)
- ❌ “Hope you’re doing well” (filler)
- ❌ “I wanted to reach out” (obvious)
Vague References:
- ❌ “At the event” (which event? when?)
- ❌ “Our conversation” (what did we talk about?)
- ❌ “As we discussed” (what did we discuss?)
Sales-y Language:
- ❌ “I think we could help” (too sales-y)
- ❌ “Let me tell you about us” (me-focused)
- ❌ “Our solution is perfect” (too pushy)
Qualification Workflow
During Follow-Up Sequence
Qualification Questions (Natural Conversation):
-
Budget Signals:
- “What’s your timeline for addressing [Challenge]?”
- “Have you allocated budget for [Solution Type] this quarter?”
- “Are you considering hiring vs. partnering?”
-
Authority Signals:
- “Who else is involved in decisions like this?”
- “What’s your role in [Decision Process]?”
- “Who would need to be involved?”
-
Need Signals:
- “What’s your biggest challenge with [Area] right now?”
- “How are you currently handling [Problem]?”
- “What would success look like?”
-
Timeline Signals:
- “When are you looking to solve [Problem]?”
- “Is this a priority for Q[X]?”
- “What’s driving the urgency?”
Qualification Scoring (Post-Engagement)
Score Each Lead (1-10):
ICP Fit (Company):
- 10: Perfect match (size, stage, industry)
- 7-9: Good match
- 4-6: Fair match
- 1-3: Poor match
Engagement Level:
- 10: High engagement (responded, interested, asked questions)
- 7-9: Moderate engagement (opened, clicked)
- 4-6: Low engagement (opened, no response)
- 1-3: No engagement
Decision Maker:
- 10: Clear decision maker (C-level, VP)
- 7-9: Influencer with authority (Director)
- 4-6: Practitioner/influencer (Manager, IC)
- 1-3: No decision authority
Pain Point:
- 10: Clear, urgent pain point identified
- 7-9: Pain point mentioned
- 4-6: Potential pain point
- 1-3: No clear pain point
Budget/Timeline:
- 10: Budget confirmed, active project
- 7-9: Budget likely, timeline in 3-6 months
- 4-6: Budget unclear, timeline in 6-12 months
- 1-3: No budget, no timeline
Total Score:
- 40-50: Highly qualified → Route to AE immediately
- 30-39: Qualified → Continue nurturing, route when ready
- 20-29: Marginally qualified → Low priority, long-term nurture
- 10-19: Not qualified → Disqualify, mark for future
Handoff Summary Format
When routing to AE, include:
## Lead Handoff: [Company Name] - [Contact Name]
**Event**: [Event Name] - [Date]
**Contact Type**: [Booth Visitor/Panelist/VIP Dinner/Meeting Logs]
**Persona**: [Executive/Practitioner/VC]
### Engagement Summary
- **Initial Interaction**: [What happened at event]
- **Topics Discussed**: [Specific topics]
- **Their Insights**: [What they said]
- **Interest Level**: [High/Medium/Low]
### Company Context
- **Company**: [Name]
- **Size**: [Employees/Revenue]
- **Stage**: [Series A, etc.]
- **Industry**: [Vertical]
- **Tech Stack**: [If known]
### Qualification Signals
- **ICP Fit**: [Score]/10 - [Why]
- **Decision Maker**: [Score]/10 - [Role/Authority]
- **Pain Point**: [Score]/10 - [What pain point]
- **Budget**: [Score]/10 - [Signals]
- **Timeline**: [Score]/10 - [Signals]
- **Total Score**: [X]/50
### Conversation Flow
- **Touch 1** ([Date]): [What happened]
- **Touch 2** ([Date]): [What happened]
- **Touch 3** ([Date]): [What happened]
### Key Insights for AE
- **What Resonated**: [What they responded to]
- **Concerns/Objections**: [If any]
- **Best Next Step**: [Suggested approach]
- **Suggested Angle**: [How to approach them]
### Resources Shared
- [Resource 1]
- [Resource 2]
### Recommended Action
- [ ] Schedule discovery call
- [ ] Send deeper technical info
- [ ] Connect with similar client
- [ ] Nurture for 3-6 months
- [ ] Disqualify (reason: [X])Long-Tail Follow-Up Strategy
3+ Weeks Post-Event
Strategy: Re-engage “cool conversations” that didn’t convert initially
Template:
Subject: [Event Name] follow-up — [Relevant Update]
Hi [Name],
Hope you're doing well! I was just thinking about our conversation at [Event Name] about [Topic]—especially your point about [Their Insight].
[Optional: Relevant update]
- "I saw [Their Company] just raised Series B—congrats!"
- "Noticed you're hiring for [Role]—growth mode!"
- "[Industry] update that's relevant to your situation"
Since we last connected, [Relevant Brainforge update]:
- [New case study/client]
- [New capability/insight]
- [Industry trend/development]
Would love to reconnect and see how [Relevant Topic] is going at [Their Company]. Still worth a quick chat?
Best,
[Your Name]
When to Use:
- Lead had initial engagement but no meeting
- Lead scored 30-39 (qualified but not urgent)
- New signal (funding, hiring, news)
- Natural re-engagement opportunity
Quality Checklist
Before sending any follow-up email:
Personalization:
- Specific event context included
- Specific interaction details mentioned
- Company-specific research included
- Relevant case study/resource included
Tone & Persona:
- Tone matches persona (Exec = concise, Practitioner = tactical, VC = vision-led)
- Language appropriate for role
- No generic phrases
- Value-forward, not sales-y
Structure:
- Clear hook (event context)
- Value prop (relevant to them)
- Social proof (case study)
- Clear CTA
Qualification:
- ICP check passed
- Qualification signals captured
- Score calculated (if engaged)
- Handoff ready (if qualified)
Analytics & Optimization
Track These Metrics
Engagement Metrics:
- Open rate by segment (Booth Visitor, Panelist, etc.)
- Click rate by persona (Executive, Practitioner, VC)
- Reply rate by touch (Touch 1, 2, 3, etc.)
- Response time by segment
Conversion Metrics:
- Meeting booked rate by segment
- Qualification score by segment
- Handoff to AE rate
- Pipeline created from events
Quality Metrics:
- Average qualification score
- Best performing templates
- Best performing personas
- Best performing segments
Optimization Playbook
What Worked:
- Document winning templates
- Document best-performing segments
- Document best timing
- Document best personas
What Didn’t Work:
- Document poor performers
- Document anti-patterns
- Document what to avoid
A/B Testing Ideas:
- Subject line variations
- Tone variations (formal vs. casual)
- CTA variations (calendar link vs. email reply)
- Resource sharing (case study vs. deck vs. blog post)
Last Updated: 2025-01-16 Next Review: [Date]