Event Lead Intelligence
Post-event follow-up, industrialized — AI research agents that turn booth scans into rep-ready briefs, and the live workspace reps actually work them in. Every scan researched before the team's flight lands.
Every badge scan is a promise somebody forgets.
The booth does its job: hundreds of scans, real conversations, warm intent. Then the event ends and the scans land in a CSV — where the warmth goes to die. Follow-up trickles out weeks later, generic and cold, written by reps who can't possibly research a thousand strangers by hand.
The math never worked: fifteen minutes of research per lead times a thousand leads is a quarter of a work-year. So the research simply didn't happen.
Why agents, and why briefs.
The decisions that shaped the system:
From a thousand scans to a worked queue.
Scan export in; an agent fleet researching, enriching, and composing in parallel; briefs landing in a Redis-backed workspace where reps pick up, work, and close the loop.
What it's made of. What it talks to.
Next.js + TypeScript, a parallel agent pipeline on Claude, Redis-backed live state, deployed on Vercel.
// One agent per lead — a bad lead can't poison its neighbors, and failures retry alone. const queue = [...scans]; // every scan from 3 days, not the top 50 const workers = Array.from({ length: CONCURRENCY }, async () => { while (queue.length) { const lead = queue.pop()!; try { const research = await agent.research(lead); // company, role, why-now — with citations const brief = await agent.compose(lead, research); await redis.hset(`brief:${lead.email}`, brief); // lands in the live workspace } catch (err) { await retries.push({ lead, attempt: att(lead) + 1 }); // alone, capped, logged } } }); await Promise.all(workers);
From scan to worked lead.
Captures from the working demo — a rep-ready brief, the workspace queue, and the event report. A short walkthrough of one lead's journey lands here next.



Follow-up that lands while it matters.
Every scan researched before the flight home — not the top fifty, all of them. Notes that read like someone was listening — because the brief remembers the booth conversation the rep can't. A queue that ends — assigned, worked, done; no CSV graveyard.
Read the briefs yourself.
The full working shell on synthetic event data — the queue, the briefs, the board. Access is by code (it rotates per conversation — if we're talking, you have one; if not, transmit and I'll send it).
ENTER ACCESS CODE →LIVE DEMO · ACCESS IS CODE-GATED

