The $1 Million Deal That Could've Ended Infosys - Infosys Co-Founder

There is a moment in our podcast with Kris Gopalakrishnan that most public tellings of the Infosys story either forget or skip over.

We almost gave up in 1989, he said. There was nothing to show for eight years of hard work.

The Infosys co-founder was telling us about the moment the company that would go on to define Indian IT almost ceased to exist. Not through failure. Through sale. A one-million-dollar offer had come in. Six of the seven founders were, in Kris’s account, ready to consider it.

The seventh was not.

What happened in that meeting reshaped the trajectory of the Indian IT industry.

The 1981 Bootstrap Reality

The founding condition of Infosys is worth understanding before the 1989 moment.

The software services industry did not exist in India. There was no reference for it. There was no ecosystem. There was no funding infrastructure.

A software company in 1981 India had no collateral. Banks lend against assets. Assets require physical form. Code has no physical form. The banking system had no framework for lending to a business whose entire value was intellectual property. The alternative to bank funding did not exist either - the venture capital ecosystem that would emerge in India decades later was not there in 1981.

The founders had no funding options other than their own resources. They bootstrapped with family savings. The operational reality was hand-to-mouth invoicing.

Whatever invoices they generated, they tried to collect as quickly as possible so they could pay salaries.

The rhythm of the early Infosys was the rhythm of the accounts receivable cycle. Not month-to-month. Invoice-to-invoice.

The 1989 Moment

Eight years into that reality, the founders sat down and took stock.

There was nothing to show for eight years of hand-to-mouth. Eight years of no assets, no VC, no bank funding, no security. Eight years of the founders living in rented apartments.

The exit offer came. A million dollars for the company.

In 1989 India, this was serious money. Enough to give each of the seven founders a life-changing amount. Enough to end the hand-to-mouth reality forever.

Then Narayana Murthy said no. I’m not going to give up, he said. I’ll continue.

The others said okay, if you’re continuing, we are continuing too.

That was the decision. Made in one meeting. Through one person’s conviction and six people’s willingness to follow that conviction.

The IPO Target

The follow-on decision was to set a target. IPO in India by 1992.

The target became the focus mechanism. It helped them focus on what needed to be done. Hopefully, the IPO would give them some money. Until then, they had none.

The target was not a dream. It was a coordination device. It gave the seven founders a shared direction, a shared timeline, and a shared metric for progress. It converted eight years of open-ended struggle into a defined finish line.

The finish line came within a year of the target date. IPO in 1993. NASDAQ listing in 1999.

Everything the Indian IT industry became was made possible by these two decisions - to not sell in 1989 and to set an IPO target for 1992.

The Y2K Growth

The context that transformed Infosys from a small services company into an industry-scale employer was the Y2K wave.

From 1997-98, because of the Y2K problem, a lot of work came to India. Infosys was growing more than 100% every year.

Growth at 100% per year is not a scaling problem. It is a rebuilding-the-company-every-year problem. The workforce had to double annually. The infrastructure had to double annually. The delivery capability had to double annually.

Infosys built the answer that eventually became the entire Indian IT industry’s model.

The Training Model

The model was recruitment at scale from campuses, then in-house training.

That model was invented at Infosys during the Y2K years. It became the standard for TCS, Wipro, HCL, Cognizant, and every other Indian IT services company that would follow.

The training lasted three months. It covered what industry actually needed.

The Academia-Industry Gap

The training model existed because academia was not producing industry-ready engineers.

What academia teaches is not what industry is doing, Kris said. Typically you would work in COBOL in industry. In the academic institution, they would teach you C.

The language mismatch was the surface of the problem. The task mismatch was deeper.

In industry, you’re doing a lot of maintenance because you’re working with existing code. In academic institution, they train you to write new software.

Academic training focused on new code. Industry work was mostly maintenance of existing code. Two completely different skill sets.

The quality-assurance mismatch was deeper still.

In academic institution, they never teach you testing, Kris said. Application side of things are not there.

Testing is a core skill in industry software work. It was not part of academic training then. It largely still is not.

Then came the insight that changed how I think about all of this.

In academic institution, the only person who uses the software is the person who writes the code, Kris said. Nobody else uses the software.

That is the philosophical foundation of the entire gap. In academia, code is written for the writer. It works if the writer says it works. There is no user to complain. There is no maintenance cycle. There is no consequence to bad code beyond the grade.

In industry, you don’t use the software, it’s everybody else who uses the software. The entire world will use the software. So you have to be extremely quality conscious. You have to write good code. You have to write code that’s maintainable.

That is the entire difference. In industry, the writer does not use the code. Everyone else does. The writer is producing something they will never consume. That requires a completely different quality standard, a completely different mental model, and a completely different training.

The Universal Insight

The academia-industry gap that Kris describes is not just a software issue.

Every profession has this gap. Medical school teaches diagnosis. Practice teaches follow-through. Law school teaches case analysis. Practice teaches client management. Engineering school teaches problem-solving. Practice teaches maintenance of existing systems. Management school teaches strategy. Practice teaches operational firefighting.

The pattern is consistent. Academic training is oriented toward the first-order problem. Practical work is oriented toward the second-order problem. Academic training assumes greenfield situations. Practical work is dominated by brownfield situations.

Every industry that has scaled successfully has built its own training model to close the gap. Infosys did it for Indian IT. Consulting firms do it through their two-year associate programs. Banks do it through their analyst tracks. The scale of the Infosys model - training millions of engineers over decades - is what made it uniquely visible.

The Founder Specialization Principle

The other thing that made Infosys was the founder specialization.

Over time, they started specializing because they didn’t want to step on each other’s toes. That’s one reason they stayed together, Kris said. Otherwise, typically what happens is the founders split at some point of time.

This is the anti-splitting principle. Most co-founded companies split because the founders overlap in responsibilities. The overlap creates friction. The friction creates resentment. The resentment ends the partnership.

Infosys did not split because the founders specialized. Each person moved into a distinct lane.

Kris on technology. Nandan Nilekani on sales and marketing (very articulate, Kris said). Narayana Murthy on finance, investment, and building the company. Three of the seven had defined lanes. The others also settled into their own domains. The overlap was minimised.

That’s one reason we stayed together, Kris said.

The reason Infosys stayed together was not personal chemistry. It was operational specialization. Personal chemistry helps, but it is not the mechanism. The mechanism is that people who are not stepping on each other’s toes have fewer reasons to fight.

What This Reveals

Three things from this segment will stay with me.

The 1989 decision. The entire Indian IT industry pivots on the moment Narayana Murthy said no to a one-million-dollar offer. The rest of the story we know exists because that one moment went the way it did.

The academia-industry gap insight. In academia the writer is the user. In industry the writer is not the user. Every quality standard, every training program, every hiring decision flows from that difference.

The founder specialization principle. Co-founded companies do not stay together because of chemistry. They stay together because the operational structure prevents overlap. The mechanism is not friendship. It is specialization.

Watch the full episode here: