Claude Skill

events-and-field-marketing

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

LLM Mart · 0 points · 16 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download cbrock84-headcount-plugins_marketing_skills_events-and-field-marketing-98d1c17.zip · 2 KB
Part of cbrock84/headcount — 160 skills

Install

skills CLI npx skills add https://github.com/cbrock84/headcount/tree/main/plugins/marketing/skills/events-and-field-marketing
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install cbrock84-headcount@llmmart
Git git clone https://github.com/cbrock84/headcount.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole cbrock84/headcount collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

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.
Files (headcount)
  • references
    • sources.md 894 B
      # Sources — `marketing:events-and-field-marketing`
      
      <!-- Generated by scripts/build-sources.py from sources/*.toml. Do not edit. -->
      
      Check these before answering on anything they cover, and cite what you used. The use note on each one is binding: most of what a professional cites is free to read and not free to reproduce.
      
      ## 2010 ADA Standards for Accessible Design
      
      US Department of Justice · US · public domain (US government) — quote freely
      
      <https://www.ada.gov/law-and-regs/design-standards/2010-stds/>
      
      **Authoritative for:** The enforceable dimensional requirements for an accessible facility — routes, clearances, reach ranges, restrooms, seating. Applies to a workplace and to an event venue alike.
      
      ---
      
      Sources are maintained in `sources/` upstream, not here. If one is wrong, out of date, or missing, fix it there — this file is regenerated and an edit to it is lost.
      
  • SKILL.md 4.2 KB
    ---
    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`.
    
    ## Sources
    
    `references/sources.md` in this skill lists the outside authorities that settle the questions
    here — what each one is authoritative for, and what you may do with it. Check them before
    answering on anything they cover, and cite what you used. Most are free to read and not free
    to reproduce; the use note on each is binding.
    
    ## 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.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related