Every IT services contract answers one quiet question before it answers anything else: if the work takes longer, costs more or delivers less than anyone expected, who pays? Time and Material, Fixed Price and Managed Services are three different answers to that question. Once you see them as risk-allocation tools rather than billing formats, most of the confusion around them disappears.

Time and Material: the client buys effort

Under Time and Material (T&M), the client pays for the hours or days people actually work, at agreed rates per role, plus any approved expenses. A senior developer might be billed at one rate, a tester at another, a project manager at a third. Indian IT firms often quote a blended rate per person-month for offshore work and a higher one for onsite staff.

The vendor’s promise here is about people and effort, not about the final outcome. If the work takes 30% longer, the client is billed 30% more. That makes T&M the natural fit when requirements are genuinely unclear, when the client wants to change direction often, or when the engagement is really staff augmentation where the client’s own managers direct the work.

For the vendor, T&M margins are predictable. If a role is billed at ₹2,500 an hour and costs the company ₹1,600 an hour in salary, benefits and overheads, the gross margin is 36% on every hour billed, whether the project runs long or short. The real commercial risks are utilisation (people sitting on the bench are not billing) and rate pressure at renewal time.

Clients usually push back on open-ended T&M with a few controls: a not-to-exceed cap, monthly timesheet approval, rate cards locked for a period, and sometimes a requirement that named key people stay on the project.

Fixed Price: the client buys a defined result

In a Fixed Price (FP) contract, the vendor commits to delivering a defined scope for an agreed amount, typically paid against milestones such as design sign-off, user acceptance testing and go-live. The client gets budget certainty. The vendor takes on the estimation risk.

A worked example shows why that risk matters. Suppose a team of five is estimated to need six months, at about 160 billable hours a month each. That is 4,800 hours. At ₹2,500 an hour, the equivalent T&M value is ₹1.2 crore. Knowing that estimates are rarely perfect, the vendor adds a 20% contingency and quotes a fixed ₹1.44 crore.

Actual effortHoursCost at ₹1,600/hrMargin on ₹1.44 crore
As estimated4,800₹76.8 lakhabout 47%
30% overrun6,240₹99.84 lakhabout 31%
60% overrun7,680₹1.23 croreabout 15%

If the estimate holds, Fixed Price is more profitable than T&M. If it slips badly, the vendor eats the overrun while the client still pays exactly ₹1.44 crore. A sufficiently bad slip turns the project into a loss. This is why delivery leaders care so much about how sales describes scope: the wording of the scope document is the only thing standing between an overrun and the vendor’s margin.

Fixed Price works well when requirements are stable and well understood, the technology is familiar to the vendor, and the client can make decisions quickly. It works badly for exploratory work, for projects that depend heavily on third parties the vendor does not control, and for clients who expect to keep adding “small” requests without a change request.

Managed Services: the client buys an outcome over time

Managed Services shift the conversation from projects to ongoing operations. The vendor takes responsibility for running something, such as application support, infrastructure monitoring, a service desk or cloud operations, against service levels. Pricing is usually a recurring monthly or annual fee, often tied to volume units: number of servers, users, tickets or applications supported, sometimes with bands so the fee changes only when volume crosses a threshold.

The contract is defined by service level agreements (SLAs): response and resolution times by ticket priority, system availability targets, and similar measures. Missing them typically triggers service credits, which are reductions in the fee. Some contracts also include bonuses or gain-share for exceeding targets or reducing ticket volumes.

Here the vendor carries operational risk. If ticket volumes rise sharply but stay inside the agreed band, the vendor absorbs the extra effort. The upside is that a well-run managed service gets cheaper to deliver over time, through automation, knowledge bases and fewer repeat incidents, while the fee stays the same. That productivity gain is where much of the margin comes from, and clients increasingly ask for year-on-year price reductions to share it.

Comparing the three side by side

Time and MaterialFixed PriceManaged Services
Client pays forEffort spentDefined deliverablesService at agreed levels
Main risk withClient (cost)Vendor (effort)Vendor (operations)
Best whenScope is fluidScope is stableWork is ongoing and repeatable
Key documentRate card, timesheetsDetailed scope and acceptance criteriaSLAs and volume bands
Typical frictionCost overruns, billing disputesScope creep, change requestsSLA disputes, transition pain

Hybrids are the norm, not the exception

Real contracts rarely pick one model cleanly. Common combinations include:

  • T&M discovery, then Fixed Price build. A short paid discovery phase clarifies requirements, after which the vendor can quote a fixed price with far less guesswork.
  • Capped T&M. Billing is by effort, but the total cannot exceed a ceiling without fresh approval. The vendor carries risk above the cap.
  • Fixed Price per sprint or per release. Common in agile work, where each increment is priced but overall scope remains flexible.
  • Build plus run. A Fixed Price implementation followed by a Managed Services contract to support what was built.

What this means for the person selling

A salesperson who pushes for Fixed Price because the client prefers it, without checking whether requirements are stable, is effectively signing the delivery team up for unpriced risk. Equally, insisting on T&M for a well-defined project can lose the deal to a competitor willing to commit. The useful skill is matching the model to how much is actually known about the work, and pricing the uncertainty honestly. Contingency is not padding; it is the price of the risk the vendor agreed to carry.

Two questions settle most choices. How confident are both parties about the scope today? And who is better placed to control the factors that will change the effort? Whoever can control the risk is usually the one who should hold it, and the pricing model should say so.

Written by the RP Strativa Team. Figures in the examples are illustrative.

Leave a Reply

Trending