For tonight's build, next weekend's party
Invitation and guest list in the same sitting: pick the design, write the invite, switch replies on, send. One evening later there is a page that counts, and you are done.
With the date and venue settled, an invitation is an evening's work. Design, wording, reply settings — an hour of decisions, then send. The build balloons only when the page and the RSVP are treated as two separate projects; together they are one pass, because you write the invitation knowing exactly what guests will answer on it. While you are in there, decide what the reply should ask for: anything you do not genuinely use, leave out — guests answer short forms gladly and avoid long ones.
And replies on the same page mean nothing to reconcile. A confirmation is a tick against a name, a plus-one arrives inside your limit, and the food notes sit where the heads they belong to sit.
The build order is identical; what you switch on differs:
Replies count children and parents separately, an allergy note travels with each child's confirmation, drop-off and pick-up times sit in the details block, and the guest limit holds the class list short. Favours get ordered from confirmed names instead of hope, and one line about who collects whom stops the four o'clock panic in the parent chat.
A firm plus-one rule and a hard deadline, the dress code named against the theme, song requests attached to replies, and the drink note settled — hosted bar or cash. The meal choice matters more than the guest count when dinner is booked.
The reward arrives at the venue. Your phone holds the same list as the page: who confirmed, who named a plus-one, who eats no meat. Reminders to the not-yet-answered can go out on the drive there, and a late confirmation still lands on the same screen. If the count is stale by eight o'clock, it is only because the plan moved — and the page will have moved with it.
How it works
Kids' confetti layouts or the darker evening palettes — birthday designs are separate families, so choose the one matching the room you are picturing.
Story, times, venue, theme line. Suggestions give you a first sentence; edit until every paragraph sounds like you.
The plus-one limit, the deadline, and whichever fields fit the crowd — meal choices for dinner, allergies for a kids' afternoon, song requests for a dance night.
Nothing is visible before publishing, so build as freely as you like. Send the link to WhatsApp or SMS tonight, and replies start while you are still picking out the playlist — then put the phone down, the counting keeps working without you.
Questions
For a party, RSVP is the reply mechanism: yes or no, who is coming, and the notes you asked for. Proper registration with capacity tiers and per-attendee access links belongs to webinar and virtual events, which are separate products. A party guest needs a name on a list, not a private join link.
Yes. Meal choices and allergies come with each reply, which is exactly what a kids' afternoon needs — the information arrives at confirmation instead of as a panicked text the night before.
Add collaborators with their own access levels — the co-host, the person handling wording, whoever. Everyone works from the same list rather than three versions of it.
Sure. Send to the family group first, close friends a day later, colleagues when the plan firms up. The guest list keeps ticking along regardless of which wave a reply came from.
Publish with less. Empty sections simply do not appear on the page, so the invitation looks finished; add the dress note or meal fields when those details land.
Get Started
Design, wording, and replies decided together — the page is sent tonight and counting tomorrow morning.
