Event to Content Playbook: One Event, 30 Days of Content
Luke Costley-White
一粒万倍
One grain, ten thousand times
Most marketers go to events. Few get anything useful out of them.
Not because the events are bad. Because there is no system for what happens after. You attend, you collect a few business cards, you write a follow-up email, and by Thursday the whole thing is a fading memory and a hotel receipt.
This playbook covers three different situations: events you attend as a participant, events you run yourself, and how to extract a month of content from either. Each one requires a different approach. All three are worth building a system around.
Part 1: Events you attend (but don't own)
The value at a third-party event is what the room is actually saying. Not what ended up on the agenda. Not the keynote headline. What came up in the Q&A, in the hallway, in the panel when someone said the thing you weren't expecting to hear.
That's what people want to read about. Not "I attended an event and here's the recap." The recap is for event organisers. Your job is to be the person who was in the room.
The capture protocol:
Before you go: decide what you're listening for. One question you want answered. One tension in your industry you're curious about. Give yourself a lens.
During: voice note. Not a notebook. One sentence after each session that mattered: "The thing that surprised me was..." That's it.
Within 24 hours: write the short take. One observation, under 100 words. Don't wait until you have "enough." One insight published fast beats a comprehensive recap published never.
The 3-post sequence from a single event:
Timing | Format | What it covers |
|---|---|---|
Day of or next morning | Short take (<100 words) | One line from the room that landed - or a question no one had a clean answer to. No context needed. |
Within 48 hours | Medium post (150-250 words) | The pattern that kept coming up. Not a summary - a single thread that ran through multiple conversations. |
Within 1 week | Carousel / document post | "5 things said in the room that don't get said in public." Designed for saves. This is the format that drives compounding reach. |
The short take creates recency. The medium post creates depth. The carousel creates saves and extends the reach window by days or weeks.
Part 2: Events you run yourself
Running your own event flips the content equation. You're no longer reporting from the room. The room is reporting to you.
The strategic difference: customer events are the highest-trust content format available to a brand. The insight comes from real people with real opinions, not from the marketing team. That's what makes it citable, shareable, and genuinely hard to fake.
The setup that makes content possible:
Before the event:
Brief 1-2 attendees in advance. Ask if they're comfortable being quoted, anonymised or named. Most people say yes when you ask directly.
Tell them what you're hoping to learn. This primes the conversation.
During the event:
Take notes on specific phrases, not general themes. "Our attribution has a 6-month blind spot" is quotable. "Attribution is hard" is not.
Flag 2-3 moments you'll use. You don't need to capture everything.
The 3-post sequence from a customer event:
Post | Format | Hook |
|---|---|---|
Short take per insight | <120 words | "A [type of professional] said this at [your event] last week:" followed by the specific observation. |
Carousel post | Document / carousel | "[X] things [your customers] said at [event] that we didn't expect." Evidence-led, save-bait. Customer proof without a pitch. |
Follow-up post (if it generates DMs) | Short take | "A lot of people reached out after that last post. Here's the pattern I'm seeing." Compound post: the original generates the response, the follow-up extends the reach window. |
The follow-up post only gets written if the original generates DMs. If it does, that response is itself proof the content was working. Publishing it publicly validates the insight and compounds the reach.
Part 3: The content extraction framework
One event, properly extracted, covers 10-12 days of content. Here is how that looks across both event types:
Participant event (e.g. industry roundtable, conference, CMO dinner):
Your own event (e.g. customer roundtable, power user session, advisory board):
The extraction checklist (run after every event):
What was the single most surprising thing said? (Short take)
What theme kept coming up across multiple conversations? (Medium post)
What would someone who wasn't there wish they'd heard? (Carousel)
Did any post generate DMs or comments worth amplifying? (Follow-up)
Did any insight connect to a broader industry pattern worth exploring? (Future pillar post)
If you answer these five questions after every event, you never start a content week from zero.
How to use this
Time required: 15-20 minutes after each event to capture. 30-45 minutes total to write and schedule the full sequence.
Start here:
After your next event, open a voice memo within 30 minutes and say out loud: "The most interesting thing said today was..." Record for 60 seconds. Don't edit.
Transcribe it the same evening or next morning. That's your short take draft.
Within 48 hours, write the medium post using one theme that came up more than once.
By day 7, turn the best 5 moments into a carousel outline (5 slides, one observation each).
What good looks like:
A single event you attended should produce 3 posts over 7 days, minimum. A single event you ran should produce 3-5 posts over 10-14 days. None of these posts should feel like a recap. All of them should feel like a practitioner sharing something worth knowing.
What to do next
Run the framework on the next event in your calendar. One event, three posts, seven days. See what it does to your inbound.
If you want a system that captures event insights, connects them to your content calendar, and briefs posts automatically - that's what DOJO AI is built for.
The Event to Content Playbook | DOJO AI | dojoai.com