For more than one kind of gathering
Birthdays, showers, reunions, launches: a single maker builds the page and its guest list at the same time. Guests reply online, their answers attach to their names, and quiet ones get a gentle reminder.
You are not hosting the same party twice, so an invitation tool that only understands one occasion is a tool you will outgrow by the next season. The useful version is one maker that handles whatever you are throwing. The path never changes: describe the event, get a page drafted, add your names, publish, and share the link. What differs from gathering to gathering is the content of the page, not the way you build it.
The thread running through every use is the guest list. It is not an afterthought bolted on at the end; it travels with the invitation from the start, so a reply is not just a yes but a yes recorded against the right person.
Same maker, two different shapes, because the events ask for different things.
Intimate by design: a personal note addressed to the guest, a menu laid out course by course, and a one-tap acceptance. Where the evening is a surprise, the venue can stay hidden behind a password until they reply.
Built for a crowd: a details block, a schedule for the day, a dress note, and a FAQ. Guests confirm within plus-one limits you set, and answers collect against the guest list.
A reunion, a naming day or a work social borrows whichever structure fits. The list, the reply button and the reminders come with it regardless of which occasion you started from.
The reminder is the part hosts remember most. Chasing non-responders by phone is uncomfortable and, worse, inconsistent: some people hear from you three times and others not at all. When the guest list and the replies live together, the quiet ones are simply the ones still unanswered, and the follow-up reaches everyone fairly without you keeping score. One maker, any event, and the administration holds the same shape each time.
How it works
Start the maker and say what you are gathering for. A dinner, a birthday or a reunion all arrive as a real page rather than a special case you have to work around.
Enter the people you are inviting. Because the list belongs to the invitation, each reply will attach to a name instead of floating in your inbox.
Send the link and watch confirmations tick names off. The running total reflects reality, not read receipts.
Anyone still unanswered receives a gentle nudge through WhatsApp or email, so you are not left deciding who to chase and when.
Questions
Yes, because the two share the same backbone. Both are an invitation with a reply system and a guest list attached; they simply show different sections. The dinner leans on a personal note and a one-tap accept, the party on a details block, schedule and FAQ. You start from the nearer shape and adjust.
It does. The list is built alongside the page, so when a guest replies their confirmation lands against their own name rather than as an anonymous yes you have to match up yourself. That is what lets you see at a glance who has answered and who has not.
The page knows which names are still unanswered, so a reminder goes to exactly those guests through WhatsApp or email. You are not copying names into a list of who to phone; the follow-up is triggered by the gap on your own list.
They are not a dedicated event type yet, but you are not stuck either. You start from the closest existing setup, adjust the wording and details, and keep the same page, replies and guest list. What you avoid is only a purpose-built corporate design, not the tools themselves.
Get Started
Build the invitation and its guest list in the same motion, whether it is a dinner for two or a reunion for forty. Start free and keep the admin familiar each time.
