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/post-event-report.md

View on GitHub
# The post-event sponsor report

The data-backed post-event report is the highest-leverage renewal action available to an organizer - "sell the logo and you get a one-year sponsor; sell the data and you get a partner". Sponsors renew on demonstrated value, and they decide on a budget cycle: a report that waits for next year's planning anchors nothing. Every number carries its method line (rules per metric in the metric-sourcing reference). Every figure below is invented, to show shape only.

## Contents

- Deadline: two stages
- Stage 1: the recap email (within 72 hours)
- Stage 2: the short form or full metrics report (within 10 business days)
- Short form
- The renew / renegotiate / drop read
- Fill rules
- Negative example

## Deadline: two stages

Published deadlines range from 24 hours to 60 days, and no study links any of them to renewal. The two-stage default is judged, not measured:

- **Within 72 hours** - the recap email (MLH organizer guide: thank-you, key numbers, highlights, best photos). Recordings and survey data do not exist yet; don't wait for them.
- **Within 10 business days** - the short form or the full report, as the report menu picks; never the recap alone for a sponsor the renewal motion will ask. Practitioner advice aims this window before the sponsor's own post-event review, where renewal budgets often get decided.
- Any miss the sponsor has not heard about goes out before either: at the top of the recap email, or the day it is discovered.

## Stage 1: the recap email (within 72 hours)

```
Subject: [Event] [edition] - thank you, first numbers, and what comes next

Hi [champion first name, or budget owner if the champion left],

[If anything was missed and they have not heard yet - first, one sentence each:
"One thing you should hear from me first: [what happened, when]. To make it
good, [make-good in kind], done by [date]."]

Thank you for [one concrete thing their sponsorship made possible].

First numbers (full figures in the report by [date]):
- Checked-in attendees: [n], excluding sponsor and organizer staff ([n] registered;
  method: unique badge pickup)
- [Their headline outcome, against what they said success looks like:
  "Workshop: 46 attendees (door count at minute 5)"]
- [Contact hand-off, only where attendees opted in to this sponsor by name:
  "Your raffle opt-ins (n unique) are in [secure transfer] until [date]; you hold
  them from receipt, and we delete our copy on [date]."]

[3-5 photos: their booth, their speaker, their logo in place]

[Name, role, direct line]
```

## Stage 2: the short form or full metrics report (within 10 business days)

One document per sponsor. GolfStatus's, Sponsorship Collective's and HeySummit's published sponsor report templates use this same summary-perks-audience-outcomes-photos-next-edition shape.

### 1. Summary (half a page)

- What their sponsorship made possible, concretely ("your workshop filled the largest room we had").
- Their stated objective (Q5) and a one-line verdict: met / partly met / not measurable by us (why) / not set at sale.
- Delivered: [x] of [y] contracted items; misses named with their make-good.

### 2. Delivered vs contracted

Their matrix column, quoted from the signed agreement.

| # | Contracted item | Status | Evidence | Note |
| - | --------------- | ------ | -------- | ---- |
| 1 | Logo on lanyard | Delivered | photo `row01-lanyard.jpg` | |
| 2 | 60-min workshop slot | Delivered | program link | |
| 3 | Logo on venue screen loop | Partial | loop log | off 13:00-17:30; make-good row 9 |
| 9 | Make-good: recording bumper + recap-post logo | Delivered | links | added after row 3 |

Status values: delivered, over-delivered, partial, missed. Sponsorship Collective's template adds a value column (what was charged per item vs what was delivered); carry it when the extra row work is worth it to the relationship.

### 3. The audience, in aggregate

- Registered / checked in / peak concurrent, as three numbers; sponsor and organizer staff excluded from every prospect count.
- Role, seniority, company size, region, each with its per-field response rate. Never a name, never a list.
- Online events: unique session viewers and virtual-booth visitors from the platform export.

### 4. Their results, labeled for what each can and can't prove

Only the rows they bought. Rows nobody counted read "not captured this edition", identically for every sponsor. HeySummit's template makes the "cannot prove" column explicit; it stops a sponsor over-reading a raw count.

| Metric | Value | Method | What it cannot prove |
| ------ | ----- | ------ | -------------------- |
| Leads / opt-ins | 187 unique (212 scans) | lead app export, dedup by badge ID, consented only, pulled [date] | intent, pipeline |
| Booth traffic (sampled) | 10-11: 58 people; 15-16: 41 people | clicker count, people present | unsampled hours; manual counts undercount |
| Session attendance | 46 | door count at minute 5 | engagement |
| Session recording | 640 views, 21 h watch time | platform analytics, day 3 after publication | who watched; whether the sponsor slide was seen |
| Prize track (hackathon) | 14 submissions used the sponsor API | judging form field | quality, continued use |
| Brand reach | X: 9,400 impressions; LinkedIn: 3,100 reach | own posts naming the sponsor, [date range], per platform | attention; never summed |

Recording not yet published, or under 30 days old: write "pending, sent by [date]" and send the 30-day figure as a one-line addendum; the renewal motion carries it to the call if the call comes first.

Standard customer-success metrics like product usage, adoption and health scores do not apply to sponsorships - a sponsorship has no usage telemetry. Substitute the sponsor's stated metric; where none was captured, say so in the report rather than inventing a proxy.

Event platforms built for larger, funnel-driven sponsorships (booth leads, meeting attribution) increasingly replace the document with a live dashboard - a fit for events selling pipeline access, not for the perk-delivery-and-relationship report this template serves.

Close with: "These are outputs we can measure. The outcomes (pipeline, signups, hires) live in your systems; if you share them, we will plan next year around them."

### 5. What attendees said about them

Recall (with the decoy baseline), interaction and perception rows with n and response rate (survey not closed yet: "survey closes [date]; results follow"); up to 3 anonymized verbatims naming the sponsor, a critical one included if it exists.

### 6. What went wrong, and the fix

| What happened | Effect on you | Cause | Fix for next edition | Owner |
| ------------- | ------------- | ----- | -------------------- | ----- |
| Screen loop failed day 2 | logo off-screen 4h30 | venue player crash | morning loop test; spare player | AV lead |

Include problems on the sponsor's side (unstaffed booth, late assets), phrased without blame.

### 7. Photos

Timestamped, peak hours, file named by contract row: their booth, their speaker, their logo in place, their raffle winner. State usage terms ("may republish" or "internal only"); exclude or blur attendees who opted out of photos. A failed placement gets its log, not a photo.

### 8. Next edition, lightly

Dates, or the date they will be fixed, and the fixes from section 6 that matter to them. The ask itself, its timing against the sponsor's budget cycle, renewal offers and any price change are `samber/dev-event-organizer-skills@event-sponsor-renewal`'s motion, not this document's job.

## Short form

The default second stage (see the report menu): all eight sections without narrative, generated from the matrix and the count plan, one per sponsor. Section 3 as the three audience numbers; section 4 with only the rows the sponsor bought; section 5 once the survey closes; section 7 as 3-5 photos linked to matrix rows. The full report adds narrative, verbatims and the value column.

## The renew / renegotiate / drop read

The sponsor's own post-event decision has three outcomes - renew (their threshold met), renegotiate (right audience, wrong package), or drop (audience mismatch). Write your read of each sponsor's likely position when handing the report to `samber/dev-event-organizer-skills@event-sponsor-renewal`:

- **Renew** - their threshold met.
- **Renegotiate** - internal read only, never in the report: note which surface produced their outcome (the workshop, not the booth). The renewal motion turns it into a swap or downgrade offer; losing a tier beats losing the sponsor.
- **Drop** - an audience mismatch is better released honestly than re-sold.

## Fill rules

- Quote contracted items from the signed agreement, never the prospectus.
- Report a small real number over a big estimated one. The sponsor's team will sanity-check every figure.
- Put the method line under every number, or drop the number.
- Report sampled counts per sampled hour; never average them into a daily figure.
- Never show one sponsor's numbers, misses or price to another.

## Negative example

```
// ✗ Bad - each line costs the renewal
"Your brand reached 1.2M people (est. media value $84,000)."
    -> invented reach and a banned currency metric; the sponsor's analyst discards the whole report
"300+ leads at your booth!"
    -> scans not deduplicated, sponsor staff not removed, no consent rule stated
"Everything went to plan."
    -> the screen loop failed; the sponsor saw it and now doubts every other row
"Lock in next year now at 20% off before prices rise!"
    -> a hard pitch in a value document, and a loyalty discount the rate card does not allow
Sent 7 weeks after the event.
    -> after the sponsor's internal review, so the champion reported with no evidence
```
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