If you work on the events side of an association, the math probably looks familiar. Budgets have been flat for years. Costs — venues, catering, AV, travel, talent — have not. And every year, leadership wants a bigger and better event than the one before. The conventional response has been to cut corners or work longer hours. Neither one is sustainable, and most event teams already know it.
But something else is starting to happen on the edges of the industry, and it's worth paying attention to.
A small but growing group of event professionals are no longer just planning events. They're building things. They're using AI tools to prototype custom solutions for their attendees, then handing those prototypes to technical teams for production. Noah Cheyer — who runs Silicon Valley Speakers Bureau and, in a fun bit of trivia, grew up nicknamed "Siri's brother" because his father co-created Siri — has had a front-row seat to this shift across the hundreds of event professionals he works with. The job description is quietly expanding. And the associations that recognize it first will have a real advantage.
Events teams sit in a peculiar position inside most associations: high visibility, high stakes, and chronically under-resourced compared to what's expected of them. They're often siloed from IT and product. They rarely get dedicated developers. They're frequently asked to deliver experiences that rival what for-profit conference companies put on, but with a fraction of the staff and budget.
That structural reality is what makes the current moment interesting. For decades, the gap between what event teams could imagine and what they could actually build was filled by either compromise or by long, expensive software projects that had to compete for the technical team's attention. Most of the time, compromise won.
What's changing is that the floor has lifted. The tools that were science projects two years ago can now do real work, and many of them don't require a developer to operate. Event professionals — who already think in workflows, attendee journeys, and edge cases — turn out to be unusually well-suited to using these tools, because they know exactly which problems are worth solving.
Here's a concrete version of what Noah is seeing.
An independent event producer is working with a healthcare conference. The conference has the same problem most large events have: attendees show up overwhelmed, unsure which of the hundred-plus sessions are actually right for them, and end up either skipping sessions entirely or sitting through ones that don't match their interests. The producer wants to give every attendee a personalized session calendar — recommendations based on their LinkedIn profile and the information they filled out at registration.
In a previous era, this would have been a feature request. The producer would have written it up, submitted it to the association's technical team, and waited in line behind every other priority on the roadmap. There's a reasonable chance it never would have shipped.
Instead, the producer uses a tool like Claude Code to build a working prototype themselves. It's not production-ready. It's not integrated with the registration system. It can't handle ten thousand attendees on its own. But it works well enough to demonstrate the concept end to end. The producer then brings it to the association's technical team and essentially says: here's what I built, can you take it to production?
That's a fundamentally different conversation than a feature request. The technical team isn't being asked to evaluate a hypothesis — they're being asked to harden a working artifact. The path from idea to launch gets dramatically shorter, and the technical team gets to do what they do best instead of building from scratch.
This is the shift in a sentence: the event professional isn't replacing developers. They're starting to operate like a product manager who can also prototype.
If you're an events leader trying to figure out where to point this energy, Noah uses a framework that translates well: rate AI's current capability for each task in your event workflow on a scale of 0 to 10. A 0 means "we never want AI doing this." A 10 means "you should already be using AI for this today." Most tasks land somewhere in the middle, and the exercise of scoring them is half the value.
Two anchor examples make the framework concrete.
A clear 0: on-site event execution. When a vendor doesn't show. When a session room has the wrong setup. When an attendee has a medical issue, or a speaker is stuck in traffic, or the registration line is somehow already three hundred people long thirty minutes before doors open. These situations require a human who can read a chaotic environment, make a call, and be accountable for the outcome. AI in that environment tends to be a "yes, and" machine — it confirms what it's been told, misses what it hasn't, and offers cheerful suggestions when what you actually need is someone running across the venue. You need a person.
A clear 10: post-event qualitative analysis. Surveys generate hundreds or thousands of open-text responses that humans rarely have time to read in full. The result is that the most interesting feedback — the patterns that show up across responses, the themes nobody asked about but multiple attendees raised on their own — usually gets lost. Modern AI tools can ingest hundreds of pages of feedback in a single pass and surface those patterns reliably. What sessions resonated. What themes came up unprompted. Where the experience fell short. This is the kind of analysis that used to take a researcher weeks and now takes an afternoon. If you're not doing it, you're leaving real intelligence about your members on the table.
The exercise we'd encourage: pick fifteen to twenty tasks your team handles in a typical event cycle. Score each one. The 8s, 9s, and 10s are where to start. The 0s and 1s are where to leave humans alone. The middle is where the conversation gets interesting and where most of your team's judgment will need to live.
If event professionals are starting to operate like product managers and prototype builders, three things follow at the leadership level — and they're worth taking seriously now rather than after your competitors do.
The skill profile is changing. The most valuable event professional five years from now is probably not the one with the deepest vendor rolodex (though that still matters). It's the one who can spot a workflow bottleneck, mock up a solution with AI tools, and partner with technical teams to ship it. When you hire your next events role, the question isn't only can they run an event? It's also can they identify problems worth solving and bring you something to react to?
The reporting structure may need to change too. When events teams start producing prototypes that touch member data, attendee personalization, and integrations with other systems, the line between "events" and "technology" gets blurry fast. Associations that keep events fully siloed from IT will find themselves blocking their own people from doing the most valuable work. The fix isn't a reorganization for its own sake — it's making sure the events team has a real partnership with whoever owns the tech stack, with clear ways to hand off prototypes for production.
Small associations may benefit the most. Counterintuitively, the associations with the smallest staffs and the tightest budgets are where this shift creates the biggest leverage. A team of three that can prototype its own tools is suddenly competitive with a team of ten that can't. If you've been running an events function with limited resources and feeling like you're falling behind, this is the moment that gap can start to close.
Flat budgets and rising expectations aren't going away. The associations that try to solve that equation through sheer effort will keep falling behind, no matter how talented their people are. The ones that recognize their event professionals as builders — and give them the tools, the permission, and the partnership with technical teams to operate that way — are quietly setting themselves up to deliver the kind of attendee experience that used to require a much larger organization.
Most job descriptions for event roles still describe the work the way it looked five years ago. The actual work is already further along than that. The question for association leaders is whether you're going to wait for the title to catch up, or get ahead of it.