Best for
- B2B teams attending conferences and needing meetings before arrival
- Field marketers coordinating sales outreach across account owners
- Sales teams that want target-account meetings instead of booth traffic alone
Turn attendee lists, target accounts, speaker signals, and sales ownership into a focused pre-event meeting booking system with daily tracking.
Create an event meeting-booking war room with target account lists, outreach copy, calendar links, sales assignments, and live progress tracking.
Quick view
Check the audience, core tools, and access before you start the detailed steps.
Best for
Core tools
6 tools used across the workflow.
Access
Preview the open steps, then unlock the remaining implementation details and prompts.
Why this works
Event ROI is usually decided before the event starts. Waiting for booth scans creates random pipeline, while pre-event meeting booking focuses the team on known accounts, relevant hooks, and calendar commitments. This workflow turns events into a coordinated pipeline motion instead of a badge-scan gamble.
Expected results
Meeting pipeline
Tiered target account plan
The workflow focuses booking effort on accounts with clear event meeting value rather than random attendee outreach.
Coordination
One war room and scorecard
Sales, field marketing, and account owners work from the same target list, status, and meeting tracker.
Time saved
6-10 hours per event
Reusable scoring, outreach, owner mapping, and daily tracking reduce manual coordination before events.
Event ROI
More pre-booked meetings
Pre-event booking creates higher-intent conversations than relying only on booth scans and walk-up traffic.
Step-by-step workflow
The first 2 steps are open. Pro unlocks the remaining steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and implementation details.
1.5-2 hours
1.5-2 hours
Set up: In HubSpot, create a dedicated event campaign or view and define the event name, dates, location, meeting goal, eligible account regions, and booking window. Combine attendee, sponsor, speaker, exhibitor, target-account, open-opportunity, customer-expansion, and partner-nominated lists into a Google Sheets workbook using stable HubSpot account IDs.
Configuration: Add CRM owner, account stage, opportunity value, customer status, industry, region, recent engagement, relationship strength, event role, event relevance, and known attendance confidence. Preserve the original source and list type for every row so the team can trace why an account entered the war room.
Action: Deduplicate at the account level, flag multiple contacts and conflicting owners, and separate confirmed attendees from inferred or unverified event participants. Apply exclusions for do-not-contact, lost or disqualified accounts, unresolved customer escalations, overlapping active outreach, and accounts outside the event strategy.
Approval: Reconcile the final account count to the source lists and save an approved audience snapshot with the extraction date, owner, and unresolved data gaps.
A reconciled event account workbook with source traceability, ownership, stage, attendance confidence, relevance, exclusions, and an approved audience snapshot.
Separate confirmed attendance from likely attendance. The outreach angle and urgency should differ when the team only suspects an account will be at the event.
60-75 min
60-75 min
Inputs: Prepare the approved account snapshot with event context, account stage, opportunity or customer status, engagement, relationship strength, attendance confidence, strategic value, and available meeting offers. Define the priority tiers and any hard rules, such as open opportunities that require AE ownership or customer accounts that require CSM review.
Set up: Open Claude, start a new event-prioritization chat, and paste the prompt below into the main chat composer. Include the event brief, account dataset, meeting goals, tier definitions, ownership rules, available executives or specialists, meeting capacity, and exclusions as source inputs.
Action: Ask Claude to assign Must Book, Should Book, Nurture at Event, or Low Priority, with evidence, conversation angle, owner, CTA, meeting format, confidence, and risk. Copy the scored table into Google Sheets and save the Claude output or conversation link with the event files.
QA: Manually review every Must Book account, low-confidence score, strategic exception, and recommendation that conflicts with the CRM owner or current opportunity plan.
A human-reviewed event priority list with tier, evidence, angle, owner, CTA, format, confidence, and strategic exceptions.
Pro workflow preview
Previewing 2 of 8 steps
Get the remaining 6 steps, copy-paste prompts, pro tips, tool-by-tool setup guidance, and ongoing workflow and prompt releases.
$9/month
Add a capacity constraint to scoring. A Must Book tier with more accounts than the team can realistically meet is not a priority system.
Score these event accounts for pre-event meeting priority.
Source inputs:
- Event brief, dates, and objectives: {{event_context}}
- Approved account dataset: {{account_data}}
- Meeting goals and available offers: {{meeting_goals_and_offers}}
- Priority tier definitions: {{tier_definitions}}
- CRM ownership and customer-routing rules: {{ownership_rules}}
- Available executives, specialists, and meeting capacity: {{team_capacity}}
- Exclusions and sensitive-account rules: {{exclusions}}
For each account, return:
1. Priority tier: Must Book, Should Book, Nurture at Event, or Low Priority
2. Evidence supporting the tier
3. Attendance confidence
4. Best conversation angle
5. Recommended owner and collaborators
6. Meeting format or offer
7. Suggested CTA
8. Risk, sensitivity, or duplicate-outreach note
9. Confidence score
10. Human review required
Prioritize realistic meeting value and event fit, not company size alone. Respect account ownership and capacity constraints.Related workflows
Continue with workflows that share a similar GTM motion, category, or tool stack.
Build a campaign launch QA system with channel checks, tracking validation, CRM routing tests, approval gates, and a reusable launch checklist.
Create a weekly demand generation sprint plan that tells the team which accounts, channels, offers, and experiments to prioritize.
Create an expansion signal engine with account briefs, play recommendations, and approved outreach assets.