Launch publicly.
Do not keep polishing in private. Put the product in front of people early enough for their response to change what you build.
Founder-led experiment · legal workflow · customer discovery
For 10 weeks, I spoke with lawyers in India and the U.S. to test whether litigation workflow pain was urgent enough for a product people would adopt and pay for.
Users are your boss.
01 · What I was testing
Vakilaru started from a problem I understood as a lawyer: litigation work is messy, repetitive, high-pressure, and poorly supported by tools.
I later renamed the product LegallyLite after acquiring the domain. This case study keeps the original Vakilaru name so the founder-led experiment stays distinct from the separate Legally Lite hackathon game.
The question was whether the pain was urgent enough for a focused workflow product. We spoke with lawyers in India and the U.S. and explored client updates, drafts, deadlines, and multilingual support. There was pain, but not a repeatable pattern strong enough to justify this exact direction.
If users do not care enough to change how they work, that is the answer.
03 · Pointers I took from the experiment
Do not keep polishing in private. Put the product in front of people early enough for their response to change what you build.
If they do not understand it, care about it, or return to it, that is your problem—not a failure on their part to understand the vision.
“This would be useful” is not enough. Look for a problem painful enough to interrupt the way someone already works.
A clean demo can get compliments. The signal is whether someone asks to use it now, comes back, or pays for it.
Decide what would justify continuing before momentum makes the decision for you. We did not find enough urgency, willingness to pay, or a repeatable pattern, so we stopped.