Every Conference Lead Has a 48-Hour Window
Every warm lead from a conference has a 48-hour window. The teams that convert conference contacts into pipeline are the ones who follow up with all 80 people – personalized, multi-channel, within two days. Not just the 12 they remembered to email on the flight home.
Most conference follow-up dies in a spreadsheet. You get back, dump the contacts, and start manually researching each one. By Thursday, half the list is stale.
Claude handles the entire pipeline – enriching every contact, scoring them against your ICP, writing personalized emails, and loading sequences into your outreach tools – while you're still at the hotel.
How Claude Helps You
Claude takes your raw conference contact list – messy CSVs from badge scanners, business card photos, a notes app full of names – and turns it into a scored, personalized, multi-channel outreach campaign ready to send.
No manual research. No copy-paste personalization. No contacts falling through the cracks.
To do this, Claude uses four skills:
- lead-qualification – batch-enriches contacts via LinkedIn and scores each one against your ICP with confidence ratings
- email-drafting – writes high-converting cold emails using personalization frameworks matched to each contact's context
- cold-email-outreach – orchestrates the full email campaign: sequence design, timing, and loading into your outreach tool
- linkedin-outreach – builds personalized LinkedIn connection requests and follow-up sequences for high-priority contacts
You provide the contact list and your ICP criteria. Claude does the rest.
The Workflow
Step 1: Import your conference contacts
Drop in whatever you have. Badge scanner CSV, a spreadsheet of names and companies, photos of business cards – Claude parses the messy data and normalizes it into a clean contact list.
Name, company, title, email, LinkedIn URL. If LinkedIn URLs are missing, Claude searches for them.
You walk away from a 3-day conference with 60–100 contacts in various formats. Within minutes, they are all in one structured list ready for enrichment.
Step 2: Enrich and score every contact
Using the lead-qualification skill, Claude enriches each contact with data pulled from their LinkedIn profile:
- Current role, tenure, and seniority level
- Company size, funding stage, and industry
- Recent LinkedIn activity and posting topics
- Tech stack signals and hiring patterns
Then it scores every contact against your ICP criteria. Each person gets a qualified or disqualified verdict with a confidence score and reasoning – not just a number, but an explanation of why they are or are not a fit.
A VP of Sales at a Series B SaaS company who posted about outbound last week scores differently than an intern you met at the happy hour.
Step 3: Write personalized follow-up emails
Personalized outreach at this scale is where most teams give up. Writing 50+ unique emails is a full day of work – or it was.
The email-drafting skill generates a custom email for each qualified contact using structured frameworks like Signal-Proof-Ask. Each email references:
- Their specific role and what they likely care about
- A relevant proof point matched to their company profile
- A conference-specific hook that makes the email feel timely, not templated
Personalization happens at the deep tier – not just swapping in a first name, but tailoring the angle based on enrichment data.
A CTO gets a technical capabilities email. A Head of Growth gets an ROI-focused one.
Step 4: Build and load your email sequence
Raw emails become a full campaign. Using the cold-email-outreach skill, Claude assembles a 3-touch email sequence for each contact:
- Touch 1: Personalized first email within 48 hours of the event
- Touch 2: Value-add follow-up 3 days later with a case study or relevant resource
- Touch 3: Soft break-up email 5 days after that
The entire sequence loads directly into your outreach tool – Smartlead, Instantly, Lemlist, Apollo, or a CSV export for any other platform.
Sending schedules, throttling, and warmup settings are configured automatically if you are using Smartlead.
Step 5: Launch parallel LinkedIn outreach
Your highest-priority contacts deserve a second channel. The linkedin-outreach skill builds a personalized LinkedIn sequence for your top-scored leads:
- A connection request referencing the conference (kept under LinkedIn's 300-character limit)
- Two follow-up messages spaced across the next week
- An optional InMail for contacts you could not connect with
Sequences export to Dripify, Expandi, PhantomBuster, or CSV.
Combined with the email campaign, your top contacts hear from you on two channels within the first week – without you writing a single message manually.
Step 6: Results land in your tools
By the time this workflow finishes, your outreach tools are loaded and campaigns are ready to send.
Email sequences sit in your outreach platform. LinkedIn sequences are queued in your automation tool. Every contact – qualified or not – is logged with enrichment data and scores, ready to sync back to your CRM for long-term tracking.
What You Walk Away With
- A scored contact list – every conference contact enriched with LinkedIn data and ICP-scored with confidence ratings and reasoning
- 50+ personalized emails – unique first emails for every qualified contact, not mail-merged templates
- A 3-touch email sequence – loaded into your outreach tool, timed for the 48-hour post-conference window
- LinkedIn sequences for top contacts – connection requests and follow-ups exported and ready to launch
- A reusable qualification prompt – your ICP criteria saved so the next conference takes half the setup time
Why This Matters
The conversion window for conference leads closes fast. Teams that follow up with personalized outreach within 48 hours see 3–4x the reply rates of those who wait a week.
Claude Code, Codex, and Goose make it possible to follow up with every single contact – not just the ones you had time to research manually.
The conference becomes a pipeline event, not a networking event that slowly fades from memory.
Build your conference follow-up workflow with Gooseworks