Case study · Corporate event management

Turning past event targets into a prospecting system

The event ICP had not been defined precisely enough. Instead of inventing it from database filters, we worked backwards from events GoGather had already judged worth targeting.

Download detailed case study (PDF)PDF · 6 pages

Case study · Event intelligence

GoGather, full-service corporate event management.

~300 historical target events as the knowledge base
372 deduplicated campaign rows
The insight
The useful signal was “large company + the right kind of event” — which didn't exist as a field in a sales database
The method
Historical target events became training data: research shared traits, infer a precise event ICP, convert to research logic
Two paths
Host/organizer research and exhibitor-derived discovery needed separate workflows — hosting the event is the stronger commercial signal

The problem

Company size wasn't enough

There are thousands of large companies. Whether they run annual meetings, leadership summits, sales kickoffs, partner conferences, franchise or dealer conventions — and whether they organize or merely exhibit — did not exist as a clean field.

Production exposed the real problem

  • The first build was operationally correct but strategically under-specified: event search could be as broad as “events in San Francisco,” which encoded nothing about commercial relevance.
  • Automation cannot compensate for an underdefined ICP — internal discussion later described the first run as too close to “shooting blind.”
  • Roughly 190 duplicate or lower-priority rows were removed; 372 deduplicated event/account rows remained in that version of the working table.

What we built

The client's past judgment became the dataset

  1. Historical targets as training data~300 previously chosen target events, expanded to ~100 events for richer analysis: type, audience, format, attendance, duration.Define
  2. Reverse-engineer the event and company ICPMaterially larger businesses with hundreds to many thousands of employees, in manufacturing, construction, consumer, financial services and telecom.Qualify
  3. Approved universe into Clay1,000 approved ICP companies imported; the event-research prompt looked back ~24 months for evidence of relevant events.Contact
  4. Pilot first, then scaleFirst production test ran on a controlled 100-row subset: can the system reliably identify the right events, and how fast does it process?Contact
  5. Host and exhibitor pathsA company exhibiting at another company's conference points to the organizer as the more relevant prospect — the event itself became a discovery mechanism.Launch

~800 franchise companies were sourced into the same event-research workflow, adding franchise conventions and network-wide gatherings as another event behavior to detect. Emails were revalidated with Enrichly as leads moved through the Smartlead campaigns; LinkedIn activation ran through HeyReach.

The broader principle

Who have you already decided was worth targeting?

The accounts you selected, the opportunities you pursued, the events you cared about and the prospects your sales team approved can reveal a more precise ICP than another workshop of adjectives.

  • Right company: does it have the size, structure and characteristics of GoGather's historical customers and targets?
  • Right reason: is there evidence it organizes a relevant event — what kind, how large, how often, for whom?
  • Right people: who owns or influences the event inside that organization?
  • Right message: the event itself creates the reason; outreach references it only then.
Find companies behaving like the companies we know are right.
Next caseA technology consultancy: a qualification-first sales engine for private equity →

Related reading

A practical guide to the research and system-design decisions behind work like this.

Why industry filters are not enough to define your ICP

Let's discuss your GTM challenge.

A short, no-obligation introductory conversation.

Schedule a conversation