Why I started it
The decorated envelope Indians give cash in at weddings, Diwali, Rakhi and birthdays deserved a digital version that keeps the ceremony and loses the logistics. It is currently being built. The GTM work around it began as a fun side project.
The product decisions
- 21 papers, 14 palettes, 5 textures and 32 mithai make the envelope feel chosen rather than templated.
- A fold animation preserves the small reveal that makes a physical lifafa feel ceremonial.
- The sender builds the nek by tapping notes instead of typing a sterile amount.
- 49 templates across 11 festivals and occasions give the product an entry point beyond weddings.
Why payments stay outside the app
I deliberately left an in-app UPI transaction out of the first version. A new product has no reason to ask people to trust it with money. The money moves UPI to UPI, person to person, and lifafa never holds it.
That decision shaped the security model too. The pay screen is owner-gated so a public link cannot become a phishing kit, financial fields are immutable after creation, and nothing is called verified unless the product can verify it. A built-in payment layer belongs after the product earns trust, not before.
Next
Get people to actually use it during the festive season.