Events
One platform. Every kind of event.
Productions with moving parts do not care what you call them. The same checklist, budget and guest list run a four-day wedding, a three-hundred seat conference and a charity gala.
Seven kinds of production
Pick the one you actually run.
Each has its own templates, its own vocabulary and its own shape of timeline. The workspace underneath is the same.
Weddings
A wedding is rarely one event. Mehndi, ceremony, dinner and next-day brunch each get their own timeline, floor plan and call sheet, all hanging off a single guest list and a single budget. Move the date once and every one of them moves with it.
Multi-day builds · household RSVPs · per-event seating
Corporate
Conferences, offsites, launches, AGMs and holiday parties. Delegates instead of guests, sessions instead of a run of show, and a budget that has to reconcile against a purchase order. Approvals sit on the event itself rather than in somebody’s inbox.
Sessions & speakers · badge lists · PO-ready budgets
Galas & fundraisers
Charity dinners, awards nights and benefit galas. Tables here are sold, not just seated, so the seating chart and the money are the same record. Sponsor tiers, table hosts and the order of the evening all live in one place.
Table sales · sponsor tiers · run of show
Birthdays & milestones
Sweet sixteens, quinceañeras and landmark birthdays. Smaller than a wedding and just as particular: one household list, one supplier sheet, and a run of show that fits on the single page a venue will actually tape to the wall.
One-page call sheets · supplier lists · day-of timing
Engagements & showers
Engagement parties, bridal showers and baby showers. Usually planned by three people at once, which is exactly where they go wrong. Everyone works from the same list, the same headcount and the same budget instead of three group chats.
Shared editing · live headcount · split costs
Cultural & religious
Mehndi, sangeet, mitzvahs, baptisms and festival days. Multi-day by default, with families on both sides and vendors who need one page rather than the whole file. The words in the interface change to the ones your families already use.
Multi-day · two-family guest lists · vendor-only views
Social & community
Reunions, retirements, graduations and community festivals. Volunteer rosters, ticket counts and a headcount that keeps moving until the week of. Everyone who has a job knows what it is and when it starts.
Volunteer rosters · ticket counts · moving headcountsWhat stays the same
Six tools, whichever event you are running.
This is the part that does not get rebuilt per vertical. A conference and a wedding both need to know who is coming, what it costs and what happens at 4pm.
Checklist
Every task, owned by someone, rolled up into a this-week view across all your sub-events.
Calendar
Move a date and everything hanging off it moves with it, including the vendors you have to tell.
Budget
Quoted against actual, per line and per event, so you find the overrun while you can still fix it.
Guest list
RSVPs, dietary needs, plus-ones and seating, held in one record rather than five spreadsheets.
Layout
The floor plan and the seating chart are the same object, so moving a table moves the people on it.
Documents
Proposals, contracts and run-of-show sheets, built from your templates and signed in place.
Every one of these is in every plan. See what changes between them.
What changes
Four things, and they are the four that matter.
This is the honest answer to whether it is built for your kind of event. Nothing underneath is rewritten per vertical, and these four are not cosmetic.
Everything else on this page is identical across all seven.
The checklist you start from
Each event type opens with a task list built for it, not an empty page you fill in from memory at the end of a long day.
For example a conference starts with AV walkthrough and badge collection; a wedding starts with the ceremony rehearsal.
What the fields are called
The words in the interface change to the ones your clients and vendors already use, so nothing has to be translated in a handover.
For example a wedding has a couple and a party; a conference has a host, delegates and speakers.
How long the run-up is
The shape of the countdown differs by event, so the milestones sit where they actually fall rather than on a generic curve.
For example a destination wedding plans over eighteen months; a corporate offsite is often six weeks.
What you have to ask for
The RSVP form carries the fields that event needs and leaves out the ones it does not, so guests are not asked irrelevant questions.
For example one asks about dietary needs and a plus-one; another asks which sessions and whether a hotel is needed.
Begin here
Run yours on it.
Whichever of the seven you are planning, the fastest way to know whether it fits is to put a real one through it.
One month free. No card to start.