IT services and outsourcing business models

The sub-sector that runs on people, not products

Every other sub-sector in this guide sells a product, whether that product is a chip, a piece of software, or access to a network. IT services sells expertise and time. That single difference explains almost everything about how the sub-sector's economics, growth strategy, and valuation differ from the rest of TMT, and it is the reason interviewers expect a genuinely different framework when a case study or comp set lands on an IT services company rather than a software one.

The four business lines inside "IT services"

The label covers several distinct models that share a labor-driven cost structure but differ in how that labor gets deployed and priced.

Staff augmentation places contract technology workers inside a client's own teams, typically billed at an hourly or daily rate, with the client directing the work. It is the simplest and most commoditized model in the group, closest to a staffing agency, and margins are correspondingly the thinnest, since the client can relatively easily switch providers or bring the work in-house.

Systems integration involves a company designing and implementing a complex technology project for a client, commonly deploying and customizing a major enterprise software platform, migrating a client's infrastructure, or building custom software to a client's specification. This work is typically priced either on a time-and-materials basis or as a fixed-fee project, and it carries more expertise and more execution risk than staff augmentation, since a systems integrator is accountable for a working outcome, not just for supplying bodies.

Managed services means a company takes ongoing operational responsibility for running a piece of a client's technology infrastructure (networks, servers, cybersecurity monitoring, help desk support) under a multi-year contract, typically billed as a recurring fee. This is the closest IT services gets to a subscription-like revenue model, and companies that can grow their managed services mix relative to lower-margin staff augmentation and project work tend to earn a valuation premium within the sub-sector, precisely because that revenue is more visible and more recurring.

Business process outsourcing (BPO) goes a step further, with a company running an entire business function on a client's behalf, commonly customer support, back-office processing, or other functions that are important to the client but not core to its competitive differentiation. BPO economics resemble managed services in structure (multi-year contracts, recurring fees) but often carry even thinner margins, since the client is usually outsourcing the function specifically to reduce cost, which puts continuous pricing pressure on the provider.

Contract structure matters within each of these lines almost as much as which line the revenue falls into. A managed services or BPO contract that renews automatically unless the client actively cancels behaves very differently, from a revenue-visibility standpoint, than one that must be competitively re-bid at the end of every term, even if both are nominally "multi-year, recurring" arrangements. A banker digging into an IT services company's revenue quality will typically ask not just what share of revenue is recurring, but how contracts actually get renewed, and how concentrated that revenue is among a small number of large clients, since losing one large re-bid can move the growth rate of an otherwise stable-looking company far more than a comparable loss would move a software company with a broader, more diversified customer base.

Why margins are structurally thin

The central economic fact of IT services is that the primary cost is compensation, and that cost scales roughly linearly with revenue: to generate more revenue, a company generally needs to bill more hours, which generally requires hiring more people, unlike a software company where a large upfront investment in the product can then be sold to many more customers at very little additional marginal cost. This is the mirror image of the software economics covered in how software companies are valued: where software margins expand as the business scales because the cost base grows much more slowly than revenue, IT services margins stay comparatively flat as the business scales because the cost base grows in close proportion to revenue.

Utilization, the percentage of a billable employee's available time that is actually billed to a client, is the single most important internal lever an IT services company has to improve margin without raising prices. An employee sitting on the "bench," meaning available but not currently staffed on a billable engagement, is a pure cost with no offsetting revenue, so a company's ability to keep utilization high, matching supply of skilled labor to client demand efficiently, is a genuine operational skill that separates well-run IT services companies from poorly-run ones. Revenue per employee is the metric that captures this efficiency at the company level, and it is one of the first things a banker benchmarks when comparing IT services peers, since two companies with identical revenue can have very different underlying profitability depending on how efficiently they deploy their people.

Growth through consolidation

Organic growth in IT services is capped by how fast a company can recruit, train, and deploy qualified people, which is a slower and more constrained process than the demand-generation-driven growth available to a software company. Because of that cap, acquisition-led consolidation is an unusually common growth strategy in this sub-sector: a larger IT services company acquires a smaller one primarily to add headcount, capabilities, or a specific client relationship faster than it could build organically, and a fragmented category (many small, regional, or specialty providers, none with dominant scale) creates a long runway for this kind of roll-up strategy. This pattern connects directly to the strategic tuck-in and consolidation logic covered in TMT deal structures, and it is one of the more reliable sources of sustained M&A deal flow within TMT precisely because the underlying fragmentation does not resolve itself quickly.

Delivery location and cost arbitrage

A structural feature of the IT services business model worth knowing is the use of offshore and nearshore delivery centers, staffing a meaningful share of client work from lower-cost labor markets rather than exclusively from the client's home country. Because compensation is the dominant cost in this sub-sector, the geographic mix of a company's workforce is a genuine, durable margin lever: a company with a larger share of its delivery staff based in lower-cost markets can generally offer more competitive pricing to clients while still protecting its own margin, relative to a competitor staffed entirely from higher-cost markets. This is part of why some of the largest players in the sub-sector built global delivery networks spanning many countries, treating workforce location as a deliberate strategic choice rather than an incidental detail.

This same labor-driven structure creates a risk that has no real equivalent in software or semiconductors: key-person and attrition risk at scale. Because the product being sold is essentially the collective expertise of the workforce, a company that cannot retain and continuously develop its skilled employees, particularly in specialized, higher-value service lines, will struggle to maintain both its utilization and its pricing power. Bankers and investors evaluating an IT services company will typically ask about employee attrition trends and the company's ability to keep its most experienced people, because a company bleeding senior talent is at real risk of a slow, hard-to-reverse decline in the quality of its client delivery, which eventually shows up in client renewal rates and pricing.

How bankers actually value the group

IT services companies are valued primarily on EV/EBITDA, reflecting the fact that the sub-sector generates real, current accounting profit rather than the growth-stage reinvestment story that pushes software toward revenue multiples. Within that EV/EBITDA framework, the specific multiple a company earns depends heavily on its revenue mix across the four business lines above: a company with a larger share of managed services and BPO revenue, more recurring and contracted, typically earns a premium multiple relative to a peer more heavily weighted toward staff augmentation and one-off systems integration projects, even at similar headline margins, because the market rewards revenue visibility. Bookings, the value of new contracts signed in a period, and the remaining contract backlog are also closely watched, since they give a forward-looking read on revenue that a trailing margin number alone cannot provide.

How this contrasts with the rest of TMT

IT services sits in an interesting position on the TMT sub-sector map: it shares software's relatively low capital intensity (no factories, no network infrastructure to build) but shares almost none of software's margin structure or growth-through-reinvestment logic. It is also worth contrasting against telecom and media, covered in media and telecom economics for bankers, which sit at the opposite end of the capital intensity spectrum entirely. Interviewers sometimes use IT services specifically to test whether a candidate has absorbed the broader lesson of this guide: that valuation approach follows business economics, not sector labels, since "technology company" tells you almost nothing about whether EV/EBITDA or a revenue multiple is the right lens until you know whether the company is selling a scalable product or billing out people's time.

Practice question

Two IT services companies have the same revenue and the same EBITDA margin. What would make you value one higher than the other?

I'd want to know the mix of business lines behind that headline margin, because not all IT services revenue is equally valuable even at the same margin. A company with more of its revenue coming from managed services or business process outsourcing under multi-year contracts has more visible, more recurring revenue than a company weighted more heavily toward staff augmentation or one-off systems integration projects, which are easier for a client to cancel, bring in-house, or move to a competitor. I'd also look at utilization rates and revenue per employee, since a company running its workforce more efficiently is more likely to sustain that margin going forward rather than needing pricing increases or aggressive cost cuts to defend it. Bookings and backlog would matter too. A company with a strong, growing backlog of signed contracts gives me more confidence in near-term revenue than one relying on a thinner pipeline of new project wins each quarter. So even with identical trailing revenue and margin, I'd generally pay a premium for the company with the more recurring, better-visibility revenue mix and the more efficiently utilized workforce, because that company's current profitability is more likely to persist.

What the interviewer is listening for: Whether you know to look past a matching headline margin into the underlying revenue mix and operating efficiency, and whether you can name utilization and revenue visibility as the specific levers that justify a valuation gap between two superficially similar companies.