The Wedding Site Studio

Why we built it

Wedding websites tend to fall into one of two camps. The first is a template with the couple's names dropped into it, which looks acceptable and collects RSVPs into a spreadsheet nobody can use. The second is a guest management tool that works properly and looks like admin software.

A wedding is one of the few things people genuinely care how it looks, and it also has real logistics attached - headcounts, dietary requirements, multiple events, guests arriving from different places and needing different information. There was no reason those two things had to be separate products.

What it does

Every household receives a personal link that already knows who they are. No accounts, no passwords, nothing to install. They answer for each person and each event - the Friday drinks, the Saturday wedding, the Sunday brunch - rather than a single yes or no for the household, and they can change their answers until the deadline.

Dietary requirements, children's meals and allergies are collected as guests reply and exported clean for the caterer, instead of being reconstructed from messages three weeks before the day.

Invitations go out by email or WhatsApp, whichever each guest actually reads, and are sent and tracked from a dashboard. Guests staying on site see different travel and accommodation guidance from those booking their own rooms, so nobody is reading instructions that do not apply to them.

The couple and their planner share a live headcount that can be handed straight to the venue.

Why it matters here

It is a working product rather than a demo, which makes it the clearest evidence of what this studio does beyond websites: a multi-tenant application with real data, real sending and a real dashboard behind a design that had to stand on its own.

It also runs on the same principle as everything else we build. The design is made for the specific wedding rather than selected from a menu, and the system underneath is built to do the boring work properly.