Strategy, experience, and execution.
My work tends to fall into a few recurring shapes. Organizations whose event technology grew up separately across regions and business units and now want one standard. Stacks that accumulated over a decade and need an honest assessment. Flagship programs where the technology has one day to hold up in front of thousands of people. Manual workflows that quietly consume a team's capacity until someone maps them end to end.
Strategy
I decide what the stack should be before deciding what to buy. Data model first, then platforms. When tool selection happens before the data model is defined, you get an expensive system that produces unusable reports.
Strategy covers platform architecture and integration across registration, attendee experience, and the systems attendee data lands in. It covers the vendor portfolio, budgets, and the contracts that determine what an organization can offer and at what cost. And it covers the operating model, which decides whether technology gets pulled in while scope is still forming or handed a finished requirement after the expensive decisions are made.
Leadership and organization
I build and lead event technology organizations. That means restructuring roles, hiring, mapping promotion paths, setting development standards, and directing offshore and partner delivery, with the budget and multiyear outlook behind it.
I sit at the strategy table for the function. I have secured leadership approval for multiyear platform investments with a business case, a revenue model, and a phased transition plan, and built pricing models that turned technology scope into new revenue.
Experience design
I start with what an attendee should walk away feeling, then work backward to the technology that delivers it.
I design the experience myself, then direct the build with the production, creative, and technical teams who put it on the floor, so the idea that worked on paper still works when the doors open. That includes engagement that makes people feel involved without feeling their privacy has been invaded, and knowing which platforms can carry an idea before anyone commits budget to it.
Privacy and data governance
Attendees notice when data handling is careless, so privacy is part of the experience, not a step at the end. I partner early with Security, Privacy, Compliance, and regional Legal teams across the Americas, EMEA, and APAC, including Japan, so attendee data questions are settled well before launch.
That includes location based consent at registration, retention and disposal rules for every connected system, privacy reviews when onboarding new vendors, and accessibility standards across event platforms.
Platform selection and vendor evaluation
I write requirements that reflect how an organization operates, build scoring criteria that survive contact with a demo, and ask the questions that show what a platform does poorly.
Almost everyone consulting in this space came from a vendor. I have spent more than 17 years on the other side, selecting, implementing, negotiating, renewing, and replacing these platforms inside large organizations. Existing contracts are a design parameter I surface early, so they shape the plan from the start.
Platforms I have worked inRainFocus · Swoogo · Cvent · Amego · ShowUp · G2Planet · Brightcove · Okta for identity · Salesforce integrations · Power BI and Tableau for reporting · Azure DevOps and Jira for delivery
Building and migration
Four online registration systems taken from concept to launch for association trade shows. Registration and onsite technology for 25+ events a year at a research university, plus a university wide event request platform. A six year enterprise registration platform build after migrating off the legacy system. A repeatable event in a box technology kit that gave 100+ field events a year the same proven setup.
When no vendor could meet the requirement, I directed a team of developers on a custom content management system, designed to support 80,000+ attendees, and we hosted the event website and streamed events on it. I run delivery in sprints as a certified product owner.
Measurement and attribution
I connect registration and attendance to the accounts and campaigns the business already tracks, so leadership can see which events moved pipeline and whether an event worked. I have moved event reporting between platforms without losing that view.
Custom tools and automation
This is the work I love most. I find the manual steps eating a team's week before anyone asks, imagine the tool that would fix it, and build it myself, pairing AI development tools with what I know about how events run. The results range from tracking and follow up to live views of hours, budget, and capacity.
Security is part of the design from the start. Access is checked on the server, sessions are signed, databases stay closed to the public, and every tool is built to be safe in front of real teams and real attendee data.
Intake processes, guidelines, office hours, and shared knowledge sites keep the work consistent once the tools are in place.