studiodiary

byKalpana Studio

Build a professional SaaS web application called Studio Diary for photographers,videographers,wedding studios and cinematographers in India.Use React,TypeScript,Vite,Firebase Authentication,Cloud Firestore and Razorpay.Do not break existing Firebase Auth,Firestore data,bookings,invoices,payments,calendar,team,subscriptions or founder records.Preserve old data and reuse existing components.Keep the UI premium,responsive and professional with dark navy/black background,gold/amber accents,white readable text,rounded cards and both Dark and Bright Mode.Fix all invisible text,labels,inputs,dropdowns and buttons.Create a public website with logo,Features,Demo,Pricing,FAQ,Login,Start Free Trial,hero section,photography visuals,testimonials and footer.Login page must contain Studio Diary logo,Email,Password,Login,Forgot Password,Continue with Google,Mobile OTP and Create Account.Each founder profile must have Studio Name,Founder Name,Logo,Photo,Mobile,Email,Address,City,District,State,GST optional and Signature.New founder gets 7 Day Free Trial.Paid plans must be 1 Month ₹90,3 Months ₹199 and 1 Year ₹349.Remove old plans.Store subscription in Firestore and show current plan,expiry and status.Use secure Razorpay order creation and server side payment verification.Never expose Razorpay Key Secret.Main dashboard must contain Studio Overview,Client Bookings Diary,Smart Shoot Calendar,Quick Shoot Desk,B2B Services,Completed Bookings and Team Freelancer Ledger.Show Total Bookings,Upcoming Events,Pipeline Value,Amount Collected,Client Balance Due and Crew Pending Dues.Remove unnecessary Studio name chip.New Booking must contain Customer Name,Mobile,Alternate Mobile,Address,Booking Fixed Date,Main Service,Primary Event Type,Referred By,Venue,Notes,Total Deal,Advance,Later Payment,Total Received and auto Remaining Balance.Allow multiple functions with Function Name,Date,Time,Venue and Specific Venue Address.Function dropdown must contain Wedding and Pheras,Haldi,Mehndi,Haldi and Mehndi,Pre Wedding,Tilak,Barichha,Ring Ceremony,Sangeet,Reception,Vidaai,Mundan,Birthday,Anniversary,Nikah,Mayun,Baraat,Rukhsati,Walima,Mangni,Dholki,Aqeeqah and Custom Function.Add a small plus icon in booking header to open Additional Event Services with LED Wall,Camera Crane,TV Screens,Drone,Standee,Selfie Point and Custom Service.Allow quantity,rate and notes.Add Album Sheets,Album Size and Cover Type with Acrylic,Leather,Crystal,Velvet,3D and Custom.Create Smart Calendar with month/year navigation and show all client functions,venue,time and team on selected date.Quick Shoot Desk should support Car Shoot,Reel Shoot,Baby Shoot,Ring Ceremony Shoot,Promotional Shoot,Land Shoot,Shop Shoot and Custom Shoot.Create separate B2B Services module with Studio Name,Founder Name,Contact,Studio Address,Venue Address,Event Date,Reporting Time,Total Deal,Advance,Later Payment,Total Paid and Remaining Balance.Services should include Photo and Video,Photo Camera,Video Camera,Photographer,Videographer,Cinematographer,Drone,Gimbal,Camera Crane,LED Wall,TV,Standee,Selfie Point and Custom Service.Allow quantity,rate,operators and notes.Reuse Additional Event Services components where possible.B2B dashboard must show Total Jobs,Deal Value,Paid Amount and Remaining Balance with View,Edit,Delete,Mark Paid and Generate Invoice options.Store B2B at studios/{uid}/b2bServices/{serviceId}.Team module must have Name,Mobile,Role,Address,Rate and Notes with Photographer,Videographer,Cinematographer,Drone Operator,Gimbal Operator,Editor,Album Designer and Custom roles.Track team payments.Work Status,Delivery Status and Payment Status must remain independent.Delivery options are Not Delivered,Partially Delivered and Delivered with Delivery Date.If material delivered but payment pending show Delivered with pending amount.Create invoices with Studio Logo,Studio Name,Founder,Contact,Customer,Functions,Venue,Services,Total Deal,Advance,Payments,Balance,Status,Signature,Invoice Number and Date.Create five invoice styles Classic Gold,Modern Dark,Clean White,Premium Wedding and Minimal Professional.Founder selects default invoice template in profile.Support Preview,Print and PDF.Add search by customer,mobile,year,month,date,function and venue.Use Firestore structure studios/{uid}/profile/main,studios/{uid}/bookings/{bookingId},studios/{uid}/team/master,studios/{uid}/subscription/current and studios/{uid}/b2bServices/{serviceId}.Each founder must access only their own data.Do not rewrite all bookings when one booking changes.Write only changed booking and delete only selected booking.Use efficient Firestore queries.Never expose server secrets.Make all forms responsive and readable.Handle loading,saving,error,no records,payment success and payment failure.Before changing existing project inspect current code,reuse working components,preserve old records and do not redesign unrelated features.After changes test build,TypeScript,Dark Mode,Bright Mode,mobile,laptop,Firestore,bookings,invoices,B2B and Razorpay.Finally report files changed,features added,database changes,environment variables and manual setup required.

Landing
Landing

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirements Document for studiodiary

1. Introduction

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.

Page 1 of 21

2. System Overview

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.

Page 2 of 21

2a. Product Interpretation and Delivery Boundary

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.

2c. Page Content and Component Coverage

Page 3 of 21

Landing

  • Information/state: Studio Diary logo, hero section with photography visuals, product positioning for Indian photographers, videographers, wedding studios and cinematographers, feature highlights, demo entry, pricing summary, FAQ preview, testimonials, footer.
  • Primary actions: Start Free Trial, Login, navigate to Features, Demo, Pricing, FAQ.
  • Supporting actions: Scroll to sections, open testimonial content, follow footer links.
  • Domain entities: Public marketing content, plan summary (1 Month ₹90, 3 Months ₹199, 1 Year ₹349), testimonial entries.
  • Component responsibilities: Hero with full-bleed wedding photograph and ink scrim, oversized Fraunces headline, gold CTA and underlined Login link; feature band; demo band; pricing band; FAQ accordion; testimonial row with monochrome founder portraits; shared footer.
  • States: Loading (imagery), empty (no testimonials configured), success (content rendered), error (imagery/content fetch failure with graceful fallback), recovery (retry or static fallback content).
Page 4 of 21

Login

  • Information/state: Studio Diary logo, Email field, Password field, Login action, Forgot Password, Continue with Google, Mobile OTP, Create Account.
  • Primary actions: Login with email and password; Continue with Google; request and verify Mobile OTP; Forgot Password; navigate to Create Account.
  • Supporting actions: Toggle password visibility, resend OTP, return to Landing.
  • Domain entities: Founder identity, authentication session.
  • Component responsibilities: Logo block, credential form, social auth button, OTP request/verify flow, recovery link, create-account link.
  • States: Loading (auth in progress), empty (blank form), success (session established, redirect to Dashboard), error (invalid credentials, OTP failure, provider error) with readable inline messages, recovery (Forgot Password path, OTP resend).
Page 5 of 21

Start Free Trial

  • Information/state: Studio Diary logo, new-founder enrollment form, 7-day free trial explanation, plan summary, Create Account action.
  • Primary actions: Create Account and begin the 7-day free trial; navigate to Login.
  • Supporting actions: Review plan pricing before committing.
  • Domain entities: New founder account, trial start date, trial status.
  • Component responsibilities: Enrollment form, trial terms block, plan summary, submit action.
  • States: Loading (account creation), empty (blank form), success (account created, trial started, redirect to Profile/Dashboard), error (validation or provider failure) with readable messages, recovery (correct and resubmit).

Features

  • Information/state: Detailed product capability descriptions covering bookings, smart calendar, quick shoot desk, B2B services, team ledger, invoices and search.
  • Primary actions: Navigate to Demo, Pricing, Start Free Trial, Login.
  • Supporting actions: Scroll through feature sections.
  • Domain entities: Feature descriptions, product screenshots/visuals.
  • Component responsibilities: Feature sections, imagery blocks, CTA band, shared footer.
  • States: Loading, success, error with fallback, recovery.
Page 6 of 21

Demo

  • Information/state: Product demonstration content for prospective studios.
  • Primary actions: Start Free Trial, Login, navigate to Pricing/FAQ.
  • Supporting actions: Step through demo content.
  • Domain entities: Demo media, walkthrough steps.
  • Component responsibilities: Demo viewer/section, CTA band, shared footer.
  • States: Loading, empty (demo unavailable), success, error with fallback, recovery.

Pricing

  • Information/state: The three paid plans — 1 Month ₹90, 3 Months ₹199, 1 Year ₹349 — and the 7-day free trial for new founders. Old plans are not shown.
  • Primary actions: Start Free Trial, Login, proceed toward subscription purchase.
  • Supporting actions: Compare plans.
  • Domain entities: Plan name, duration, price, trial terms.
  • Component responsibilities: Plan comparison band, trial callout, CTA band, shared footer.
  • States: Loading, success, error with fallback, recovery.
Page 7 of 21

FAQ

  • Information/state: Frequently asked questions about Studio Diary, plans, trial, data privacy and usage.
  • Primary actions: Expand/collapse questions, Start Free Trial, Login.
  • Supporting actions: Navigate to Pricing/Features.
  • Domain entities: Question/answer entries.
  • Component responsibilities: Accordion list, CTA band, shared footer.
  • States: Loading, empty (no entries), success, error with fallback, recovery.

Dashboard

  • Information/state: Studio Overview, Client Bookings Diary, Smart Shoot Calendar, Quick Shoot Desk, B2B Services, Completed Bookings and Team Freelancer Ledger entry points. Six headline figures: Total Bookings, Upcoming Events, Pipeline Value, Amount Collected, Client Balance Due, Crew Pending Dues. No Studio name chip.
  • Primary actions: Navigate to each module; open a booking, B2B job, team record or invoice.
  • Supporting actions: Switch Dark/Bright Mode, open Profile, open Subscription.
  • Domain entities: Bookings, functions, B2B services, team records, invoices, subscription state, aggregate figures.
  • Component responsibilities: Navigation rail, Studio Overview panel, module entry cards, six-figure summary band, mode toggle.
  • States: Loading (aggregates computing), empty (no records yet, with guidance to create the first booking), success (figures rendered), error (query failure with retry), recovery (retry or partial figures with notice).
Page 8 of 21

Profile

  • Information/state: Studio Name, Founder Name, Logo, Photo, Mobile, Email, Address, City, District, State, GST (optional), Signature, and the default invoice template selection.
  • Primary actions: Save profile; upload Logo, Photo and Signature; select default invoice template.
  • Supporting actions: Edit individual fields, preview signature.
  • Domain entities: Founder profile record at studios/{uid}/profile/main.
  • Component responsibilities: Profile form, media upload controls, GST optional field, invoice template selector.
  • States: Loading (profile fetch), empty (new founder with no profile yet), saving, success (saved confirmation), error (validation or write failure) with readable messages, recovery (correct and resave).
Page 9 of 21

Subscription

  • Information/state: Current plan, expiry and status; 7-day free trial state for new founders; the three paid plans 1 Month ₹90, 3 Months ₹199, 1 Year ₹349.
  • Primary actions: Purchase or renew a plan through Razorpay; view current plan, expiry and status.
  • Supporting actions: Compare plans, retry a failed payment.
  • Domain entities: Subscription record at studios/{uid}/subscription/current; Razorpay order and verification result.
  • Component responsibilities: Plan selector, current-plan panel with expiry and status, Razorpay checkout trigger, payment result handler.
  • States: Loading (subscription fetch), empty (no subscription yet, trial offered), saving (order creation), success (payment verified, plan and expiry updated), error (order or verification failure), payment failure (clear failure message with retry), recovery (retry purchase without duplicating a verified payment).
Page 10 of 21

Bookings

  • Information/state: Client Bookings Diary list and Completed Bookings view; searchable by customer, mobile, year, month, date, function and venue.
  • Primary actions: Create a new booking; open a booking; search and filter; delete a selected booking.
  • Supporting actions: Sort and page through records; jump to Smart Calendar.
  • Domain entities: Booking records at 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.
  • Component responsibilities: Booking list, search/filter bar, new-booking action, row actions, empty-state guidance.
  • States: Loading, empty (no bookings, with create prompt), success, error (query failure with retry), recovery (retry or narrowed query).
Page 11 of 21

Booking Details

  • Information/state: Customer Name, Mobile, Alternate Mobile, Address, Booking Fixed Date, Main Service, Primary Event Type, Referred By, Venue, Notes, Total Deal, Advance, Later Payment, Total Received and auto-calculated Remaining Balance. Multiple functions with Function Name, Date, Time, Venue and Specific Venue Address. Additional Event Services with quantity, rate and notes. Album Sheets, Album Size and Cover Type.
  • Primary actions: Save booking; add/remove functions; open Additional Event Services via the small plus icon in the booking header; add/remove event services; set album details.
  • Supporting actions: Select function from the accepted dropdown; select cover type; enter custom function, custom service or custom cover type.
  • Domain entities: Booking record, function rows, event service rows, album specification.
  • Component responsibilities: Customer block, money block with live Remaining Balance, function row editor with the full function dropdown, plus-icon drawer for Additional Event Services, album block.
  • States: Loading, empty (new booking), saving, success (saved confirmation), error (validation or write failure) with readable messages, recovery (correct and resave; only the changed booking is written).
Page 12 of 21

Smart Calendar

  • Information/state: Month and year navigation; all client functions, venue, time and team shown for the selected date.
  • Primary actions: Navigate months and years; select a date; open a function or booking.
  • Supporting actions: Jump to a booking from the calendar.
  • Domain entities: Booking functions with date, time, venue and assigned team.
  • Component responsibilities: Month grid, month/year navigator, selected-date detail panel.
  • States: Loading, empty (no functions on the selected date), success, error (query failure with retry), recovery.

Quick Shoot Desk

  • Information/state: Quick shoot records supporting Car Shoot, Reel Shoot, Baby Shoot, Ring Ceremony Shoot, Promotional Shoot, Land Shoot, Shop Shoot and Custom Shoot.
  • Primary actions: Create a quick shoot; select shoot type; save; open an existing quick shoot.
  • Supporting actions: Use Custom Shoot for unlisted types.
  • Domain entities: Quick shoot records with shoot type and associated details.
  • Component responsibilities: Shoot type selector, quick shoot form, quick shoot list.
  • States: Loading, empty (no quick shoots, with create prompt), saving, success, error with readable messages, recovery.
Page 13 of 21

B2B Services

  • Information/state: B2B dashboard showing Total Jobs, Deal Value, Paid Amount and Remaining Balance, with View, Edit, Delete, Mark Paid and Generate Invoice options.
  • Primary actions: View, Edit, Delete, Mark Paid and Generate Invoice on a B2B job; create a new B2B job.
  • Supporting actions: Filter and sort B2B jobs.
  • Domain entities: B2B service records at studios/{uid}/b2bServices/{serviceId}.
  • Component responsibilities: B2B summary band, job list, per-row action set, new-job action.
  • States: Loading, empty (no B2B jobs, with create prompt), success, error with retry, recovery.

B2B Details

  • Information/state: Studio Name, Founder Name, Contact, Studio Address, Venue Address, Event Date, Reporting Time, Total Deal, Advance, Later Payment, Total Paid and Remaining Balance. Service lines with quantity, rate, operators and notes.
  • Primary actions: Save B2B job; add/remove service lines; select services; mark paid.
  • Supporting actions: Select from the accepted service list; enter a Custom Service.
  • Domain entities: B2B service record with service lines and payment data.
  • Component responsibilities: Client/studio block, event block, service line editor reusing Additional Event Services components where possible, payment block with live Remaining Balance.
  • States: Loading, empty (new B2B job), saving, success, error with readable messages, recovery (only the changed record is written).
Page 14 of 21

Team Ledger

  • Information/state: Team master records with Name, Mobile, Role, Address, Rate and Notes; roles Photographer, Videographer, Cinematographer, Drone Operator, Gimbal Operator, Editor, Album Designer and Custom. Team payments tracked. Work Status, Delivery Status and Payment Status kept independent. Delivery options Not Delivered, Partially Delivered and Delivered with Delivery Date; when material is delivered but payment is pending, show Delivered with pending amount. Crew Pending Dues surfaced.
  • Primary actions: Add/edit/remove a team member; record a team payment; set Work Status, Delivery Status and Payment Status independently; set Delivery Date.
  • Supporting actions: Select role from the accepted list; enter a Custom role.
  • Domain entities: Team master at studios/{uid}/team/master; team payment records; status fields.
  • Component responsibilities: Team master list, member form, payment tracker, independent status controls, delivery status with date, pending-dues display.
  • States: Loading, empty (no team members, with add prompt), saving, success, error with readable messages, recovery.
Page 15 of 21

Invoices

  • Information/state: Invoices containing Studio Logo, Studio Name, Founder, Contact, Customer, Functions, Venue, Services, Total Deal, Advance, Payments, Balance, Status, Signature, Invoice Number and Date. Five styles: Classic Gold, Modern Dark, Clean White, Premium Wedding and Minimal Professional. The founder's default template from Profile is preselected.
  • Primary actions: Generate an invoice; Preview; Print; export PDF; select an invoice style.
  • Supporting actions: Override the default style for a single invoice; open the source booking or B2B job.
  • Domain entities: Invoice records derived from bookings and B2B jobs; invoice style; invoice number and date.
  • Component responsibilities: Invoice list, style selector, invoice sheet renderer for all five styles, Preview/Print/PDF toolbar.
  • States: Loading, empty (no invoices, with generate prompt), saving, success (invoice generated), error with readable messages, recovery (regenerate without duplicating).

Search

  • Information/state: Record discovery across bookings and B2B jobs using customer, mobile, year, month, date, function and venue.
  • Primary actions: Enter search criteria; run search; open a result.
  • Supporting actions: Clear filters; combine criteria.
  • Domain entities: Booking and B2B records matching the criteria.
  • Component responsibilities: Search form with all accepted criteria, results list, empty-state guidance.
  • States: Loading, empty (no matching records), success, error with retry, recovery (broaden or clear criteria).
Page 16 of 21

3. Functional Requirements

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.

Page 17 of 21

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.

Page 18 of 21

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.

Page 19 of 21

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.

Page 20 of 21

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

Page 21 of 21
Landing design preview

Landing: Open public site

Login: 1. Sign in to studio workspace

Login: 2. Recover password via Forgot Password

Dashboard: Open B2B services module

B2B Services: 1. Review total jobs and balances

B2B Services: 2. Create a new B2B job

B2B Details: 3. Enter studio, contact and event details

B2B Details: 4. Add service lines with quantity and rate

B2B Details: 5. Save job and check remaining balance

B2B Details: 6. Correct validation error and resave

B2B Services: Mark job paid

B2B Services: Edit selected job

B2B Services: Delete selected job

B2B Services: Generate invoice for job

Search: 7. Search jobs by studio and venue

Landing design preview

Landing: Open public site

Login: 1. Sign in to studio workspace

Login: 2. Recover password via Forgot Password

Dashboard: Open B2B services module

B2B Services: 1. Review total jobs and balances

B2B Services: 2. Create a new B2B job

B2B Details: 3. Enter studio, contact and event details

B2B Details: 4. Add service lines with quantity and rate

B2B Details: 5. Save job and check remaining balance

B2B Details: 6. Correct validation error and resave

B2B Services: Mark job paid

B2B Services: Edit selected job

B2B Services: Delete selected job

B2B Services: Generate invoice for job

Search: 7. Search jobs by studio and venue