Every guest. Every room, car and seat. One place.
Your guest list stops being eleven tabs and becomes one record per person — with their travel, their room, their car and every conversation attached. Starting from the spreadsheet you already have.
In events since 2014
Built by someone who works events for a living, not by a software company.
Running guest management since 2022
For real clients, on the same spreadsheets this is meant to replace.
Nothing locked in
Export everything, any columns you like, whenever you want.
Spreadsheets hold the data. They can't hold the relationships.
Which is why the same guest gets typed in eleven times, why the headcount is a guess, and why the full picture of one person doesn't exist anywhere.
The same guest, eleven times.
RSVP, rooming, transport, seating — each its own tab, each its own copy of the same person, each quietly drifting from the others.
A headcount you can't defend.
One row means one guest. Or a family of four. Or a family of four and a companion nobody added. Counting rows counts nothing.
Ten minutes to answer one question.
“What's happening with Mr. Sharma?” Three files, two tabs, and a call to whoever touched it last.
Nobody remembers who said what.
You know he was called. You don't know by whom, when, about what — or what somebody promised him.
Same file. A real system underneath it.
Three steps, and the first one is the file already sitting on your desktop.
- 01
Bring in the file you have
Any shape, any layout. One row per guest or one row per family — both work. You say what the columns mean, once.
- 02
It becomes people, not rows
Guests, families and parties come out the other side as real records that can no longer drift apart.
- 03
Everything attaches to the person
Rooms, cars, seats, conversations — added when you need them, hanging off the guest they belong to.
Buy the part you actually need.
Some companies run the whole guest journey. Some only run transport. Both are complete products here, and neither one depends on the other.
Guest communications
RSVP status, travel details and the chasing that goes with them — with every conversation kept on the record.
Hospitality
Room inventory and allocation. Who's sharing with whom, who needs an extra bed, and who still has no room at all.
Logistics
Arrivals, departures and movements. Vehicles, drivers, duty types, and what each one is costing you.
Rooms, vehicles, charter seats and tables all work the same way: people go into a limited thing, capacity is checked as you go, and the list of who still has nowhere to be is never more than a glance away.
Turn one module on today and another next month. Nothing needs re-importing, and nothing you've already done breaks.
Everyone records the last conversation. Nobody records all of them.
The part that saves you when a guest asks why something changed, and the reason nobody has to remember what was agreed in March.
When a guest calls to ask why their room moved, you can see who spoke to them in March, what was agreed, and what somebody promised — instead of a cell that says “called”.
Every interaction carries its channel, its date, the person who had it, and whether it left something open. None of it is overwritten when the guest's details change later.
They see their part. Not the whole file.
Your transport coordinator needs arrival times and drop points. They don't need the family's private notes sitting four columns to the right.
Access is set per event and per person, down to the individual field. The same freelancer can run the door at one event and see nothing at all at the next.
Which means you can stop solving this the way everyone solves it today — by keeping a second, sanitised copy of the file and hoping the two never drift apart.
Works where the signal doesn't.
Venues have bad network. That's the real reason your team is still on a local file — and it's designed for, not argued with.
Built for a phone, not a laptop
Find a guest by name, mark them arrived, move on. One guest at a time, in a crowd, in the dark.
Keeps working offline
Updates queue on the device and sync themselves the moment there's signal again. Nobody waits for a bar to appear.
The office sees it happen
Arrivals, check-ins and placements land on the dashboard your client is watching, as they happen.
You always hold a complete copy.
Your spreadsheet stays current automatically — in your own Drive, or on your own machine. Not an export you have to remember to run. A copy that's simply always there.
To be exact about it: that copy carries your data, not the app's structure. The permissions, the history and the dashboards live here.
But if this disappeared tomorrow, your guest list would still be sitting in the file it has always been in — current, complete, and yours.
The three things you're probably thinking
“We already work in Excel.”
Good — bring the file in exactly as it is. It gets read in whatever shape it's in, and handed back the same way whenever you want it.
“Our team isn't technical.”
Neither am I, by trade. Upload a file, see your guest list, carry on. There's no setup to work through before it's useful to you.
“We only handle transport.”
Then turn on transport and nothing else. You'll never see an RSVP screen, and you can add the rest later if you ever want it.
See it running on your own guest list.
I'm working with a small number of teams before opening this up. Tell me what you run, and I'll show you how it fits.