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; set it in My studio · Expected dates.
Everything you sell, and everything anyone has ordered. Approve an order to add it to the invoice and start its own small production track — Delete if it was a mistake. What you sell is the catalogue behind all of it: couples before the day, couples after, and guests.
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.
Your studio backs up to your own database on Hostinger. The front-door sign-in is also your sync sign-in — nothing to configure here; 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. Sign-in details are kept. If backup is connected you’ll be offered a database wipe too — otherwise synced data returns on next sign-in.
Backed up to your Hostinger database automatically — every booking, order and setting syncs across your devices once you’ve signed in at the front door.
Touchpoints and message drafts follow these six stages automatically. Tap a swatch to recolour a stage — tags, lists and the calendar follow.
Find a couple and give any stage a date — their portal wears a gold “Expected · 16 July 2026” pill on every page that hasn’t opened yet. Clear the date and the pill returns to “after your day”.
Add your photographers and videographers once — assign them to booking days, and their per-event charge flows into crew payouts and your year by itself.
Drag the gold point to the couple. Phone crops tall, desktop crops wide — both keep your point in view. Publishes like the packages page; the pages follow on their next open.
Phone
Desktop
The point becomes one CSS line the live pages read — nothing is re-cropped or re-uploaded.
New bookings pick from these — line items and price pre-fill in one tap, still fully editable per couple.
packages.mustajabweddings.com and mustajabweddings.com/collections both read from here — every configuration, price, inclusion and term. Save & publish and the pages follow.
Every reminder, agreement and invoice reads these — change a number and the automations follow.
Agreements, reminders and the portal all follow these.
Powers break-even in Year in review.
Tag every payment out, so your P&L shows where money goes.
Every message the studio sends — to couples, to crew, to you — lives here as one row: who it goes to, which channels, auto or by hand, and your own words. Nothing sends without a row. Nothing floods, by design.
Held sends wait for you here until released — nothing held ever sends itself.
Everything aimed at you can fold into the Monday digest instead of arriving one by one — set per row below. Quiet hours are yours to choose — nothing sends inside them; it waits and arrives at the hour you set.
Not linked yet — rows wait here; one tap opens WhatsApp on this device.
The moment an enquiry lands, they get a warm WhatsApp — email when they left no phone. First to reply usually wins the wedding. Edit words ›
A WhatsApp note to your own business number — “New enquiry — Ayesha & Omar · Dec 14” — so you can jump in while they’re still browsing. Edit words ›
If they never replied after the welcome — one follow-up, once, ever. Edit words ›
Day before every event, each assigned member gets their duty WhatsApp — couple, venue, time. Needs phones on the roster. Edit words ›
Every send still lands in WhatsApp → Outgoing first (editable during the window), obeys the daily cap, and shows its tick in Conversations or the Crew room. The welcome and your ping go instantly — speed is their whole point.
Each one worth keeping. Everything else waits quietly in your portal — the only wedding studio that promises you silence.
Reminders only exist when something stalls — a smooth journey never sees them. Push stays reserved for the gallery.
Duty reminders are one send per crew member per event, deduped hard — they were the flooder. The assignment-change email stays retired; push only.
Digest mode folds these into Monday’s single email — switch any row to “Now” only if it truly can’t wait.
Everyone who left an email at a gallery door. One note a year, in the month you choose — the server refuses a second copy to the same person for 300 days, so this can never become a newsletter.
Why this never needs a redesign. Every row already carries its recipient, its channels, its mode and its words. Connecting the WhatsApp Business API only changes what happens after “send” — the same rows flip from queued to automatic, and nothing on this page moves.
One note reaches everyone who allowed notifications — couples, families and crew with the app installed. Use it sparingly: dates opening, an album month, a film worth watching. Nothing here ever sends by itself.
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.
Every wedding puts you in front of hundreds of guests — the exact people getting married next. This is where they arrive: the email door at the gallery, the card at the end of the photographs, and the list they build for you.
Every working sign-in for the crew room and client suites, read from the connected database. A password someone sets themselves can’t be read back — only reset from here.
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: