How it works
You send the details once. That's the job.
The whole reason this exists is that wedding website builders turn into another thing on the list. This one doesn't, because you are not the one building it.
A fifteen minute call
Not a demo and not a pitch. Questions about your day: the venue, the rough running order, how many guests, who is coordinating it, and what is already turning into a faff. Most of the value in this call is working out whether you actually need it.
One form, once
Guest list, timings, venue details, dress code, dietary questions, the parking situation, gift registry links, and anything you have already had to explain more than twice. If you have a spreadsheet, send the spreadsheet. Nothing here needs you to go and find out something new.
It comes back built
Within a week. You get a link, open it on your phone, and see the actual thing rather than a mockup. Then you tell me what is wrong with it and one round of changes goes in.
Your guests get a link
And a QR code for the invitations if you want one printed. They tap it, enter the code, and they are in. No download, no account, no password to forget.
Then it does the work
RSVPs come in, dietaries collect themselves, and the questions stop. In the fortnight before the day, changes are usually same day. On the day itself the timeline updates as things move, which they will.
After
It stays live for twelve months so everyone can get the photos. You can extend it, or turn the photo wall into a printed book.
What I need from you
Roughly an hour, total.
- Fifteen minutes on a call
- Twenty minutes filling in one form
- Twenty minutes reviewing it and saying what to change
- Nothing on the day
No account to set up. No builder to learn. No support tickets. Changes go to a person in Brighton who answers.