Score before generating
Research and personalization effort is spent on the most relevant accounts first. Generation follows qualification instead of becoming a substitute for it.
Event outreach automation
A time-boxed pipeline that turns an event attendee graph into prioritized, owned and personalized outreach.
automation · in use
System designer and builder · Updated Aug 2026
- Automation
- GTM operations
- Enrichment
- Workflow design
01 · Problem
Conference sponsorship produces a short-lived list of names but not the context, prioritization or ownership needed for timely follow-up.
02 · System
The workflow reconstructs the attendee graph, enriches and scores it against the target profile, then drafts and routes personalized sequences with explicit ownership and follow-up.
03 · Outcome
12 qualified meetings from one event; affiliate channels produced 18 leads in month one, while earlier outreach automation increased prospect coverage by 20%.
Context
The useful window after an event is short. A manual sequence of list cleanup, research, routing and copywriting consumes most of that window before the first relevant message is sent.
The system therefore had to optimize for elapsed time and accountable handoffs, not merely generate more copy.
Architecture
- 01Attendee graph reconstruction from available event data
- 02Identity resolution and account enrichment
- 03ICP scoring with explicit qualification rules
- 04LLM-assisted message drafting grounded in event and account context
- 05CRM ownership, routing and follow-up checkpoints
- 06Campaign reporting tied back to qualified conversations
Decisions & trade-offs
Make ownership part of the pipeline
A contact without a next action and a named owner is treated as unfinished data, not a completed enrichment record.
Measure conversations, not output
The system is judged by qualified meetings and usable coverage rather than the number of generated messages.
Evidence
- 12 qualified meetings from a single event
- 18 leads from affiliate channels in the first month
- 20% improvement in prospect coverage from earlier outreach automation
What this taught me
- The bottleneck in outbound work is usually coordination and context assembly, not prose generation.
- An agent becomes operationally useful only when its output has a destination, an owner and a feedback signal.
Follow the system
Connected work is resolved from the shared content graph.