The booking, on one page — the money rail follows as you scroll. Save writes it into your Calendar, Invoice and the couple's portal.
The board — every column is a stage. Drag a couple forward as life moves; tap a name to open the booking. Money and the next step stay on the card.
Days you shoot for other studios — kept apart from your own weddings, counted into your year. Paid days flow into Finances and Year in review by themselves.
A booking joins the line when you mark it Edit, then moves stage by stage to the couple's hands — the promise date follows your rules; adjust it on any card.
Extras couples ordered from their portal. Approve to add it to their invoice and start its own small production track — Delete if it was a mistake. The couple watches the same track from their side.
What they chose, what they approved — and what they said after. Family favourites stay with the couple; you see the counts only.
What the couples said once everything was home — straight from their portals.
Every rupee, in its place. Client payments flow in from bookings by themselves — you only record what you pay out.
The control room — every rule, price and word your studio and its automations use, in one place.
These details flow into every invoice, agreement, portal and message — written once, used everywhere.
Front-door sign-in for you and your assistant — username + password. The studio password (MJB007 by default) still works as a fallback.
One-time setup: create a free project at supabase.com → SQL Editor → run supabase-setup.sql from your app folder → Authentication → Users → add your owner email & password → paste the URL and key below and sign in. After that, phone and laptop always match.
Asked at the front door when the studio opens on a new device (or after Logout). The master code MJB007 always works as a fallback.
Wipes every booking, order, selection and setting on this device — a clean first-run for going live. Cloud sign-in details are kept. If cloud sync is already connected, previously synced data can return on next sign-in; clear the Supabase tables too for a true zero.
Touchpoints and message drafts follow these six stages automatically. Tap a swatch to recolour a stage — tags, lists and the calendar follow.
Add your crew and their standard per-event charge. Assign someone to a booking day and a committed payable is created automatically — the dashboard reminds you to pay them after the event.
New bookings pick from these — line items and price pre-fill in one tap, still fully editable per couple.
Every reminder, agreement and invoice reads these — change a number and the automations follow.
Each automation drafts from these — you always see the draft before anything is sent.
Every confirmed couple gets a private code and page — coverage, payments and journey — published automatically whenever you save their booking. Copy any couple's link from the Tracking list.
One key from console.cloud.google.com (Google Drive API, restricted to your site) lets couples browse their photo folder and heart their favourites. Paste each couple's Drive folder link in their booking.
These settings restyle the entire studio and your client documents — calendar and invoice follow the theme. Saved on this device.
A wedding year moves in seasons, not months — four chapters, then the accountant's pages. Printable for tax season.
Download this year's records as spreadsheet-ready CSV files (open in Excel or Google Sheets).
Revenue figures are based on the invoice totals of bookings in this year. Received reflects payments logged to those bookings.
Every paper the studio hands a couple, in the order they meet it — statuses follow the selected booking.
Everything for your weddings in one place — bookings, calendar, payments, delivery and the documents you send couples. Start with one of these: