"When Your Customers Jump Through Hoops, You've Found Product-Market Fit"

The Journey

Girish Redekar spent two to three years building products nobody wanted before landing on RecruiterBox. Then he bootstrapped it to 2,500+ customers and eventually sold the business.

But the most important signal he got came before any of that success. Before Stripe existed. Before they had a way to collect payments. When the product was held together with duct tape and a PayPal link.

That's when he learned something most founders miss. You don't find product-market fit by measuring NPS scores or tracking activation metrics. You find it by watching whether customers will endure pain to use your product.

The Early Days: Duct Tape and PayPal Links

RecruiterBox launched pre-Stripe. Think about that for a second. No recurring billing. No payment processing. No way to charge a credit card inside the product.

So they improvised. "If you liked RecruiterBox and you wanted to pay for it, we'd give you like a PayPal link. You go there, you swipe your card and depending on how much you paid there, we would add a certain number of credits in RecruiterBox and they would basically get deducted on like a daily basis."

Eventually you ran out of credits. Then you had to go back to PayPal and swipe your card again.

"It was really bad," Girish admits. No subscription. No auto-renewal. Manual PayPal transactions every time your credits ran dry. Daily credit deductions ticking away like a meter.

Every founder instinct says fix this immediately. Build proper billing. Make it seamless. But the broken billing system turned out to be the best product-market fit test they ever ran.

The Signal: Pain Tolerance as a Metric

"What really surprised us was how many customers actually went ahead and did that."

That's the line. That's the entire lesson.

People were voluntarily going through a terrible payment process, repeatedly, to keep using RecruiterBox. Nobody forced them. Nobody gave them a discount for the hassle. They chose the pain because the product solved a real problem.

Girish saw it clearly: "We're doing this in such a bad manner and yet people are taking that pain in order to actually go and do that. That means what we are building is valuable, at least for these set of customers."

The friction wasn't a bug. It was a filter. Only customers who genuinely needed the product would tolerate that experience. And enough of them did to prove the market was real.

The Lesson: Validation Through Friction

Years later, when Girish started Sprinto, he took a completely different approach to validation. He read The Mom Test, which "had a big influence on me fundamentally because it was written by a person who is basically a software engineer and about how to go about really knowing whether what you're building is valuable and useful."

He told himself: "We're not going to write a line of code until we can validate what we are building is valuable." He did 15 to 20 interviews before committing to the idea.

But the principle was the same one he'd learned at RecruiterBox. Are people willing to endure discomfort to get this problem solved? With RecruiterBox, they proved it accidentally through broken billing. With Sprinto, they proved it intentionally through rigorous validation.

Both approaches asked the same question. Is the pain of the problem worse than the pain of the solution?

What You Should Steal

• Watch for pain tolerance, not satisfaction. The best PMF signal isn't "customers love it." It's "customers tolerate terrible UX to keep using it." If people jump through hoops, you're onto something.
• Don't fix friction too fast. Early friction reveals who your real customers are. The ones who stick around despite a bad experience are telling you something important.
• Use The Mom Test before you build. Girish learned the hard way (two to three years of failed ideas) that talking to people first saves time. Validate before you code.