Skip to content
All work

Product build · 2026

Everly Wedding Planner

A wedding planner that keeps the whole wedding in one place — budget, guest replies, seating, suppliers, checklist and the wedding-day run sheet — with an assistant that reads the plan before it answers.

Role
Design, front-end and back-end
Stack
Next.js App RouterTypeScriptMongoDBTailwind CSSStripeTurnstile
Live
everly-wedding-planner.vercel.app
Source
GitHub
The Everly landing page

01What the build involved

01

One plan object, eleven views

Every tab — overview, budget, guests, seating, suppliers, checklist, wedding day, details, honeymoon, assistant, share — reads and writes a single plan document. The numbers that matter are derived in one place: cost per head comes from the budget split and the confirmed guest count, committed spending comes from the budget lines, and overdue tasks come from the checklist and the wedding date. Tabs can disagree about layout, not about arithmetic.

02

An assistant that can see the plan

The assistant is not a chat window bolted to the side. Before a question is answered, a brief is assembled from the plan — what is committed against the budget, which invitations are still unanswered, what is due next — and that brief is what the model reasons over. The reply talks about this couple’s wedding, using their own numbers, instead of generic planning advice.

03

Guests reply without an account

Owners share a link; each guest gets a reply token and answers for their own party, so an eighty-guest list never needs eighty sign-ups. Lists can be pasted in or imported from a CSV, and everything guests type is sanitised before it lands in the plan — the couple’s data stays theirs, and the reply page never sees the budget.

04

A beta with a queue

The plan is capped at fifty accounts. When the last one is taken the site switches to a waitlist rather than quietly degrading, paid access and donations run through Stripe checkout, and Turnstile guards the public forms. Accounts keep login, recovery codes and a guarded plan route so a returning couple lands back where they left off.

05

Printed matter from the same data

The invitation card, the print-friendly run sheet and the QR code that links to the invitation are generated from the plan itself, with six colour palettes and an optional custom heading. Change a detail in the app and the card follows — there is no second copy of the wedding to keep in sync.

02What it left behind

Outcome

A capped beta of fifty accounts with a waitlist that takes over when the last one is taken, live at everly-wedding-planner.vercel.app. Budget, replies, seating and the run sheet all resolve against one plan, and a guest can answer for their party without an account.

Another pass

The eleven tabs each grew their own fields, so the plan document now carries data that only one view reads. A second pass would group the fields by the question they answer and delete the ones nothing reads. I would also cache the assistant brief: assembling it on every message is the expensive part, and it changes far less often than the questions do.

03Inside the product

Each tab is a view over the same plan: the guest count feeds the cost per head, and suppliers feed the budget rather than sitting beside it.
Starting a plan asks only for two names and a date. The budget split and the 45-day checklist are derived from that, so the first screen is not a form of thirty fields.

Click any screenshot to view it full size

Next case study

Safety, Sparkle & Green

A booking site for a Scarborough cleaning company: priced services, a two-minute request form, and an admin dashboard that runs the week — with bookings in MongoDB and email confirmations that stay optional.