Conference Prep

From sponsorship to closed-won — the full conference motion.

Exactly what to do, week by week, before, during, and after a conference to fill your calendar and convert badge scans into pipeline.

The plan

The full conference motion, week by week.

Seven steps from attendee list to closed-won. Each step links to the deep reference if you want to go further. Each step also has the obvious alternative: have us do it.

  1. 6–4 weeks before

    1. Pull the attendee list, score against ICP

    Get the attendee list (sponsor benefit or list-vendor purchase). ICP-score every name. Filter to a target list of 100–300.

    Why: Without this filter, you'll spend the conference talking to non-buyers.

  2. 4–3 weeks before

    2. Begin pre-event outreach (touch 1)

    Send the warmup touch — recognition of their presence at the event, no meeting ask yet. Deliverability handoff from your email setup.

    Why: 78% of attendees never get touched pre-event. The 4-week window is the difference between a full calendar and an empty floor.

  3. 3–1 weeks before

    3. Schedule meetings + book VIP dinner

    Touch 2: explicit meeting ask with calendar link. Confirm 30–50 meetings. Lock down the VIP dinner venue + invite list.

    Why: VIP dinners convert 5–10x per attendee vs booth conversations. Most teams skip them — that's the opportunity.

  4. 1 week before

    4. Reconcile and brief team

    Final outreach push, calendar reconciliation, brief team on top 20 accounts and the asks.

    Why: Walking the floor without a daily plan reduces conversion by half. The pre-event brief makes the time on-site usable.

  5. During the event (3 days)

    5. Daily debrief + note capture

    Capture every conversation in a structured system. Same-day debrief on what got committed. Real-time scheduling for missed meetings.

    Why: Human memory degrades on 40 conversations in 72 hours. Without capture, half the value is lost in the noise.

  6. 24 hours after

    6. Same-day follow-up

    Bespoke follow-up touches (not templated). Reference specific conversation moments. Calendar link for next conversation.

    Why: Bespoke 24h follow-up converts at 25–40%. Templated 'thanks for chatting' converts at 0–3%. The window is short.

  7. Weeks 4–12 after

    7. 30/60/90-day re-engagement

    Built-in nurture sequences for warm prospects who didn't convert in week 1. Lead-magnet write-ups to re-trigger conversations.

    Why: Most post-event pipeline closes in months 2–3, not week 1. Without the nurture layer, that pipeline dies.

What you're setting up

The four layers, in plain English.

A conference motion has four layers. Each layer answers one specific question about whether the event will actually move pipeline.

Strategy

When conferences beat cold outbound, and the ICP-discovery velocity argument for early-stage teams. The case for showing up before the case for spending.

Pre-event

Outreach math, meeting-density math, and VIP dinner architecture. The work that decides whether you walk in with 50 meetings booked or none.

During

Conversation engineering and real-time note capture. How to make 40 conversations in 72 hours legible enough to act on by Friday.

Post-event

Follow-up cadences and lead magnets for re-engagement. Most post-event pipeline closes in months 2–3 — this is the layer that keeps it alive.

Reference

Go deeper — the operational reference.

For the operator who actually wants to learn this. Eight chapters covering every layer of the motion — strategy, pre-event, during, post-event — and every failure mode we've hit running it at SaaStr, AWS re:Invent, and HubSpot INBOUND. Read by chapter to debug something specific, or read in order to build the motion from scratch.

Skip the build

We run the whole conference motion as a service.

Pre-event prospect list, ICP scoring, multi-touch sequence, on-the-floor scheduling, post-event follow-up. Same playbook we've run at SaaStr, AWS re:Invent, HubSpot INBOUND.

Book a call →