
If you've ever tried to justify the cost of a corporate event, you'll know the uncomfortable moment when someone asks for the ROI. The instinct is to reach for numbers - how many people came, what they scored the catering, what the cost per head worked out to. These numbers are easy to gather and easy to present. They're also almost entirely useless.
Attendance tells you how many people were in the room. It tells you nothing about whether the room was full of the right people, whether they spoke to each other, or whether anything changed as a result. A packed room of the wrong audience is a worse outcome than a half-empty room of the right one.
Satisfaction surveys, when they're filled in at all, tend to measure the wrong things. Was the food good? Was the venue nice? Was the speaker engaging? These are questions about delivery, not outcomes. A perfectly delivered event that changes nothing is a well-executed waste of money.
Cost per head is the most misleading metric of all. It tells you how much you spent. It tells you nothing about what you got. An event that costs £200 per head and produces a single meaningful new client relationship has a dramatically better ROI than one that costs £50 per head and produces nothing.
The real return on investment in an event is almost always relational. It shows up as a client who calls you a month later with a question they wouldn't have thought to ask before. A prospect who, having met your team in person, moves through your pipeline faster. A relationship that deepened so quietly nobody noticed it happening. An employee who mentions the offsite as the moment things started to click.
None of these outcomes arrive with a receipt. None of them can be neatly attributed to the event in a spreadsheet. But they are the entire point.
Instead of asking "how many people came?", ask "what should be different after this event than before it?" before the event even begins. The answer might be stronger client relationships, warmer prospects, better internal collaboration, increased engagement, or greater industry authority.
Once you know what you want to be different, you can design the event to produce it - and look for it afterwards. The measurement shifts from counting to observing: who followed up, what conversations continued, what changed in the weeks that followed.
Event ROI is harder to measure than people pretend. The things worth measuring are slower to surface, harder to attribute and less satisfying to present in a board meeting. But they're the only things that matter.
If you design events around relationships and outcomes, the return will come - quietly, slowly, in ways that are hard to put in a report but impossible to ignore. If you design events around headcounts and satisfaction scores, you'll get exactly what you measured: numbers that look good in a slide deck and tell you nothing about whether the event was worth doing.
The choice isn't between measuring and not measuring. It's between measuring what's easy and measuring what matters.
How do you measure event ROI? Start by defining what you want to be different after the event. Then look for those specific outcomes - follow-up conversations, relationship changes, commercial momentum - in the weeks and months that follow.
What's a good ROI for a corporate event? It depends entirely on the objective. An intimate dinner that produces a single high-value client relationship can have extraordinary ROI. A large conference that generates no follow-through has poor ROI regardless of attendance.
How soon after an event should you measure ROI? Immediately for operational feedback. But the real ROI unfolds over weeks and months. Check in at 30, 60 and 90 days to see what conversations continued and what relationships changed.