Sarah runs field marketing at a security software company. Her team just hosted a dinner in Boston: fourteen guests, two of them customers who invited their peers, one investor who brought a CISO she'd been trying to reach for a year. The conversation ran past ten. Everyone left saying they'd stay in touch.
On Monday, the follow-up goes out. A thank-you email from marketing, a link to a recap, and every guest added to a nurture sequence.
By Friday, the evening has turned back into a list.
This is where most events lose their value. Not at the venue, not at the guest list, but in the week after, when the room was full of relationships and the follow-up treated it like a list of leads.
What an event actually produces
The usual way to measure an event is attendees, then meetings booked. That misses most of what happened in the room.
An event produces three things:
- New relationships between guests and your team. Your CRO now knows the CISO personally. That's a path that didn't exist on Thursday.
- New relationships between guests. Your happy customer spent an hour talking to a VP of Engineering at an account you're targeting. Your customer is now a connector into that account.
- Proof for the connectors who helped. The customer and the investor who brought guests just saw the event go well. They're more likely to help again, if someone tells them how it went.
A thank-you email and a nurture sequence use none of the three.
The seven-day plan
Day 0, the same night: capture who met whom
Before anyone goes home, the hosts spend ten minutes writing down the room. Not notes on each guest's pain points. Who talked to whom, at length.
For each guest, capture:
- Who they spent the most time with, from your team and from the other guests
- Who invited them
- One thing they said they cared about
This is the most valuable data the event will produce, and it's gone by Monday morning if nobody writes it down. A shared doc works. So does a voice note to the event owner.
Day 1: thank the connectors before the guests
The customers, investors and advisors who brought guests hear from you first, with a line on how the evening went for the person they invited. "Priya and our CRO talked for an hour about their SOC rebuild. Thank you for bringing her."
Connectors who hear back help again. Connectors who never hear back quietly stop. We wrote about this in how to fill an executive dinner, and it matters even more after the event than before it.
Then thank the guests, from the person they spent the most time with, not from a marketing alias.
Days 2 and 3: sort the room into three groups
Using the Day 0 notes, every guest goes into one of three groups.
- Ready for a direct follow-up. The guest is at a target account and had a real conversation with someone on your team. That person follows up one to one. No sequence.
- A new connector. The guest isn't a buyer, or isn't the right buyer, but now knows someone on your team well and works with or near people you want to reach. They're a source of intros, not a lead.
- A bridge between guests. Two guests met and got on. If one of them is a customer and the other is at a target account, your customer is now the warmest path you have into that account.
Notice who's missing: nobody goes into a generic nurture sequence by default.
Days 3 to 5: send the intro requests while the evening is fresh
This is the step most teams never get to.
For each "new connector" and each "bridge", draft one intro request. The ask is short, specific and easy to forward:
"Great to meet you on Thursday. You mentioned you work closely with the platform team at Northwind. Would you be open to introducing me to their VP of Engineering? Happy to send a two-line note you can forward."
Two rules keep this from feeling transactional:
- One ask per person. Don't ask a guest you met three days ago for four intros. That's how connector fatigue starts.
- The ask comes from the person they spent time with. If the guest talked to your CRO all evening, the request comes from your CRO.
The window matters. A week after the event, the guest still remembers the conversation. A month after, the same ask reads like any other cold request.
Day 6: no-shows get a note from whoever invited them
Every event has guests who accepted and didn't come. Don't add them to the recap email. Ask the connector who invited them to send a short "missed you, here's what you missed" note, with an offer to set up a smaller conversation. A no-show who hears from a friend often converts better than an attendee who hears from marketing.
Day 7: close the loop and count
The event owner sends a short summary to everyone who helped: which intros went out, which were accepted, which meetings are booked. Then record three numbers for the next event:
- Intro requests sent per attendee in the first seven days
- Acceptance rate on those requests
- Meetings from intros, separate from meetings with attendees directly
The third number is the one almost nobody tracks, and it's the one that shows what the room was really worth. A dinner with fourteen guests is a small number of buyers. It's a much larger number of paths.
The same plan for conferences and booths
Bigger events have the same three outputs, just more of them and messier.
- At a sponsored conference, the Day 0 capture is your team's list of real conversations from the floor, not the badge scan list. Badge scans are leads. Conversations are relationships.
- The "bridge" group is larger at a conference, because your customers are there talking to everyone. Ask your customers who attended which conversations they had that you should know about.
- The seven-day window is the same. Conferences produce a flood of follow-up email the week after, so a specific intro request from someone the guest actually talked to stands out more, not less.
The event-led sales glossary covers the wider motion, and the field marketing playbook shows how teams run it across a full events calendar.
Where Boomerang fits
Rudy, the agent inside Boomerang, does the parts of this that usually get dropped. It maps which guests connect to which of your target accounts, through your team, customers, investors and partners, and drafts the intro request for whoever should send it. Rudy never sends anything. The person who spent the evening with the guest reads the draft and sends it from their own account, and every ask is tracked, so the Day 7 numbers are already counted.
Frequently asked questions
How soon should you follow up after a B2B event?
Thank connectors and guests within a day, and send any intro requests within a week. After about a week the guest's memory of the conversation fades, and a request that would have felt natural starts to read like a cold ask.
Should event attendees go into a nurture sequence?
Not by default. Guests who had a real conversation with your team should get a one-to-one follow-up from that person. Guests who aren't buyers are often more valuable as connectors to people who are, and a nurture sequence uses neither relationship.
What should you track after an event besides meetings?
Track who met whom, the number of intro requests sent per attendee in the first week, the acceptance rate on those requests, and meetings that came from those intros. That last number is the one most teams miss, because it counts the pipeline an event creates through its guests' networks rather than through the guests themselves.
How do you ask an event guest for an introduction?
Have the person who spent the most time with them ask, within a week, for one specific introduction tied to something the guest said at the event. Offer a two-line note they can forward so the ask takes them seconds.
.png)
