An Indian information technology (IT) services company does not sell software off a shelf. It sells engineering capacity — people, and increasingly finished outcomes — to large enterprises that are almost all outside India. A bank in New York, a retailer in London or a carmaker in Stuttgart hands over a slice of its technology work, and an Indian vendor runs it from Pune, Hyderabad or Bengaluru for a fraction of what doing it locally would cost.
That one sentence explains most of what the sector's numbers do. Revenue is invoiced in dollars, euros and pounds; salaries are paid in rupees. Growth depends on how much technology budget Western enterprises release. Margin depends on how many of your people are billing, at what rate, and how junior you can afford to make the team. Hold those four ideas together and an IT quarterly result stops being a wall of acronyms.
What does an IT services company actually sell?
At the simplest end, it sells time. A client needs forty engineers to keep an insurance claims system running; the vendor supplies them and bills for their hours. This is the old outsourcing model, and it still funds a large part of the industry.
Above that sits managed services: the vendor takes responsibility for the whole system — uptime, upgrades, support — for an agreed annual fee. The client stops counting heads and starts buying a service level. And above that sits transformation and product engineering work, where the vendor designs and builds something new rather than maintaining something old.
The higher up that ladder a company's revenue sits, the less its price can be undercut by whoever has cheaper engineers. That climb — into digital transformation, into generative artificial intelligence (GenAI) work, into engineering research and development (ER&D) — is the strategic story of the sector, and it has its own longer treatment at /learn/know-your-sector/indian-it-sector. This page is about the machine underneath it.
Earned in dollars, spent in rupees
Almost every large Indian IT company bills in foreign currency and pays most of its costs in rupees. That mismatch is the single most misread thing in the sector.
When the rupee weakens, the same dollar invoice converts into more rupees. Reported revenue and margin improve without a single extra hour being sold. When the rupee strengthens, the reverse happens and a decent operating quarter can look like a bad one. Neither move tells you anything about whether clients are buying more.
This is why companies report constant-currency growth: growth recalculated with exchange rates held fixed at the prior period's levels. It strips the currency out and leaves only the volume-and-price change. Constant-currency growth is the honest growth number. Reported growth is the one the currency happened to hand you.
Constant-currency growth = growth measured with exchange rates held fixed- Reported growth = constant-currency growth ± the currency effect
- A weak rupee flatters reported growth; a strong rupee hides it
Note — Cross-currency matters too. A company with large European revenue is exposed not just to the rupee against the dollar, but to the euro and pound against the dollar. Read the currency commentary in the results release, not just the headline growth line.
Time-and-materials versus fixed-price
Every contract sits somewhere between two shapes, and the shape decides who carries the risk.
In time-and-materials work, the client pays for hours delivered. If the project takes longer, the client pays more. The vendor's margin is fairly predictable, but so is its ceiling — you only earn more by billing more hours.
In fixed-price work, the vendor quotes a number for a defined outcome and keeps whatever it does not spend. Deliver efficiently and margin expands well beyond the hourly equivalent. Underestimate the work, or let the scope creep without a change order, and the overrun comes straight out of profit. A rising fixed-price share is therefore both an ambition signal and a risk signal — it is what a company with real delivery discipline chooses, and what punishes a company without it.
- Time-and-materials (T&M)
- Billed per hour or per person-month. Cost risk sits with the client; the vendor's margin is steady but capped.
- Fixed-price / outcome-based
- One quoted price for a defined deliverable. The vendor keeps the efficiency gain and eats the overrun.
- Scope creep
- Work the client asks for that was not in the original statement of work. Unbilled scope creep is the classic way a fixed-price project loses money.
The three levers that decide margin
Operating margin in IT services is not really about pricing. Rates move slowly and are set by competition. Margin is made or lost in how the workforce is arranged, and every lever below is disclosed in the quarterly fact sheet.
Utilisation is how much of your paid workforce is on billed work. People between projects — 'on the bench' — cost the same and earn nothing. The pyramid is the ratio of junior engineers to senior ones on a project: a wide base of freshers doing work a senior does not need to do is cheaper to staff and still billable. Attrition is how many people leave; high attrition forces replacement hiring, retention bonuses and re-training on live projects, and all three land on the cost line.
| Lever | What it measures | Healthier direction | What worsens it |
|---|---|---|---|
| Utilisation | Share of billable staff on paid client work | Stable or rising quarter on quarter | Hiring ahead of deals that then slip |
| Pyramid shape | Freshers versus senior staff on a project | A widening base of junior engineers | Senior-heavy teams doing commodity work |
| Attrition | People who left over the last twelve months | Falling, and below the peer group | A hot hiring market and wage bidding |
| Onsite mix | Work done at the client site, not from India | More of the work shifted offshore | Visa curbs, clients demanding local staff |
| Fixed-price execution | Whether fixed-fee projects land on budget | Growing fixed-price share, steady margin | Scope creep the client will not pay for |
Deal wins come first. Revenue comes later.
An IT company announces the total contract value (TCV) of the deals it has signed — the full value of the work over the contract's life. That announcement happens in one quarter. The revenue arrives in slices across the several years the contract runs.
This is why TCV leads and reported revenue lags. A strong signing quarter tells you about revenue two, four, six quarters out. A weak one is an early warning that will not show in the profit and loss statement for a long time. Two details matter when you read it: how much of the TCV is genuinely new work rather than a renewal of business the company already had, and how long the contract runs, because the same TCV spread over seven years is a much smaller annual number than over three.
Pro tip — TCV is disclosed in the quarterly investor presentation and the earnings call, not in the headline results table. If a company stops breaking out net-new TCV separately from renewals, that change in disclosure is itself information.
Who the clients are is the real cycle
Two things decide how exposed a vendor is: how concentrated its revenue is in a few clients, and which industries those clients sit in.
Concentration is straightforward. If the top handful of clients account for a large share of revenue, one of them insourcing a programme or cutting its budget can undo a year of growth elsewhere. Companies disclose the revenue share of their top client, top five and top ten — read the trend across several years, not one snapshot.
Vertical mix is subtler and more important. 'IT demand' is not one thing. It is banking demand plus retail demand plus manufacturing demand, each on its own cycle. A vendor weighted to banking, financial services and insurance (BFSI) moves with Western bank cost programmes. One weighted to manufacturing moves with industrial capital spending. They can have opposite quarters.
| Vertical | What drives its technology spend | What stalls it |
|---|---|---|
| BFSI | Regulation, payments, core-system upgrades | Credit stress and bank cost-cutting drives |
| Retail & consumer | E-commerce, supply chain, store systems | Weak US or European consumer demand |
| Manufacturing | Factory software and product engineering | Industrial slowdown, deferred capital spend |
| Healthcare & life sciences | Compliance, claims and clinical data systems | Payer cost pressure and policy change |
| Communications & media | Network software, billing, content platforms | Telecom capex pauses between build cycles |
| Energy & utilities | Grid systems, metering, transition projects | Commodity price swings hitting budgets |
Defensive at home, cyclical abroad
Indian IT is routinely described as a defensive sector, and in a domestic context that is fair. Its customers are not Indian, so a weak Indian consumer, a bad monsoon or a rate rise by the Reserve Bank of India barely touches its order book. Balance sheets in the sector are typically cash-rich rather than debt-laden, which is the other half of the defensive label.
But it is not defensive in any absolute sense. It is cyclical — the cycle just belongs to somebody else. When a US or European recession forces enterprises to freeze discretionary technology budgets, transformation projects are the first thing paused. What survives is the maintenance work, which is lower-margin. So the sector can hold revenue while its mix deteriorates, and the mix damage shows up in margin a few quarters after the headline stayed calm.
Watch out — Do not treat 'defensive' as 'safe'. In a global slowdown IT can fall alongside global equities while domestic-facing Indian sectors hold up — the opposite of what the defensive label makes people expect.
Large-cap and mid-cap IT are different risk profiles
They are not two sizes of the same business. A large vendor competes for enormous multi-year contracts, serves thousands of clients, and has a decades-long relationship history that makes it hard to displace. That breadth is what dampens its swings — and what caps them.
A mid-cap vendor usually wins by being unusually good at one thing: a vertical, a platform, an engineering discipline. KPIT Technologies, for example, is an engineering-services specialist tied to automotive software, so its cycle is set by carmakers' research budgets rather than by banking technology spend. That focus can produce growth far above the industry average while the niche is hot, and far below it when the niche cools. Concentration cuts both ways, and it is the reason mid-cap IT deserves position sizing that reflects a wider range of outcomes.
| Dimension | Large-cap IT | Mid-cap IT |
|---|---|---|
| Client base | Very broad, deep multi-decade ties | Fewer, larger, more concentrated |
| Growth range | Closer to the industry average | Can run far above or far below it |
| Deal size | Bids for very large multi-year contracts | Wins inside a niche or one vertical |
| Cash return | Long record of dividends and buybacks | More often reinvests for growth |
| Volatility | Typically shallower drawdowns | Sharper moves in both directions |
| Main fragility | Legacy revenue mix, slow decisions | Losing a single large client |
What retail investors get wrong here
- Reading reported revenue growth without checking the constant-currency number, and mistaking a weak rupee for demand.
- Treating headcount growth as a proxy for business growth. Adding people without billable work destroys utilisation and margin.
- Assuming 'defensive' means it will hold up in every fall — when the fall originates in the US or Europe, it usually will not.
- Ignoring the deal-win disclosure because it is not in the headline result, then being surprised by revenue two quarters later.
- Buying a mid-cap on a large-cap thesis, without sizing for the client concentration that comes with the niche.
- Extrapolating one strong quarter's margin without asking which lever produced it — a genuine pyramid improvement is repeatable, a one-off currency gain is not.
How to actually track it
- 1
Each quarter, open the investor presentation first
Not the press release. The presentation carries constant-currency growth, deal TCV, utilisation, attrition and vertical-wise growth in one place.
- 2
Write down five numbers per company
Constant-currency growth, operating margin, utilisation, trailing-twelve-month attrition, and TCV of deals won. Track the direction of each across four quarters, not the level in one.
- 3
Read the vertical table, not the total
Growth by vertical tells you whether a slowdown is broad or confined to one client industry. A total can hide one collapsing vertical funded by another that is booming.
- 4
Listen for guidance language on the call
Management's phrasing about discretionary spend, deal ramp-ups and decision-making cycles is where a demand change is first admitted, usually before it reaches the numbers.
- 5
Keep an eye on the currency, but separately
Note the rupee's move over the quarter so you can mentally subtract it. Currency is a translation effect, not a business event.
What sector analysis will not tell you
Everything above describes how the industry earns money. It does not tell you whether any one company is executing well inside it, and the dispersion between vendors in the same quarter can be very wide. Two companies with the same vertical mix and similar rates can report opposite margin trends purely on delivery discipline and how they staffed a handful of large programmes.
Sector work is for framing: it tells you which questions matter, which disclosures to open, and what a number means when you find it. The company-specific work — the client list, the contract book, the delivery record, the balance sheet — still has to be done one name at a time, and nothing on this page is a view on any particular one.
Key points
Revenue ≈ billable headcount × utilisation × billable hours × realised rate per hour
Example — A vendor signs a fixed-price contract to rebuild a client's claims platform for a quoted fee. Halfway through, the client asks for two extra integrations. If they are captured in a change order, the fee rises and margin holds. If the delivery team absorbs them to keep the relationship warm, the same revenue now takes more engineer-months — and the whole overrun lands on operating margin, in a quarter where revenue looked perfectly fine.
Pro tip — Build the habit of reading two numbers together: constant-currency revenue growth and the total contract value of deals won. Growth tells you what already happened; deal wins tell you what is coming. When those two diverge for more than a couple of quarters, that gap is usually the most useful thing in the results.
Warning — A quarter that looks strong purely because the rupee weakened is not a strong quarter. The currency translation flatters revenue and margin without a single additional hour being sold, and it reverses just as mechanically when the rupee firms up. Always check the constant-currency line before concluding demand improved.
Frequently asked questions
What is constant-currency growth and why do IT companies report it?
Constant-currency growth restates this period's revenue using the previous period's exchange rates, so the currency move is removed and only the change in volume and pricing remains. Indian IT companies bill mostly in dollars, euros and pounds, so exchange-rate movement alone can swing reported growth in either direction. Constant currency is the number that tells you whether clients actually bought more.
Where do I find utilisation, attrition and deal wins for an IT company?
All three sit in the quarterly investor presentation or the accompanying fact sheet on the company's investor-relations page, not in the headline results table filed with the exchanges. Utilisation is usually given both including and excluding trainees — compare like with like across quarters. Attrition is normally quoted on a trailing-twelve-month basis, and deal wins are given as total contract value, sometimes split between new business and renewals.
What is total contract value (TCV) and how is it different from revenue?
TCV is the full value of a contract over its whole life, announced in the quarter the deal is signed. Revenue is the portion of that work actually delivered and recognised in a given quarter. A large TCV signed today converts into revenue gradually over the following years, which is why deal wins move ahead of reported revenue. The same TCV spread over seven years is a far smaller annual contribution than one spread over three.
Is fixed-price or time-and-materials work riskier for an IT company?
Fixed-price carries more risk for the vendor. The company quotes one price for a defined outcome, so any underestimate, delay or unbilled scope addition comes out of its own margin. Time-and-materials passes that risk to the client because every extra hour is billed. The trade-off is upside: fixed-price work lets a disciplined vendor keep the entire efficiency gain, which time-and-materials never does.
Why do Indian IT stocks often weaken when the rupee strengthens?
Because the invoices are in foreign currency and the salaries are in rupees. A stronger rupee converts the same dollar invoice into fewer rupees, so reported revenue and operating margin compress even though nothing changed in the underlying business. It is a translation effect on the profit and loss statement rather than a demand event, which is exactly why the constant-currency line exists.
What separates a structurally strong IT business from a commoditised one?
Three disclosed things, read as trends rather than snapshots. First, where revenue sits on the ladder — maintenance and staffing work is easier to underprice than transformation and engineering work. Second, client concentration: a business where a few clients carry a large share of revenue is more fragile than one with a broad base. Third, whether margin holds when utilisation and currency are both neutral, which is what genuine delivery discipline looks like.
Is mid-cap IT more volatile than large-cap IT, and why?
Mid-cap IT generally shows a wider range of outcomes because it is more concentrated — in a vertical, a platform or a small set of large clients. That concentration produces growth well above the industry average when the niche is in demand and well below it when the niche cools, and the loss of a single large client matters far more. Large-cap vendors have thousands of clients across many verticals, which dampens both the upside and the downside.