Wedding consultation booking
Couples book a slot against the planner's real availability, with buffer time between meetings built in.
SIZ Group designs and builds a customer self-service app for wedding planners, so couples and their families can book consultations, request changes, see each task and receive reminders without flooding the planner's inbox. It is built around the long stretch between a signed contract and the wedding day.
A wedding planner may run a dozen weddings at once, each with its own guest list, vendors, deposits and timeline. Couples text about a flower change late at night, and parents email about seating. The planner ends up answering the same question in three channels, and the wedding file falls further behind.
The app gives couples a place to see what happens next, request a change, book a consultation and check whether a vendor has confirmed. It does not replace the planner's judgment. It keeps the planner in control of what is shared and when, and it stops the same question from arriving four times.
Work usually moves from a discovery call to a proposal, a signed contract and a planning period of several months. The breakdown points are predictable. Vendor details sit in one person's inbox, a guest count change never reaches the caterer, and a deposit reminder goes out late or not at all.
The most expensive handover is from the planner to the day-of coordinator. Notes from a dozen calls rarely reach the coordinator in a usable form. The app should keep each request, approval and vendor confirmation attached to the wedding record, so anyone who opens it sees the current state.
The first release should cover the requests couples send most often: consultation booking, change requests for guest counts and menus, a status view for each planning task and deposit reminders. Those four features remove most repeated questions without changing how the planner works.
Later phases can add a shared moodboard, a seating planner, a vendor directory and a guest RSVP tracker. Each of those adds data the team must keep correct, so they wait until the core flow is working.
Couples book a slot against the planner's real availability, with buffer time between meetings built in.
Guest counts, menus and timeline changes reach the planner first, so nothing goes to a vendor unchecked.
One place for couples to see tasks, documents and the next dates on their wedding timeline.
Deposit, final payment and headcount reminders follow the contract schedule without manual sending.
Each task shows as done, waiting on the couple or waiting on a vendor, so the next step is obvious.
A bride-to-be opens the app two months before her wedding, after a cousin has confirmed travel from abroad. She logs in with the email address the planner used at signing and sees the next three tasks on her timeline. She taps the guest count, enters the new number and adds a short note about dietary needs.
The whole exchange takes a few minutes for the couple. The planner sees one approved change instead of three emails, and the file shows who asked for what and when.
Planners usually juggle a client management tool such as HoneyBook, along with email, a shared drive, a calendar and vendor spreadsheets. The portal should read contacts, contracts and dates from whichever of those the planner trusts, and never ask anyone to type a date twice. The scoping call settles which tool is the master record.
Deposits should be paid through a hosted checkout, so card details never sit in the app. Calendar invites can go through Google Calendar or Outlook, and reminders go by email, with text only where the couple has consented. Vendors who run their own systems can receive a simple email update instead of a login.
Mobile apps start at $4,500. Two things move the figure most here: whether vendors receive a login of their own, and how many planning tools the portal has to read. The scoping call prices every optional module on its own line, starting from the first release.
The firm keeps spend steady by signing off the first release first and parking every later idea on a separate list. A change gets costed before it is built. Once the portal is live, support handles bugs and minor adjustments.
They will use a tool that saves them time, and most planning questions are repeats, so the app is the quickest answer. We keep the first screen simple and show the next task, not a menu of features. The planner decides how much to share, and couples can always reach a person.
No. Contracts, payment terms and meetings stay exactly as the planner runs them. The app records requests and status, so meetings can focus on decisions. The contract schedule feeds the reminders, so nothing is missed.
Yes, if the planner chooses to share it. Wedding day timeline sharing gives couples a read-only view of the final schedule, including each vendor's arrival time. Changes come from the planner, and the version date is always visible.
The app keeps only what planning needs: names, contact details, dates, guest counts and dietary notes. Payments run through a hosted provider. Marketing messages require consent, and the planner can export or delete a couple's record on request.
Vendors receive a simple email update with a secure link to confirm details, so they do not need to learn a new system. The planner controls which vendors appear on each timeline and what each one can see.
Show us how a typical couple moves from enquiry to wedding day, and we will sketch the portal around that path.