Converts old COBOL mainframe software at banks and insurers into modern cloud code using its own automated tools.
At a glance
- Depends onDownstream position: depends on 9 industries, supplies 5
- Scale
Converts old COBOL mainframe software at banks and insurers into modern cloud code using its own automated tools.
What this company is and how it runs — written from structure, not news.
Hexaware Technologies takes the decades-old COBOL code that runs core banking and insurance systems on IBM z/OS mainframes and converts it into modern Java or .NET applications using automated tools built specifically for banking and insurance logic — not generic COBOL translation. Because those tools already know the recurring rule structures in core banking and claims systems, they compress what would otherwise be a three-year manual rewrite into twelve to eighteen months, which is what makes it possible to offer clients a fixed price rather than an open-ended labour bill. Once a project is underway, the client's transaction flows are split between the old mainframe and the partially converted cloud environment, so swapping vendors mid-stream would mean a new entrant reverse-engineering half-finished code, reapplying for mainframe security clearances, and reconstructing months of configuration knowledge — a risk high enough that most clients stay. The whole model depends on banks and insurers continuing to run COBOL on traditional mainframes in the first place; if new cloud-native core banking platforms make that legacy stack obsolete before it needs converting, the compression advantage that justifies fixed-price contracts disappears along with the client base.
How does this company make money?
The company signs fixed-price contracts worth between $5 million and $50 million each, covering the full transformation of a defined set of systems. Clients do not pay everything upfront — payments are tied to milestones, such as successfully migrating a specific module or passing user acceptance testing. The business model works because the automated tools reduce the hours of expert labor needed, which means the company can quote a fixed price without risking losses from an open-ended rewrite.
What makes this company hard to replace?
By the midpoint of a project, the code exists in a half-converted state that only the company fully understands. A new vendor would have to reverse-engineer that partially converted COBOL, learn the client's specific mainframe configuration from scratch, and go through the months-long process of obtaining the security clearances and regulatory approvals needed to access the mainframe environment. Core banking systems cannot simply be handed off — the integration runs too deep, and the cost and risk of starting over mid-stream is high enough that most clients stay.
What limits this company?
The company can only run as many projects at once as it has people who genuinely understand both IBM z/OS mainframes and modern cloud systems. That combination takes more than ten years to develop. No amount of tool licenses or client demand changes this — the delivery centers in Chennai and Pune can only field so many of these specialists at any given time.
What does this company depend on?
The company cannot operate without access to clients' IBM z/OS mainframes for the analysis phase of each project. It relies on its own automated COBOL-to-Java conversion tools as the engine of every engagement. AWS and Microsoft Azure are the target environments where converted systems are deployed, making those partnerships essential. H-1B and L-1 visa approvals are needed to place Indian technical staff at client sites in North America. Finally, the secure delivery center infrastructure in Chennai and Pune — which connects directly to client mainframe environments — underpins everything.
Who depends on this company?
Large banks running core banking on IBM mainframes are the most exposed: if a project is abandoned halfway through, their transaction processing systems are split across two environments and neither works cleanly on its own. Insurance companies with COBOL-based claims systems would lose the ability to update policy rules or connect with digital channels. Travel companies using legacy reservation systems would be unable to link to modern booking platforms and mobile apps.
How does this company scale?
The automated conversion tools and standardized methods can be applied to new projects without the cost rising in proportion — that part scales well. What does not scale is the senior specialist headcount. People who can work fluently across both IBM z/OS and cloud platforms cannot be trained quickly, so as demand grows, the company is forced to pick its projects carefully rather than take on everything at once.
What external forces can significantly affect this company?
When the Indian rupee falls against the US dollar, the cost of running delivery centers in Chennai and Pune drops, which helps margins — but multi-year fixed-price contracts make currency swings hard to manage cleanly. US immigration policy is a direct operational risk: if H-1B or L-1 visa approvals tighten, the company loses its ability to put senior staff on-site at client mainframe environments in North America. Banking and insurance regulators also impose specific security certifications and audit requirements during modernization work, adding compliance overhead to every project.
Where is this company structurally vulnerable?
If large banks and insurers stop running IBM z/OS mainframes — for example by adopting new cloud-native banking platforms that never accumulate COBOL in the first place — the pool of systems the company's tools are built to convert would shrink steadily. Fewer source systems means the speed advantage disappears, fixed-price contracts stop making financial sense, and the core business loses its reason to exist.
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?
Current close sits in the upper portion of the 14-week high-low range; current close sits in the upper portion of its 20-week Bollinger Bands; RSI sits above its 20-week recent mean (Bollinger %B applied to RSI).
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.
5 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 FCF-denominator ratios co-occur in their elevated ranges: FCF/total assets, FCF/total shareholders' equity, and industry-benchmarked FCF/OCF. The configuration describes free cash flow scaling against three different denominators at the latest annual snapshot.
Is this company growing?
Three multi-year observations co-occur: revenue increased year-over-year in each of the last three fiscal years, gross profit (absolute level) increased year-over-year in each of the last four fiscal years, and net income was positive in each of the last five fiscal years. The configuration describes growth-and-profitability persistence across three different windows.
Three observations align on a healthy multi-year growth profile: revenue grew every year over the trailing five-year window, operating margin in the most recent year is at an elevated level, and revenue grew every year over the trailing three-year window. Together they describe sustained top-line continuity at a high current margin level.
Where is this company structurally exposed?
Three observations describe the current configuration: the weak-bounce composite is elevated, acute-decline markers are active, and drawdown from the prior peak is significant.
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