Girish Redekar and the value of an inconvenient question

Girish Redekar once delivered a sales pitch so badly matched to the customer that the customer called a recess. Thirty minutes, please. During the break, the prospect explained why the product would not solve the problem. For an engineer who had come prepared to persuade, it was an unusually considerate defeat. He left with something more durable than an order: a reason to listen before building.

Years later, Redekar would run Sprinto, a company devoted to removing the work that stands between a business and a buyer’s trust. The rejected pitch makes a useful place to begin. His career has repeatedly turned on the distance between what software can do and what someone actually needs. Closing that distance has required code, patience, a co-founder who stayed for the next round, and the occasional admission that the founder himself was slowing things down.

The programmer who learned on the job

Redekar describes himself as an engineer first. His education included the Indian Institute of Technology, Madras; his working life included ZS Associates and HSBC Card Services before Recruiterbox. But an engineering education did not mean arriving at entrepreneurship as a practiced software developer. He and his friend Raghuveer Kancherla taught themselves programming during the early months of their startup efforts.

Their first attempts consumed savings faster than expected. Products failed to catch on. They kept making things, learning to ship more quickly and to absorb feedback. There is something instructively untidy about this beginning. The skills that later made Redekar look suited to starting software companies were partly acquired by starting software companies badly.

Hiring supplied a problem they recognized. Both friends had been involved in growing teams at their employers, where spreadsheets and shared drives made recruiting cumbersome. Recruiterbox offered a place to handle applications and hiring decisions. Alongside fellow co-founder Raj Sheth, they built a business whose practical appeal was easy to explain to anyone who had lost a promising applicant somewhere between a spreadsheet and an inbox.

That early customer’s intervention belongs to this period. The lesson was less flattering than encouragement and more useful: enthusiasm could carry a conversation straight past its purpose. Redekar’s later preference for spending time with the problem has a very human origin. Someone had to stop him talking.

“Problems are more valuable than ideas.”

Girish Redekar

A successful company, and an awkward admission

Recruiterbox grew without venture funding to more than 2,500 customers and a team of over 50 across India and the United States. Those numbers describe a substantial business. They also describe a long apprenticeship in almost every job a software company contains. Redekar moved from programming into product, design, marketing and sales as the business required.

Bootstrapping made him attentive to work that customers would pay to have done. It also encouraged documentation and automation: a small team could hardly afford to solve the same internal problem afresh every week. The attraction of an engineered organization was already taking shape. A process that worked repeatedly was worth more than another heroic evening.

Yet self-sufficiency had a cost. Looking back, he has acknowledged that doing so much himself made him a bottleneck. Learning each function was valuable to the founder; waiting for him to learn it was expensive for the company. That is a remarkably plain admission from someone recounting an eventual exit.

In March 2018, the acquisition of Recruiterbox by Turn/River Capital was reported as an undisclosed cash deal. The plan put it within Applied Training Systems’ HR software business. Redekar said the team would continue in its existing roles, with the buyer bringing sales and marketing expertise. The founders had built something people used; another owner could help carry it further.

The customer question that became a company

Inside Recruiterbox, another problem had been accumulating. Prospective customers wanted assurances about security and compliance. The requests mattered because larger deals depended on them. They also appeared costly and difficult, which made postponement attractive for as long as postponement remained possible.

When the founders finally undertook the work, Redekar recalls six months of effort and tens of thousands of dollars without a clear finish. Compliance was competing with building the product. For engineers, this was an especially irritating arrangement: much of the effort appeared repetitive enough for software to handle, yet people were still doing it by hand.

Here was the seed of Sprinto. The underlying buyer question was reasonable. Before entrusting data to another company, a customer wanted evidence that its commitments held up. The machinery for supplying that evidence was the troublesome part. Redekar and Kancherla had encountered a business opportunity while trying to complete an obligation.

Redekar later put the ambition in terms of giving smaller businesses a “right-to-compete.” If meeting an enterprise buyer’s requirements demanded resources available only to established companies, capable young suppliers faced a barrier before their products even got a hearing. Making that work affordable could have a commercial consequence well beyond the audit itself.

A demo call has better questions

The second venture made room for conversations before construction. Redekar has described interviewing prospective customers and working with design partners to establish what they needed. The harder product question was whether a process usually delivered through human expertise could be made into repeatable software. Demand alone would not settle that.

He kept an appreciation for direct contact even as Sprinto grew. In a 2023 conversation, he explained why demo calls and personalized onboarding could teach the company things documentation could not. A document answers the questions its author anticipated. A customer can introduce a question nobody thought to put on the page.

That difference matters when companies arrive with varied systems, obligations and experience. Hearing where someone gets stuck helps the team improve the onboarding process and decide what belongs in the product. A sales conversation can therefore do two jobs: explain the software and expose its assumptions.

The early customer network included younger software companies and relationships with venture firms. Growth also brought organizational questions. Sprinto was a remote company, and Redekar discussed the need to establish culture deliberately and introduce goals and processes as teams expanded. The product was not the only system that needed design.

Capital changes the assignment

Sprinto announced a $10 million Series A in February 2022, led by Elevation Capital with Accel and Blume Ventures participating. In April 2024, it announced a $20 million Series B from those investors, led by Accel. Redekar had moved from building with customer receipts to building with a larger pool of money and the expectations attached to it.

He has treated the funding choice pragmatically. Venture capital fits an ambition to build a large company quickly. Bootstrapping offers another set of trade-offs. Having lived both arrangements, he has little reason to turn either into a moral position. Money can change how quickly a company hires; it cannot make a customer’s problem worth solving.

In the Series B announcement, his priorities included more research and development, intelligent automation, and stronger internal and third-party risk products. Accel’s investors described knowing the founders since Recruiterbox. This was a continuing relationship with people whose execution they had already observed.

The audience has expanded too. Sprinto now reports more than 4,000 customer organizations across 75 countries. The first business gave Redekar experience selling software internationally; the second has carried the same practical concern into a broader market. Every additional customer brings another version of the question: can we rely on you?

The daydreamer’s preference for discipline

For all this talk of controls and operating systems, Redekar’s own introduction is pleasantly informal. His personal website describes a programmer who likes building software businesses, drinks plenty of tea and is susceptible to daydreaming and distraction. There is no attempt to make his attention sound mechanically perfect.

His account of childhood is similarly unpolished: quiet, introverted, often lost in thought, filling pages with doodles. In his professional advice, consistency does much of the work that founder mythology assigns to inspiration. The point is to keep returning to a worthwhile problem long enough to understand it.

He credits his brother with financial and emotional support during the first startup, and his wife with support during Sprinto’s early days, when they were new parents. These acknowledgments widen the picture of how a company gets built. The founder’s working hours rest on arrangements and generosity that never appear in a funding announcement.

His management language follows the same preference for useful arrangements. He talks about giving people autonomy, assigning real problems and letting them ship ideas that can be judged by customer impact. The ambition is substantial, but the daily unit of progress remains small enough to examine.

“Pain is the ultimate compass.”

Girish Redekar

A promise that survives the paperwork

In March 2026, Sprinto introduced its Autonomous Trust Platform. Its stated direction is to have software agents monitor changes and carry routine compliance work through to completion, while people retain judgment. Redekar’s writing that month examined the gap between what a periodic report records and what a changing system is doing now.

His concern extends to the credibility of the process. In an essay about compliance as a promise, he argued that an independent assurance signal has value only when the work behind it is real. Faster production of paperwork would be a poor destination if the paperwork became less dependable.

He is also hosting The Trustsmiths, a series of conversations with leaders responsible for trust and governance. One episode pairs him with Michael Rasmussen to discuss the development of GRC over 24 years. The founder who once needed a prospect to interrupt his pitch now has a format built around asking questions.

The through-line is recognizable. A customer interrupted a confident explanation. A hiring workflow became a product. A compliance burden became another company. Redekar keeps returning to the moment when a tidy solution meets an untidy working day. There is usually something to learn there, provided the person doing the building can stop talking long enough to hear it.