Rohan Joshi and the price of a quarter-second

A quarter of a second can be a surprisingly expensive interval. Rohan Joshi remembers losing an enterprise customer because a query took Wolken’s software 0.3 seconds. The competitor’s took 0.03. Wolken’s lower price did not rescue the deal. The decimal point had voted, and the buyer agreed.

Joshi’s telling of the episode contains no heroic speech to the procurement department. His team reworked the product and returned. The customer eventually became one of Wolken’s largest. “You have to go in with zero ego,” he says. It is a useful instruction for a founder whose working life has included selling software across continents, running international businesses and learning how much of that experience a new company can actually spend.

An education with several time zones

Before Wolken, Joshi’s career crossed several versions of the technology business. He studied electronics engineering at BMS College of Engineering and business administration at Schiller International University. His professional history includes product management at Philips, European operations at Infosys, Latin America and the Caribbean at i-flex, global operations at Valtech, and European operations at L&T Infotech.

The geography matters. Selling into Europe and leading a business across Latin America and the Caribbean meant that his experience of enterprise technology extended well beyond the engineering department. Software had to make sense to people operating in different markets, within different organizations, with different reasons for saying yes. A product could travel electronically; confidence in its supplier still had to travel person to person.

At L&T Infotech, he and Sudhir Prabhu became colleagues before becoming founders. Joshi led sales for Europe, a business he has described growing from zero to more than $120 million. Prabhu brought the experience of overseeing a roughly $90 million profit-and-loss account and 1,200 professionals. Their eventual partnership paired commercial experience with responsibility for delivering technology at scale. Neither arrived at the new venture straight from a classroom.

First, twenty-five conversations

Wolken began in 2011. Joshi dates the conception of its ServiceDesk to September that year. The initial effort was small: a consulting product architect, a key developer and about six months spent working through the design, database, interface and technology choices. There is something pleasingly concrete about that inventory. A company begins, and somebody must decide what the database looks like.

The listening came early. Joshi says the team met more than 25 chief information officers across India, Europe and the United States to understand their requirements. What would a service desk need to do inside an enterprise? Where did existing systems cause trouble? These were questions to ask before the product’s makers became too attached to their answers.

The work changed shape. From 2011 to 2014, Wolken developed collaboration software called Team Toq. Between 2014 and 2017, it worked on IT service management, including the tracking of technology assets. It subsequently broadened into configurable cloud service desks for customers and employees. The changes make the company’s early history look less like a launch followed by a smooth ascent than a sequence of revisions.

The work hidden inside a service desk

A service desk sounds like a modest piece of office furniture. Its digital equivalent gets a rather larger assignment. It must collect requests, send them to the right people, preserve the history and make the answer available when the question comes round again. At enterprise scale, the small request quickly acquires a passport, a permissions policy and an escalation rule.

By 2023, Joshi and Prabhu were explaining this through the ordinary questions employees ask: how leave works, how payroll is calculated, what happens next in a career. Their description of HR case management emphasized privacy, routing and escalation. A multinational organization might also need articles in several languages, translations and rules about where information can be hosted.

Those details help explain the nature of Joshi’s business. The experience visible to an employee may be a simple question and answer. The machinery underneath must accommodate access, language and organizational responsibility. In that setting, simplicity demands a considerable amount of arrangement backstage. The receptionist may smile; someone still needs to know which door opens where.

A smaller customer, a shorter runway

Wolken Care took that service desk idea toward smaller businesses. At its launch, Joshi spoke about customer experience and the challenges of providing support. A live product demonstration followed. The company presented a browser-based application with knowledge management, reporting and customer feedback features, extending its work beyond the large enterprises that had shaped its earlier product.

The 2023 explanation of Care was practical: it used a subset of Wolken’s enterprise solution, with practices and master data already included. That preparation was meant to reduce the work needed before a smaller company could begin using it. The intended customer had less time and fewer resources to devote to setting up a support operation.

Joshi’s writing on self-service gives this expansion a wider context. In January 2022, he described customers finding answers, signing up and learning at their own pace. Tutorials, documentation and knowledge bases all belonged in that picture. The commercial attraction was straightforward: an organization could serve more people without requiring a person to attend every step. For customers, the attraction was equally understandable. A useful answer at midnight has an advantage over a very courteous promise to reply tomorrow.

There is a particular discipline in making the first steps understandable. Joshi’s self-service argument extended beyond putting a help page online: it included onboarding, demonstrations and guidance that help someone use the product. The customer is being asked to do more independently. The software company must therefore make the route easier to follow. Otherwise, the work has merely changed desks.

The expansion inside an existing customer

By December 2022, Wolken described a “Land and Expand” strategy: build an initial relationship, then extend the product’s use. Its portfolio included customer service, IT service management, and HR and quality case management. The company reported around 40 clients at that point, about half in the Fortune 500, and end users across 60 countries.

These are dated company figures, a view of the business at that stage. Their interest lies in the kind of expansion they describe. Once a service platform is inside an organization, the next application may be another department with a familiar administrative problem. The same broad discipline of receiving, assigning and resolving a request can have several addresses within one customer.

Wolken also described seeking local partnerships in new geographies. That fits the shape of Joshi’s earlier career: international business development coupled with attention to the organization already buying the software. A larger footprint could mean a new country, another department, or a deeper relationship with an existing client. The sales map had more than one dimension.

“You have to go in with zero ego.”

Rohan Joshi

A little Céline Dion in the boardroom

Joshi’s public thanks to Wolken’s board offers a less technical view of the founder. Responding to a company post celebrating its directors, he borrowed from Céline Dion to describe being lifted up when things were down. He credited Vivek Mansingh, Subodh Bapat and Doug Tracy with mentoring the founders over several years.

He also thanked them for tempering the founders’ excess enthusiasm. That is a revealing item to include in an expression of gratitude. Encouragement is easy to applaud; restraint rarely receives such a warm notice. Joshi praised their patience and empathy, then declined the company post’s grander language about greatness. His reply placed Wolken somewhere more workmanlike: on the right path.

It is an amusingly musical way to describe governance, and a useful glimpse of how he talks about the people around him. The founder’s account makes room for advisers who made difficult stretches easier and brought exuberance back within bounds. Someone at the table was allowed to turn the volume down.

The queue meets the AI agent

In June 2025, Joshi and Prabhu used a Wolken all-hands meeting to introduce the company’s move toward agentic AI. The proposed direction was greater autonomy in enterprise service work. For a business built around handling requests, the question became how much of the journey from question to completed task software could take on.

By August 2026, Joshi was writing about customer service as a potential contributor to revenue. His argument identified three areas: recognizing useful customer signals, resolving routine work autonomously, and escalating to people when their judgment could make a difference. He stressed that customer information scattered across disconnected systems would limit what an AI system could achieve.

That emphasis gives the new vocabulary an older foundation. Service history, account information and the next responsible person still matter. So does deciding whether a problem has actually been resolved. In Joshi’s account, automation needs access to the relevant information and a sensible point at which to involve a human. A convincing answer is only part of the job.

The ambitions have changed in scope since the first database and the early CIO conversations. The buyer’s test remains concrete. Does the work get done, quickly enough, in a way the organization can trust? Joshi’s career offers a long education in that question. Somewhere in the lesson book, there is still a decimal point.