A real project, run with tools that don't talk to each other
The guest list is in one spreadsheet, the budget in another, vendor quotes in the mailbox, the seating plan on a sheet of paper, and decisions in a chat thread nobody can re-read. Every question — “who hasn't replied?”, “how much is left on the catering budget?” — means cross-referencing several sources.
As a couple it's worse: files diverge, you annotate different versions, and nobody's sure they're looking at the right one.
Your wedding, described then generated
Describe your setup: “We're planning our wedding. We have guests (with table, dietary needs, reply status), a budget per category (catering, venue, photographer, flowers), vendors with quotes and deposits, and a countdown of tasks with due dates. We want to see who hasn't replied, how much is left per category, and which tasks are late.”
Blueprint Maker generates the matching application: guests and their replies, the budget and its categories, vendors and their payments, tasks and their due dates — and a dashboard answering your real questions.
Your budget categories, your guest groups, your milestones become the structure of the application, because it's your description that draws it.
- Guests: table, dietary needs, reply status
- Budget per category with spent / remaining
- Vendors: quotes, deposits, balance
- Countdown of tasks with due dates
- Dashboard: replies, budget, overdue tasks
Shared between two (and with the witnesses) on one URL
The application is a web application at its dedicated address. Both partners — and the witnesses if you want — access the same up-to-date data, from phone or computer. No more contradictory spreadsheet versions the night before the big day.
Nothing to install: open the link, add a guest, the other person sees it.
For the length of a project, and it stays yours
The Discovery plan (€0) lets you generate a first complete application — often enough for a wedding. Paid plans are for iterating, with the cost shown before each generation.
Because the code is exportable, the application is yours: keep it as a memento, reuse its structure for the family's next big event, or archive it. It doesn't vanish because a subscription ends.
Typical generated entities
- Guest
- Table
- Budget category
- Vendor
- Task
Generated screens
- Guest list with reply status
- Seating plan by tables
- Budget per category (spent / remaining)
- Vendors: quotes, deposits, balance
- Task countdown
- Wedding dashboard
Dashboard indicators
- Guests confirmed / pending
- Budget spent vs planned
- Deposits paid to vendors
- Overdue tasks
Frequently asked questions — wedding planning
Do I need technical skills to create this app?
No. You describe your setup in plain language — guests, budget, vendors, tasks — validate a plan, and the application is generated without writing code.
Can two people use it, and the witnesses too?
Yes: it's a centralised web application. Both partners and the people you choose access the same up-to-date data on a shared URL.
Does it handle the seating plan and dietary needs?
Yes if your description provides for it: each guest can carry a table, a dietary need (vegetarian, gluten-free…) and a reply status, with views and counts per table.
And after the wedding, what happens to the app?
It stays yours: the code is exportable, you can archive it, keep it online, or reuse its structure for another family event.
Is it really free to start?
Yes: the Discovery plan generates a first application without paying. The cost of further generations is shown before launching them.