Ninety minutes is a long time to spend discussing your worst decisions with someone you hope to advise. Aayush Ghosh Choudhury has described making exactly that conversation part of Scrut Automation’s process for choosing advisors. Failures are welcome. Embarrassment has a seat at the table. A polished account of an uninterrupted ascent would rather miss the point.
He wants the conversation to be “transparent, authentic, and vulnerable.” There is a practical bargain beneath the discomfort: someone else has already paid for an expensive lesson. Perhaps the next founder can learn it at a lower price.
That makes an apt entrance to Choudhury’s own story. The company he now leads grew from the difficulties of another venture. Scrut began when he and his co-founders took seriously a piece of work that was supposed to stay in the background. Their original business had acquired an inconvenient second job: proving that enterprise customers could trust it.
Before the software, a machine for sowing seeds
Before the security questionnaires came a very different kind of machinery. Choudhury studied mechanical engineering at the Indian Institute of Technology Ropar, graduating in 2012. His student work included a project developing a low-cost machine to sow several crops simultaneously on ridges.
The project gives his biography some welcome texture. Here is an engineering problem one can picture: seeds, rows, a mechanism, time spent doing a repeated task. Years later, his business would concern another kind of repeated task. The resemblance is interesting without requiring a childhood prophecy about compliance software.
He went on to study management at the Indian School of Business in 2015-16. His subsequent career included McKinsey & Company and the cloud software company PandoCorp. Engineering, management education, consulting, and software gave him several different places from which to observe how organizations work.
The work that interrupted the work
Choudhury and Jayesh Gadewar then built Gomigo, a procurement software venture serving enterprise customers. Selling into a large organization brought requirements beyond the product itself. The supplier had to demonstrate its security and compliance practices. A small team could find itself spending substantial time retrieving evidence and answering questions before a deal could proceed.
The founders built internal automation to handle that work. In time, the supporting tools became a business opportunity of their own. Kush Kaushik brought compliance experience into the founding group, joining Choudhury and Gadewar. The product grew from the founders’ own difficulty getting through the process.
“Scrut wasn’t the company we planned to build.”Aayush Ghosh Choudhury
The transition to Scrut took place in November 2021. The change of direction is the central event in his entrepreneurial story: the founders had encountered a recurring obstacle, built something useful for themselves, and recognized that other teams might need it too. An administrative burden had begun competing with the original product for their attention.
- Procurement softwareEnterprise buyers ask for proof of security.
- Internal automationThe founders reduce their own evidence work.
- Scrut AutomationThe supporting tools become the product.
A pitch survives a bad connection
One early encounter with an investor has the untidy setting that business origin stories often tidy away. Near the end of 2021, Lightspeed partner Dev Khare spoke with Choudhury over Zoom while travelling from Koramangala to Bengaluru airport. Rohit at Darwinbox had urged the meeting. The connection was patchy.
Khare remembered a clear argument coming through the imperfect call. Companies were facing growing pressure to demonstrate security and compliance to their customers. Scrut proposed a single cloud-native way to help them manage that work. The two met in person in Delhi NCR the following day. A few hours into that meeting, Lightspeed offered a term sheet to co-lead the seed financing with Endiya.
The airport drive supplies the scenery; the useful detail is the speed with which a specific problem could be understood. Choudhury was describing something his own team had experienced. For once, the video call’s most consequential feature was neither the camera nor the microphone.
Acronyms, translated into work
Choudhury has a useful phrase for part of the problem: “acronym fatigue.” In a 2023 interview about Scrut’s ReguSense offering for fintech companies, he discussed the overlapping requirements that sit beneath different security standards and regulatory frameworks. The names multiply. Some of the underlying controls overlap.
His argument concerned the effort required to translate between them. If teams keep rebuilding evidence for related requirements, the administrative workload expands along with the list of frameworks. Mapping common controls can reduce that duplication. The appeal is easy to understand for anyone who has supplied the same information in several differently worded forms.
He also defended the need for strong requirements. When asked whether Indian financial regulation was too strict, he supported the standards’ intent. That position matters to the portrait: his proposed business opportunity depended on helping companies carry out the work efficiently while preserving its purpose. The ambition was to make a demanding obligation manageable for teams with finite time.
The CEO in the interviewer’s chair
Choudhury has also explored those questions by asking other people to explain their work. As a host of Scrut’s Risk Grustlers podcast, he interviewed security practitioners about the decisions behind the technical vocabulary.
In a conversation with Outreach security leader Satya Nayak, his questions moved from the guest’s route into security to team leadership, budgets, board conversations, and the multiplication of compliance frameworks. He asked how an organization could preserve the independence of security specialists while building an effective team. He also asked how a growing company should decide what it could sensibly spend.
Another episode, with leadership and team coach Jason Leuenberger, explored communication and relationship-building within governance, risk, and compliance. These subjects broaden the picture of what Choudhury pays attention to in public. The software sits inside an organization. People still have to explain priorities, gain cooperation, and persuade colleagues that a particular task deserves their time.
The interviewer’s chair gives him a way to make those practical concerns visible. A security control may be technical; getting it adopted can require a much more ordinary conversation.
Money with a job to do
By April 2024, Scrut had announced a $10 million growth investment from existing backers Lightspeed, MassMutual Ventures, and Endiya Partners. Disclosed cumulative funding at that point was $20.5 million. These were company financing figures, attached to a particular announcement and a particular stage of the business.
Choudhury described plans to use the money for research and development and to accelerate Scrut’s US go-to-market work. AI use cases were already being piloted. The company also intended to expand further in North America and Europe. A venture that had started with the founders’ own enterprise-sales problem now had an international operating agenda.
April 2024
May 2024
His comments about spending were restrained. He said the business had been prudent with its earlier capital and still had money available from previous raises. Alongside the financing, Scrut reported a team of 120 people across India, Southeast Asia, and the United States. Growth had made the coordination problem larger as well as the opportunity.
Expertise for the team that cannot hire it
By February 2026, Choudhury’s public argument had moved further into access to expertise. Small and mid-sized businesses, he explained, often combine security, risk, and compliance responsibilities in a handful of people. Buying tools still leaves a team with decisions about which signals matter and what to do next.
He described AI agents as a way to make some of that practical knowledge available more cheaply and continuously. He also discussed governance for the agents themselves: their access should reflect the privileges of the users they represent, and companies need control over what information enters models and connected tools. Automation creates work of its own around judgment and permission.
Scrut had announced certification for its AI management system in February 2025. The company was applying formal governance to an area increasingly central to its product direction. For Choudhury, the ambition remained tied to the customer with a small team and an extensive list of obligations.
In a July 2026 conversation with Khare, he discussed a further shift: customers reaching Scrut through applications such as Slack or through its MCP server, while the company focused on reliable completion of work. The accumulated context of an account could help the system make better use of past actions and decisions.
There is a pleasing circularity here. Scrut began because work surrounding one product demanded too much attention. Its CEO now talks about software that can complete more of that surrounding work without requiring the user to keep returning to a dashboard.
Choudhury’s advisor conversations offer a fitting last detail. Ask someone where a decision failed, and the useful knowledge becomes specific: the assumption, the constraint, the missed signal. His company is pursuing its own version of that specificity. The small team has a real task waiting. The test is whether it gets done.