Owning a consumer product end to end

On Vivaahli I did not hire a designer, a marketer, and a backend team. I owned the whole surface: what to build, how it looks, how money moves, and how families find it. That is the job I am describing when I say “product engineer” or “end-to-end.”

The product job

Indian weddings have two jobs that keep failing in existing tools:

1. A biodata elders will print and hand over
2. A digital invite cousins will open on WhatsApp

I scoped Vivaahli to those two makers. Preview free, pay once, no signup until trust. Live preview must match the PDF. Field labels work in Indian languages. AniReco is the parent company on Razorpay; Vivaahli is the name families see.

That scope is a product decision, not a tech one. Saying no to a matrimony marketplace and a subscription SaaS kept the surface shippable by one person.

Design without a design org

Design here meant:

• Choosing templates families would actually print (not Dribbble cards)
• Making the form readable for parents checking details in Hindi or Marathi labels
• Keeping the invite microsite calm enough for elders and shareable enough for cousins
• Matching on-screen preview to the PDF so “what you see” is not a surprise at the printer

I did not write a brand book. I iterated with real wedding timelines and WhatsApp feedback. Taste was a constraint: if a father would not hand the PDF to a relative, the template was wrong.

Marketing without a growth team

Go-to-market for a wedding tool is not a SaaS playbook. Families show up with a date and leave when the job is done. What worked:

• Clear pricing on the page (from ₹99, one-time). No “contact sales.”
• Parent brand honesty. Bank statements may say AniReco. The site explains that.
• Distribution through the job. A good biodata gets forwarded. A good invite gets opened. Product quality is the funnel.
• Lightweight analytics to see where people stall in the maker, then fix those steps.

I did not run a large paid ads machine as the primary channel. For a one-shot consumer job, trust and shareability beat CAC gymnastics.

Tech that serves the evening

The stack (Next.js, Razorpay, PDF generation, Cloudflare) exists so a family can finish in about five minutes. Payments and PDFs are load-bearing. Clever architecture that slows the preview is a product bug.

Internals stay shallow in the public case study because the product is live. The ownership story does not need a schema dump: I built the makers, the pay wall, the templates, and the path to first share.

What “owning it” selects for

If you hire me for product ownership, you get someone who:

• Narrows scope until one person can ship
• Treats design and go-to-market as part of engineering, not afterthoughts
• Will kill a product when the economics fail (see AniReco)
• Prefers real usage metrics over slide decks

Live metrics on Vivaahli (biodatas created, family rating, time to finish) are the resume line. The rest is judgment.

More on fit and track record: About.