One engine, many gatherings

One event record. Every operational handoff stays connected.

Mezze starts after the venue, flights and hotels are booked. Add people once, then use that shared record to run registration, assignments, program, rooming, transport and the documents your vendors need. When an input changes, Mezze highlights the plans it affects.

For company offsites For weddings

Change one thing. Mezze tells you what else must change.

This is the whole product in one sentence. A guest's flight slips three hours — that is not one edit, it is five: the shuttle they were on, the driver's manifest, the rooming list, the dinner headcount, and the first session they will now miss.

Spreadsheets hold information. Project tools hold tasks. Neither knows that these five things are connected. Mezze does, because they all come from the same record.

Where it came from

A 200-guest, 45-nationality, three-day wedding on a Greek island — run on eleven Excel tabs, a hand-annotated floor plan, and a timeline nobody trusted by six in the evening. Every failure that weekend was a coordination failure, not a planning failure. The plan was fine. Keeping five documents in agreement with each other was the impossible part.

So we built the layer that should have existed: one list of people, and every operational document generated from it.

Two front doors, one engine

Mezze for weddingsSeating that understands family politics, RSVPs that collect meals and hotels, a timeline that recalculates, shuttle manifests. Built for couples and independent planners running multicultural and destination weddings. Mezze for company offsitesAttendee operations after the flights are booked: registration, rooming, arrivals, breakout groups, program and shuttle waves. Built for the EA, Chief of Staff or People Ops lead running 30–300 people.

Same accounts, same engine, same exports. The vocabulary, templates and defaults change; the machinery does not.

What the engine actually does

One record per person — dietary needs, accessibility, travel, lodging, group assignments and follow-up state, entered once.
Constraint-aware assignment — seat or group hundreds of people around keep-apart rules, departments, families, accessibility needs and capacities, in seconds.
A program that recalculates — pin the immovable commitments, and everything else moves when reality does.
Documents that write themselves — rooming lists, driver manifests, kitchen sheets, run of show, place cards. Exported in the formats hotels, caterers and drivers actually accept.
Readiness checks — a live list of what is missing and who it belongs to, before it becomes a day-of problem.

What we deliberately do not do

Mezze does not book venues, sell flights, sell tickets, or take a commission on anything. Those markets are well served and monetised through the transaction, which is exactly why nobody builds the operational layer underneath. We start after the confirmations arrive.

Where it goes next

Two doors are open and validated: complex weddings and internal company gatherings. The same engine fits other gatherings where people, time, rooms, food and movement depend on each other — but we add a door when a customer pays for one, not before.

See it for offsites Talk to us