Skip to content

coreyhaines31/marketingskills / skills/events

events

Verified

When the user wants to plan, run, sponsor, or speak at events, or asks whether an event or booth is worth the money: webinars, conferences, booths, meetups, show-up rates, and follow-up into pipeline. For launches, see launch. For joint webinars, see co-marketing. For community programs, see community-marketing. For podcasts, see public-relations. For event emails, see emails.

FileKindSize
SKILL.mdskill md11.4 KB
evals/evals.jsonconfig10.9 KB
references/event-portfolio-strategy.mdmarkdown7.8 KB
references/speaking.mdmarkdown5.2 KB
references/sponsorship-roi.mdmarkdown6.1 KB
references/webinar-funnel.mdmarkdown8.0 KB

references/sponsorship-roi.md

View on GitHub
# Sponsorship & Exhibiting — Evaluate, Negotiate, Work the Floor, Follow Up

Sponsorships are the most expensive way to do event marketing and the easiest to waste. The discipline: treat every sponsorship as a paid-acquisition channel with a cost-per-qualified-meeting, and make it beat your alternatives or don't buy it.

## Should We Sponsor? (the evaluation)

Run this before looking at the prospectus pricing:

1. **Audience–ICP overlap, in absolute numbers.** Not "5,000 attendees" but *how many attendees are your buyer*. Ask organizers for the attendee breakdown by role/company type; check last year's attendee/speaker lists and social chatter. A 5,000-person event with 200 ICP attendees is a 200-person event for you.
2. **Do the meetings math backwards.** Realistic qualified conversations = a small fraction of ICP attendees (a well-worked booth might convert 10–20% of relevant walk-bys into real conversations — directional, varies wildly by event). Then: total cost (sponsorship + travel + staff time + booth build) ÷ expected qualified meetings = **cost per qualified meeting**. Compare against what a meeting costs you from outbound or ads. If the event is 3× your outbound cost with no strategic upside, pass.
3. **Strategic multipliers that justify a premium**: your exact buyers concentrated nowhere else, a category-defining event where absence is conspicuous (late-stage), or access you genuinely can't buy elsewhere (exec attendees who ignore cold outreach).
4. **The counterfactual check**: what would the same budget produce in your best-performing channel? Sponsorship must beat that, not zero.

Red flags in prospectuses: attendee counts without composition, "impressions" as the headline metric, leads defined as badge scans, and last year's sponsor logos heavy on companies that didn't return.

## Negotiation: The Prospectus Is a Starting Point

Sponsorship pricing is soft, especially inside 8 weeks. What to negotiate for (in rough order of value):

1. **A speaking or panel slot** — worth more than a bigger booth; stage time converts better than floor space (see [speaking.md](speaking.md)).
2. **Side-event rights** — permission/space to host a dinner, breakfast, or workshop for a curated list during the event.
3. **Attendee list reality check** — full lists are increasingly rare (privacy); negotiate for opt-in scans, the registration-page question, or sponsored-session registrant lists. Get what's actually deliverable in writing.
4. **Placement and timing** — booth position near traffic (coffee, entrances, main stage exit); demo-day timing if the event has one.
5. **Price** — last, after the package is right. Unsold inventory close to the date discounts heavily.

## The Side-Event Play (often better than the booth)

The highest-leverage move in field marketing: skip or downgrade the booth, and **host a curated dinner or breakfast adjacent to the conference**.

- 8–14 seats, hand-picked ICP attendees + a couple of magnetic guests (a respected practitioner draws acceptances)
- Invite via personal outreach 2–4 weeks out (→ **cold-email** for craft); "join 10 [role]s for dinner during [event]" converts far better than any booth pull
- No pitch. The host halo and the conversations are the product; follow-up carries the commercial weight
- Economics: a dinner typically costs a fraction of a mid-tier sponsorship and produces *deeper* meetings with *chosen* accounts. This is also the play when you can't afford (or aren't allowed) to sponsor at all — you don't need the event's permission for your own dinner across the street.

## Working the Booth (if you buy one)

- **Staff it with people who can qualify and demo**, not whoever was free. Two energetic people beat five tired ones; write a shift schedule — floor fatigue is real and visible.
- **A 30-second qualifying question** beats a pitch: "what does your team use for X today?" sorts buyers from swag collectors instantly. Have a graceful fast exit for non-ICP traffic.
- **Capture context, not just scans**: after every real conversation, 15 seconds of notes — what they said, what they care about, the agreed next step. Voice memo or CRM app, same-hour. This is the raw material of follow-up that converts; a bare badge scan is a name with amnesia.
- Demo stations for depth, one clear message on the booth itself (the category problem, not your feature list), and book-a-meeting QR that goes to a calendar, not a form.
- **Book meetings before the event** with target attendees — the booth is a venue for pre-booked meetings, not just a net for walk-bys.

## Follow-Up: Where the Sponsorship Is Won or Lost

- **24–48 hour SLA**, tiered:
  - **Hot** (real conversation, next step agreed): personal email referencing the conversation, calendar link, same or next day.
  - **Warm** (conversation, no commitment): personal note + one relevant asset matched to what they said.
  - **Scan-only**: one light "we were both at [event]" touch or nothing. Never dump scans into a sales sequence — it burns domain reputation and brand on people who don't remember you (→ **revops** for routing/scoring).
- Whoever worked the booth writes or reviews the follow-up — the context lives in their heads and their notes.
- Sequence the not-nows into nurture with event source tags (→ **emails**).

## Measuring the Sponsorship

- Log every touched contact with an event source tag; measure **qualified conversations → meetings → opportunities → pipeline → closed-won influenced**, on an influence window that matches your sales cycle (90 days is common for B2B; long cycles need longer windows).
- Report **cost per qualified meeting and cost per opportunity** against your other channels — this is the renewal decision for next year, made with data instead of vibes.
- Self-reported attribution ("met you at [event]") catches influence that source tags miss (→ **attribution**); badge-scan counts and booth traffic are activity, not outcomes — track for logistics, never report as results.
- Judge a first-time event against a discount: your team's first run of any event underperforms its potential. A promising-but-unprofitable first year is a redesign signal, not necessarily a no.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 323kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall