63 — Events Strategy
Status: CANONICAL · Commercial OS
Owner: Founder
Last verified: 2026-07-21
Purpose
Which rooms are worth the founder's physical presence, what happens in them, and the follow-up system that converts hallway conversations into pipeline. Events are precision strikes (50 §3) — 2–3 per year, chosen for ICP density, never booth theater.
Target audience: Founder; future marketing hire.
1. The Portfolio (2026–2027)
| Event | Why | Play |
|---|---|---|
| Dreamforce (annual) | The MuleSoft/Salesforce ecosystem home turf (48 P1); founder alumni credibility; the ICP's CRM universe in one building | No booth. 15–20 pre-booked meetings (ecosystem contacts + open pipeline + design-partner intros); ecosystem-party circuit; one campfire/community talk if secured |
| CS-practitioner conferences (1–2/yr — Gain Grow Retain-adjacent, Pulse-adjacent, or regional CS meetups) | P1/P2 personas concentrated; wound stories on stage everywhere | The talk (§2) if secured; otherwise strategic attendance: 10 pre-booked conversations, teardown-driven hallway presence |
| Local/virtual CS & RevOps meetups (monthly-opportunistic) | Cheap reps for the talk; ICP in listening mode | The 20-minute version of the flagship narrative (61) |
| Industry mega-conferences (SaaStr etc.) | Attend only with ≥ 8 pre-booked meetings; otherwise skip | — |
The standing rule: no sponsorships, no booths, no swag pre-Series A. A booth is a $15K way to stand still; the founder walking with a calendar full of pre-booked meetings outperforms it every time at our stage.
2. The Talk (the event asset, one narrative refined all year)
Title: "The Human API: why your best people are your worst integration — and what AI actually changes."
Arc (20 or 40 min builds): the $8M wound story (14) → the eight-tab teardown with live audience math → why bolted-on AI failed (the Four Enemies, the Quiet Demotion) → the principle stack (shared bench · owned truth · approval between) → one live moment: the approval + receipt, 90 seconds, from the phone if needed. No product tour; the talk sells the category, the hallway sells the product.
The close: never "visit our website" — always the question: "What's your team's version of the eight-tab morning? Come tell me — I collect them." (It works. They come. The collection becomes essays 56.)
3. The Event Operating System
Before (2 weeks out): target list from attendee/speaker rolls filtered by ICP (33) · outreach referencing something true ("your churn-postmortem post") · calendar goal: 60% booked before flying · LinkedIn "I'll be at X — collecting eight-tab mornings" post.
During: meetings > sessions, always · same-evening notes per conversation (voice memo standard: who, pain quote, why-now signal, next step) · the demo lives on the laptop, shown only when asked twice (scarcity posture).
After (the week the ROI happens): every conversation gets its specific follow-up within 72h — the thing promised (an essay, an intro, a POV conversation), never a generic deck · ICP conversations enter CRM as sourced pipeline (74) · one "what I learned at X" essay banks the trip (56 T4).
4. Hosting (small, owned, deferred-but-designed)
The Workbench Dinner (post-launch, quarterly, one city): 8–10 CS/RevOps leaders, no presentation, one structured question ("what did AI actually change on your team this year?"), Chatham House rule. Cost ≈ $1.5K; yield: relationships no conference produces. First one gates on: 10 customers + launch done. Scales later into the community's annual moment (62 §2).
KPIs: pre-booked meeting rate ≥ 60% before travel · conversations → CRM-logged ≥ 90% · 72h follow-up compliance 100% · event-sourced pipeline per event ≥ 5 qualified conversations · cost per qualified conversation < $500 · talk acceptances/year (leading indicator of category traction).
Related: 48 Partners · 57 Founder-led · 61 Webinars · 62 Community