본문으로 건너뛰기
cccskills
무료GitHub에 공개

events-and-field-marketing

Plan conferences, trade shows, webinars, and field programs around a clear business goal. Weigh audience fit and full costs, prepare follow-up, and measure direct and influenced pipeline with stated assumptions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

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.

실행 점수 미검증

설치 방법 보기

이럴 때 유용합니다

  • Deciding whether to sponsor an event
  • Planning a conference booth or webinar
  • Designing timely follow-up for attendees
  • Measuring event impact on pipeline

포함된 파일(2)

  • SKILL.md4.2 KB
  • references/sources.md894 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Design and review access so people and services have appropriate permissions. Use it to plan roles, audit accounts, reduce always-on admin rights, manage credentials, handle departures, and improve sign-in with single sign-on or multi-factor authentication.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing who can access each system
  • Planning role based permissions
  • Removing access during offboarding
cbrock84/headcount2.1천2026년 10월 19일 업데이트

Plan account-based marketing for a defined set of companies. Assess whether the economics fit, prioritize accounts, map the people involved in buying, coordinate outreach across sales and marketing, and track account movement through the pipeline.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Assess whether account-based marketing fits the business
  • Build and prioritize a target account list
  • Map buying roles within target companies
cbrock84/headcount2.1천2026년 10월 19일 업데이트

Improve the path from signup to a new user’s first meaningful result. Define the action that signals real value, refine signup and onboarding, and diagnose where people drop off so more accounts become active users sooner.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Designing or fixing signup and onboarding
  • Finding why signups do not become active users
  • Reducing time to a first meaningful result
cbrock84/headcount2.1천2026년 10월 19일 업데이트

Design a repository’s multi-agent structure by assigning exclusive file areas, defining builder and reviewer roles, and checking ownership rules with a CI script. Use it to divide work, prevent overlapping edits, and decide whether another agent is needed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Dividing repository work among agents
  • Defining agent roles and file ownership
  • Auditing overlapping agent responsibilities
cbrock84/headcount2.1천2026년 10월 19일 업데이트

Use this skill to define an AI system’s intended use, evaluate its errors across user groups, plan monitoring and meaningful human review, and document its limits. It supports deployment and retirement decisions, especially when AI could affect consequential outcomes for people.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Set evaluation criteria before deployment
  • Investigate model behavior drift
  • Plan monitoring and human review
cbrock84/headcount2.1천2026년 10월 19일 업데이트

Use this skill to analyze markets, map competitors, assess trends, and compare strategic options such as market entry or build versus buy. It produces a cited research brief that separates established facts from inferences and estimates, states confidence, and connects findings to a decision.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Sizing a market or analyzing an industry
  • Mapping competitors and buyer differences
  • Comparing market entry or build versus buy
cbrock84/headcount2.1천2026년 10월 19일 업데이트

cbrock84의 스킬 모두 보기

이 스킬의 문제 신고