Create pre-event account briefs for every scheduled booth meeting

Export scheduled meetings from your event calendar or CRM into a working sheet. Include attendee name, title, company, meeting time, meeting owner, current account stage, event source, and any known reason they agreed to meet. Mark which meetings are customer, prospect, partner, analyst, or vendor conversations.

Review each account in HubSpot and capture lifecycle stage, open opportunities, past meetings, prior objections, current owner, relevant campaigns, and recent engagement. Keep the notes short. The brief should help the rep prepare, not recreate the entire CRM timeline.

Use Perplexity and LinkedIn Sales Navigator to gather recent company updates, hiring patterns, leadership changes, product launches, funding, expansion, regulatory pressure, or relevant industry news. Capture only items that could affect the meeting. Avoid padding the brief with generic company facts the rep can find in five seconds.

Use Claude to synthesize CRM history, attendee role, company context, and event goals into one-page briefs. Each brief should include account summary, why this meeting matters, likely priorities, recommended opening, 3 smart questions, relevant proof points, and next-step suggestion.

Create a one-page pre-event account brief for this scheduled meeting.

Event context:
{{event_context}}

Meeting details:
{{meeting_details}}

CRM history:
{{crm_history}}

Recent company context:
{{company_research}}

Our event offer or CTA:
{{event_offer}}

Output:
1. Account snapshot
2. Why this meeting matters
3. Likely business priorities
4. Recommended opening line
5. Three smart questions
6. Relevant proof point or customer story to mention
7. Risks or topics to avoid
8. Recommended next step after the meeting

Keep it concise enough to read in two minutes.

For each attendee, use Claude to generate questions based on their title and likely priorities. A VP should get strategic questions, a director should get operational questions, and a technical evaluator should get implementation questions. Add these to the brief so reps do not use the same discovery script with every person.

Generate role-specific questions for this event meeting.

Attendee:
{{attendee_name}}, {{title}}, {{company}}

Account context:
{{account_brief}}

Our event goal:
{{event_goal}}

Create:
- 2 strategic questions
- 2 operational questions
- 1 proof-seeking question
- 1 next-step question

Rules:
- Match the attendee's seniority
- Do not ask questions we should already know from public research
- Avoid generic discovery questions

Send each brief to the meeting owner for a quick review. Ask them to confirm account stage, sensitive topics, proof points, and desired next step. Make edits before the event and flag any meeting that needs executive support, partner support, or a technical expert present.

Use Claude to create a short note template for reps to complete immediately after each meeting. Include fields for meeting quality, pain discussed, objections, next step, follow-up asset, buying committee notes, and urgency. Put the template in Google Docs or HubSpot notes so post-event follow-up starts from clean data.

Create a post-event meeting note template for sales and field marketing.

Event type:
{{event_type}}

Meeting types:
{{meeting_types}}

Fields needed by sales and marketing:
{{required_fields}}

Output a short template with checkboxes and fill-in fields that captures:
1. Conversation summary
2. Pain or priority discussed
3. Objections
4. Buying committee notes
5. Follow-up asset needed
6. Agreed next step
7. Owner and due date

Keep it fast to complete in under three minutes.

After the event, review whether briefed meetings produced better notes, clearer next steps, higher follow-up completion, or faster opportunity creation. Ask reps which briefs were useful and which were too generic. Use that feedback to improve the next event briefing format.