Skip to content

samber/dev-event-organizer-skills / skills/event-sponsor-fulfillment

event-sponsor-fulfillment

Verified

Deliver everything a signed event sponsor was promised, from countersignature to the post-event report - the tier-by-perk fulfillment matrix built from the signed agreement, payment-gated perk release, sponsor asset collection against deadlines, the day-of sponsor experience (setup, shipping, staffing, A/V), consented lead capture such as an opt-in raffle, and the post-event sponsor report that anchors the renewal ask. Use whenever the user mentions onboarding a signed sponsor, tracking sponsor deliverables, booth logistics, sponsor logo placement, or a post-event sponsor report or recap - even without saying "fulfillment". Do NOT use for the sale - use samber/dev-event-organizer-skills@event-sponsor-outreach; use samber/dev-event-organizer-skills@event-sponsor-renewal for the renewal ask.

references/day-of-logistics.md

View on GitHub
# Day-of sponsor logistics

## The answered sponsor FAQ

A real, filled-in sponsor FAQ from DevOpsDays Des Moines (2025 sponsor page; the same table recurs across that city's editions since 2019). Six questions every sponsor asks, with that event's answers as a realistic baseline:

| Question                                      | Des Moines answer                                                                        |
| --------------------------------------------- | ---------------------------------------------------------------------------------------- |
| What dates/times can we set up and tear down? | An hour before registration on the first day                                             |
| How do we ship to the venue?                  | Contact the organizers directly                                                          |
| Whom should we send?                          | "Somebody that can tell your story and participate with the community" - not a sales rep |
| Electricity - how much, any fees?             | Contact organizers to set expectations with venue staff                                  |
| WiFi - how much, any fees?                    | Included at the event, no additional cost                                                |
| Additional A/V equipment?                     | Contact organizers                                                                       |

Two instructions fall out of that table:

- **Send the answered version before sponsors ask.** Fill in this table for your own event and venue, and put it in the day-of brief. A sponsor chasing setup times two days out reads the event as poorly run.
- **Schedule the contact, don't assume self-service.** Every non-trivial answer above routes to a direct organizer email, not a published doc - shipping, power, and A/V are venue-specific negotiations. Put "logistics call or thread with each sponsor's on-site lead" on the fulfillment calendar rather than waiting for the questions.

## The day-of brief

One document per sponsor, sent about a week out:

- The answered FAQ.
- Their booth location and size.
- Their staff badge count and pickup.
- Their scheduled slots (pitch time, workshop, raffle draw, social-event speech).
- The on-site organizer contact's phone.
- Teardown rules.

Walk the booths at doors-open with the matrix in hand - premium placement, banners, and signage are cells to evidence with a photo.

## Consented raffle mechanics

The opt-in lead-capture mechanic (Des Moines sponsor page): sponsors "offer raffle prizes to capture attendee contact information in exchange for a chance to win" - the attendee volunteers their own info to a specific sponsor; organizers schedule the raffle time and take winner photos.

Run it as a delivered perk:

1. Confirm the prize and the entry method (a fishbowl, a form at the booth) with the sponsor beforehand.
2. State plainly at the point of entry what is collected and that it goes to that named sponsor - entry is the consent, so what is consented to must be visible.
3. Schedule the draw where the agenda has attention (a break, closing), announce it, photograph the winner - the photo is report material.
4. Hand the entries to that one sponsor only, and delete the organizer's copy after hand-off. The entries never merge into any organizer list.
5. Evidence the cell: draw time, entry count, hand-off confirmation.

The raffle is distinct from and never substitutable for an attendee list. If a sponsor pushes to widen it ("just add a newsletter checkbox for us"), that is the deleted bulk-capture rung wearing a costume; the answer is the aggregate-demographics document, not a broader capture.

## Staffing guidance to pass along

Forward this framing to every sponsor when booth staff names are collected: the community expects participants, not a pitch. A sponsor rep who attends talks and joins conversations outperforms a badge-hunting one on the sponsor's own recruiting and product-feedback goals - and the guidance coming from the organizer, in writing, gives the sponsor's event lead cover to pick the right person internally.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall