events-and-field-marketing
GitHub用于规划和执行能产生销售线索的市场活动(会议、展会、网络研讨会等),评估投入产出比,制定赞助策略及后续跟进流程,确保活动支出转化为实际业务价值。
Trigger Scenarios
Install
npx skills add cbrock84/headcount --skill events-and-field-marketing -g -y
SKILL.md
Frontmatter
{
"name": "events-and-field-marketing",
"description": "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."
}
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.
Decide before you sponsor
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:
- Who is actually there. Attendee seniority and function, not the headline number. A ten-thousand-person event where forty of your buyers attend is a forty-person event.
- What the goal is, and pick one: pipeline from new accounts, advancing deals already open, 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.
- Total cost. Sponsorship is often under half. Add booth build, shipping, travel, staff time out 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.
Follow-up is where the money is lost
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.
Webinars and digital formats
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.
Measure with the attribution honesty the channel needs
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.
Tooling
Event and webinar platforms, roughly by scale: Luma or Zoom Webinars for small and recurring formats; Goldcast, ON24 or Bizzabo where the recording and the follow-up data matter; Cvent for large multi-track events, and similar.
Lead capture at physical events: the organizer's badge scanning, or your own — and whichever it is, test the export path into the CRM before the event rather than discovering the format afterward.
The tooling that actually decides the outcome is the follow-up sequence, which lives in your lifecycle platform and should be built before the event opens.
Never
- Sponsor an event without a single stated goal.
- Report badge scans as leads.
- Leave follow-up ownership undecided until after the event.
- Claim event-influenced revenue without stating the attribution assumption.
Version History
- d58a7ee Current 2026-09-02 21:07


