Reviewer's guide · every page, what to tap, what we're asking
The tour
Every mockup is interactive, and the interactions are the argument — buttons flip states, boards update, signatures land. Each entry: whose seat you're sitting in, what the page proves, what to tap, and the question your feedback should answer. Use the ✎ FEEDBACK button (or ✏ ANNOTATE to pin notes to specific spots) on any page.
Short on time? The 20-minute spine
Ten stops that carry the whole thesis — one wedding, Priya & Arjun, followed from setup to settling:
Start & plan HOW A WEDDING IS BORN
15 · New Wedding WizardPLANNER OR COUPLE
Two minutes of setup: couple, dates, funding sides — and the admin-seat choice that defines the whole tenancy model.
TRY Toggle planner-led ↔ self-plan and read how the explainer changes; note the muhurat hand-off link.
ASKING Is "who holds the admin seat" the right first question, or too much machinery on screen one?
09 · Traditions OnboardingPLANNER OR COUPLE
Pick community packs; the wedding's events, ritual checklists, and song/shot seeds generate live. Packs are data — a new culture is a new file, not new code.
TRY Select Tamil Brahmin + Punjabi Sikh and watch the fusion event list build.
ASKING Do the generated events match how real families think about their sequence? What's missing from the packs you know?
02 · Couple PortalCOUPLE
The couple's scoped surface: decisions awaiting them, typed e-signature, small joyful choices (baraat picker).
TRY Sign a decision with a typed signature; pick a baraat option.
ASKING Does signing feel weighty enough to matter but light enough to actually happen same-day?
16 · Self-Plan HomeCOUPLE (ADMIN)
Same engine, couple in the driver's seat — with the invite-a-planner handoff card: the growth loop, visible.
TRY Tap "Invite a planner" and read what transfers.
ASKING Would a self-planning couple trust this enough to start here — and does the handoff promise feel real?
10 · Roles & PermissionsPLANNER (ADMIN)
Capability grid per module, role bundles, and "view as" preview — the permission model that RLS enforces at the database.
TRY Flip a capability; use "view as" to see a family member's world.
ASKING Are six bundles the right set? What role exists at real weddings that this can't express?
11 · Muhurat FinderCOUPLE / FAMILIES
Community + calendar inputs → a candidate-date shortlist framed for the family's panditji — a shortlist, never a verdict. Sikh mode swaps to gurdwara availability.
TRY Change community and watch the calendar system and framing change.
ASKING Is the deference to the panditji pitched right — helpful without overstepping?
13 · Outfits & TrousseauCOUPLE / FAMILIES
Looks per event per person, tailor status, fitting dates — the parallel logistics track weddings actually run on.
TRY Walk the looks across events; check a fitting status.
ASKING Core module or delightful extra? Be honest — it affects sequencing.
Guests HOUSEHOLDS, RSVPS, ROOMS
04 · Guest RSVPGUEST · NO LOGIN
A browser link, per-event responses, meals — the invite matrix from the guest's side.
TRY RSVP yes to ceremony, no to reception; pick meals.
ASKING Could your parents complete this without calling you?
06 · Guest HubGUEST · PUBLIC
The wedding's public face — schedule, dress codes, maps — deliberately themed in a different palette (Rani & Aubergine) to prove per-wedding theming over one engine.
TRY Compare its skin against every other page's Sindoor & Silk.
ASKING Does per-wedding theming feel premium, or does the tool's identity need to win?
22 · SeatingPLANNER
Households seat together by default; person is the unit of assignment. Named, described tables and a draggable to-scale floor plan — the arrangement is data.
TRY Tap ✂ on the Gills, seat the kids (watch them prefer Gulab Jamun), rename Marina Beach and watch the floor plan sync, then drag tables around.
ASKING Does household-default-with-splits match how you've actually seated weddings?
Vendors SOURCE → QUOTE → BRIEF → CONFIRM
08 · Sourcing & RFQ ComparePLANNER
One structured scope to N vendors; quotes come back comparable side-by-side, with roster history in view.
TRY Compare the three quotes; accept one and see what it triggers.
ASKING What column is missing from the comparison that decides real vendor picks?
The other side of 08: quoting against a fixed scope, with W-9/COI riding along from the global vendor account — never emailed again.
TRY Toggle teardown off and read the flag warning; submit.
ASKING Would a busy vendor do this instead of emailing a PDF? What would make them?
03 · Vendor PortalVENDOR × ONE WEDDING
Everything a vendor sees for one engagement: song list to confirm, info request to fill, invoice upload. Nothing outside their slice exists.
TRY Confirm the song list; fill the info request (day-of contact, arrival) — those fields flow to the run sheet.
ASKING Is this small enough that a DJ actually uses it?
18 · Brief BuilderPLANNER
Composing what 03 receives: ritual moments seeded from packs, photo groups from real RSVP, couple must-haves, versioned send.
TRY Add a must-have shot; send v3 and read the versioning promise.
ASKING Does seeding from packs + RSVP save real time, or would you start from scratch anyway?
23 · Vendor ConfirmationsVENDOR + PLANNER
The T-1 call sheet, compiled automatically, one-tap confirmed against a content snapshot. Born from a real caterer disaster. Told is deniable; confirmed is not.
TRY Both paths — tap "Something's off" and send the flag (watch the board and planner alert), then reload and tap Confirm instead.
ASKING Would this have prevented your worst vendor story? What detail is missing from the sheet?
Money FUNDERS, CHANGES, THE CHASE
05 · Family Funder PortalFAMILY VOICE
A parent's world: only their side's budget lines, payment requests routed to them, ACH or record-a-Zelle.
TRY Approve and pay a request; record an off-platform payment.
ASKING Would your father-in-law use this — and does side-scoping defuse or create tension?
20 · Change OrderALL PARTIES
Locked scope + delta + budget impact computed before signing, with the funder in the chain because it's his line.
TRY Send CO-2 for signatures; watch the chain queue.
ASKING Does this retire the "but you said" fight, or just move it?
25 · Payments CommandPLANNER (ADMIN)
The money week across all weddings: funder-routed dues, stuck approvals, and reconciliation drift caught weeks early.
TRY Nudge the Taj approval; escalate the overdue florist invoice.
ASKING Which drift check would have saved you real money on a past wedding?
Run the day EXECUTE
07 · Run SheetPLANNER / EVENT LEAD
Per-event timeline with vendor call times (from info requests) and photo groups called from the real RSVP list.
TRY Shift the timeline +15 minutes and watch the ripple.
ASKING Day-of, phone in hand — is this readable at a glance under stress?
12 · NotificationsSYSTEM / ALL
Digest-first rules, escalation ladder, WhatsApp first-class, guests capped at 4 lifetime messages.
TRY Read the ladder; note what interrupts vs what batches.
ASKING Is the 4-message guest cap brave or reckless?
21 · Announcement ComposerPLANNER
Role × event scoping with a live reach preview before send — 428 people never get a message meant for 12.
TRY Toggle audience chips and watch the count recompute; send.
ASKING Is the reach preview enough to make you trust bulk-send?
30 · Comms HubPLANNER
One trail across channels: WhatsApp/SMS/email auto-captured through wedding rails; calls as metadata + outcome; personal iMessage as an honest 10-second LOGGED capture. Everything files into The Record.
TRY Read the channel table (auto vs logged), then file the off-platform text at the bottom.
ASKING Does "paved roads + honest escape hatches" match reality, or will people just never log?
Close it out SETTLE & THE RECORD
17 · SettlePLANNER / COUPLE
Reconciliation, deliverable tracking, shagun log — and the review that visibly lands on the roster. The flywheel turning on screen.
TRY Submit the Rasoi review and read where it goes.
ASKING Would planners actually do reviews here, and is the roster payoff visible enough to motivate it?
27 · The RecordPLANNER / ALL
The audit trail as a surface: every signature, confirmation, payment, and announcement, filterable per party, exportable. You don't argue — you print.
TRY Filter to "Rasoi / Kavita" and read her complete history; then "Signatures only."
ASKING Deterrence feature or paranoia feature — how does it land emotionally?
The studio THE PLANNER'S COMPOUNDING IP
01 · Planner StudioPLANNER (ADMIN)
All weddings in one dashboard, the vendor roster with tiers and private notes, decisions in flight, tag-anywhere Issues.
TRY Send D-15 for signature; open Issues and tag one to an object.
ASKING Is this the screen a planner lives in — what's missing from their morning?
24 · Studio PulsePLANNER (ADMIN)
Proactive signals computed from the studio's own history — RSVP pace vs your curve, aging decisions, double-bookings — each with a one-tap action. Patterns become rules.
TRY Expand the RSVP signal and queue the nudge; make the decor-pad rule at the bottom.
ASKING Which signal would you trust enough to act on without double-checking?
26 · Master CalendarPLANNER (ADMIN)
Every event across every client plus roster engagement dates, cross-checked — the Lumière double-booking caught 124 days out, with resolution paths.
TRY Resolve the Lumière conflict (either path); assign a lead for the Kapoor reception.
ASKING Second crew vs roster backup — are those the real resolution options, and what's the third?
28 · Venue & Layout StudioPLANNER (STUDIO ASSET)
Venues → rooms with real dimensions → to-scale layout sketching, saved per room and reloadable at any future wedding there — plus policy tags (open flame, outside catering/alcohol, baraat horse, curfew) cross-checked against the wedding's traditions-pack requirements at booking. Honest counts: 22 rounds with a dance floor, not "probably 25."
TRY Switch rooms (canvas reshapes to scale), place a mandap, drag it, save a named layout — then run "Check against Shreya & Vikram's requirements" and read the agni and Scotch verdicts.
ASKING Rough-sketch fidelity — enough for real planning, or does this need CAD-grade precision to be trusted?
29 · Template LibraryPLANNER (STUDIO ASSET)
Anything good becomes reusable — schedules, layouts, song seeds, budgets — with personal data auto-stripped. Traditions packs are the same machinery, platform-authored.
TRY Filter by type; save something from a wedding and watch it land in the grid.
ASKING What's the first thing from your own weddings you'd templatize?
31 · Mobile App ShellPLANNER
The installable phone shell — Today / Weddings / Inbox / Pulse — wrapping everything: PWA install, iOS push, offline day-of with the next 48h cached.
TRY Tap all four tabs; read the offline and no-install-for-guests cards.
ASKING PWA-first with native-later — right call, or do planner sales need an App Store icon on day one?
Meta pages THE ARGUMENT ITSELF
Theme ExplorerEVERYONE
The planner home in eight switchable skins — the token-swap mechanism behind studio and per-wedding theming.
TRY Cycle all eight; the feedback template asks for your preferred theme — answer it, this is an open question.
ASKING Which direction wins: 01 Pink City Modern, 03 Charcoal & Genda, 05 Ivory Editorial, or the current Sindoor & Silk?
The PitchFOUNDING PLANNERS
Pain vignettes, value blocks, and pricing — flat tiers plus the 15%-of-fee alternative. The founding cohort is price discovery.
TRY Read pricing as a skeptical planner would.
ASKING Flat or % — which would you pick, and which number makes you flinch?
Data ModelBUILDERS
~30 entities, four domains, key relations, RLS-per-seat — everything the mockups imply, destined to be migration 0001.
TRY Read the relations table — the flywheel and the planner handoff are each one foreign key.
ASKING What entity or relation is missing before we cut the first migration?
THE TOUR · 33 PAGES · EVERY INTERACTION IS THE ARGUMENT