It starts with the couple, not a blank page
The planner sends the couple a short questionnaire. Their answers, dates, guest estimate, formality, the words they want the day to feel like, flow straight into the wedding record and the design brief.
Why it matters: the planner opens a wedding that already knows its own shape, instead of re-typing everything the couple said on a call.
Venue first, then one design direction
The venue is set before anything else, with its seated capacity, music curfew and vendor load-in times as real fields. Then a single aesthetic direction is agreed, and each moment of the wedding, ceremony, dinner, the after-party, is designed against it.
Why it matters: the room decides the seating, the curfew decides the schedule, and one agreed direction keeps every vendor brief consistent.
A guest list that understands a whole weekend
Guests are added by hand or imported from a spreadsheet. For a wedding weekend, each guest can RSVP to each event on its own, so a guest who comes to the wedding but skips the welcome dinner is counted correctly for each night.
Why it matters: the catering count, the transport and the seating each read the right event, so nobody is over-catered for on Friday and short on Saturday.
The room, drawn to scale, seated around real relationships
The reception room is drawn to scale. Auto-seating places every attending guest around the rules the planner sets: keep-together for families and couples, keep-apart for the relatives who should never share a table. When a group is too big for any free table, Mezze asks before splitting it rather than doing it quietly.
Why it matters: this is the part planners dread, and it is the part software usually gets wrong by treating a seating chart as a spreadsheet column.
Transport and the run of the day, checked for conflicts
Shuttle waves, arrival windows and the schedule are laid out together. Mezze flags the things that quietly go wrong: two moments that overlap, a handoff with no owner, ten minutes to move a whole wedding between two rooms, or a first dance that runs past the venue curfew.
Why it matters: these are the details a planner holds in their head and occasionally drops. Mezze holds them instead.
Every vendor gets exactly the document they need
A kitchen sheet with covers and dietary counts for the caterer. A floral brief with the palette and the approved references for the florist. A driver manifest for transport. A seating chart for the venue. Each is generated from the live wedding record, so when an RSVP changes, Mezze tells the planner the caterer's sheet is now out of date.
Why it matters: the planner never rebuilds a document by hand, and never sends a vendor a count that quietly went stale.
It is not a CRM, a proposal tool or an invoicing suite. Planners keep those. Mezze is the operational layer for the wedding itself, the part that happens after the contract is signed, and it is built to sit alongside whatever a studio already runs its business on.
Questions planners ask
Can Mezze keep certain guests from sitting together?
Yes. Set a keep-apart rule on a guest, for example divorced parents, and auto-seat never puts them at the same table. Keep-together rules hold families on one table, and Mezze asks before splitting a group when no table has room.
Does it handle a multi-day wedding weekend?
Yes. Each guest RSVPs to each event separately, and every count, catering, transport, seating, reads the correct night.
What does it cost?
Free for one active wedding, unlimited guests, every feature. Paid removes the one-wedding limit for planners running several at once.
Do couples get their own view?
Yes. The couple is invited into a shared workspace to answer questions, approve design directions and see their guests and seating. They never see the budget, vendors or private notes unless the planner shares them.
See it with a sample wedding
Open Mezze, choose "Explore a sample wedding", and the whole flow above is already populated. No account needed to look around.
Open a sample wedding