Events Won the Budget. Orchestration Is How You Prove the Return.
By Peter Micciche, CEO, Certain
TL;DR (the short answer): Events grew faster than any other marketing line this year, which makes them the next line finance will question. Proving their return is an orchestration problem, not a measurement problem. When the signals an event produces reach every team and system in real time, the evidence a budget review wants builds itself while the event is still live. When those signals sit in an export instead, a program that produced real intelligence walks into its review with nothing to show.Which line in your marketing budget grew fastest this year? In a year when almost every line is being questioned, the answer is events, and events used to be the hardest line to defend.
The IPA’s Bellwether report for the second quarter of 2026 found events leading every category for new investment, for the second consecutive quarter. Over the same period, marketers’ confidence in their own financial prospects fell to minus 25.1 percent. They are nervous about the year ahead, and they are still putting money into events.
Why are events the fastest-growing line in your marketing budget?
Events are the fastest-growing line because buyers still choose to meet vendors in person even when confidence in the wider outlook is low, and that choice shows up in where the money goes. The second-quarter Bellwether put events ahead of every other category for new investment for the second consecutive quarter, while marketers’ own confidence in their prospects sat at minus 25.1 percent.
The fastest-growing line is never safe for long. It is the first one questioned when budgets tighten, because a large and rising number invites the question of what it produces. Events just became that line, and the review is coming.
Why is your event budget under scrutiny right now?
Your event budget faces sharp scrutiny because leadership spent the first half of this year asking what its funded technology programs returned, and that standard does not retire when the AI review ends. It moves to the next fast-growing line on the page, and per the Bellwether, that line is events. Artificial intelligence on its own no longer sets an event program apart, and the bar now is measurable business value.
The evidence that the standard is real is in how companies are staffing. On July 26, 2026, Chip Cutter reported in The Wall Street Journal that companies from CSX to Alphabet have told investors they plan to add people again, after a long stretch in which major employers added headcount only as a last resort. Booz Allen’s chief operating officer said the firm needs to accelerate hiring because it has fallen behind, and ServiceNow is looking for quota-bearing sales execs to capture growth in cybersecurity.
Sarah Franklin, the chief executive of the HR platform Lattice, told the paper that many companies stopped hiring entry-level employees on the assumption that agents would cover the work, and have since found that people are necessary alongside AI. Companies running AI sales agents still need salespeople. The lesson leadership took from its AI review is that funded technology has to show what it returns, and the event line comes up for review with that lesson fresh.
Why does proof of event ROI so rarely arrive?
Proof of event ROI rarely arrives because the signals your events produce never travel to the places where they count. Your events already generate first-party signals from the prospects you most want to reach, in the questions they ask, the sessions they choose, and the problems they came to solve. Those signals stay stranded because the architecture was built to confirm attendance, not to carry intent.
The record of what happened comes back late, to one team, in a form built to confirm attendance. Everything a budget review wants to see, including which teams acted, what pipeline moved, and what it cost to produce, has to be rebuilt by hand weeks later. By the time that picture comes together, the quarter has closed, and the prospects have moved on. The number that finally emerges describes a moment the business can no longer act on.
None of this reflects on the teams running events. They execute them extraordinarily well, and the signals are produced exactly as intended. The architecture was simply never asked to carry those signals to the people who could prove their worth.
Proof begins while the event is still live, in how the signals move. When signals are orchestrated in real time into every system and team that can act on them and account for them, the proof comes together as a byproduct of the work. When signals sit in an export instead, there is nothing to assemble, and a program that produced real intelligence is unable to show it in a review.
This is the same readiness gap I described in why you do not have to wait to be AI-ready, seen from the budget side of the table.
What can five teams do with the signals from a single event?
A single event’s signals can do different work for five teams in the same window, and each team adds to what the others can see. Growth marketing accelerates a warm account while the interest still holds. Field marketing plans the next regional touch. Product marketing sharpens the message. Sales opens a real conversation. Customer success reads expansion or risk early, while there is still time to act.
Follow one event’s signals through those teams and the compounding becomes clear. Growth marketing moves a warm account into an accelerated program while the interest still holds. Field marketing learns which accounts came closest to a decision and builds the next regional touch around them. Product marketing hears which problems drew the largest audiences and sharpens the message against what prospects said rather than what the team assumed. Sales gets the context to open a real conversation instead of a cold one. Customer success sees expansion or risk early, while there is still time to act.
And finance, often for the first time, can see cost per opportunity by event type. Measurable business value looks like this in practice, with every team acting on the same signals while they are warm, and a shared view that ties the spend to the pipeline it created.
Without changing the event budget or the data collected, the return multiplies every time those signals reach another team that can act on them. Much of this starts at the door, which is where I made the case for the buying signals you can capture at check-in.
Each of those teams is also standing up an agent this year, and every agent runs better on a proprietary input that its competitors’ agents will never see. Each one also needs a person able to act on what the agent surfaces, which is the lesson the last eighteen months taught at some expense. You pay to orchestrate those signals once. In every quarter you do not, the interest cools, the teams work from stale exports, and the largest line on the budget goes into its review with little to show for itself.
Why does orchestration belong in the event foundation, not bolted on at the end?
Orchestration belongs in the foundation because a go-to-market stack that runs on agents acting in seconds cannot wait for a record exported after the event ends. Built in, orchestration moves each signal out of the event the moment it is created and into every system, team, and agent that can act on it or account for it, across every event you run, so the event returns something the business can use now.
For two decades, event platforms were designed to run the day, the registration, the agenda, the badge, and the venue. The data they produced was a record of what happened, exported once the event was over, because that was all anyone asked of them. That design was sufficient while the rest of the go-to-market stack moved at human speed. The stack now runs on agents that act in seconds, inside a business that expects proof in real time, and a record exported after the fact does not serve it.
Orchestration bolted on at the end as a batch export keeps producing a record that arrives too late to matter. Built into the foundation, it moves the intelligence out of the event while the moment is still live, and the event returns something the business can act on.
What question should you bring to your next event?
Your company has already decided to fund events, and to grow that funding faster than almost any other line this year. The harder conversation comes next year, when you and your finance partners review that line, now the largest and fastest-growing one you own, and ask together what it returned.
So here is the question to bring into the planning meeting for your next event. When the event is over and its signals are scattered across your teams and systems, will those signals have reached everyone who can act on them and account for them while the event was still live, or will the answer have to be rebuilt from exports long after the event has ended?
Frequently asked questions
How do you prove the ROI of your event program?
You prove event ROI by orchestrating the signals your events produce in real time, so the evidence assembles itself while the event is still live. When each signal reaches every team and system that can act on it and account for it, the record a budget review needs is a byproduct of the work rather than a reconstruction project weeks later.
Why is event spend under scrutiny right now?
Leadership spent the first half of 2026 asking what its funded AI programs returned, and that standard moves to the next fast-growing line once the AI review ends. Per the IPA Bellwether, events are that line. AI on its own no longer sets an event program apart, and the bar now is measurable business value.
What can five teams do with the signals from a single event?
Growth marketing accelerates a warm account, field marketing plans the next regional touch, product marketing sharpens the message against what prospects said, sales opens a real conversation, and customer success sees expansion or risk early. Finance, often for the first time, sees cost per opportunity by event type. The return multiplies each time the same signals reach another team.
Why should orchestration be built into the event foundation instead of bolted on?
A go-to-market stack that runs on agents acting in seconds cannot wait for a record exported after the event ends. Orchestration built into the foundation moves each signal out of the event the moment it is created and into every system that can use it, so the event returns something the business can act on now rather than a report that arrives too late.
Where to start
The full argument, with the plays that put this into practice, is in the Event Signal Playbook, free and ungated. The first part shows the plays you can run with data you already collect. The second, on orchestrating event signals at scale, is where the proof becomes a system.
Peter Micciche is CEO of Certain, the AI-powered Event Intelligence platform for enterprise B2B companies. Connect with Peter on LinkedIn or visit certain.com to learn more about turning events into revenue.