Monday. 11:20 PM. Nineteen days before doors open.
An operations lead, on the phone, reading registration numbers off four different spreadsheets that didn't agree with each other.
"I genuinely don't know how many people are coming," she said. "And we sold out three weeks ago."
Conference Technology — Nimbus Summit
Building the backbone nobody sees
Nimbus Summit — Conference Technology
01
The Challenge
1,200 seats sold across four separate booking channels, none of which talked to each other. Every category swap, cancellation, and comp registration was being reconciled by hand.
02
The Thinking
There wasn't time to build a new platform. There was time to build the layer that made the four existing systems agree with each other — a boring, correct fix, not a clever one.
03
The Execution
We mapped every registration path and addon across all four channels, then built a reconciliation engine that flagged conflicts instead of silently overwriting them. Every change produced a manifest a human could review in minutes, not a database update nobody could audit.
Shipped nine days before the event. Migrated eleven days of backlog in one overnight run. Ran live sync through doors-open.
04
The Outcome
Check-in ran with a verified attendee count for the first time in the event's five-year history. Zero double-booked seats. Zero manual overrides needed on-site.
05
Lessons Learned
The unglamorous fix — reconciliation, not reinvention — was the one that actually saved the event.