In February 2026 a founder posted a year of conference sponsorship numbers on a public Web3 developer forum. Six events in 14 months and a six-figure total produced 847 badge scans, 412 follow-up emails after deduplication, 38 replies, 11 discovery calls, 3 qualified leads and one closed deal. The author concluded that sponsorship is broken for startups.
We read the same funnel differently. The booths did their job: 847 people stopped. The loss came afterwards, between the scan and the reply, where more than nine in ten follow-up emails went unanswered. The post does not say how quickly those emails went out or what they said, so we will not guess at that team's process. The shape is still a familiar one: plenty of conversations during the event and very little to show for them a month later.
Why conference leads go cold so quickly
A conference conversation depends on context. The person you met had just watched a panel, or had just described a problem to you, and your pitch landed because of it. Two weeks later that context is gone. What remains in your CRM is a name and a company, which the recipient cannot tell apart from a cold list.
The calendar makes it worse. TOKEN2049 Singapore closes on October 8, 2026. Money20/20 USA opens ten days later, and Hong Kong FinTech Week and Web Summit both fall in the first half of November. Someone on that circuit can be two or three events further on before a slow follow-up reaches them.
None of this is an argument against the spend. A booth at a tier-one crypto conference is a mid five-figure commitment before travel and staff, and the larger packages cost several times that. The money buys two days with a few thousand relevant people in one building. Whether it becomes revenue is decided afterwards, by work that is cheap by comparison and usually has no owner.
Most teams know this and still plan the booth for three months and the follow-up for none. They assume the month after the event will take care of itself once everyone is back at their desks, which is when everyone is furthest behind.
A 30-day conference follow-up plan
This is the sequence we recommend. Very little of it can be improvised afterwards, because most of it depends on decisions made before the doors open.
Days 0–2: follow up while the conversation is warm
- Write down every conversation the same day, with context: who they were, what they said, what they asked for. A badge scan without a sentence attached is a business card.
- Send the first follow-up within 48 hours and refer to the specific conversation. A templated “great to meet you at TOKEN2049” tells the reader they were a scan.
- Ship anything you promised in the room now, whether that was a deck, an introduction or a demo slot.
Days 2–7: publish while the event is still news
For about a week the event is still a live topic. Panel footage, floor interviews and photographs get far more attention in that week than they will a month later, when the industry has moved to the next city.
- Cut clips from any speaking slot and publish them while the event hashtag is still active. If the stage is the hard part, we cover that in how to get a speaking slot at a crypto conference.
- Write a recap that is useful to people who did not attend: what was said, what changed, who mattered. A photo album does not count.
- Tag the organiser and the people you featured. Organisers notice who publishes, and it makes the next press credential easier to get.
Days 7–21: separate interest from politeness
- Enrich and segment the list. Many of the people on it were being polite. Score each contact against the customer profile you sell to and move the rest to a newsletter or nurture sequence, not to a salesperson.
- Make the second touch from a different angle: the recap, the clip they appear in, something relevant to the problem they described. “Just circling back” is not an angle.
- Book the meetings the event was supposed to produce. Meetings booked is the one number worth reporting at day 30.
Days 21–30: decide about the next event
Sponsorship decisions for the following year are often made with no data from the previous one, which is how companies end up back at the same event out of habit. By day 30 you should be able to state, for each event, the conversations logged, the contacts qualified, the meetings booked, the pipeline created and the cost per meeting.
Planning your circuit for next year?
We'll look at your event list and tell you where we'd spend and where we wouldn't.
How to measure conference ROI at 30 days and at six months
A 30-day report tells you whether the follow-up worked. It cannot tell you whether the event paid, because B2B deals that start at a conference usually take months to close. Report meetings booked and cost per meeting at 30 days, then pipeline and closed revenue at six months. Teams that judge an event on revenue after one month will cancel good events.
Use the same five numbers for every event so they can be compared. After three or four events you will know your own cost per meeting by format, which is more useful than any published benchmark. Our breakdown of what a year of conference sponsorship costs gives the cost side of that sum.
What to decide before the event
- Who owns the follow-up, by name. If it falls to whoever has capacity, it falls to nobody.
- Who captures content. A person working the booth cannot also film the panel.
- What the sponsorship says about attendee data. If the package includes no lead retrieval or attendee list, your lead capture is whatever your team scans and writes down by hand.
- Which format you are buying in the first place. A hosted dinner gives you a guest list to follow up with, and a booth gives you a pile of scans. We compare them in booth vs side event vs speaking slot.
Run the follow-up once, not once per event
A company that treats five events a year as five separate projects improvises the follow-up five times. Run as one programme, the lead capture, the content pipeline and the routing rules are built once and reused at every stop. A year of conferences then produces a pipeline you can measure, where before it produced five invoices.
That is how Powerclub Global (PCG) structures its roadshow management service: event selection, coverage and the 30-day follow-up are planned together before anything is booked. If you have an event coming up and no follow-up owner, schedule a call and we will go through the plan with you.
Frequently asked questions
How soon should you follow up after a conference?
Within 48 hours, while the person still remembers the conversation. Refer to something specific they said or asked for. After about two weeks most attendees have been to other events or cleared their inbox, and your message reads like cold outreach from a stranger.
What should a conference follow-up email say?
Keep it to three parts: one line that proves you remember the conversation, the thing you promised (a deck, an introduction, a demo time), and one clear next step. Leave out the company overview. If you cannot recall the conversation, the note you took at the booth was too thin.
How do you measure conference ROI?
Track conversations logged, contacts qualified, meetings booked, pipeline created and cost per meeting for every event. Report meetings and cost per meeting at 30 days, and pipeline and closed revenue at six months, because deals that begin at a conference usually take months to close.
How many leads should a conference booth generate?
There is no benchmark we would trust, because badge scans measure foot traffic and not interest. Count conversations with a written note attached and meetings booked afterwards. A booth with 100 scans and 15 booked meetings has outperformed one with 800 scans and three.
Who should own conference follow-up?
One named person, chosen before the event, with time blocked in the two weeks after it. Sales staff returning from a conference are behind on everything else, so follow-up that belongs to the whole team tends to slip until the leads have gone cold.