The permanent-versus-contract question is usually argued on cost, which is the least interesting axis. The real variables are time, certainty and reversibility.
Time: a permanent hire in Indian IT takes 60–90 days from requisition to joining — if the offer isn't dropped for a counter. A contractor from a staffing partner with a live bench lands in one to two weeks. If the work starts this sprint, the math is already done.
Not either-or. Both, deliberately.
Certainty: contract staffing shines exactly when scope is uncertain. A migration that might take four months or nine; a product bet that might be killed at the next board meeting. Permanent headcount turns scope uncertainty into severance conversations. Contracts absorb it by design.
Reversibility: the underrated dimension. A wrong permanent hire costs a year — probation, improvement plans, re-hiring. A wrong contractor costs a replacement notice to the vendor, who bears the guarantee. When a role is new and its shape unclear, the reversible option lets you learn the role before you buy it.
When permanent wins: institutional knowledge you want compounding for years, roles central to your product's identity, and positions where team continuity is the value. Staff those permanently — ideally after a contract-to-hire trial has de-risked the choice.
The mature model most of our clients converge on: a permanent core that owns architecture and product direction, with a contract layer that flexes with delivery load. Not either-or. Both, deliberately.