The Conversation: Outsourcing Changed IT. What Comes Next?

The modern outsourcing story cannot be reduced to one explanation. Cost mattered enormously. But so did the rapid expansion of computing, the Internet, telecommunications, enterprise software, Y2K remediation, the dot-com era, globalization, shortages of certain technical skills, improvements in international communications, and the emergence of highly educated technology workforces around the world. India was exceptionally well positioned. It developed a large English-speaking technical workforce. Indian technology companies built sophisticated delivery organizations. Telecommunications improved. Work that once had to be performed in the same building, or at least in the same country, could increasingly be performed thousands of miles away.

By 2023-24, India exported approximately $190.7 billion in software services, according to the Reserve Bank of India. Approximately $125.5 billion of that was categorized as IT services, about $50.1 billion as BPO services, and another $9.6 billion as engineering services. The United States alone accounted for approximately 54 percent of India's software-services export destination, or about $103.2 billion under the RBI survey methodology. And roughly 90 percent of those software services were delivered off-site. Those numbers tell us something important. Outsourcing to India is not a small experiment that might disappear if we simply argue about it long enough. It became an enormous economic system. More broadly, total U.S.-India services trade reached approximately $83.4 billion in 2024, with about $41.8 billion of U.S. services exports to India and $41.6 billion of U.S. services imports from India. The relationship is therefore more complicated than the simple picture of money flowing in only one direction. Today, India's technology sector itself has crossed another milestone. Industry estimates reported in 2026 put annual technology-sector revenue at approximately $315 billion and employment at roughly 5.95 million people. Those are millions of engineers, developers, analysts, cybersecurity professionals, managers, support personnel, operations specialists, and their families.

We should be equally honest here.

Some experienced American employees were asked to document systems and transfer knowledge before their positions disappeared. Some managers watched teams they had spent years building get dismantled. For someone who spent twenty years developing a career and then lost that career because the work could be purchased somewhere else for less money, an economist explaining that globalization increases aggregate efficiency provides very little comfort.

Here we have to resist an attractive temptation: producing one enormous number and calling it fact. There is no authoritative cumulative count of American IT jobs lost specifically to India. The U.S. Government Accountability Office has repeatedly pointed to limitations in government data for measuring services offshoring. Employment changes happen simultaneously because of outsourcing, automation, recessions, mergers, new technologies, business failures, changing occupations, productivity improvements, and companies reorganizing work. That makes attribution difficult. One of the most famous numbers from the early outsourcing debate was a Forrester Research forecast that approximately 3.3 million U.S. service jobs could move offshore by 2015. Forrester later raised the projection slightly to about 3.4 million. That was a forecast across service occupations. It was not an official count of 3.4 million Americans who actually lost their jobs to outsourcing. We should not present it as one. Government data available at the time captured only portions of the phenomenon. GAO noted, for example, that mass-layoff statistics could substantially undercount offshoring because they were designed to capture particular kinds of large layoffs rather than every position gradually transferred overseas. So the honest conclusion is uncomfortable but important: We know displacement occurred. We can document individual cases, occupational changes and corporate decisions. But anyone claiming to know the exact cumulative number of American IT careers eliminated by outsourcing should explain how that number was measured.

There is another fact that deserves equal attention. American technology employment remained enormous and evolved into new occupations. The Bureau of Labor Statistics estimates approximately 5.4 million computer and mathematical jobs in 2024, with employment projected to reach almost 6 million by 2034. The median annual wage for that occupational group was approximately $105,850 in 2024, compared with $49,500 across all occupations. Software development remains particularly large. BLS counted approximately 1.69 million software developers in 2024 and projects employment to increase by almost 268,000 positions by 2034. At the same time, some older technology occupations are contracting. Computer programmer employment, for example, is projected to decline about 6 percent from 2024 through 2034. BLS specifically identifies automation, including AI, and movement of some higher-level work into software-development roles as factors. This is why simplistic arguments fail. It is possible for America to have a thriving technology economy while particular American technology workers experience severe disruption. It is possible for software-development employment to grow while traditional programming roles shrink. It is possible for companies to become more productive while career ladders disappear underneath individual workers. And it is possible for outsourcing to produce economic benefits while imposing concentrated costs on people who never agreed to become the adjustment mechanism.

We should also resist rewriting the business side of the story. Companies did not build global delivery organizations solely because executives woke up one morning wanting to eliminate American jobs. Cost was a major incentive, certainly. But outsourcing also provided access to larger talent pools, specialized skills, around-the-clock operations, faster scaling, standardized delivery organizations, and the ability to convert some fixed internal costs into externally delivered services. Economic research has also found productivity benefits associated with services offshoring. Those advantages mattered. If outsourcing had produced no economic value, companies would not have expanded it for decades. The problem is not that the gains were imaginary. The problem is that the gains and losses were distributed very differently.

Saying that the first five things happened does not erase the sixth.

We should recognize what the technology industry accomplished for India. A global market emerged for Indian engineering, software development, IT operations, consulting, business-process services, cloud services, cybersecurity, and increasingly artificial intelligence. Millions of people entered technology careers. Companies headquartered in India became global corporations. Technical expertise increased dramatically. Indian professionals moved between India and the United States, built companies, managed international teams, created intellectual property, purchased homes, raised families, and contributed to both economies. That is a remarkable economic development story. Americans do not need to deny India's achievement in order to discuss what happened to American workers. And Indians do not need to deny American job displacement in order to celebrate what India's technology industry accomplished. Maturity requires us to hold both truths at once.

This distinction is particularly important. A skilled engineer legally moving to the United States and working here is economically different from moving the engineer's job from the United States to another country. The H-1B program, for example, is a temporary nonimmigrant worker program for specialty occupations. The regular statutory cap is generally 65,000 positions per fiscal year, with another 20,000-position exemption for qualifying holders of advanced degrees from U.S. institutions, in addition to various cap-exempt employers and situations. The program has legitimate controversies. There have been concerns about wage competition, outsourcing-company usage, worker dependency on sponsoring employers, displacement and whether existing protections adequately protect American workers. Those concerns should not be dismissed. The Government Accountability Office itself has previously concluded that weaknesses in H-1B oversight and worker protections warranted reform. U.S. labor rules are intended to address part of this risk. For covered employment-based visa programs, employers generally must satisfy prevailing-wage requirements; for H-1B workers, employers are required to pay at least the prevailing wage or the employer's actual wage for similarly qualified workers, whichever is higher. Rules, however, only matter when their design is sound and they are properly enforced.

Those goals are not mutually exclusive.

The evidence that immigrants contribute disproportionately to American innovation and entrepreneurship is substantial. Recent economic research found that immigrants represented about 16 percent of U.S. inventors but produced approximately 23 percent of patents. When researchers incorporated the productivity spillovers immigrant inventors generated among collaborators, they estimated immigrants were responsible for roughly 32 percent of aggregate U.S. innovation in their model. Other research using U.S. Census administrative data found that immigrants were approximately 80 percent more likely to start businesses than U.S.-born individuals and were disproportionately represented among companies that grew into large employers. That matters. When a talented Indian engineer comes legally to America, joins an American company, helps create a product, forms a startup, employs Americans, purchases services, pays taxes, buys a house and becomes part of a community, that is not the same economic event as eliminating an American department and transferring its work abroad. We should stop pretending those two things are identical. There is another fascinating wrinkle. Research on H-1B restrictions has found evidence that when multinational companies cannot obtain skilled workers in the United States, some respond by expanding employment at foreign affiliates, including in India, China and Canada.

We should be capable of pursuing all four objectives.

Between the giant American corporation and the giant global outsourcing company sits an enormous group of people whose future deserves more attention: experienced local IT professionals.

People who have built networks, recovered failed servers at midnight, negotiated with vendors, migrated email systems, defended companies from ransomware, managed budgets and explained technology to executives. When their position disappears, we frequently tell them to find another position. But perhaps that is not the only answer. What if experience itself could become the foundation of a business? Research into entrepreneurship provides an encouraging clue. Analysis using Census Bureau administrative data found that the average founder of the fastest-growing new businesses was about 45 years old, and industry experience was strongly associated with entrepreneurial success.

This is where the conversation we want to have begins. Imagine an experienced IT professional who knows customers, understands technology and has earned trust over decades. That person may be capable of managing several small or midsize businesses. But becoming an MSP traditionally means building an organization. They need monitoring. Cybersecurity. Cloud expertise. Backup. Networking. Infrastructure. Automation. Escalation engineers. A NOC. Vendor relationships. Billing systems. Processes. Documentation. Coverage when they are sleeping, sick or on vacation. That can require significant capital and personnel before the entrepreneur has enough customers to support it.

So instead of asking:

How can one person build all of that?

Perhaps we should ask:

Why should one person have to build all of it?

What if the local IT entrepreneur owns the customer relationship, understands the business, provides strategic guidance, coordinates local needs and builds recurring revenue?

And what if a technology platform and global engineering organization operates behind that entrepreneur?

Not instead of them. Behind them. That distinction is the idea we will explore throughout this series.

The traditional outsourcing equation was often perceived this way:

We want to explore another architecture:

This does not reverse globalization. It reorganizes participation in globalization.

Companies use that phrase too easily. If one side saves money and another person loses a career, calling the transaction win-win does not make it so. Our eventual objective is more demanding. We will explore what we call a Five-Way Win:

But we will not declare victory simply because five groups appear on a diagram. Each participant must receive real economic value.

If one participant is systematically exploited to subsidize everyone else, the model has failed its own test.

There is another reason to have this discussion now. Artificial intelligence is changing technology work again. And this time the disruption is not exclusively American. Indian technology workers are confronting automation too. In 2026, India's technology industry is expected to generate approximately $315 billion in revenue and employ roughly 5.95 million people, even as AI changes the traditional labor-intensive services model. The lesson should be obvious. American workers are not the only people whose jobs can be disrupted by technology.

The next argument therefore cannot simply be: Where should the jobs go? It needs to become: How do we build an ecosystem in which people use technology to become more productive, more entrepreneurial and more economically independent?

netPulz is a technology company. We are building technology and operational capabilities that we believe can help local IT professionals become independent providers without having to build every technical capability themselves. That gives us a point of view. It also gives us a commercial interest. We should acknowledge that openly. This series will eventually explain how we believe netPulz can participate in a different model. But before presenting a solution, we need to understand the problem. That is why the first several parts of this series will spend more time discussing outsourcing and its consequences than discussing netPulz. We want to earn the right to propose an alternative. And we expect people to disagree with us.

Those disagreements belong in the conversation.

Part 1 - Outsourcing IT to India: The Conversation America Still Needs to Have

We will examine how India became the center of global IT outsourcing, why American businesses embraced the model, what economic advantages it produced, and why the consequences for American technology workers still deserve an honest discussion.

Part 2 - The Damage: What IT Outsourcing Did to the American IT Career

We will focus on the people: job displacement, career disruption, wage pressure, lost institutional knowledge, changing career ladders, and IT managers caught between corporate economics and the people they managed.

Part 3 - The Problem: India Was Not the Problem. The Outsourcing Model Was.

We will separate the people performing the work from the economic structure that frequently forced workers in different countries to compete primarily on labor cost.

Part 4 - The Opportunity: What If the American IT Manager Became the MSP?

Instead of assuming that an experienced IT professional whose role disappears must find another employer, we will explore another possibility: what if they became the provider?

Part 5 - The Independence: The One-Person MSP Can Become a Real Business

We will examine whether an individual technology professional can realistically manage multiple customers, generate recurring revenue, build equity, save for retirement, hire others and create a sustainable independent business.

Part 6 - The Invisible IT Department: How netPulz Can Power Local MSPs

Then we will show the infrastructure required behind that entrepreneur: monitoring, infrastructure, cloud, cybersecurity, backup, automation, engineering, escalation, operations and vendor relationships.

Part 7 - The Five-Way Win: A Different Economics for Global IT Services

We will put the economic model to the test. Can the customer, local entrepreneur and workforce, netPulz ecosystem, netPulz itself, and the India technology team genuinely benefit from the same transaction?

Part 8 - From Outsourcing to Shared Prosperity: A New American-Indian IT Partnership

Finally, we will ask whether the next chapter of American-Indian technology collaboration can move beyond labor arbitrage: not America versus India, not local versus global, but local entrepreneurship supported by global technology.

We cannot bring back the technology economy of 1995. And perhaps we should not try. Cloud computing is real. Global engineering is real. Automation is real. Artificial intelligence is real. India's technology industry is real. And the frustration of American technology professionals who watched portions of their careers move overseas is also real. The question is what we do with those realities. Perhaps the next era of IT should not be built around deciding which country's worker gets the job. Perhaps it should be built around giving more people ownership in the economic system technology creates.

That is the conversation we want to have. Not because we believe we already know every answer. But because after thirty years of outsourcing, another decade of cloud transformation, and the arrival of AI, we should at least be willing to ask a better question. Outsourcing changed IT. What comes next?