At four in the morning, Wolfsburg railway station was less a gateway to Europe than a wind tunnel with timetables. High-speed trains arrived every half hour. Between them, a graduate student from Hyderabad spread salt, cleared snow and tried not to freeze. Krishna Dunthoori did the job through three German winters, roughly one hundred early shifts in all. He also delivered pizza and worked in restaurants while completing a master's degree in computer science. The glamour arrived later, if it arrived at all.
It is tempting to treat this as a tidy parable about grit. Dunthoori's career is more interesting than that. The snow, the code, the consulting projects and the companies all reveal the same operating instinct: stand close to the awkward work, watch where the system fails, and improve the part that everyone else has learned to tolerate.
A founder's route, measured in useful discomfort
01 / An unexpected syllabus
A week in veterinary school, then a lifetime in software
Dunthoori was born and raised in Hyderabad. His father worked in government; Krishna was the younger child in a family with several siblings. School was in Telugu. He has said he did not write a complete paragraph in English until he was 19, a detail that makes the later map of his working life - Germany, Atlanta, New York, Silicon Valley, Texas - feel less like a straight line than a series of earned translations.
His first turn toward technology was almost accidental. After high school, he did not secure a place in medicine but did win one in veterinary studies. He lasted a week. Around that time, a new computer applications program opened, and he worked his way into it. Programming suited him because he cared about the question behind the code: what problem is this meant to solve?
In 2000, a full scholarship took him to the University of Applied Sciences in the Braunschweig and Wolfsburg region. The trip to Germany was his first flight and his first visit to an airport. There were more fashionable destinations for Indian students, but fashion had little to do with the arithmetic. Germany was affordable. The scholarship made it possible. The railway shifts paid for the life around it.
02 / The elephant in the conference room
When implementation succeeds and the work still fails
After graduate school, Dunthoori joined a telecommunications company in Frankfurt as a junior programmer. He spent almost four years there, consulting across Europe. A meeting with an American SAP implementation team led to an H-1B visa and, in September 2005, a move to Atlanta. He became a solutions architect working with Clarity, the project and portfolio management software acquired by Computer Associates.
The work offered an education no business school could tidy into a case study. Customers bought robust software, then spent multiples of the license price trying to make it useful. On one implementation, the system cost about $4.5 million. Eight months after launch, a major meeting still depended on manually assembled data because the software's output could not be trusted. The product existed. The implementation had happened. The promised value remained somewhere offstage, presumably checking its calendar.
“It's not the software, it's how you're using it.”Krishna Dunthoori
Dunthoori saw room for targeted add-ons that could close the gap. The insight became Excers, a services and implementation business founded in 2009. He hired developers, including a team in India, and funded the company with $50,000 of his own money. He and his wife postponed buying their first home. He avoided debt and declined outside capital, believing he should be willing to risk his own money without making the same wager on behalf of others.
The gamble had boundaries, but it was still a gamble. Dunthoori went without a salary for nearly two years. Excers recorded $30,000 in revenue in 2010, $450,000 in 2011 and $3.8 million in 2012. By 2016, he said it had reached $12.8 million with a team of roughly 55 to 60 people across the United States and India. At times the team became so absorbed in customer work that it forgot to send invoices. Few growth charts annotate that particular operational hazard.
03 / Services as a listening device
The second company was hiding inside the first
Excers concentrated knowledge. By helping enterprises implement one complicated system, Dunthoori learned where users hesitated, which workarounds endured and how quickly training evaporated once ordinary work resumed. A broad conclusion emerged from a narrow practice: the adoption problem was not peculiar to Clarity. It appeared wherever a company bought a consequential application and expected a launch date to change human behavior.
This is the most portable part of the story. Services can be more than a way to finance a product. They can be a listening device. Repeated manual work reveals what software should absorb. Repeated customer complaints reveal the shape of the market. Familiarity becomes an advantage only when someone remains curious enough to notice that the same irritation has appeared for the twelfth time.
Dunthoori founded the new company in 2017; its public launch followed in 2018 under the name letzNav. The first version provided on-screen navigation, an extra layer over enterprise applications that could show users what to do next. It gained its first Fortune 500 customer in its opening year and became Apty in 2019. The new name was shorter. The premise remained stubbornly practical.
An early contract supplied a useful comic correction. A small customer bought an unlimited-user plan for $5,000 a year, then interpreted “unlimited” as permission to include its own customers and resell the product under its brand. Apty objected. The customer pointed out that nobody had specified whose users counted. A lawyer and clearer contracts soon joined the company toolkit. Product-market fit is charming; product-contract fit pays the bills.
04 / The quiet work after go-live
Training is an event. Adoption is evidence.
Apty sits over web-based enterprise applications and supplies interactive walkthroughs, contextual help, input validation and analytics. A new employee can receive guidance inside the application instead of leaving it for a manual or a class. An administrator can see where a workflow breaks down. A company can catch a mistake while data is entered, rather than discovering it inside a report three weeks later.
That difference matters because enterprise transformation is often narrated from the buyer's side. The contract is signed. The platform is configured. The launch is announced. Dunthoori's view begins one chair over, with the employee looking at the screen. Can that person complete the process? Is the data reliable? Does the new system reduce work, or merely give the spreadsheet a more expensive neighbor?
The company announced $5.4 million in post-seed financing in 2020, then a $7.5 million Series A led by 645 Ventures in 2021. Its published customer roster has included Boeing, Delta Air Lines, Broadcom and Mary Kay. Apty says its platform now reaches more than 1,000 customers and 7 million users across more than 1,000 applications. Those are company-reported figures, but they clarify the scale of the problem Dunthoori chose: user confusion is not a corner case when software is the workplace.
A first six-figure sale arrived early in Apty's journey. Dunthoori remembers it because the contract was five times larger than the company's previous sales record and because the whole team helped close it. The money mattered. Validation mattered more. A large American customer had paid to solve the same pain he had observed years earlier from inside implementation projects.
05 / Curiosity without romance
Know when to persist, and know the line
Dunthoori's advice to founders is not built for a motivational poster. Ideas, he says, are cheap. Decisions should be made quickly enough to create information. Mistakes should not be repeated merely because persistence sounds noble. Wait too long and there may be no company left; move at every twitch and nothing has time to work. His phrasing is brisk: do not wait too long, then do not wait another second.
That balance appears throughout his own choices. He was prepared to leave a stable consulting role because the pace frustrated him. He was prepared to invest his savings and skip a salary. He was not prepared to borrow without limit or gamble assets he could not replace. Courage, in this version, comes with a ledger.
“What's your strength today is your weakness tomorrow.”Krishna Dunthoori
The sentence explains why Apty has kept changing its machinery while preserving its question. The platform now emphasizes AI-assisted content, natural-language support, interface detection, cross-application workflows and real-time process validation. The vocabulary has moved from walkthroughs toward signals and automation. The test is unchanged: does the software produce measurable value in the way people work?
Dunthoori describes curiosity as a cultural requirement. Teams can reward creativity and still miss important discoveries if everyone is too occupied to ask probing questions. His career supplies the concrete version of that belief. Why spend millions to deploy a system that produces untrusted data? Why repeat classroom training when confusion occurs inside the application? Why treat user adoption as a soft outcome when errors, support tickets and time can be measured?
The route from Hyderabad to Texas can be read as migration, entrepreneurship or technical ambition. Its sharper reading is observational. Dunthoori kept returning to the uncelebrated last mile, the place after software has been purchased and before it has become useful. It is where impressive strategies encounter ordinary Tuesdays.
There is no permanent finish line in that work. Interfaces change. Employees join. Policies move. Artificial intelligence makes software more capable and, often, more complicated. Adoption begins again. The founder who once cleared snow before the first trains arrived now builds tools for another kind of obstruction: the small accumulations that keep people from moving through systems as intended.
The snow returns too. The useful question is whether you noticed where it gathered.