Helps banks and insurers replace old core systems by sending specialist engineers from Bangalore to work onsite at client offices.
What this company is and how it runs — written from structure, not news.
Mphasis takes banks and insurers off aging core banking platforms like Temenos and Murex by deploying engineers who already know how those platforms are structured and which outputs trigger US or European regulatory reporting rules — knowledge that only accumulates through repeated live migrations and cannot be hired in from outside. Delivering that expertise inside a US client's firewall requires H-1B visas, so the immigration queue between Bangalore and the client site becomes the rate-limiting step between a signed contract and the high-margin onshore hours that make the engagement profitable. Because a bank partway through a multi-year migration has already built its replacement system on Mphasis's proprietary tools and would need twelve to eighteen months just to transfer compliance certifications to a new vendor, clients rarely switch once a project is underway. The whole model depends on H-1B approvals continuing at roughly current levels — if US immigration authorities tighten access for Indian IT firms, the Bangalore practitioners holding the platform knowledge stay in India, the onshore delivery collapses, and what remains is a lower-margin, higher-risk offshore-only product.
How does this company make money?
For day-to-day consulting and development, the company bills clients by time and materials — hours worked at an agreed rate. For full modernization programs it sometimes agrees a fixed price for the whole project upfront. Once a migration is complete, clients often pay a recurring subscription fee for the company to manage the new cloud infrastructure. On longer multi-year BFSI engagements, some contracts tie a portion of the fee to hitting specific transformation milestones.
What makes this company hard to replace?
A bank or insurer that is partway through a multi-year migration has already built its replacement system on this company's proprietary migration tools, and the offshore team holds detailed knowledge of how the client's own legacy systems are structured. Transferring regulatory compliance certifications to a new vendor takes 12 to 18 months on its own. On top of that, the custom API connections built between the new system and the core banking platform require full documentation handover and a fresh round of training before another vendor could safely take over.
What limits this company?
The US government caps the number of new H-1B visas each year and USCIS controls how fast they are processed. No amount of hiring or investment can move engineers from Bangalore to a US client's office faster than that queue allows. The highest-margin part of every engagement — the onsite work during a live cutover — is therefore capped by immigration policy, not by the company's own capacity.
What does this company depend on?
The company cannot operate without H-1B and L-1 visa approvals from US immigration authorities to place engineers at client sites. It also depends on AWS and Microsoft Azure for the cloud platforms its migrations target, Reserve Bank of India approval to move banking data across borders, reliable power and office infrastructure at its Bangalore delivery centers, and SWIFT network access credentials to carry out financial services integration work.
Who depends on this company?
US regional banks that are mid-migration would face delays or stalls in their core banking system replacements if the company stopped delivering. European insurance companies running planned infrastructure upgrades would experience policy administration system outages if the work halted. Logistics companies relying on the company to move supply chain applications to the cloud would lose real-time shipment tracking during those transitions.
How does this company scale?
Adding more offshore delivery capacity in other Indian cities and applying standardized cloud migration methods across new client engagements is relatively cheap to do. What does not scale easily is the senior solution architects who hold deep BFSI domain knowledge and understand the regulatory layer — that expertise builds up only over multiple live migration projects and cannot be trained quickly or replaced by automation.
What external forces can significantly affect this company?
US immigration policy is the most direct external force: any change to H-1B availability immediately shrinks how many engineers can work onsite in the US. Fluctuations in the INR-USD exchange rate also matter because the company pays its Bangalore staff in rupees but bills clients in dollars, so a stronger rupee compresses margins. European GDPR rules and US banking data residency requirements limit which development tasks can be done outside the client's home country, restricting how freely work can move between locations.
Where is this company structurally vulnerable?
If US immigration authorities cut H-1B approvals for Indian IT firms — through lower quotas, higher wage requirements, or new employer restrictions — the Bangalore engineers who know Temenos and Murex cannot legally be stationed inside US client sites. The onsite delivery model stops working, the margin premium disappears, and what remains is a lower-value offshore-only service during the most sensitive phase of a core banking migration.
Price is read as structure — trend, levels, range, peak and volatility drawn on the chart. It does not predict where price goes next.
Sign in to view price data.
Sign in1 interpretation currently present — each is a set of fired observations whose alignment reads as one structural pattern. Click an observation to see the numbers behind it.
Screen for these patternsHow is this stock behaving?
Three observations describe the present configuration: a high share of the trailing three years' weekly closes were higher than the prior week, the company has reported positive net income in each of the last five annual periods, and the book-value-increase-consistency composite over the trailing 5 years is elevated.
An interpretation is present only while every observation it reads stays fired (score ≥ 70). It describes what the aligned readings show — never a verdict, never a prediction.
What the company actually pays, and whether its own cash supports it.
The reported statements, read against the company's own industry.
3 interpretations currently present — each is a set of fired observations whose alignment reads as one structural pattern. Click an observation to see the numbers behind it.
Screen for these patternsIs this company financially stable?
Three observations have aligned: most-recent-quarter total cash is in the upper portion of its mapped range against most-recent-quarter total debt, EBITDA-to-total-liabilities is in the upper portion of its mapped range, and FCF-to-total-liabilities is in the upper portion of its mapped range.
How does this company use capital?
Three industry-benchmarked return-on-capital ratios are simultaneously in their elevated ranges: ROE, ROA, and operating ROA. Because ROA and operating ROA both fire alongside ROE, the configuration is not solely a function of equity multiplier; the underlying asset base is also producing elevated returns relative to peers.
How is this stock valued?
Retained earnings are a large share of total assets; net income was positive in each of the last 5 fiscal years; shareholders' equity is in the upper part of its industry's equity-to-assets range.
An interpretation is present only while every observation it reads stays fired (score ≥ 70). It describes what the aligned readings show — never a verdict, never a prediction.
Shared structure with peers — never a ranking.
Structural observations derived from financial data, industry benchmarks, and supply chain position.
Companies that share the same coordination system — how they create, deliver, or capture value.
Companies that share active interpretations — structural patterns currently present in both stocks.
CompanyGraph