Create pre-event account briefs for every scheduled booth meeting

Export scheduled meetings from your event calendar or CRM into a working sheet. Work in hubspot and google docs and capture the concrete operating details: source links, buyer context, audience, claims, proof points, owner, review status, and the final deliverable link. Keep the work narrow: complete step 1, record the decision or asset created, and avoid changing unrelated parts of the workflow. Before moving on, check that the handoff is tied to the right account or record and the owner knows the next action; the expected handoff is A clean meeting roster with account, attendee, owner, and meeting-type fields.

Review each account in HubSpot and capture lifecycle stage, open opportunities, past meetings, prior objections, current owner, relevant campaigns, and recent engagement. Work in hubspot and capture the concrete operating details: source links, buyer context, audience, claims, proof points, owner, review status, and the final deliverable link. Keep the work narrow: complete step 2, record the decision or asset created, and avoid changing unrelated parts of the workflow. Before moving on, check that the handoff is tied to the right account or record and the owner knows the next action; the expected handoff is CRM context notes for every scheduled account meeting.

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. Work in perplexity and linkedin sales navigator and capture the concrete operating details: source links, buyer context, audience, claims, proof points, owner, review status, and the final deliverable link. If an AI assistant is involved, give it the source inputs and the exact structure you want back instead of asking for a broad summary. Before moving on, check that the handoff is tied to the right account or record and the owner knows the next action; the expected handoff is Recent account context that can shape meeting angles and questions.

Use Claude to synthesize CRM history, attendee role, company context, and event goals into one-page briefs. Work in claude and google docs and capture the concrete operating details: source links, buyer context, audience, claims, proof points, owner, review status, and the final deliverable link. When you use the prompt template attached to this step, paste the real source material, name the expected output sections, and ask the model to flag uncertainty instead of filling gaps. Before moving on, check that the prompt includes the actual inputs, the requested output format, and clear rules against invented facts; the expected handoff is Rep-ready one-page briefing document for each scheduled meeting.

For each attendee, use Claude to generate questions based on their title and likely priorities. Work in claude and linkedin sales navigator and capture the concrete operating details: source links, buyer context, audience, claims, proof points, owner, review status, and the final deliverable link. When you use the prompt template attached to this step, paste the real source material, name the expected output sections, and ask the model to flag uncertainty instead of filling gaps. Before moving on, check that the prompt includes the actual inputs, the requested output format, and clear rules against invented facts; the expected handoff is Role-specific meeting questions attached to each account brief.

Send each brief to the meeting owner for a quick review. Work in google docs and hubspot and capture the concrete operating details: source links, buyer context, audience, claims, proof points, owner, review status, and the final deliverable link. Keep the work narrow: complete step 6, record the decision or asset created, and avoid changing unrelated parts of the workflow. Before moving on, check that the handoff is tied to the right account or record and the owner knows the next action; the expected handoff is Approved pre-event briefs with owners aligned on meeting goals and next steps.

Use Claude to create a short note template for reps to complete immediately after each meeting. Work in claude, hubspot, and google docs and capture the concrete operating details: source links, buyer context, audience, claims, proof points, owner, review status, and the final deliverable link. When you use the prompt template attached to this step, paste the real source material, name the expected output sections, and ask the model to flag uncertainty instead of filling gaps. Before moving on, check that the handoff is tied to the right account or record and the owner knows the next action; the expected handoff is Standard post-meeting note template for consistent event follow-up data.

After the event, review whether briefed meetings produced better notes, clearer next steps, higher follow-up completion, or faster opportunity creation. Work in hubspot, google docs, and claude and capture the concrete operating details: source links, buyer context, audience, claims, proof points, owner, review status, and the final deliverable link. If an AI assistant is involved, give it the source inputs and the exact structure you want back instead of asking for a broad summary. Before moving on, check that the handoff is tied to the right account or record and the owner knows the next action; the expected handoff is Post-event briefing QA summary with improvements for the next field program.