Event attendee prep

Purpose

At a conference, the useful question is not who registered but which accounts we want, who the buyer is there, and whether that person is actually in the room. A registration export answers none of this on its own. It has names, sometimes stale titles, and no account context. This skill turns the export into a short dossier the team can read on the way into the event.

When to use

• A registration or attendee list is available one to three days before a face-to-face event.
• A booth, dinner, or talk needs a target list.
• The team wants to know which of its existing accounts will be present.

Route elsewhere when:

• The question is the event's calendar, booking links, or personal plan. Use event-logistics-planning.
• The question is building the broader target list. Use prospect-list-building.
• The question is the account's full profile. Use account-research-brief.

Inputs

• The attendee export, with names, employers as entered, and titles as entered.
• Live access to the CRM, so account status is read now, not from an old export.
• The product's target segments and the decision-maker titles for the market.
• Any sponsor, speaker, or dinner lists that show who is present in which capacity.

Procedure

1. Map every registrant to a company. Use the employer field, then the email domain where available. Flag registrants who cannot be mapped rather than guessing.
2. Join against the live CRM. For each company, record its status: customer, open deal, closed-lost, prospect, or unknown. Read the CRM now. An export from last month can say a deal is open when it closed.
3. Verify each person. Confirm current title and employer for every person you plan to use. Registration data goes stale quickly, especially for people who have changed jobs recently. Drop anyone whose current role cannot be verified from the list of people to approach.
4. Size and qualify each company against the ICP: size, funding, segment, and any hard exclusions such as competitors or investors. Mark companies that fail as not worth pursuing.
5. Identify the buying committee for each account worth pursuing. Name the economic buyer, the day-to-day champion, and any other stakeholder whose title suggests a role in the decision. Write these by hand for each account. Do not auto-fill from titles alone.
6. Rank the accounts. Warm accounts first: existing customers with expansion potential, open deals with a person present, and any account with an existing relationship. Then new targets by fit.
7. Build the dossier as a short, readable document, one account per page. Each card states, in order:
   • the account and its status,
   • who the buyer is, and whether they are registered, present, or unknown,
   • one line on why this account matters now,
   • the opening line for the approach. A card must be readable in about five seconds.
8. Flag gaps. List any account where the buyer could not be confirmed and any person who could not be verified, so the team does not walk in on a wrong assumption.

Output

• A dossier: one account per page, ranked warm-first, each card readable in five seconds.
• A list of unmapped registrants and unverified people, with the reason for each.
• The CRM status of every account in the dossier, as read at the time of prep.

Quality bar

The CRM is read live, not from the export. Every person in the dossier has a verified current title and employer. The buying committee is written per account, not inferred from titles. Each card can be read in five seconds and says whether the buyer is in the room. Watch for stale deal status from an old export, unverified titles presented as current, and a dossier that lists every registrant instead of the accounts worth pursuing.