For the host who ends up ordering the cake
A builder that stops at a pretty page leaves you with the hard part. This one ties every design choice to a count — guests, plus-ones, meals — so the list is ready before you order anything.
The mechanics are three moves. Pick a design from the birthday library, and the page takes its shape — headings, colours, the rhythm down a phone screen. Fill the details block, which wants the date, times, venue, and the one or two notes guests would otherwise text to ask. Switch on replies, and the builder separates itself from a poster maker: every guest who confirms lands in a live list under their own name.
Nothing is locked in. Swap the design halfway through and the details carry over. Leave a section empty and it simply does not appear on the page, so a half-built invitation looks deliberate instead of unfinished.
Birthdays are calmer than weddings but demand more counting, because nobody budgets six months for them:
Each reply ticks a name off and the running total grows in front of you. No tallying by scrolling backwards through a chat.
Guests bring someone only within the limit you set, and each plus-one is recorded against the person who invited them.
Meal choices and allergies arrive attached to the reply, so the catering list writes itself while there is still time to change it.
When the baker or the venue calls for final numbers, the list leaves the page instead of being read out to you over the phone.
Three settings decided in the builder save arguments later:
None of this is clever for its own sake. It exists because the alternative is worse: ordering on vibes, setting out plates by feel, and discovering at half past four that the numbers never added up. Build the page once, and the counts come with it.
How it works
Birthday templates come in separate families for kids' parties and adult evenings, so pick the tone before the wording. You can change it later; choosing early just means the drafting suggestions fit the room you are imagining.
Set the plus-one rules and the reply deadline now. Guests who reply against a clear rule do not negotiate it later, and the headcount stays clean from the first confirmation.
Date, times, venue, directions note, parking. Publishing is the gate — nothing is visible to guests until then, so build as openly as you like and open the door once.
Share to WhatsApp or SMS, and replies gather against names. Reminders to non-responders go out without you typing another follow-up.
Questions
Yes. The link stays fixed, so a design swap or a reworded details block appears on every phone that opens it afterwards. Edit early where you can, though — guests screenshot invitations.
No. Replying happens straight on the page. Accounts are for hosts and collaborators managing the event, not for the people confirming a place at it.
When you invite a family, each member can sit on the guest entry, and the reply shows exactly who is coming. The number you order from is the number that is confirmed, not a guess from a name on a card.
Yes — add collaborators with their own access levels. This is how a party hosted by three friends stays one source of truth instead of three competing versions of the guest list.
A free plan covers the start, and you upgrade as your guest list grows. Actual prices live on the pricing page rather than in guessed figures here.
Get Started
Build the page, set the reply rules, and let the cake order rest on confirmed names instead of read receipts.
