Skip to content
0→1 build·live

Sutradhar

An AI copilot for wedding planners that turns WhatsApp chaos into a plan.

A working MVP live for solo freelance wedding planners: structured intake, a completeness copilot, and WhatsApp automation for chasing confirmations, built on a direct Meta Cloud API integration with no middleware.

ReactNode/ExpressGeminiNetlifyRenderMeta WhatsApp Cloud APIProblem framingGTM strategyRoot cause analysisNorth Star metrics
Sutradhar full deckOpen full screen

What it is

The one who holds the thread.

Wedding planners run entire events out of WhatsApp threads and memory. Sutradhar — Sanskrit for the one who holds the thread — structures the intake, flags what a plan is missing, and chases confirmations automatically, so nothing culturally important dies under forty unread messages.

Built with Sandeep Upadhyay and Shagun Jain. I own the product, the AI layer, and the WhatsApp automation design.

How it works

From a rough brief to a chased confirmation

  1. 1
    Client brief lands

    Rough and messy, exactly as planners actually receive it.

  2. 2
    AI structures the plan

    Intake turns it into a full event plan. No retyping into a notes app.

  3. 3
    Gaps get flagged

    A completeness copilot checks the plan against cultural and preference knowledge.

  4. 4
    WhatsApp chases for you

    Vendor and family confirmations, sent directly through the Meta Cloud API.

  5. 5
    The day starts prioritized

    Top urgent items across every active event, surfaced each morning.

Product

What it looks like

Sutradhar dashboard showing active events
Dashboard
New client intake screen
New intake
Structured event plan view
Event plan
WhatsApp confirmation message sent through the Meta Cloud API
WhatsApp automation

The pivot

Couples were the wrong user. Planners are.

PlanMyVows · killed
  1. Built for couples planning their own wedding.

  2. One wedding, ever. No repeat use.

  3. No compounding data, no reason to come back next year.

Sutradhar · built
  1. Built for the solo freelance planner.

  2. Dozens of events a year, repeat use by design.

  3. Every event makes the tool smarter for the next one.

A real market to exist in

$105B
India wedding services, 2024
$238B
projected by 2030
46%
of couples hire a planner
0
middleware layers on WhatsApp

Tradeoffs

Decisions I'd defend

Chose

Build for the professional planner

over Building for the couple

A couple is a one-time, low frequency user with no compounding data. A planner runs events repeatedly and the product gets more useful to them the more events it sees. That's a business worth building on.

Chose

Integrate the Meta Cloud API directly

over Using a WhatsApp middleware provider

Middleware is faster to stand up but adds a cost layer and a dependency I don't control. Direct integration took longer but means the confirmation flows aren't renting someone else's rate limits.

Chose

AI flags gaps, a human still confirms them

over Fully automatic plan completion

A planner's judgment on cultural and family specifics is the actual product. The AI's job is to make sure nothing gets missed, not to decide what matters.

Honest gaps

What isn't built yet

Human-in-the-loop review
Next

AI suggestions still write straight into the plan. An approval queue for the planner is the next fix.

No accuracy benchmark
Open

Quality is measured by planner accept, edit, or reject. No labeled precision number yet, and I won't invent one.

Meta platform dependency
Risk

Template approvals and pricing sit with Meta. A risk I plan around, not one I control.

The North Star is events completed on their target date with no missed vendor deadlines — a stricter bar than engagement, and the only number that reflects whether the product did its job.
North Star — events completed, not messages sent
Next · build

TailorTrip

Bring a mood, get a decision. A travel planner that does the cognitive heavy lifting.

Continue