An Automated CRM for Photographers Who Are Done Chasing

Every photographer has had the week where the shooting went perfectly and the business went backwards. Two inquiries that came in on Friday went unanswered until Monday and booked somebody else. A balance that should have been collected before the ceremony got collected six weeks after the album shipped, after four awkward messages. A couple who loved their photographs never got asked for a review, because by the time you thought of it the moment had passed.

None of those are photography problems. They are all the same problem: the admin depends on you remembering at the exact moment you are least able to.

An automated CRM is one where that dependency is gone. This page is about what changes, not how it is wired. For the mechanism, see the automation page.

Monday morning, before

You open your phone to eleven WhatsApp threads and no idea which of them is a real inquiry. Somewhere there is a couple who asked about a December date on Saturday afternoon. You scroll for them. While scrolling you notice a client whose balance was due last Thursday, which you had forgotten, and which you now have to raise without sounding like you had forgotten.

Monday morning, after

The Saturday inquiry is in the pipeline with a reply already written, because it arrived through your booking page rather than into a chat thread. The overdue balance is at the top of the Payments list, marked "4 days overdue" in plain language, with the reminder composed. Two more clients are shown as due in the next seven days, before they are late.

You spend six minutes sending three messages you did not have to write. Then you go and shoot.

What is already done when you open it

• Every inquiry from the last night is captured with the date, the event type and the budget band the client selected
• Every unanswered inquiry past your follow-up interval has a nudge drafted
• Every unpaid advance on a confirmed booking has its reminder ready
• Every balance due before an upcoming shoot has been flagged ahead of the date, not after
• Every booking that reached Booked has its pre-shoot questionnaire drafted onto it
• Every completed delivery has its review request waiting

The three places the money was leaking

The response gap

The interval between an inquiry arriving and someone replying is the single most expensive number in a photography business, and it is entirely invisible until something measures it. Inquiries arrive at night and on weekends, which is exactly when a photographer is either shooting or asleep.

A public booking page captures the inquiry as a structured record rather than a chat message: name, date, event type, and the budget band the client picked from a list. The follow-up is drafted immediately. You are replying at breakfast to something that arrived at midnight, which for the client is indistinguishable from having replied at midnight.

The balance chased too late

Money is easy to collect before the shoot and hard to collect after the album has been delivered. The difference is entirely one of timing, and timing is what gets lost when you are shooting four weekends a month.

The balance reminder is tied to the shoot date rather than to your memory, and it stops the moment the payment is recorded. The Payments screen is one list in urgency order with three figures above it: overdue, due in the next seven days, and collected this month. Tapping any figure filters the list to exactly what it counted, so the number and the work are never two different screens.

The review never asked for

A client is most willing to write a review in the week they receive their photographs and least willing three months later. Almost every studio asks in the wrong window, because asking depends on remembering, and by then attention has moved to the next wedding.

The request is prompted when delivery completes.

What stays yours

The last tap is always yours. Studio Ryzen writes the message and opens WhatsApp with it ready; you read it and send it. Nothing goes to a client unseen.

This is a deliberate limit. A studio's relationship with a wedding family is worth more than the few seconds saved by sending unattended, and a payment reminder that fires by itself into the middle of a wedding week is exactly the message that should have had a human glance at it first.

Equally, nothing is hidden from you. The onboarding asks what you shoot and what you are trying to fix, and uses the answer to decide which screen you land on and whether to point you at the client importer. It does not hide features, reorder your navigation or decide what you are allowed to see.

What it takes to get there

Pick the package blueprint closest to what you shoot - there are twelve, covering weddings across three days, pre-wedding, engagement or roka, first birthday, naming ceremony, portraits, maternity and newborn, corporate events, product catalogue, destination weddings, fashion lookbooks and multi-day conferences. It arrives with its events, its payment split and its six workflow messages. Then pick the automation recipe that matches. That is the setup.

If you are moving from another tool or from a spreadsheet, the CSV importer brings clients across and creates a booking per row where a date, an amount or a booking type is mapped. Imported bookings land as Booked so that migrated history does not flood today's follow-up prompts with reminders about weddings you shot two years ago.

Fourteen-day trial, no card. Plans in rupees from ₹849 a month.

Related reading

For exactly what fires and what stops it, see the automation mechanism page. For the WhatsApp side, see the WhatsApp CRM page. For the category overview, start at the photography CRM India hub.