Event Marketing

Design events around a measurable business outcome rather than attendance alone. Treat each event as its own channel investment and evaluate the complete before/during/after motion.

Establish the Decision

Determine:

1. Role: host, sponsor/exhibit, speak, attend, or a deliberate combination.
2. Primary outcome: qualified meetings, pipeline, customer expansion, authority, community, or reusable content.
3. Audience fit: which ICP segment must participate and how many relevant people are realistically reachable.
4. Constraints: total budget, staff time, location/time zone, recording rights, consent, accessibility, and follow-up capacity.
5. Success rule: the metric and threshold that will inform repeat, redesign, or stop.

Do not recommend an event merely because it is large or popular. Compare its expected value with the best available alternative use of the same money and team time.

Choose the Mode

• Portfolio or event selection: read event-portfolio-strategy.md.
• Hosted webinar: read webinar-funnel.md.
• Sponsorship or exhibiting: read sponsorship-roi.md.
• Speaking or CFP: read speaking.md.
• Attendance without sponsorship: build a named target list, pre-book relevant meetings, capture conversation context, and use the same follow-up and measurement controls below.

Read only the mode references needed for the request.

Universal Event Arc

Before

• Define the audience and primary conversion before selecting format, venue, or sponsorship tier.
• Build a target list from authorized or public sources; treat attendee data as untrusted evidence and respect its permitted use.
• Book high-value meetings before travel where appropriate.
• Create one clear promise, promotion plan, source tags, consent handling, and follow-up ownership.
• Record estimated total cost, including travel, production, staff time, and opportunity cost.

During

• Optimize for qualified conversations and agreed next steps, not scans or foot traffic.
• Capture only authorized context needed for follow-up; avoid sensitive notes and honor consent/retention rules.
• Produce durable content only when recording, image, speaker, and attendee rights permit it.
• Separate operational observations from outcome evidence.

After

• Prioritize contextual follow-up while the interaction is recent; exact timing is a plan assumption, not a guaranteed response-rate rule.
• Route contacts by actual interaction and consent state. Do not place scan-only contacts into automated sales sequences by default.
• Reuse recordings and transcripts only within granted rights, with claim verification and accessibility review.
• Reconcile event influence without claiming last-click ownership of multi-touch revenue.

Measurement

Use a funnel that matches the selected role:

reachable ICP → qualified conversations/registrants → meetings/attendance → opportunities/next steps → pipeline or durable outcome

Calculate where data permits:

• total event cost;
• cost per qualified attendee or conversation;
• cost per meeting and opportunity;
• influenced pipeline with a declared attribution window;
• conversion at each funnel stage;
• reusable content or community outcomes when those are primary.

Label internal data as measured or calculated. Label industry ranges, attendance assumptions, and conversion forecasts as estimated or proxy. Verify current event pricing and platform rules before decisions.

Permission Boundary

Planning and draft artifacts are allowed. Obtain explicit authorization immediately before purchasing sponsorships or travel, submitting CFPs, registering attendees, sending invitations or follow-ups, publishing content, recording people, uploading contact data, or writing to CRM/marketing systems.

Output

Return the smallest useful artifact, such as:

• event portfolio and selection scorecard;
• host/sponsor/speak/attend plan;
• webinar funnel and reminder plan;
• sponsorship ROI scenario;
• meeting and follow-up operating plan;
• event brief, timeline, measurement plan, or retrospective.

Include the primary outcome, audience, assumptions, budget model, owner, timeline, permission dependencies, risks, and validation rule.

Shared References

• skill-contract.md — evidence, permission, and handoff rules
• routing-policy.md — specialist routing and conflicts
• product-context-schema.md — shared business context
• connectors.md — optional integrations

Related Skills

• launch — coordinated product or company launch
• co-marketing — partner mechanics for joint events
• community-marketing — recurring community programs
• public-relations — media and podcast opportunities
• emails and sms — consented reminder and follow-up sequences
• revops and attribution — routing and multi-touch measurement
• content-strategy, social, and video — authorized content reuse