TL;DR
- A conference keeps producing useful context after its last day, as attendees post recaps about sessions, ideas, products and the people they met.
- A recap tells you what someone chose to write about. Treat it as context. It says nothing reliable about their priorities or budget.
- SignalRaven's Conference Intelligence keeps running for about a week after the event and finds relevant recap authors and people engaging with event posts, then completes itself.
- In the week after, look for relevant recap authors, the people engaging with those conversations, the topics that keep coming up and new activity from people or accounts you've already seen.
- Most recaps are context for an account owner or for marketing. A few give you a real reason to write.
A conference's last day is a poor place to stop paying attention. In the days after, LinkedIn fills with recaps. People write about the sessions they found useful, the ideas they disagreed with, the products they noticed, the people they met and the themes they kept hearing.
Read together, recaps tell marketing which topics outlasted the event. They show sales who kept taking part and which target accounts stayed in the conversation, including people who never came near your booth. They can also sharpen follow-up, without turning every recap into an excuse for outreach.
What a recap tells you
A recap is a choice. Out of three days of sessions, conversations and dinners, the author picked a few things worth writing down in public. That makes the topic real and the person's interest in it visible.
It doesn't make the recap a statement of priorities. Someone who praises a session on forecasting may be evaluating nothing at all, and a post about a product they noticed is a long way from a project with a budget. Read the recap for what it says: these ideas stood out to this person this week.
That's still useful. It tells an account owner what a contact chose to write about this week. It gives a follow-up a specific subject. And across many recaps, it shows marketing which ideas from the event actually stuck with the people you care about.
How Conference Intelligence keeps running after the event
A SignalRaven conference source doesn't stop when the doors close. It keeps checking daily for the first few days after the last day, then moves into a wrap-up period and checks every couple of days until about a week after the event. Then it marks itself Completed in your Sources list.
Recap activity becomes a signal in two ways:
- The author. When a relevant person posts a first-person recap, SignalRaven evaluates the author directly against your ICP. The post is the activity, so nobody else has to react to it first.
- The engagers. People who react to or comment on the event's top posts are evaluated too, up to a per-event limit. The host's staff are filtered out, consultants and agencies are always left out on event sources, and everyone else is scored against your ICP.
In the portal and the signal email, each signal names the event next to the person. You can add an event up to ten days after its last day, and its first run sweeps back through the attendance posts and recaps. How Conference Intelligence works covers setup.
What to look for in the week after
Open the event's signals once or twice in the week after, from the event's source page (admins and managers) or by filtering Signals to the Event source type.
Relevant recap authors. People in your ICP who wrote about the event. Their recap says, in their own words, what they took away.
People engaging with those conversations. Recaps travel beyond the attendees. Colleagues and peers react and comment, and some of them fit your market even though they never went.
Topics that keep coming up. When several relevant people write about the same session, problem or launch, that's a pattern worth passing to marketing and to the people planning next year's event.
Activity from people and accounts you've already seen. A person who posted that they were attending and later engaged with event posts can have more than one signal around the event, and so can an account whose people turn up at different points. Signals from the same person or company in the last 90 days raise urgency on every plan, and the Companies view groups them by account, so a cluster around one account is easy to spot.
Decide what each recap is for
The week after a conference is when follow-up tends to get generic. The fix is to decide what each piece of activity is for before writing anything.
Someone you met. Their recap gives you a better follow-up than the one you were going to send. Picture a fictional head of finance operations at a 600-person logistics company who stopped by your booth and later posts that the session on close automation was the most useful hour of her week. A follow-up could be as simple as: "Good to meet you on Tuesday. Your recap on the close automation session lined up with what you said about month-end at the booth. Happy to compare notes if that's useful."
Someone relevant you never met. Decide whether there's a real reason to write. If their recap is about a problem you work on, a short note about the idea itself can make sense. A fictional director of revenue operations writes that a panel on territory planning changed how he thinks about rep capacity. Something like this works: "Your recap of the territory planning panel was a good read. What changed your mind on capacity?" If there's no real reason, follow the person, note the topic and let a later signal decide.
An account you're already working. Pass the recap to the account owner as context and add it to the account record. Several recaps from one account show which topics that team chose to write about.
Marketing's read of the event. The topics, sessions and launches that relevant people kept writing about are a better guide to next quarter's content than the booth's scan count.
Know when a recap isn't a reason to write
Plenty of recaps aren't invitations. A post that's mostly thanks to the organizers and a photo of the team, a personal milestone or a congratulations thread gives you little to talk about. Being in the same building for three days isn't a connection either.
When the only thing you could say is that you saw the post, don't send the message. Keep the signal as context.
Close out the event
When the source marks itself Completed, close the event with a count: meetings held, conversations started in the week after, target accounts active around the event and the topics that kept coming up. A tag category for the event, with values such as Met there and Meeting booked, turns that count into a filter on the signals you already have. Conference ROI: why you should measure more than booth traffic sets out the full scorecard and the break-even to compare it with.
FAQ
How soon after a conference should I follow up?
For people you met, within the first few days, while the conversation is still fresh for both of you. Recaps arrive through the following week, so a note written after reading someone's recap lands at a natural time.
Should I mention that I read their recap?
Yes, if the recap is what you want to talk about. They posted it so people would read it. Open with the idea in it and skip any mention of how it reached you.
Does Conference Intelligence keep running after the event ends?
Yes. It keeps checking daily for a few days after the last day, then every couple of days until about a week after, and then marks itself Completed.
Can I still catch the recaps if I didn't set up the event in advance?
Yes, if you add it within ten days of its last day. Its first run sweeps back through the event's attendance posts and recaps.