How Infosys grew from seven broke engineers to a $75 billion empire

At the turn of the millennium, a so-called computer bug had presidents warning of chaos, news anchors speaking about planes falling from the sky, and banks preparing for the worst. The Y2K problem sounded like a plot from a disaster movie, but for one Indian company, it became the payoff for nearly two decades of quiet struggle. Infosys, started by seven middle-class engineers with 10,000 rupees and no computer, used that moment to turn years of patient groundwork into a global IT empire.

This story is less about overnight success and more about people who were willing to write code on paper, cook dal in a cramped apartment after 14-hour days, and wait years for policy changes and clients to finally swing in their favor. When you zoom out, the rise of Infosys reads like a manual on how reputation, timing, and stubborn consistency can turn a small services firm into a $75 billion giant.

The Y2K crisis that turned into a once-in-a-lifetime opportunity

To understand why Infosys exploded in 1999, you need to start with the strange economics of computing in the 1960s and 70s. Memory was so expensive that even 1 MB could cost millions of dollars, so programmers saved every possible byte. One of their tricks was to store years with two digits instead of four, writing 61 instead of 1961. It worked for decades, until someone realized that when the year rolled from 1999 to 2000, many systems would interpret it as 1900 instead.

That tiny shortcut threatened critical systems. Banks risked broken interest calculations, aviation systems could misread maintenance logs, and power grids faced the chance of emergency shutdowns because software could not handle the new date. Fixing it meant combing through millions of lines of old code, much of it running on mainframes and legacy systems. In the United States and Europe, most programmers were busy chasing the dot-com wave and building the future, not cleaning up the past. There was money in flashy startups like Amazon and Google, not in tedious date fields buried deep in COBOL programs.

This gap created a very specific kind of demand: companies were desperate for patient engineers who understood old systems and were willing to do repetitive work at scale. That was exactly the kind of work Infosys had quietly been doing for 18 years. When American and European corporations started looking for help, Infosys could confidently say they had teams ready, knew legacy environments inside out, and could work while clients slept thanks to the time difference. Y2K did not magically create Infosys, but it amplified everything they had been building since 1981.

Starting in 1981 with 10,000 rupees and no computer

The company’s beginning could hardly have looked less promising on paper. In 1981, India was stuck in the licence raj, where running a business meant endless permissions, high taxes, and long waiting lists even for basic items. Computers were rare, foreign exchange was tightly controlled, and the idea of building a world-class software firm out of a one-bedroom apartment in Pune sounded almost naive.

The seed capital came from a metal box filled slowly, month after month, by Sudha Murty. When Narayana Murthy told her he wanted to start a software company, she opened the box and counted 10,250 rupees. That was effectively the first and only personal investment. There was no venture fund, no rich relative underwriting their risk, and not even a machine of their own to run code. What they did have was a small group of engineers very good at their craft and willing to make uncomfortable choices for years.

Murthy’s previous job at Patni Computer Systems turned out to be their first real bridge. A client in New York, Don L., trusted his work so much that when Murthy left to start Infosys, Don agreed to give him a contract. The rate he negotiated was low because he knew Murthy needed the business and lacked a large team. It was hardly a dream deal on paper, but it was enough to get the company moving. That early relationship explains a core pattern in the Infosys story: when you have no brand, your reputation as an individual is the only real currency you own.

Writing code on paper and living on dal and jam

The lack of a computer meant that for the first two years, the founding team worked in a way that feels almost unreal today. They took turns flying to the United States, living out of a small apartment, and using the client’s IBM mainframe to write and test code. Back in India, they wrote programs on paper and sent them across, knowing that any error would cost time and money. It demanded both technical sharpness and a high tolerance for inconvenience.

The lifestyle matched the constraints. While American colleagues went out to restaurants after long shifts, the Infosys engineers cooked a big pot of dal in their cramped place and stretched it across meals. For lunch, they often survived on simple bread and jam instead of eating out. These details matter because they show that the sacrifice was not theoretical. These were toppers from premier institutes, people who could have chosen comfortable careers, yet they were washing utensils at night to save money for bus fare and rent.

There is also a mental cost to this kind of grind. Imagine watching your peers buy cars, upgrade to better apartments, and settle into stable jobs while you worry about your next client and spend weekends debugging code halfway across the world. It is very easy to start comparing lives and feeling like you made a mistake. One of the key points in the video is that comparison can slowly kill your motivation. The founders pushed through that phase by accepting that birthdays, weddings, and regular social life would often take a backseat to what they were building.

Building on reputation and partnerships instead of chasing giants directly

For a long time, Infosys lived with client concentration and thin margins. From 1983 to 1987, up to 90 percent of their revenue came from Don’s business. Most of the money went back into hiring engineers, renting offices, and buying infrastructure. Salaries stayed modest. There was always the risk that one decision from a single client could knock the company off balance, but at their size there was little choice. They needed cash flow more than they needed perfect diversification charts.

The real shift came when their work for Don caught the attention of KSA, a consulting firm advising retailers. KSA could design strategies and recommend inventory systems, but it could not build the actual software. Infosys used that gap smartly. Instead of trying to sell to giants such as Reebok directly, they proposed a partnership to KSA: whenever KSA told a client to build software, they would recommend Infosys as the implementation partner. That move led to Reebok as a client and, over time, to deals with Fortune 500 companies in the US and Europe, including names like General Electric, Nestlé, Cisco, and Apple.

There is a simple insight here that still applies to small firms today. It is often more effective to sell through the people your ideal customer already trusts than to knock on their door as a complete unknown. In many markets, the real gatekeepers are advisors, agencies, or system integrators. If you can solve their execution problem, you inherit their credibility. Infosys leaned into that model early, and it compounded over time as more consultants saw them as a reliable back-end team they could confidently recommend.

Liberalization, Y2K, and the leap in scale

The next big external shift arrived in 1991 when India opened up its economy. Import duties on computers dropped, foreign currency rules eased, and the perception of entrepreneurs inside the country started to change. For a company built on software exports, those changes were not cosmetic. Access to better hardware, simpler procedures, and a friendlier tax structure allowed Infosys to invest more aggressively and serve global clients with fewer bureaucratic delays.

The numbers tell the story. Infosys’s revenue grew from single-digit crores in the early 1990s to around 500 crores by 1999. Then Y2K hit, and all the preparation met its moment. Western corporations, nervous about date failures, were now willing to sign large contracts with offshore partners who understood old systems and could throw enough engineers at the problem. Infosys was exactly in that position, with teams trained on those very technologies. They worked through the crisis, cleaned up legacy code, and, more importantly, converted that trust into longer-term multi-million dollar engagements once the immediate panic passed.

By the early 2000s, revenues had jumped sharply, eventually crossing tens of thousands of crores. The company grew into one of the largest IT service providers in the world, with offerings expanding beyond Y2K fixes into consulting, digital projects, and a full suite of technology services. The Y2K scare may have faded from public memory, but for Infosys, it was the moment when 18 years of patient investment, frugal living, and reputation-building finally translated into clear financial scale.

Lessons founders and professionals can borrow from Infosys

There are a few clear lessons in this journey that go beyond cliché motivation. First, reputation travels with you even when everything else changes. Murthy’s first contract came because a client trusted his work, not because of a pitch deck or branding. In any job, the way you handle today’s tasks silently shapes what options you will have when you want to branch out on your own.

Second, distribution often hides inside other people’s relationships. Instead of cold-calling multinational executives, Infosys built alliances with consultants who already had those conversations. If you are building a product or service now, it may be more realistic to partner with three strong intermediaries than to dream about landing fifty direct enterprise clients from scratch. The KSA partnership shows how one well-chosen ally can open doors that would otherwise stay closed.

Third, persistence has a very unglamorous side. For ten years, Infosys worked without applause or headlines. For two years, they did not have a computer of their own. Their big break in Y2K arrived only because they stayed in the game long enough to be around when the opportunity finally appeared. It is tempting to romanticize the outcome and ignore the long stretch when it feels like nothing is moving. The more honest takeaway is that most people quit in that boring middle, long before the compounding becomes visible.

Finally, there is a quiet warning in their early lifestyle. The founders made uncomfortable financial and personal choices for years, and those decisions are easy to gloss over when you only look at today’s valuation. If you plan to build something of your own, it is worth asking yourself, with full honesty, whether you are ready for seasons of cold bread dinners, awkward comparisons with richer friends, and delayed gratification. The Infosys story suggests that talent and timing matter, but the willingness to endure that stretch is the filter that decides who is still standing when the big moment arrives.