Validating a Fintech Idea in India Before Writing a Single Line of Code — The UdharPay Approach

The Most Expensive Mistakes a Founder Can Make

The most expensive mistake a founder can make is building something nobody wants. The second most expensive mistake is spending six months validating something so obvious that validation itself was the waste of time.

The truth about UdharPay's validation is somewhere in between — and the process taught me more about building products than any course, book, or mentor advice ever did.

Why I Decided to Validate Before Building

I had two pieces of evidence before I started:

• My friend's shop had ₹47,000 in outstanding credit and no system to collect it.
• Khatabook raised $60 million proving that Indian small business owners would use digital tools to track credit.

Neither of these is validation. One is an anecdote. One is a market signal that someone else captured.

What I needed to know was: would shop owners pay ₹299 per month for automated WhatsApp reminders? Would they find it useful? Would they be suspicious? Would they trust a tool to contact their customers on their behalf?

I could not answer these questions from my desk. I needed to talk to shop owners.

The Google Form Strategy

Before building anything, I created a 12-question Google Form. The form had four sections:

• Section one asked about the business — type, outstanding credit, number of customers.
• Section two asked about the pain — problems faced collecting payment, losses, current tools.
• Section three asked about the solution — usefulness of a WhatsApp reminder tool, willingness to pay ₹299 per month, must-have features.
• Section four was the waitlist — phone number and business name, promise of lifetime free access to the first 50 respondents.

I shared this form on Instagram, LinkedIn, WhatsApp groups, Facebook groups for kirana store owners, and Reddit. I personally visited five shops near my home and helped owners fill it in on the spot.

What the Data Said

In the first seven days, 73 people completed the form. Of those 73:

• 61% said automated WhatsApp reminders would be extremely useful (5/5)
• 54% said they would definitely pay ₹299 per month
• 23% said they would pay only if the product was free
• 8% said they were happy with their current setup

The must-have features, in order of frequency, were:

• WhatsApp auto-reminder
• UPI QR code in the message
• One-click mark as paid
• Hindi language support
• Monthly collection report

The Insight That Changed the Product

The most valuable data came from the open-ended question: "Any other pain or feedback we missed?"

One response from a hardware shop owner in Nagpur changed the product permanently:

"Mujhe reminder se zyada dikkat ye hai ki customer ko pata hi nahi hota ki kitna baaki hai. Agar message mein amount clearly likha ho aur pay karne ka ek button ho — toh 90% log turat pay kar denge."

Translation: My bigger problem is that customers do not even remember how much they owe. If the message clearly states the amount and has a single button to pay — 90% of people will pay immediately.

This confirmed that the UPI QR code inside the WhatsApp message was not a nice-to-have. It was the product. The reminder plus frictionless payment in a single message — that combination is what makes people pay. Everything else is supporting infrastructure.

What Validation Did Not Tell Me

Validation told me that shop owners wanted this product. It did not tell me whether they would actually change their behavior to use it. Saying you will pay for something and paying for something are two different things. The only true validation is a paying customer. Everything before that is signal, not proof.

I treat my 73 form responses as strong signal. My first ₹299 payment will be proof. We are 50% through development. The moment that payment comes in, I will write about it here.

The Lesson for Other Founders

If you have an idea, especially in fintech or tools for Indian small businesses, do not spend six months building before validating. A Google Form, a WhatsApp broadcast, and one afternoon of walking into local shops will tell you more than six months of assumptions.

Total time invested before starting to code: approximately 20 hours. Total insight gained: enough to change two core features before building them. That is the best ROI I have ever generated.

Need a website for your business?

We build custom websites, apps, and e-commerce stores. Based in Pune, India.

More from the Blog