← All work

Case study

Vivaahli

Wedding-tech for Indian families

Live
Biodatas created
1.4K+
Templates
20
Languages
10
Family rating
4.8/5
Time to finish
~5 min
Pricing
From ₹99
Role · Solo (product, design, marketing, UI, payments, PDF pipeline)Timeline · 2025-presentRead · ~12 min (skim or deep)
  • Next.js
  • TypeScript
  • Razorpay
  • PDF generation
  • Cloudflare

90-second story

Indian families need a biodata for elders and a shareable invite for cousins, often in the same evening. Generic Canva templates and matrimony dumps both fail that job. I built Vivaahli as two focused makers: marriage biodata and digital invites. I owned product, design, go-to-market, payments, and the PDF pipeline. Preview free, pay once, no signup required. Live preview matches the PDF. Field labels work in Indian languages so a parent can check the form. AniReco is the parent company on Razorpay; Vivaahli is the consumer brand. This writeup stays at product-system depth because the product is live.

The story

A wedding in an Indian family is not one audience. Fathers want a printed biodata they can hand over. Cousins want something on WhatsApp. Planners want an RSVP count without calling every relative.

The problem: Existing tools force a bad split. Canva or Word means fighting layout, print size, and language labels by hand. Matrimony sites dump forms that feel like paperwork, not something you share with pride.

Constraints I designed around:

  • No signup before the family trusts the preview.
  • Live preview must match what they download or print.
  • Field labels in Indian languages so elders can check details themselves.
  • One-time price. A wedding is a one-shot job, not a subscription.
  • Bank statements may show AniReco (parent company). Vivaahli is the name families see on the site.

Approach: what I considered

  • Canva / Word templatesRejected

    Fast to start, then every family fights layout, language, and print size again. Not a product.

  • Account-required SaaS + subscriptionRejected

    A wedding is a one-shot job. Forced accounts and monthly fees kill trust before the preview.

  • Purpose-built maker, preview free, pay onceChosen

    Guided fields, designer templates, Indic labels, live preview that matches the PDF. Pay when happy.

I shipped two products under one brand: a biodata maker (20 designer templates, Indic labels, print-ready PDF) and digital wedding invites (microsite, QR, WhatsApp card, RSVP by name). Families use one or both across the wedding journey.

How it works

In one sentence: A family picks a template, fills guided fields (labels can be in an Indian language), watches a live preview, pays once when they are happy, then gets a print-ready PDF or a shareable invite with RSVP.

The flow in plain language

This is what happens end to end:

  1. Pick a design. Browse curated biodata or invite templates. Filter by language, community, and style.
  2. Fill guided fields. Labels can switch to an Indian language so a parent can review every line.
  3. Watch the preview. The on-screen layout updates as you type. What you see is what you get.
  4. Keep going without an account. The draft stays in a private browser session until you pay or claim the download.
  5. Pay once. Razorpay checkout. The charge may appear as AniReco on the bank statement; that is the parent company.
  6. Take the output. Biodata: print-ready PDF plus a shareable image. Invite: microsite link, QR code, WhatsApp card, and RSVP by name with live counts.

If that makes sense, the diagram below shows where each step sits. The chapters after explain why those product choices matter.

Why this diagram: Families stay in the maker until they trust the preview. Checkout and merchant branding are a deliberate seam, not an accident.

Product map: browser session to paid outputs

  1. 1. Pick a template

    Biodata or invite. Filter by language, community, and style.

  2. 2. Fill guided fields

    Indic labels so elders can check the form themselves.

  3. 3. Live preview

    On-screen layout updates as you type. Preview matches the download.

  4. 4. Draft in the browser

    Private session. No account required before pay.

  5. 5. Pay once

    Razorpay. Statement may show AniReco (parent company).

  6. 6. Take the output

    Biodata: PDF + image. Invite: microsite, QR, WhatsApp card, RSVP.

One session mapped to the steps above

No account until pay

Abstract: Force a signup before the preview and you lose families who are just trying a template for their parents. Vivaahli lets them build first.

You can start immediately. The draft lives in a private browser session until you pay or claim the download. That matches how people actually shop for a biodata: open a few designs, fill a few fields, show mom, decide.

This chapter stops at the product rule. How the session is stored is intentionally out of scope for a live product writeup.

Abstract: One biodata has to satisfy two generations. Print for elders. Phone share for cousins. The form itself has to be checkable by a parent who does not want English-only labels.

The public product promise is simple: live preview that matches the PDF, and 11 Indian language labels on the fields. That is not decoration. A mother reading Tamil labels and a father carrying a printed sheet to a meeting are the same purchase.

One artifact or two?

  • Separate print template and WhatsApp cardRejected

    Families would maintain two designs and two sets of details. Errors multiply.

  • One template, dual outputChosen

    Same content, print-ready PDF plus shareable image. Preview is the contract for both.

Two products, one wedding

Abstract: A biodata and a wedding invite solve different jobs. Bundling them into one “wedding OS” would slow both checkouts.

Biodata maker Digital invites
Job Marriage biodata for print and share Shareable invite with RSVP
Price From ₹99, one-time ₹699, one-time, 1 year hosting
Output Print-ready PDF + image Microsite, QR, WhatsApp card, RSVP by name
Languages 10 (11 Indic field labels) 6

Families can use one, or both, across the wedding. Each product has its own start path on the homepage.

Wedding OS vs focused makers

  • One wedding platform, one checkoutRejected

    Different jobs, different price points, different success criteria. One funnel would blur both.

  • Two products, shared brandChosen

    Biodata and invites stay focused. Same brand, usable together when the family needs both.

What I took away

Vivaahli is live. Families have created 1.4K+ biodatas. Average family rating sits at 4.8/5. Median time to finish is about five minutes.

What I keep coming back to:

  1. Trust the preview. If the screen matches the download, people pay without a sales pitch.
  2. Design for the family, not just the buyer. Indic labels and print fidelity are product requirements, not polish.
  3. Ship focused jobs. Two makers beat one bloated wedding suite for this audience.
  4. Name the merchant clearly. AniReco is the parent company on Razorpay and bank statements. Vivaahli is the consumer brand. Confusion here is a support ticket waiting to happen.

This writeup stops at the product system on purpose. The live app keeps the LLD private. If you want to see the product, visit vivaahli.com.