Plans and runs events that produce pipeline — conferences, trade shows, webinars, field programs, and measuring whether any of it worked. Use this to decide whether to sponsor an event, plan a conference presence or webinar, design a field program, or work out why event spend is not producing pipeline.
npx skills add https://github.com/cbrock84/headcount --skill events-and-field-marketing
Events are the most expensive marketing channel per contact and the easiest to spend badly on,
because the outputs — booth traffic, badge scans, attendance — feel like results and are not.
The question is never "should we be at this event" but "what specifically do we expect, and what is
that worth." Answer three things first:
ten-thousand-person event where forty of your buyers attend is a forty-person event.
customer retention and advocacy, or category presence. These need different booths, different
staff, and different follow-up, and an event asked to do all four does none.
of the field, and the content produced for it. The fully loaded figure changes decisions.
Small, self-hosted, targeted formats — a dinner for fifteen right accounts, a focused workshop —
routinely outperform large sponsorships per dollar for enterprise pipeline, and are unglamorous
enough that they get proposed rarely.
Most event spend is wasted after the event, not during it. A scanned badge is not a lead, and the
value decays in days.
Agree before the event: who follows up, in what timeframe, with what message, and how those contacts
are treated differently from inbound. Route it through revenue:revenue-operations so the tracking
exists in advance, and hand the sequence to demand-generation:lifecycle-messaging.
Score contacts honestly. Everyone who took a branded item is not a lead, and passing them to sales
as if they were is how sales stops working the source at all.
Same discipline, different economics. Registration is not attendance and attendance is not interest;
the segment worth pursuing is people who stayed and asked something.
The recording usually outperforms the live event over time, so plan the content as a durable asset —
marketing:content-strategy and marketing:video-content — rather than as a one-time performance.
Events are structurally hard to attribute: they influence deals that close months later through
paths no model captures cleanly. Overclaiming destroys the channel's credibility; refusing to
measure destroys its funding.
Track influenced pipeline with the assumption stated, alongside the honest direct-source number, and
compare cost per opportunity against your other channels through
demand-generation:marketing-analytics.
Take cbrock84/events-and-field-marketing from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.