Setup that seeds itself
Pick “Wedding” and the events, workstreams and checklists arrive already built — Haldi, Sangeet, Reception. Nobody starts from an empty page.
The whole thing, once through
From “yes” to “I do”
Every flow of a wedding — one continuous journey. Sixty-six seconds covering every flow a wedding actually needs — hosts, planners, teams, vendors and guests, on one thread.
0:00 / 1:06
Brand title settles over warm paper
Loading the film…
What each stretch is proving
One timeline, every dependency
Ceremonies get dates, venues and a Lead. The master timeline surfaces the critical path and flags the one conflict worth arguing about.
338 guests, zero accidental messages
Importing a list never notifies anyone — invitations are always an explicit act. A guest RSVPs from a link in about thirty seconds, with no app and no login.
Vendors are not guests
They live in their own records, mapped to workstreams, so a caterer can never land in a guest count, an RSVP total or an “invite all pending” blast.
A delay handled in one tap
The baraat runs twenty minutes late. One change propagates to the run sheet, the team and the shuttles — and the guest simply sees the new time.
The celebration closes properly
Photos flow to a shared wall, vendors get rated, payments settle, and the whole thing archives — so the next celebration starts from something real.
One celebration. One thread.
Start with the part you are dreading most — the guest list is usually it.