WedBuild
All-in-one wedding planner: RSVPs, seating, budget, etc
A year ago my wife Elise and I got married. I'm an accountant, she's an engineer — we assumed the planning would be the easy part. It wasn't. Our budget and guest list were two spreadsheets that never agreed with each other, and the "real" plan lived in a dozen open tabs.
The first thing we built wasn't a company. It was a QR code so our guests could scan and find their table, the room map, and who they were sitting with. People talked about it all night. That reaction is why WedBuild exists.
A year of evenings and weekends later, it's a live product: guest list, RSVPs, seating charts, budget and a wedding website that all stay in sync — change one thing, everything updates. Bootstrapped, built in Adelaide, paying customers.
Some decisions we made that go against the grain, and the reasoning:
One-time pricing (A$99/A$199), no subscription. Weddings end; a subscription to wedding software is a bit absurd. Churn isn't a bug in this market, it's the whole point.
A genuinely free tier (guest list, RSVPs, full wedding website, no time limit) — because that's what we needed most desperately in month one of our own planning.
We charge couples instead of selling vendor leads. The incumbents are "free" because the couple is the inventory. We didn't want to build that.
The tradeoff is obvious: every customer is one-and-done, so we live or die on a steady stream of newly engaged couples finding us. SEO and word-of-mouth are the whole game.
Curious about one thing from anyone who's been here: Every customer we win is gone in ~12 months by design. For those who've built in weddings, moving, job-hunting or similar 'one season of life' markets — what replaced retention as your growth engine?
5 Comments
I like that your pricing reflects how customers actually use the product. The interesting challenge now isn't retention—it's making each completed wedding increase the probability of the next customer. In markets like this, acquisition often becomes the product's long-term moat.
This is how we've started thinking about it too. Weddings are the one market where the customer assembles a room full of prospects for you — every guest is an engagement away (excuse the pun) from needing us, and the QR seating code is the one part of the product all of them touch on the day. The trick is doing something with that without turning someone's reception into an ad. Post-wedding, when guests come back to the website for photos, feels like the honest moment. Have you seen products that turned an end-of-life moment into the referral trigger? Would love an example.
That's a good question.
I do have a couple of examples in mind, but the more interesting part isn't the examples themselves—it's why I think they apply to what you're building. I don't think I could explain that properly in a thread without oversimplifying it.
If you're open to it, what's the best email to reach you on?
Of course, happy for you to email me anytime at admin@wedbuild .com
Thanks! I’ve just sent it over.
Looking forward to hearing your thoughts whenever you have a chance.