India: Contractor Rate Savings and the Cost of Coordination
The value case for a contractor in India is usually built on one line: the rate here versus the rate there, multiplied by volume. The line is correct and incomplete — it is missing the other half of the equation, the half that sits on your side.
That other half is the requirements owner: the person who frames the task, answers questions, accepts the result, and resolves edge cases. Their time does not appear in the contractor's rate, but it is part of the cost of the work, and it is what determines whether the rate difference actually pays off.
Rate savings from a contractor materialize only when you have your own requirements owner working in the same rhythm as the contractor. Measurements of distributed software development show that tasks requiring cross-site coordination take several times longer than same-site tasks. That delay is not a property of the contractor — it is a property of the setup, and it can be priced in advance.
What Makes Up Coordination Cost
Break it down into components, each of which is paid for with your time, not the contractor's rate.
Task framing. A requirement that takes five minutes to explain to a colleague in the next room has to be written down and made unambiguous for an external team. That is not bureaucracy — it is the only way to transfer context the other side does not have.
Waiting for a reply. A time zone difference turns a clarifying question into half a day lost, and a chain of two clarifications into a full day lost. The effect compounds on every ambiguity in the brief.
Acceptance and the rework cycle. Each round of revisions costs one waiting cycle. Three rounds on a task mean three calendar days, regardless of how much actual effort the fix takes.
Resolving edge cases. Situations the brief does not cover require a decision from you. If you are unavailable, the contractor will decide on their own, and the decision will be reasonable from their point of view.
| Component | Who pays | What reduces it |
|---|---|---|
| Task framing | Your requirements owner | Brief templates and an explicit exclusions list |
| Waiting for a reply | Both sides, in calendar time | Working-hours overlap and a response-time rule |
| Rework cycles | Project calendar time | Acceptance criteria fixed in advance |
| Edge cases | Result quality | A decision rule for when the customer is unavailable |
The third column is the work that needs to happen before the collaboration starts. None of the four items requires budget; all four require the requirements owner's time.
How Much Cross-Site Coordination Costs, Measured
The size of the delay has been measured in a study that included sites in India.
Change requests handled by a single site took, on average, about 5 days; requests requiring cross-site coordination took 12.7 days — more than 2.5 times longer. The difference in delay duration between local and cross-site tasks is statistically significant.
I will name the limitation directly: this is one technology company, data from the late 1990s, and it concerns internal distributed development, not client-contractor outsourcing relationships. Communication tools have changed radically since then. What holds up is not the value of the multiplier but the structure of the delay: it does not arise in the communication channel, it arises in agreeing on what counts as done. I cover the same pattern in the piece on distributed-team readiness.
The Size of the Indian Outsourcing Market
Engineering and R&D services exports from India's technology sector are projected to reach $56 billion, up from $33 billion six years earlier; the country accounts for 27% of global technology exports. Global capability centres employ more than 1.9 million specialists and generate over $60 billion in value.
The limitation is material: it is not specified what exactly counts as R&D services or how capability centres are selected for the count. I am using it as an order of magnitude. The practical takeaway for choosing a collaboration model is separate: the growing share of global capability centres means mature customers are increasingly building their own on-site team instead of outsourcing — and doing so precisely because of coordination cost.
The Regulatory Framework Worth Knowing
The Code on Wages, 2019 was introduced in the lower house of parliament on 23 July 2019, passed by the lower house on 30 July, and by the upper house on 2 August 2019. This source does not reflect the current status of its bringing into force.
Here I limit myself to the fact that the bill passed parliament, and I state plainly that its enforcement status has not been verified against an official source. There is one practical consequence for the customer: the relationship model — outsourcing, staff augmentation, or an owned centre — carries different labour-regulation consequences, and it is chosen together with local counsel, not by the hourly rate.
When the Rate Savings Are Real
The first condition is the most expensive and the most often skipped. A requirements owner on your side takes up no less than a quarter of their working time under a steady flow of tasks; if that time is not allocated, it gets spent anyway — in interrupt mode, and with worse-quality briefs.
The fourth condition often draws an objection: "let them ask." Practice shows the opposite — when the customer is unavailable, the decision still gets made, just without them. An explicit rule ("if there is no response within 24 hours, the simplest option is chosen, and the decision is recorded in writing") delivers predictability instead of randomness.
Four Conditions Before Starting Work With a Contractor
Allocate time to a requirements owner
Not a part-time role. Under a steady flow of tasks, this is a significant share of working time.
Fix acceptance criteria before the start
Three to four points per task type. Every undefined point is one extra rework cycle.
Agree on working-hours overlap and a response deadline
Two to three hours of overlap and a response rule remove most of the calendar-time delay.
Define what happens without your response
A decision will be made either way. The rule makes it predictable.
If the value calculation has no line for your employee's time, it is not describing project economics — it is describing the difference between two price lists.
Frequently Asked Questions
Is it worth outsourcing development to a contractor in India?
It is worth it when four conditions are met on your side: dedicated time for a requirements owner, acceptance criteria fixed before the start, working-hours overlap with a response rule, and a decision rule for when you are unavailable. Without them, the rate difference is absorbed into calendar time: measurements of distributed development show that tasks with cross-site coordination take several times longer.
How do you reduce coordination cost?
Reduce ambiguity, not communication. A task-brief template with a mandatory list of what is out of scope, acceptance criteria of three to four points, and a response rule with an agreed deadline remove most of the clarification cycles. Adding more meetings has the opposite effect: it compensates for the absence of written criteria in the most expensive way possible.
Outsourcing or an owned centre in-country?
It depends on the volume and steadiness of the task flow. Outsourcing makes sense for variable load and a limited number of task types; under a steady flow, coordination cost becomes comparable to the rate difference, and mature customers move to owned centres — the growth in the number of such centres in India reflects this. The decision is made together with local counsel: the models differ in their labour-regulation consequences.
How applicable are measurements that are twenty years old?
The multiplier — no. The structure of the delay — yes. The study was conducted before modern communication tools existed and on internal distributed development, not on client-contractor relationships. But the delay did not arise in the communication channel, which has changed radically since then — it arose in agreeing on what counts as done, and that source of delay is not eliminated by tools.
The author's background includes work with contractors and distributed teams, including a partner model of purchasing contractor employees' time and work with contractors in China. A specific project with an Indian contractor is not described in the available documents, so this article is built on official and research sources and contains no internal numeric metrics. The list of four conditions and the breakdown of coordination cost is the author's generalisation from practice working with external providers, not a description of a specific case. This article is not legal advice.
- Herbsleb J. D., Mockus A., Finholt T. A., Grinter R. E. An Empirical Study of Global Software Development: Distance and Speed. ICSE, 2001. mockus.org
- NASSCOM. Industry overview of India's technology sector. nasscom.in
- PRS Legislative Research. The Code on Wages, 2019: bill track. prsindia.org