Event Followup

Written before the event. Sent inside 24 hours. Every team that plans to write follow-up afterward sends it days late, and days late turns a warm conversation into a cold email.

When to use

• T-3 weeks. This is the correct time to run this skill
• Immediately after an event where nothing was prepared, when speed still matters
• A recurring event program where follow-up should be systematized

Inputs

• Reads: workspace/events/<event>/meetings.csv, the staffing assignments, the format plan
• Needs from user: who sends what, and what was promised to whom (filled in on the day)

Workflow

1. Tier the follow-up by what actually happened

The single most important design decision. One templated blast to everyone scanned is worse than nothing, because it tells the people you actually talked to that they were a row in a spreadsheet.

Tier 5 is the one everybody forgets. A no-show is frequently a person who genuinely wanted to come, and a warm, guilt-free note with the material outperforms most first touches.

2. Write the templates before the event

For each tier: the structure, the sender, the timing, and the placeholders for what can only be known afterward. Then afterward the only work is filling the blanks, which is the only part that has to happen afterward.

Tier 1 structure:

<Name>, good to meet you <yesterday / at the dinner>.

<One specific thing they said, in their words. This is the whole email.>

<The thing you promised, attached or linked. Delivered, not "I'll send it over.">

<The specific next step, with a proposed date.>

Three to five sentences. No recap of your product. No deck unless one was requested. The specific reference in sentence two is what makes it a real email, and a generic version of it is worse than not sending.

3. Capture on the day so the specifics exist

Follow-up quality is decided during the event, not after. Every conversation gets a same-day note with what was discussed, what was promised, and the next step. Notes written three days later produce generic follow-up, and it shows.

Give every team member the note format in advance so it takes thirty seconds on a phone.

4. Deliver what was promised, first

If anything was promised in a conversation, that is the follow-up. An introduction, a document, an answer, a pricing question. Deliver it before anything else, and do not attach a next step to it if it was a favor.

5. Route the attendee list properly

The full attendee list, if you receive one, is not follow-up material. It is list-building material. Enrich it, score it against the ICP, and route it into the target list so the next event starts warmer. Do not email it as though those people met you.

6. Sequence the second and third touches

Most event pipeline comes from the second and third touch, not the first.

• T+1 week: the content from the event, from marketing, to everyone in tiers 1 through 3
• T+2 weeks: a personal check-in from the owner to tier 1 and 2 non-responders
• T+4 weeks: a genuinely useful, non-event reason to reconnect
• Then into normal nurture

7. Track it, by name

Per person: tier, owner, sent date, replied, next step, and the date. An event that produced twenty conversations and no tracked follow-up produced nothing.

8. Quality gate

Everything runs through writing-quality. Event follow-up is unusually prone to inflated warmth: "it was incredible to connect", "the energy in the room was amazing." A specific detail does that work better and reads as human.

Output

• Writes: workspace/events/<event>/followup/ with a template per tier, the note-capture format, the sequence calendar, and the tracking sheet
• Prints: the tier table with owners and timing, the templates, and the capture format for the team

Rules & quality bar

• Written before the event. This is the point of the skill
• Tiered by what actually happened. Never one blast
• Tier 1 inside 24 hours
• The specific reference is mandatory. A generic tier 1 note is worse than none
• Deliver what was promised first
• Same-day notes. Follow-up quality is decided during the event
• No-shows get a real, guilt-free message
• The attendee list is list building, not follow-up
• Everything runs through writing-quality

Related skills

• Reads: meeting-engine, staffing-and-briefing, run-of-show
• Pairs with: event-content (different audience, same deadline)
• Feeds: event-measurement