Chapter 11 of 12
Post-event engagement, measurement, and the honest readout
Beyond the sales sprint: keeping the room warm, counting what happened, and deciding repeat/scale/kill. Event Manager + Analyst co-own the numbers.
Post-event engagement (the non-sales track)
- The recap ladder ships on schedule (chapter 08: A1 T+1 → A4 T+14) — it is also the value-add material inside the tier-B sequences. Photos go to guests within 24–48h; guests who receive photos share them, and their sharing out-markets the company recap.
- Materials as the follow-up excuse: slides, the workshop worksheet, the session-notes doc — "the thing you asked for" is the highest-legitimacy touch there is. Plain subject lines outperform clever ones here.
- Registrants who didn't attend are still leads. Free-event no-show runs 30–50%+; most no-shows "got busy", they didn't lose interest (memo-05). They get their own track (pack slot 10d): what was discussed + materials + the next date. For anything recorded, the replay audience is real pipeline — a third of registrants only ever consume on-demand.
- Community continuation: the compounding move is the standing invitation — this quarter's dinner guests hear about next quarter's table first; workshop alumni get the next masterclass date before the public. Quarterly is the minimum cadence for compounding; above monthly overruns local ICP supply (memo-05). A LinkedIn thread, a short survey (sent fast — response rates fall with every hour), and the host's personal thank-yous complete the loop.
Measurement: definitions before dashboards
- Sourced = this event was the first meaningful touch that created the contact/opportunity. Influenced = the event touched an existing opportunity. Report both, side by side, never summed — sourced-only undervalues events, influenced-only flatters them (memo-05; healthy B2B norms: marketing sources 25–45% of pipeline, influences 60–85%).
- Account-level credit. B2B buying committees run 9–11 people; the dinner guest is often not the signer. Credit the account the guest belongs to, or events get systematically under-counted.
- Attribution window matched to our cycle, not tool defaults: with Consulting's 6–16-week-to-SOW and longer-to-revenue motion, run 90-day checkpoints inside a 12–18-month influence window (the "1.5× sales cycle" rule). A 30-day window on our cycle zeroes out most of what events do.
- Self-reported attribution is kept, verbatim. An open-text "how did you hear about us / what prompted this?" at inbound and at Path A intake catches the dark-funnel touches (dinners, word-of-mouth) software never sees — the measured gap between software and self-reported attribution is enormous (HockeyStack SRA 2024: 41% of closed-won deals self-reported a channel multi-touch gave <5% credit).
- Mechanics: one CRM campaign per
event_id; attendees added with status (registered/attended/dinner guest/meeting held); original-source field locked at creation, never overwritten. This hygiene is created at capture (chapter 09) — it cannot be reconstructed at T+90. - Cost per opportunity beats cost per lead as the event unit metric; badge-scan CPL flatters everything (memo-05).
The readout cadence
| When | Artefact | Contents | Audience |
|---|---|---|---|
| T+3d (72h) | Debrief (pack part 1) | Numbers vs targets so far, budget actuals, what worked, kill list, pack improvements | Team |
| T+7 | Scorecard note | P1–P3 + S1–S4 vs targets, spend, urgent follow-ups; ≤300 words (output-discipline: weekly snapshot cap) | CMO + Jay |
| T+30 | Cost/ROI check | Cost variance explained; early conversion pace; renew/kill leaning | CMO |
| T+90 | ROI readout (pack part 2) | Sourced + influenced opps and pipeline, pipeline multiple vs the pre-commit test, cost per opportunity, decision | CMO + Jay |
| T+180 | Revenue view | Wins to date; cohort still maturing noted honestly | CMO (rolled into quarterly) |
Pipeline is judged at T+90, revenue at T+180+, and for our ACV the cohort keeps converting past that — the readout says "matured X% of expected window" rather than pretending the story is over.
The debrief (72 hours, 45 minutes, timeboxed)
Agenda: (1) numbers vs targets; (2) budget actual vs plan, variance why; (3) what worked — do again; (4) kill list — never again; (5) the four questions: what were we trying to achieve, what happened, why, what changes; (6) decision leaning: repeat / scale / shrink / kill; (7) pack improvements — concrete edits PR'd back to templates/event-pack/ and this playbook. Post-mortems run on successes too — that's how formats become repeatable. Surprises and market intel route to the Researcher; learnings that outlive the session go in the log (TEAM.md §5).
The repeat / scale / kill decision
Made at T+90 by CMO + Event Manager, recorded in the pack:
- Repeat — passed the investment test; same shape, incorporate the kill list.
- Scale — passed with headroom (quota'd out, waitlist, oversubscribed dinner) → bigger room, second city, higher tier. Scale one variable at a time.
- Shrink — value concentrated in one component (the dinner worked, the booth didn't) → keep the component, cut the rest.
- Kill — failed the floor once with no redeeming influence signal → second chance only with a changed mode; failed twice → out of the portfolio (the two-strike rule, chapter 03). The register keeps the score so next year's decision starts from evidence.
Closing the loop: state: closed in the event brief, log entry appended, rollup updated, and the next edition's scorecard opens with this report attached.