LATEST
●SEPTEMBER 2026 · ROUT LISTED TO SPEAK ON SUPPORT TICKETS THAT RESIST AI DEFLECTION●FROM GREXIT TO HIVER · A PRODUCT BUILT AROUND THE WORK INSIDE EMAIL

People / Founders / The working life

Niraj Ranjan Rout and the trouble with a perfect number

The Hiver co-founder has spent years untangling the work hidden inside email. Between failed ideas, a Greek naming crisis and an AI joke taken seriously, he keeps returning to a practical question: does this actually help?

Niraj Ranjan Rout had a number to announce: 91.67 percent. That, he told LinkedIn, was the proportion of Hiver’s code being written by AI. It was an admirably precise figure, the sort that looks as though someone has spent a responsible afternoon with a spreadsheet. He offered a step-by-step playbook to anyone who asked for it using a rather less respectable phrase. The playbook did not exist. The number was a joke.

People asked anyway. In a follow-up, Rout explained that the post had been written in jest, and that dozens of readers had wanted him to reveal the method. His point was about the distance between the public performance of AI progress and the work happening inside companies. He described himself as an early adopter of technology, while arguing for a more grounded conversation about what AI could do.

It is a useful way into the life of Hiver’s co-founder and CEO. He builds software for customer service, a field in which a convincing answer and a useful answer can be separated by several frustrating exchanges. A customer eventually needs the thing fixed. Rout’s career has revolved around that inconvenient requirement. The jokes are optional; the work waiting underneath them tends to be stubborn.

Before the inbox, there were chips

Rout grew up in Jharkhand and West Bengal, primarily in Jharkhand. His father had a small auto-parts shop alongside the family’s service background. After tenth grade, he moved to Kolkata for further schooling, with an engineering education in mind. Mathematics and science interested him, but so did art. The path toward engineering was clear enough; the creative appetite would prove harder to file away.

At IIT Kharagpur, he studied Electronics and Electrical Communications Engineering, graduating in 2002. He then spent five years at Mentor Graphics, working in electronic design automation. This was a world of silicon-chip design, emulation and C++ code. The software helped engineers check whether their designs behaved as intended. Before he made tools for people answering customers, he made tools for people building chips.

The office also supplied a less technical education. Work passed between people on different continents, with email carrying the conversations. Useful information accumulated inside individual inboxes. Bringing someone new into a project meant finding the relevant history and making it available. The difficulty was familiar enough to be overlooked: the message had arrived, but the knowledge inside it had acquired an owner, a location and a chance of disappearing from view.

In his later recollection, Rout enjoyed the people and the technical work at Mentor Graphics, then grew restless about what to do next. He considered further study, including a PhD. Entrepreneurship appealed because its future was open-ended. There was room to decide what he would become. Leaving a defined career for an undefined one was the attraction, rather than an unfortunate side effect.

Niraj Ranjan Rout beside framed music posters against a brick wall
Office walls with a soundtrack. Rout in a 2019 press photograph. Photo: The Economic Times.

A business that worked, and a reason to leave

He became an entrepreneur in 2007. The first attempts did not settle the question of what to build. One involved local search on mobile phones, at a time when GPRS connections could be unreliable and expensive. In a 2011 account of those beginnings, Rout was blunt that two initial ideas had failed. There was no elegant product waiting at the end of the resignation letter.

The team found a way forward through Mobicules, providing web and mobile application development for clients, primarily in the United States. The business grew to 35 people in 20 months. Nitesh Nandy, another IIT Kharagpur graduate, joined that earlier venture and worked on demanding development projects. The relationship that would become Hiver’s founding partnership was being tested through actual work, before it needed a founding story.

A services company could pay people and attract clients. It also required the founders to spend their days meeting other people’s specifications. Rout wanted to make a product of his own. In January 2011, he exited Mobicules to start GrexIt. The distinction mattered: the next business would have to persuade many customers to use the same piece of software, rather than build a different application for each one.

The email problem offered a starting point. Rout and Nandy had encountered information trapped in inboxes across their working lives. Their first proposition was to turn those conversations into shared organizational knowledge. One early customer needed an accessible history of support exchanges, so that new colleagues could understand what had happened before they arrived. The product’s usefulness could be described without a vocabulary lesson: let the next person see the conversation.

When five people were a crowd

In the early weeks, the founders checked their logs and celebrated when even five people added new email conversations. Rout remembered the pleasure of making something intelligent that other people found useful. The scale was small enough to inspect closely. Activity meant that someone had found a reason to return, which was more helpful than a flattering description of the idea.

GrexIt began in 2011, with an early beta and a planned subscription model. Its initial ambition was knowledge management; over time, the work moved toward collaboration and customer support. Shared labels, notes and eventually shared inboxes helped turn email from a collection of individual conversations into something a team could manage. An incoming request could have an owner, a status and internal discussion attached to it.

The central choice was to work where customers already worked. In 2019, Rout described Hiver’s appeal in terms of avoiding a new interface and new terminology. Gmail was familiar. A team should be able to coordinate its replies without endlessly switching between the inbox and another tool. The product respected a habit that many software companies would rather replace. Familiarity was part of the design.

AN INBOX BECOMES A TEAM’S WORKSPACE
01A request arrivesThe customer’s conversation
02Give it an ownerResponsibility and status
03Keep context togetherInternal notes and shared history
04Finish the workA coordinated customer response
The practical idea behind Hiver’s shared inbox: make responsibility visible.

The eurozone enters the naming meeting

GrexIt had seemed a sensible name. Grex means a crowd or flock in Latin, which suited a product for collaboration. The domain was available, too. Then the word acquired another job: shorthand for a possible Greek exit from the eurozone. A small software company suddenly found itself sharing a name with a European financial drama. Brand recognition had arrived with an unusually unhelpful brief.

Rout described the traffic bumps that followed news about Greece, accompanied by higher bounce rates. Visitors were arriving with the wrong question. By 2015, the association had become difficult enough that the company changed the product’s name to Hiver. The new name came from the beehive, with its associations of organization and collective work. The legal company name remained GrexIt, Inc.

There is something comic about building software to reduce confusion and then having international politics confuse your own front door. It also places a limit on tidy accounts of entrepreneurship. The founders could improve the product, its pricing and its website. They could not arrange for the financial press to select a different word. Sometimes the practical decision is to order new stationery and get back to work.

“Extraneous circumstances”

Rout’s explanation for the GrexIt name change

The customer who needed no phone call

Hiver’s early sales approach relied heavily on customers finding the product and setting themselves up. In 2017, Rout described a New Zealand company booking 150 seats without a single phone call. The website, signup flow and explanatory material had done enough of the work. For a founder selling better communication, it was a pleasing demonstration of how much communication could be spared.

By October 2018, Hiver had more than 1,100 paying customers and a team of 50. It raised $4 million from Kalaari Capital and Kae Capital after years of largely growing from revenue, following a small earlier investment. Rout highlighted frugality and inbound marketing when discussing the round. Customers included Harvard University, HubSpot and Vacasa. A company built in Bengaluru had found much of its market overseas.

In March 2022, Hiver raised a $22 million Series B led by K1, with existing investors participating. Rout said the money would go toward product development and growth. He also described plans to bring more customer communication channels into the product. Email had provided the entry point; the work of serving customers reached beyond it. Expansion followed the job people needed to finish.

A SNAPSHOT, OCTOBER 2018
1,100+paying customers
50people on the team
$4mfunding round
Years of revenue-funded growth preceded the larger investment.

The guitars got there before the furniture

There is another version of Rout’s working life, one with amplifiers. He has long described a love of fusion music and guitar. Recalling his move to the United States in August 2023, he said his first rented house had no furniture, but did have guitars and an amp he had brought with him. A chair could evidently wait. The musical equipment had made the crossing.

At Hiver, a World Music Day video became a team jam session. Rout’s initial request had been for something modest. After seeing the result, he publicly invited his colleagues to keep ignoring that particular advice. The exchange is a small but revealing scene: a CEO gives an instruction, the creative work outgrows it, and the CEO is happy to concede the point.

His writing about company culture offers a parallel. When an employee proposed a strong idea, he described making that person responsible for planning and execution, with even the founders reporting to the project’s owner. Authority could move to the person doing the work. That was his stated practice, rather than a theory about how every workplace ought to operate.

Music has also produced a neat crossover with the business. Rout discovered that Wildwood Guitars had been a Hiver customer for years, then acquired a Wildwood-spec Fender Custom Shop Telecaster. He posted himself playing Jimi Hendrix’s “Little Wing” on it, with a candid assessment: “My playing, of course, is not perfect.” The customer relationship had become an instrument, and the instrument still required practice.

“My playing, of course, is not perfect.”

Niraj Ranjan Rout, on playing “Little Wing”

The work beyond the demonstration

By 2026, Rout was discussing AI as part of the whole customer-service workflow: triage, routing, drafting, quality checks and insights. In a February podcast, he stressed the importance of usable knowledge, clear boundaries and explicit handoffs to people. Counting generated lines of code, he argued, could miss whether the code did what it was supposed to do. Counting deflected support requests could be similarly shallow.

His March 2026 essay developed that argument through operational design. He proposed judging tools by time to value, voluntary adoption, reduced workload and the team’s ability to operate without constant vendor assistance. The questions are refreshingly unglamorous. Has the work become easier? Are people choosing to use the system? Can they run it themselves? A demonstration ends after applause; an inbox keeps receiving messages.

Hiver now offers both its Gmail-based product and Hiver Omni, a dedicated platform for support across channels. The company says more than 10,000 teams use it worldwide. Its September 2026 summit listing put Rout on the agenda to discuss difficult tickets that resist deflection. The early concern with shared knowledge has widened into a concern with context, coordination and resolution.

Across those changes, the recurring question remains practical. What happens to the person trying to get something done? It appears in the new colleague searching old correspondence, the customer setting up 150 seats, and the support worker handling an awkward request. Rout’s career has given that question several products, one forced name change and a musical accompaniment. The decimal point may earn the attention. The unfinished work earns the next morning.

Follow the conversation