The form was forgotten. The fine was not. Harshvardhan Kariwala was running a bootstrapped company when an outsourced accounting partner missed a required compliance filing. The penalty came to $4,000. In a mature corporation, that might become a grim line item and an even grimmer meeting. In a young company counting every dollar, it becomes an education with a receipt.
Kariwala did what product people often do when annoyance becomes specific enough: he built something. His team made an internal compliance tracker so responsibilities, deadlines, and reporting could stop falling through gaps. It was designed for their own use, not presented as a startup thesis. There was no ceremonial unveiling. There was simply a recurring failure that should not recur.
That plain beginning is the key to understanding VComply, the governance, risk, and compliance software company Kariwala now leads from the United States. Its first job was not to impress an enterprise buyer. Its first job was to make forgetting difficult.
01 · The useful stingPaperwork acquires a plot
Kariwala was born and raised in Kolkata. He has said he started his first company at 18, finding work by approaching agencies that needed technology projects executed. Study took him to Singapore and then the University of Manchester, where he completed an economics degree focused on accounting and finance. His early venture, LIME Learning Systems, operated in education technology. VComply was not the obvious next chapter.
In fact, he has described it as his third startup and an external product that happened by accident. The compliance failure at his earlier business exposed a basic operational weakness. Outsourcing the task had not outsourced the consequence. Someone still needed to know what was due, who owned it, and whether it had actually been completed.
The team turned those needs into a wonderfully small product brief. Who needs to do the task? What needs to be done? How often? They shipped a first version in two to three weeks, put it in front of their colleagues, and used those colleagues as the first focus group. The feedback loop could hardly have been shorter: the builders and users worked inside the same operation.
The simplicity mattered. Compliance products had a reputation for complexity, heavy implementation, and interfaces that seemed to punish anyone already burdened by regulation. Kariwala saw room for something smaller organizations could configure around their own workflows. The internal tool gave him proof before it gave him a pitch.
Focus on getting the product right.Harshvardhan Kariwala
02 · The accidental customerBoston calls the internal website
To make the tracker easy for his own teams to reach, Kariwala bought a domain and wrote a basic website explaining how the product worked. Then someone from the City of Boston found it. The visitor wanted a demonstration of software that, from Kariwala's perspective, was not really for sale.
He took the call. The city ran a pilot. Then it wanted to purchase the product. There was one administrative wrinkle worthy of a compliance comedy: Kariwala had created the tool, but not yet the business that could accept its first order. He recalled staying up all night to set up the new company.
That customer did more than produce revenue. It changed the status of the idea. The tool had moved from an internal answer to an external need, and the buyer was neither a friend nor a carefully recruited design partner. It was a stranger who found a page and recognized its own problem.
Kariwala began discussing the product with investors in Palo Alto. In July 2019, VComply announced a $2.5 million seed round led by Accel. Contemporary reporting said the platform had about 4,000 users in more than 100 countries and served organizations across a range of industries. The product's early promise was flexibility: one dashboard, adapted to the regulations and processes each customer actually had.
In January 2021, VComply raised a $6 million Series A led by Counterpart Ventures and Accel. Kariwala called it an opportunistic round, noting that the company still held much of its seed capital. The money was intended for U.S. go-to-market work and hiring across engineering, product, and marketing.
03 · The founder in the systemAccountability gets personal
There is a satisfying symmetry between VComply's product and Kariwala's own lessons. The software exists to clarify responsibility across an organization. The founder has been candid that building alone made responsibility heavy. He has said that a co-founder or the right founding team would have made the hardest decisions easier. He has also reflected that hiring the right people and defining roles more clearly could have improved the early journey.
This is not the polished hindsight of a founder claiming every mistake was secretly strategic. It is more useful than that. A solo founder can move quickly because every decision has an obvious owner. The same arrangement can become exhausting because every difficult decision has the same owner too. That pressure is easy to romanticize and expensive to carry indefinitely.
Solo founding makes every difficult choice land on the same desk.
His stated operating preferences are consistent. He calls himself a product person at heart. He advises founders to understand a customer's pain, keep a constant feedback loop, practice explaining the problem clearly to investors, and treat rejection as information for the next pitch. He recommends documenting processes because an organization works better when knowledge is visible rather than trapped in one person's head.
Even his favorite founder advice has the texture of a checklist, though a humane one: build the right thing, speak clearly, keep learning. VComply is essentially that temperament turned into software.
04 · From file cabinet to infrastructureThe larger argument
By 2025, Kariwala was articulating a broader thesis. Compliance, he argued, should be treated as infrastructure rather than paperwork. The distinction changes when the work happens. Paperwork waits for an audit. Infrastructure runs every day. It distributes ownership, preserves evidence, and lets problems appear before they become emergencies.
That language suits the origin story. A missed filing is a small event right up to the moment it produces a penalty. The danger was never a shortage of policy. It was a broken chain between obligation and execution. VComply's expanding product vocabulary - covering compliance, risk, policy, audits, controls, and cases - keeps circling the same gap.
The company has also begun adding AI-oriented features to that system. In January 2025, it announced a partnership with Gan.AI to bring personalized, multilingual video training into its policy product. Kariwala has since written about AI, control mapping, audit readiness, trust management, and the practical difficulty of proving that a documented process is really being followed.
His public aspiration reaches back toward Kolkata as well. In a recorded conversation about building VComply from India, Kariwala pointed to young talent and education as ingredients for globally relevant software. His advice to prospective SaaS founders was brisk: begin now, because nobody fully knows how to start until they have started.
It's not paperwork. It's infrastructure.Harshvardhan Kariwala
05 · The quiet lessonBuild the memory your company lacks
Founders are often told to look for enormous markets. Kariwala's story offers a smaller opening move: look for the thing your own company keeps failing to remember. Then make the failure visible enough to fix. The elegance is not in discovering that compliance matters. Regulators had already established that point rather firmly. It is in giving an abstract obligation a person, a task, and a clock.
The first VComply website was meant to help an internal team log in. The first buyer arrived without being invited. The company itself had to catch up with the product overnight. Those accidents worked because the underlying tool already did a job somebody needed.
Years later, Kariwala is still writing about the difference between possessing a policy and proving that people follow it. The subject may be governance, but the idea applies widely. Organizations forget. They defer. They assume. Software earns its keep when it remembers without becoming another burden to manage.
The $4,000 fine remains the cleanest explanation of VComply because it contains both sides of the business: a preventable mistake and a founder unwilling to pay for the same lesson twice. It deserves a system.