Client Bookings Diary
Every customer booking in one ruled ledger — enquiry, functions, venue, total deal, advance, later payment and the remaining balance worked out automatically.
Studio Diary is a professional SaaS web application for photographers, videographers, wedding studios and cinematographers in India. It is the operating system of a studio's commercial life: the client booking diary, the shoot calendar, quick commercial shoots, B2B rental and crew jobs, the team and freelancer ledger, invoices in five house styles, and the subscription that keeps the studio running.
The product intent is to give an Indian studio owner a single premium workspace where a ₹15L wedding booking, a ₹4,000 car shoot, an LED-wall rental to a rival studio, a drone operator's pending dues and a signed GST invoice all live in one place — accurate, searchable, printable and private to that studio.
The audience is the studio founder/owner and the small trusted team around them who handle client bookings, B2B jobs, crew ledgers and invoicing. Every founder sees only their own studio's data.
Studio Diary is delivered as a React + TypeScript + Vite single-page web application backed by Firebase Authentication and Cloud Firestore, with Razorpay handling subscription payments through secure server-side order creation and verification.
Current delivery. A public marketing website (Landing, Features, Demo, Pricing, FAQ) with Login and Start Free Trial entry points; an authenticated studio workspace containing the Dashboard, Profile, Subscription, Bookings, Booking Details, Smart Calendar, Quick Shoot Desk, B2B Services, B2B Details, Team Ledger, Invoices and Search.
Actors. The accepted active human personas are the Studio Founder / Owner, the Booking & Client Coordinator, the B2B Services Manager, the Team & Freelancer Ledger Manager, and the Invoice & Payments Handler. Firebase Authentication, Cloud Firestore and Razorpay are non-persona system and provider actors.
Accepted behaviour. Founder profile management, 7-day free trial and three paid plans, subscription status display, booking creation with multiple functions and additional event services, album specification, smart calendar, quick shoot desk, B2B services module with dashboard actions, team master and payment tracking with independent work/delivery/payment status, five invoice styles with preview/print/PDF, multi-criteria search, and full loading/saving/error/empty/payment-success/payment-failure handling.
Narrow exclusions. Old subscription plans are removed and only 1 Month ₹90, 3 Months ₹199 and 1 Year ₹349 remain. The unnecessary Studio name chip is removed from the dashboard. The Razorpay Key Secret and all server secrets are never exposed to the client. Existing Firebase Auth, Firestore data, bookings, invoices, payments, calendar, team, subscriptions and founder records must not be broken, and unrelated features must not be redesigned.
Studio Diary is a first-party, application-owned product. The studio's identity, profile, bookings, B2B jobs, team ledger, invoices and subscription state are owned and persisted by Studio Diary in Cloud Firestore under the founder's own uid, and every founder is restricted to their own data.
Access is split into two boundaries. The public website — Landing, Features, Demo, Pricing, FAQ, Login and Start Free Trial — is reachable without an account. The studio workspace — Dashboard, Profile, Subscription, Bookings, Booking Details, Smart Calendar, Quick Shoot Desk, B2B Services, B2B Details, Team Ledger, Invoices and Search — requires an authenticated founder session. Identity is established through the accepted methods on Login (Email + Password, Continue with Google, Mobile OTP) and through Create Account / Start Free Trial for a new founder, who then receives a 7-day free trial.
Payment for paid plans is provider-owned at the money-movement layer: Razorpay processes the transaction, while Studio Diary owns order creation and server-side verification and records the resulting subscription state in Firestore. The Razorpay Key Secret and all server secrets remain server-side only.
Everything described in this document is current scope. No future-horizon capabilities are asserted.
studios/{uid}/profile/main.studios/{uid}/subscription/current; Razorpay order and verification result.studios/{uid}/bookings/{bookingId} with customer details, fixed date, main service, primary event type, referred by, venue, notes, deal/advance/later payment/total received/remaining balance, functions, additional event services, album details.studios/{uid}/b2bServices/{serviceId}.studios/{uid}/team/master; team payment records; status fields.Each requirement is stated as a story point with provenance, lifecycle facts and observable acceptance.
FR-1 — Build Studio Diary as a professional SaaS web application. As a Studio Founder / Owner I should use Studio Diary as a professional SaaS web application built for photographers, videographers, wedding studios and cinematographers in India so that my studio's commercial operations run in one place. Provenance: explicit. Lifecycle: initiator — founder; trigger — opening the application; observable result — the product is available and usable for Indian studio operations; failure/recovery — application load failure surfaces a readable error with retry; continuation — founder proceeds to Landing or Login. Acceptance: the application is delivered as a professional SaaS web application for the stated Indian studio audience.
FR-2 — Use the specified technology stack. As a Studio Founder / Owner I should have the application built with React, TypeScript, Vite, Firebase Authentication, Cloud Firestore and Razorpay so that it runs on the required, supported platform. Provenance: explicit. Lifecycle: initiator — system; trigger — build and runtime; observable result — the application runs on React, TypeScript, Vite, Firebase Authentication, Cloud Firestore and Razorpay; failure/recovery — build or runtime errors are surfaced and corrected; continuation — normal operation. Acceptance: all six named technologies are in use.
FR-3 — Preserve existing data and components. As a Studio Founder / Owner I should have existing Firebase Auth, Firestore data, bookings, invoices, payments, calendar, team, subscriptions and founder records preserved, with old data kept and existing working components reused so that nothing I already rely on is lost or broken. Provenance: explicit. Lifecycle: initiator — founder; trigger — any change to the existing project; observable result — existing records remain intact and working components are reused; failure/recovery — if a change would break existing data or components, it is corrected before release; continuation — normal operation on preserved data. Acceptance: no existing Firebase Auth, Firestore data, bookings, invoices, payments, calendar, team, subscriptions or founder records are broken; old data is preserved; existing components are reused.
FR-4 — Premium, responsive, professional UI with Dark and Bright Mode. As a Studio Founder / Owner I should use a premium, responsive and professional interface with a dark navy/black background, gold/amber accents, white readable text, rounded cards and both Dark and Bright Mode so that the product feels like a premium studio brand on any device. Provenance: explicit. Lifecycle: initiator — founder; trigger — opening any page; observable result — the interface renders premium, responsive and professional in both modes; failure/recovery — layout or contrast problems are corrected; continuation — normal use. Acceptance: dark navy/black background, gold/amber accents, white readable text, rounded cards and both Dark and Bright Mode are present and responsive.
FR-5 — Fix all invisible text, labels, inputs, dropdowns and buttons. As a Studio Founder / Owner I should have all invisible text, labels, inputs, dropdowns and buttons fixed so that every control and label is readable in both modes. Provenance: explicit. Lifecycle: initiator — founder; trigger — viewing any form or control; observable result — all text, labels, inputs, dropdowns and buttons are visible and readable; failure/recovery — any remaining invisible element is corrected; continuation — normal use. Acceptance: no invisible text, labels, inputs, dropdowns or buttons remain.
FR-6 — Public website. As a prospective studio founder I should see a public website with logo, Features, Demo, Pricing, FAQ, Login, Start Free Trial, hero section, photography visuals, testimonials and footer so that I can evaluate Studio Diary before signing up. Provenance: explicit. Lifecycle: initiator — prospective founder; trigger — visiting the public site; observable result — all named public elements are present and navigable; failure/recovery — missing or broken public content is corrected; continuation — visitor proceeds to Start Free Trial or Login. Acceptance: logo, Features, Demo, Pricing, FAQ, Login, Start Free Trial, hero section, photography visuals, testimonials and footer are all present.
FR-7 — Login page contents. As a returning Studio Founder / Owner I should see the Studio Diary logo, Email, Password, Login, Forgot Password, Continue with Google, Mobile OTP and Create Account on the Login page so that I can sign in by the method I prefer. Provenance: explicit. Lifecycle: initiator — founder; trigger — opening Login; observable result — all named elements are present and functional; failure/recovery — failed sign-in shows a readable error and offers retry or an alternate method; continuation — successful sign-in continues to the Dashboard. Acceptance: Studio Diary logo, Email, Password, Login, Forgot Password, Continue with Google, Mobile OTP and Create Account are all present on the Login page.
FR-8 — Founder profile fields. As a Studio Founder / Owner I should maintain a founder profile with Studio Name, Founder Name, Logo, Photo, Mobile, Email, Address, City, District, State, GST (optional) and Signature so that my studio's identity appears correctly on records and invoices. Provenance: explicit. Lifecycle: initiator — founder; trigger — opening Profile; observable result — all named fields are editable and saved; failure/recovery — validation or write failure shows a readable error and allows correction; continuation — saved profile is used by invoices and records. Acceptance: all named fields exist, GST is optional, and the profile persists.
FR-9 — 7-day free trial for new founders. As a new Studio Founder / Owner I should receive a 7-day free trial so that I can evaluate Studio Diary before paying. Provenance: explicit. Lifecycle: initiator — new founder; trigger — creating an account; observable result — a 7-day free trial is active; failure/recovery — trial state errors are surfaced and corrected; continuation — founder uses the product during the trial and can then purchase a paid plan. Acceptance: a new founder receives a 7-day free trial.
FR-10 — Paid plans and removal of old plans. As a Studio Founder / Owner I should see paid plans of 1 Month ₹90, 3 Months ₹199 and 1 Year ₹349, with old plans removed so that only current pricing is offered. Provenance: explicit. Lifecycle: initiator — founder; trigger — viewing Pricing or Subscription; observable result — exactly the three named plans are offered and old plans are absent; failure/recovery — stale plan data is removed; continuation — founder selects a plan. Acceptance: only 1 Month ₹90, 3 Months ₹199 and 1 Year ₹349 are offered; old plans are removed.
FR-11 — Subscription stored in Firestore with plan, expiry and status. As a Studio Founder / Owner I should have my subscription stored in Firestore and see my current plan, expiry and status so that I always know where my account stands. Provenance: explicit. Lifecycle: initiator — founder; trigger — opening Subscription; observable result — current plan, expiry and status are displayed from Firestore; failure/recovery — read failure shows a readable error with retry; continuation — founder renews or continues. Acceptance: subscription is stored in Firestore and current plan, expiry and status are shown.
FR-12 — Secure Razorpay order creation and server-side verification. As a Studio Founder / Owner I should have my subscription payment processed through secure Razorpay order creation and server-side payment verification so that my payment is trustworthy. Provenance: explicit. Lifecycle: initiator — founder; trigger — purchasing a plan; observable result — an order is created securely, payment is completed, and the payment is verified server-side before the subscription is updated; failure/recovery — order creation or verification failure shows a readable error and allows retry without duplicating a verified payment; continuation — verified payment updates plan and expiry. Acceptance: order creation is secure and payment verification happens server-side.
FR-13 — Never expose the Razorpay Key Secret or server secrets. As a Studio Founder / Owner I should have the Razorpay Key Secret and all server secrets kept off the client so that my studio's payment credentials are never compromised. Provenance: explicit. Lifecycle: initiator — system; trigger — any client request; observable result — no Razorpay Key Secret or server secret is present in client code or responses; failure/re

Public site navigation for Studio Diary
Bookings, invoices and crew ledgers for Indian wedding studios.
Capabilities
Bookings, calendar, crew ledgers, B2B rentals and invoices — held in one place for photographers, videographers, wedding studios and cinematographers.
Every customer booking in one ruled ledger — enquiry, functions, venue, total deal, advance, later payment and the remaining balance worked out automatically.
A month grid with year navigation that lays every client function on its date — venue, call time and assigned crew — so a selected day opens the full shoot detail.
Short jobs kept separate from full weddings — car, reel, baby, ring ceremony, promotional, land and shop shoots, with a custom type whenever the brief does not fit.
Rentals and crew work for other studios recorded as their own jobs, with services, quantities, rates, operators and the paid amount tracked against the balance.
Freelancers and crew carry their role, rate and dues in one ledger, with work status, delivery status and payment status tracked as three independent things.
Studio logo, founder, customer, functions and services on one sheet, with the signature above the signatory line and five templates chosen as the studio default.
Find any record by customer, mobile number, year, month, date, function or venue — the fastest way back into a booking you took months ago.
Seven capability areas, one studio record — from the first enquiry to the signed invoice.
See all featuresProduct Demo
Walk the whole path once — a wedding booking with its functions, the shoot calendar, a B2B rental, crew dues, then the invoice. Step through the demo with sample studio records.
Step through the demoEvery plan unlocks the full Studio Diary workspace — bookings, calendar, crew ledger and GST invoices. No per-seat charge for your studio team.
Full access for seven days. Pick a paid plan only when you decide to continue.
The short answers on plans, the free trial and how your studio records are kept. Open a question to read it here, or browse the full set.
Every new Studio Founder starts with a 7-day free trial — no card needed. You can set up your studio profile, log client bookings, build shoot functions and draft invoices for the full seven days. When the trial ends, choose a paid plan to keep writing to your studio diary.
Studio Diary offers three plans: 1 Month at ₹90, 3 Months at ₹199 and 1 Year at ₹349. Older plans are retired, so only current pricing is shown. Your plan, expiry date and subscription status live on the Subscription page and you can move to a longer plan whenever you like.
Only you. Each founder signs in to their own studio account and reads and writes only their own records — bookings, B2B jobs, team master and subscription are stored under your studio, never pooled with another studio. Payment credentials stay on the server and are never sent to the browser.
Yes. Invoices carry your studio logo, studio and founder name, contact, customer, functions, venue, services, deal value, advance, payments and remaining balance — plus invoice number, date and your signature. Five templates are included: Classic Gold, Modern Dark, Clean White, Premium Wedding and Minimal Professional. Pick a default in your profile and preview, print or export to PDF.
B2B Services is a separate module for rental and crew jobs: studio and venue details, event date, reporting time, deal value, advance, later payment, total paid and the balance that follows. Pick services such as Photo and Video, Drone, Gimbal, Camera Crane, LED Wall, TV, Standee or Selfie Point with quantity, rate and operators, then track each job to Mark Paid and Generate Invoice.
Studios across India run their bookings diary, crew ledger and invoices on Studio Diary.
Wedding studio founder, Jaipur
Cinematographer, Kochi
Photography studio owner, Ludhiana
Testimonials are published by studio founders · Studio Diary

Public site navigation for Studio Diary
Bookings, invoices and crew ledgers for Indian wedding studios.
Capabilities
Bookings, calendar, crew ledgers, B2B rentals and invoices — held in one place for photographers, videographers, wedding studios and cinematographers.
Every customer booking in one ruled ledger — enquiry, functions, venue, total deal, advance, later payment and the remaining balance worked out automatically.
A month grid with year navigation that lays every client function on its date — venue, call time and assigned crew — so a selected day opens the full shoot detail.
Short jobs kept separate from full weddings — car, reel, baby, ring ceremony, promotional, land and shop shoots, with a custom type whenever the brief does not fit.
Rentals and crew work for other studios recorded as their own jobs, with services, quantities, rates, operators and the paid amount tracked against the balance.
Freelancers and crew carry their role, rate and dues in one ledger, with work status, delivery status and payment status tracked as three independent things.
Studio logo, founder, customer, functions and services on one sheet, with the signature above the signatory line and five templates chosen as the studio default.
Find any record by customer, mobile number, year, month, date, function or venue — the fastest way back into a booking you took months ago.
Seven capability areas, one studio record — from the first enquiry to the signed invoice.
See all featuresProduct Demo
Walk the whole path once — a wedding booking with its functions, the shoot calendar, a B2B rental, crew dues, then the invoice. Step through the demo with sample studio records.
Step through the demoEvery plan unlocks the full Studio Diary workspace — bookings, calendar, crew ledger and GST invoices. No per-seat charge for your studio team.
Full access for seven days. Pick a paid plan only when you decide to continue.
The short answers on plans, the free trial and how your studio records are kept. Open a question to read it here, or browse the full set.
Every new Studio Founder starts with a 7-day free trial — no card needed. You can set up your studio profile, log client bookings, build shoot functions and draft invoices for the full seven days. When the trial ends, choose a paid plan to keep writing to your studio diary.
Studio Diary offers three plans: 1 Month at ₹90, 3 Months at ₹199 and 1 Year at ₹349. Older plans are retired, so only current pricing is shown. Your plan, expiry date and subscription status live on the Subscription page and you can move to a longer plan whenever you like.
Only you. Each founder signs in to their own studio account and reads and writes only their own records — bookings, B2B jobs, team master and subscription are stored under your studio, never pooled with another studio. Payment credentials stay on the server and are never sent to the browser.
Yes. Invoices carry your studio logo, studio and founder name, contact, customer, functions, venue, services, deal value, advance, payments and remaining balance — plus invoice number, date and your signature. Five templates are included: Classic Gold, Modern Dark, Clean White, Premium Wedding and Minimal Professional. Pick a default in your profile and preview, print or export to PDF.
B2B Services is a separate module for rental and crew jobs: studio and venue details, event date, reporting time, deal value, advance, later payment, total paid and the balance that follows. Pick services such as Photo and Video, Drone, Gimbal, Camera Crane, LED Wall, TV, Standee or Selfie Point with quantity, rate and operators, then track each job to Mark Paid and Generate Invoice.
Studios across India run their bookings diary, crew ledger and invoices on Studio Diary.
Wedding studio founder, Jaipur
Cinematographer, Kochi
Photography studio owner, Ludhiana
Testimonials are published by studio founders · Studio Diary
No comments yet. Be the first!