CompanyGraph
Wipro Ltd.
WIPRO · NSE India · India
Runs IT projects for large US companies by pairing engineers in Bengaluru with visa-holding staff inside client offices.
Wipro takes business requirements from large US companies and turns them into working IT systems by splitting the work across two layers: visa-holding engineers sit inside client offices gathering requirements, while separate teams in Bengaluru do the actual system work using years of accumulated knowledge about that specific client's SAP configurations, COBOL code, and mainframe access credentials. Because those Bengaluru teams hold security clearances and configuration histories that the client granted over many years, a competitor starting fresh would need to go through the same multi-year access process before it could do equivalent work — the knowledge is embedded in that team's history with that client's systems, not in the technology itself. The onsite layer is the only channel through which new requirements reach Bengaluru, which means the entire delivery model depends on a steady supply of H-1B and L-1 visas — and the US government caps H-1B approvals at 85,000 annually across all applicants, so Wipro cannot deploy more onsite engineers no matter how many are ready in Bengaluru. That makes the visa cap both the ceiling on how fast the company can grow and the single point that breaks first if US immigration policy tightens, because without cleared onsite personnel feeding requirements in, the Bengaluru teams have nothing to act on and the client relationships they have spent years building begin to lapse.
How does this company make money?
The company charges clients by the hour for offshore development teams, with a blended rate that reflects the mix of engineers working on a project. For projects with a clearly defined scope, it agrees on a fixed total price upfront. For clients who need ongoing maintenance and support after a system goes live, it signs annual managed services contracts that provide recurring income year after year.
What makes this company hard to replace?
A client's SAP and Oracle implementation certifications are tied to this company's specific teams and their history with that client's environment. The mainframe access and security clearances held by the Bengaluru teams were granted by the client over many years and cannot be transferred to a new vendor. CMMI Level 5 and ISO certifications are registered to particular delivery center locations and team compositions. Switching providers means starting that entire multi-year access and certification process over again from the beginning.
What limits this company?
The US government issues at most 85,000 H-1B visas per year across every company and industry combined. No matter how many engineers are ready and waiting in Bengaluru, they cannot be deployed at US client sites faster than that cap allows. Growing the Bengaluru workforce does not translate into more client work unless matching visa slots open up — and no single company controls that.
What does this company depend on?
The company cannot operate without H-1B and L-1 visa approvals from US immigration authorities for its onsite workers. It relies on the Indian Institutes of Technology and other engineering colleges to fill its Bengaluru teams. It needs NASSCOM certifications to validate its offshore delivery centers. It depends on client VPN and secure connectivity infrastructure to link onsite and offshore teams. And it requires active implementation partnerships with Oracle and SAP to carry out the software work clients hire it to do.
Who depends on this company?
Fortune 500 financial services firms depend on its COBOL and mainframe specialists — without them, core banking system upgrades would stall. North American healthcare systems rely on its Epic and Cerner integration teams to implement and connect electronic health records; those projects would face serious bottlenecks without them. Global manufacturing companies count on its Bengaluru delivery centers for SAP S/4HANA migrations, a type of work concentrated there that they could not easily replace.
How does this company scale?
Delivery center infrastructure and project management methods can be rolled out relatively cheaply across smaller Indian cities, where wages follow predictable patterns. What does not scale through hiring is the senior relationship managers and domain specialists who have spent years building trust with specific Fortune 500 clients — those relationships are personal and take a long time to develop, so they remain a bottleneck no matter how fast everything else grows.
What external forces can significantly affect this company?
US immigration policy is the most direct external threat — any tightening of H-1B processing times or approval rates immediately limits how many engineers can be placed at client sites. If the Indian rupee rises against the US dollar, the cost savings that make offshore delivery attractive narrow, which weakens the company's pricing advantage. And if large clients move further toward remote-first work models, the demand for the traditional onsite-offshore split could shrink.
Where is this company structurally vulnerable?
If the US government tightened H-1B and L-1 approval rates significantly, the onsite layer inside client offices would shrink. Without those onsite workers gathering requirements and managing access, the Bengaluru teams stop receiving the input they need to do billable work. Client relationships weaken, and the clearances and certifications that took years to build quietly lapse.