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/fulfillment-matrix-and-onboarding.md

View on GitHub
# Fulfillment matrix and sponsor onboarding

## The matrix shape

Rows = perks, columns = tiers (one column per sponsor once custom-negotiated deltas exist). Each cell carries a state: **promised** (quoted from the signed agreement) → **scheduled** (owner and date assigned) → **delivered** → **evidenced** (link, screenshot, or photo attached). This mirrors the checkmark tier table sponsors were sold from - same rows, but tracking delivery instead of price.

A flat perk list is the wrong shape: it loses the per-tier view, so an undelivered top-tier perk hides behind a wall of completed small ones.

## Two real row sets

**DevOpsDays Des Moines 2025** (sponsor page; the same structure recurs across that city's 2019-2025 editions - a standing per-edition template, not a one-off). Tiers Platinum $15,000 / Gold $6,500 / Lanyard $2,500 / Silver $2,000; rows checked off per tier:

- Included tickets (6 / 4 / 2 / 2)
- "Presented By" event branding (top tier)
- 3-5 minute welcome speech
- Logo on event slides, sized by tier (large / medium / small / small)
- Logo on the printed lanyard (Lanyard tier's exclusive surface)
- Logo on pre-event communication
- Acknowledgment at opening and closing ceremonies
- Full 96"×30" table, premium-located for the top tier
- Timed pitch to the audience
- Kickoff speech at the social event
- Roll-up banners at the social event

**DevOpsDays Graz 2026** (published sponsorship kit). Tiers Gold €4,000 / Silver €2,500 / Bronze €1,500 / Lanyard €1,500 / Swag Bag €1,500; line items in printed order:

- Guest tickets included
- Booth staff count
- 20% discount on additional tickets
- Booth (large / small / none)
- Main-stage banner (Gold)
- 3-minute on-stage pitch (Gold)
- Logo on rotating break slides (Gold)
- Logo in newsletter (all)
- Social-media announcement (all)
- Logo on event page (all)
- Swag-bag inserts (all)
- One tier-specific exclusive surface (logo on lanyard / logo on swag bag)

Use these as the vocabulary of realistic rows; build the actual matrix from what this event's agreements promised, not from either list.

## The published-cap rule

Graz publishes hard caps per tier - Gold 3, Silver 6, Bronze 20, Lanyard 1, Swag Bag 1. The matrix must honor every published cap: never schedule more exclusive surfaces, premium placements, or pitch slots than the prospectus disclosed. An oversold exclusive surface is a promise two sponsors hold at once, and delivering it to one breaks it for the other in public.

## The payment gate

Des Moines pairs its live tier inventory ("6 of 11" Gold remaining) with a payment link or invoice-request address per tier: benefits exist only after fees are paid in full. Apply it as a column in the tracker - invoiced date, paid date - and a rule: no cell leaves **promised** while payment is open. Communicate the hold through the liaison ("your booth assignment and logo placements are queued behind the invoice"), never as a surprise at setup time.

## Phased onboarding checklist

The phases fit the event context; the SaaS content (health scores, usage reviews) does not - do not import it.

1. **Welcome / kickoff** - within days of payment: confirm the liaison on both sides, restate the perk list from their matrix column, send the asset checklist with deadlines, and offer the kickoff call where the menu promotes it.
2. **Asset collection** - chase against the deadline table below; validate formats on receipt, not at the printer.
3. **Pre-event delivery** - place logos, mentions, codes as assets land; evidence each cell.
4. **Day-of handoff** - the logistics brief goes out (see the day-of reference), booth and schedule confirmed, on-site contact named.

## Asset intake list

What sponsors actually supply, per perk sold (from MLH organizer guide and Des Moines staffing):

- Logo - vector plus the raster formats each surface needs; the printed surfaces set the earliest deadline.
- Company blurb for the event page and program.
- Job posts, where a recruiting perk was sold.
- Workshop title, abstract, and speaker - scheduled Friday/Saturday, not the final day (attendees are too exhausted by then except for pitching/submission sessions).
- Sponsored prize-track definition, kept broad enough not to narrow participant creativity, prize value matched to the organizer's own prizes.
- On-site representative names - with this guidance: send "somebody that can tell your story and participate with the community," not a sales rep.
- Booth equipment and power needs, so venue expectations are set before arrival.

## Deadline table shape

One row per asset: asset → format → needed by → what drives the deadline (printer date, program lock, newsletter send). Sort by date; the top row is the fulfillment clock. Share the sponsor-facing subset in the welcome email so the deadline is theirs too.
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