Start with the decision, not the directory
Write down what a commercially useful event looks like for your team. Then define the customer you want, the customer you do not want, and the business objective. Only after that should you collect company names from an event ecosystem.
Define the ideal customer and exclusions
Describe the offering, preferred company type, size or segment if it actually changes fit, and exclusions. Exclusions matter. A vendor standing next to your booth is still a vendor.
Separate fit from event association
A company can appear in an event directory and still be a poor account. Event association is not individual attendance and is not buying intent. Treat it as context, then test the account against your buyer definition.
Gather permitted evidence
Use publicly available information and sources you have the right to use. Record the source and the date you reviewed it. If you cannot point to a source, do not present the statement as a fact.
Evaluate fit, unknowns, function, and priority
For each account, write: why it fits or does not; what is unknown; which business function to approach; and a qualitative priority such as high fit, review, or deprioritize. Avoid unexplained precision scores.
Worked illustration
The following rows match the public Hawk example. Illustrative example. Fictional companies; not verified research.
Example carrier A is prioritized because the described business matches a claims-workflow buyer. Example administrator B stays in review because the segment fits but more operating detail would be needed in real work. Example vendor C is deprioritized because it is a solution provider, not the customer.
Checklist
- Buyer definition and exclusions are written down.
- Event directory names are treated as candidates, not the finished list.
- Each kept account has fit reasoning and a source date.
- Unknowns are listed instead of filled with guesses.
- A function is recommended without inventing a named contact.
- At least one attractive but poor-fit account is explicitly deprioritized.
- Someone is assigned to refresh the list after the event.
Review and refresh
A list decays. After outreach or after the event, correct errors and retire stale event claims. If Hawk published a factual error, use the request form as the correction channel.
Related questions
Is an exhibitor list enough?
It is a starting inventory. It does not tell you which companies match your offer.
Should every account include a contact?
Only when the source and permitted use support it. Function-level direction is still useful without a name.
Continue to What You Get, the example map, or ITC Vegas 2026.