Chasing the balance over WhatsApp feels free. You're not writing a cheque to anyone; you're just sending a message. So most studios never put a number on it, and never question the workflow.
Put a number on it and the workflow stops looking free.
This is a comparison of the two ways an Indian wedding studio can get paid for a shoot: deliver-then-chase (the Drive-link-and-follow-up default) versus pay-before-delivery (gate the high-res files behind a payment that unlocks them). If you want the how-to for the second one, read how to collect payment before delivering wedding photos in India. This piece is about why it's worth switching.
What deliver-then-chase actually costs
The cost isn't one big line item. It's three quiet ones that add up across a season.
1. Your hours. Every album that isn't paid on delivery becomes a small project: the first reminder, the "just following up," the call, the re-share because the link expired, the mental overhead of remembering who still owes you. Across a busy month of weddings, that's hours you spent on collections instead of shooting or editing — the two things that actually grow a studio.
2. Your cash flow. Money you've earned but haven't collected isn't yours yet. It can't pay your second shooter, your editor, or your equipment EMI. Deliver-then-chase pushes your payment to the latest possible moment — weeks after you did the work. Pay-before-delivery pulls it to the earliest moment the client wants their photos.
3. The balances you write off. Not every chase ends in payment. Some clients go quiet after they've quietly downloaded the Drive folder. Some negotiate the balance down because they already have what they need. Every rupee written off was a rupee you earned and then handed back because of the order of operations.
Side by side
| Deliver-then-chase | Pay-before-delivery | |
|---|---|---|
| When you get paid | Weeks after delivery, if at all | The moment the client wants their files |
| Who does the asking | You, repeatedly, by hand | The system, once, automatically |
| Leverage at payment time | None — they already have the files | Full — files unlock on payment |
| Follow-up effort per album | Several messages, sometimes a call | A single "your gallery is ready to unlock" |
| Write-off risk | Real, and recurring | Near zero — nothing is released unpaid |
| How it feels to the client | A payment chase in the family chat | A clean checkout for photos they chose |
The objection worth taking seriously
The honest counter-argument is: won't a payment gate cost me bookings? It's the right thing to worry about, so don't wave it away.
In practice, the fear is bigger than the effect — on one condition: the gate has to be paired with a fast, generous preview and set at booking, not sprung after the wedding. A client who has already browsed a beautiful gallery of their own wedding, chosen their favourites, and is one UPI tap from the full set is not a client looking for the exit. They're a client at checkout. The studios that lose people to a payment gate are almost always the ones who introduced it as a surprise, or who gated a gallery the client hadn't seen yet.
Get the sequence right and the gate doesn't cost you bookings. It costs you the three weeks of chasing you used to treat as free.
How PhotoSelect makes the switch low-risk
PhotoSelect runs the pay-before-delivery model end to end so you don't have to assemble it yourself: a WhatsApp-ready preview gallery that works through bad venue networks, a payment-gated vault for the originals, and an automatic unlock the instant a UPI/Razorpay payment confirms. The delivery ledger shows you who opened, selected, and paid, so the rare follow-up you do send is precise instead of a guess.
And the economics stay clean: a flat studio plan, and zero commission on what your clients pay. The point of switching is to stop leaking time and cash — not to hand a cut of it to your software.