Wedding studio CRM
Enquiries, quotations, contracts and follow-ups built around how a wedding studio actually books work — not a generic pipeline with the field names changed.
Sound familiar?
The enquiry arrives on WhatsApp at 11 PM and is forty messages deep by Sunday, under three other weddings.
You quote from last season’s PDF with the names swapped, and version 7 goes out carrying the old price.
Nobody remembers which couple was told what, because the conversation lives on one person’s phone.
A lead goes cold because the follow-up was a mental note, not a task.
The contract is a scan of a signature, filed in an email thread.
What changes
New → qualified → proposal → won, with call and WhatsApp activity logged against the lead, tags for source and season, and CSV import if your history lives in a spreadsheet. Converting to a client keeps the whole history attached.
Send a quotation as a link the couple can accept online. It converts into a contract, gets signed in the browser with an audit trail, and both are auto-numbered so your records are continuous rather than improvised.
Automations react to real events — lead created, contract signed, payment recorded — with email, WhatsApp and team notifications. You shoot; the studio chases.
The lead becomes a client, the client gets a project, the project carries events, crew, galleries, selections and invoices. Everything about a wedding hangs off one thread instead of being reassembled from memory.
Side by side
| What you need | Without a system | With Wedding OS |
|---|---|---|
| Where an enquiry lives | WhatsApp, a call log, someone’s memory | A lead card with logged activity |
| Quoting | Last season’s PDF, names swapped | A link the couple accepts online |
| Signing | A scan in an email thread | Signed in-browser, audit trail attached |
| Follow-up | Remembering to | Automations on real studio events |
| Built for | Any business with a sales pipeline | Wedding studios, INR, WhatsApp-aware |
FAQ
Both are good products. The difference is what happens after the booking: a generic CRM manages the business but not the files, so you still need a gallery service, a storage plan and a delivery workflow beside it. Wedding OS carries the same enquiry through shooting, post-production, client selections, album approval, delivery and payment. There is also the India-first part — INR invoicing, GST-ready billing, UPI collection and WhatsApp messaging, which most US-built CRMs do not do.
Yes. CSV import maps your existing columns onto leads, and one click converts a lead into a client with its history intact.
Yes. Assign shooters, editors and assistants per event, run multiple branches under one studio, and use 80+ fine-grained permissions so a freelance editor sees production without seeing your P&L.
Nothing. Lite is free forever with the full workflow at solo scale — one team member, one branch, no card. Paid plans start at ₹416/month billed yearly when your team outgrows it.
Start free on Lite — every feature at solo scale, no card, and a full export any time you want out.