Contract Staffing in India, Done as Real Employment

Contract staffing is one of those phrases that means five different things depending on who is selling it to you. A Bengaluru agency means temp workers on its own payroll. A US recruiter means independent contractors on monthly invoices. A platform means freelancers. And what most founders actually want is a fourth thing entirely: a full time person, working only for them, without the founder carrying an Indian entity or an Indian payroll.

Here is the honest taxonomy. Once you can name the model you are actually buying, half the confusion in vendor calls disappears.

The first model is the one that gets US and UK companies into trouble, and the last two are the ones that get them out of it. A contractor who works fixed hours, uses your equipment, reports to your manager and has no other clients is not a contractor in the eyes of an Indian labour inspector. He is an employee you have not registered. We will get to what that costs in chapter two.

📇 Contract staffing vs contract to hire

Contract to hire, or C2H, deserves its own line because it is the model this page is really about. You take a person on for a defined period, usually 90 days, on someone else's payroll. If the person works out, you convert them to a permanent seat. If not, you part ways with a short notice period and no severance drama. The trial de-risks the hire. The conversion locks in the win.

In practice the person is full time from day one. The contract part is your commitment level, not their working pattern. That distinction matters when we get to misclassification, because Indian law looks at the working pattern, not the label on the agreement.

If you want the wider comparison of staffing structures and what each costs, we broke that down in our guide to IT staffing models. This article stays on the India specifics: the law, the cost math, the 90 day playbook and the compliance calendar that comes with it.

Not a lawyer's lecture. Just the four things that decide whether your contract staffing setup in India is clean or a liability with a delay on it.

🧾 The Contract Labour Act sets the licence

The Contract Labour (Regulation and Abolition) Act 1970, CLRA, governs classic temp staffing. Any establishment engaging 20 or more contract workers needs registration, and the staffing agency supplying them needs a licence. The principal employer, that is you or whoever the workers report into, stays on the hook for wages and welfare if the contractor defaults. CLRA is why serious staffing in India runs through licensed entities and not through a folder of freelance agreements.

🧾 The Labour Codes rewired the definitions

India consolidated 29 labour laws into four Codes, operational from 21 November 2025. Two changes matter for contract staffing. First, the Codes formally recognise fixed term employment: you can hire someone for a defined term with the same statutory benefits as a permanent employee, including gratuity on a pro rata basis. Second, the wage definition now forces Basic plus DA to be at least 50 percent of CTC, which mechanically raises PF and gratuity outflows for structures that used to pack pay into allowances.

⚠️ The misclassification test

Indian authorities apply a control test, not a label test. Fixed working hours. A single client. Your equipment, your email domain, your reporting lines, your sprint board. Tick those boxes and your contractor is an employee, whatever the agreement says. Reclassification means back dated PF with 12 percent annual interest under Section 7Q, damages of up to 25 percent under Section 14B, unpaid gratuity, and in the worst cases a permanent establishment question over your company's India revenue.

The practical exposure runs 25,000 to 40,000 dollars per misclassified head once you stack the arrears, interest and penalties. Multiply by a team of six contractors held for two years and the number stops being a rounding error.

🚧 Who carries the risk in each model

In temp staffing the agency carries the payroll risk but you keep principal employer duties. In staff augmentation the vendor carries everything but you lose control of the person. In a raw contractor setup you carry all of it. In an EOR backed C2H arrangement the employer of record carries statutory employment on its own Indian entity, which is the cleanest split available to a company with no entity here: you direct the work, the EOR owns the employment law.

One paragraph of positioning and then back to the mechanics. Versatile is an India native EOR: the people you hire sit on our own registered Indian entity, we run PF, ESI, TDS and gratuity in house across 28 states, and conversion from contract to permanent happens on paper we already hold. The rest of this article works whichever vendor you pick.

On paper, a contractor looks cheaper than an employee. No PF, no ESI, no gratuity, one clean invoice. In practice the comparison is rigged, because the contractor's invoice quietly includes the benefits they are not getting, and the risk you are silently carrying does not show up in any spreadsheet until it does.

Here is the real stack for a mid level engineer at 25 lakh INR CTC, roughly 30,000 dollars a year.

💰 The margin question nobody asks

Staffing agencies price as a markup on salary, anywhere from 15 to 40 percent, forever. The person's raise raises the vendor's fee. A flat fee EOR breaks that link: Versatile charges 149 dollars per employee per month, 129 dollars past 20 employees, first month free, no setup or exit fees. Ten people cost 1,490 dollars a month in fees. The same ten people at a 25 percent markup on a 30,000 dollar salary cost you 75,000 dollars a year in margin. Same people. Same work.

💸 FX is the invisible line item

Most companies wire salaries through their bank and lose 3 to 5 percent on the spread without ever seeing it as a fee. On a 100,000 dollar monthly India payroll that is up to 5,000 dollars a month, gone. Ask every vendor one question: which exchange rate do you settle at? The clean answer is the RBI reference rate with the spread at zero. Any other answer is a second margin.

For the fuller pricing comparison across providers, our breakdown of payroll outsourcing companies in India runs the numbers vendor by vendor. The short version: flat fees beat percentage fees the moment salaries are above entry level, and India engineering salaries are above entry level.

Here is the C2H sequence we run, laid out so you can hold any vendor to it. The timeline assumes a mid level role in engineering, data or design. Senior searches stretch the front end, not the back.

⏰ The two numbers that matter

Nine days to shortlist. Five days from signed offer to a fully onboarded employee. Every week a role sits open costs you roughly the weekly salary in lost output, so the front of the funnel is where staffing vendors earn or waste your money. Ask any vendor for their median days to shortlist and their median days to onboard, and ask for the last quarter's numbers, not the brochure's.

💰 What conversion costs

Our recruitment fee is 12 percent of annual CTC for junior and mid roles, 15 percent for senior, invoiced at day 90, not at offer. The day 90 trigger matters: if the hire does not survive the trial quarter, you do not pay a placement fee for a person you no longer employ. Vendors who invoice 100 percent at offer have no financial stake in the person still being there in month four.

🔁 What conversion changes for the person

Nothing disruptive, and that is the point. The employee already sits on a registered Indian entity with PF, ESI and TDS running. Conversion is a status change on existing paper: same UAN, so provident fund history is unbroken, same payroll rails, same manager. The person feels a promotion, not a re-hire. Compare that with converting a raw contractor, which is a first time registration that exposes the entire prior period to the misclassification questions from chapter two.

One honest caveat. C2H suits roles where you genuinely might not convert: first hires in a new function, roles with an unproven scope, markets you are testing. If you already know you want the person for years, skip the theatre and hire permanent from day one. The trial you do not need is three months of hedging you pay for in candidate trust.

Every one of these is a real pattern. None of them announces itself in the sales call. All of them are catchable with one blunt question asked early.

❌ The permanent contractor

A US startup keeps its first India engineer on a contractor invoice for three years because it worked fine so far. Then a funding round triggers diligence, and the acquirer's counsel finds an employee shaped liability with 36 months of back dated PF, 12 percent interest and a 25 percent damages exposure attached. The question that catches it: if this person is still here in month seven, what is the plan? Fine so far is not a structure.

❌ The 40 percent markup that compounds

An agency quotes a blended rate that looks reasonable in year one. Salaries rise 10 to 15 percent a year in Indian tech, the markup rides the raise, and by year three the vendor margin exceeds what a flat fee EOR would have cost for the whole team. The question: is your fee a percentage of salary or a flat amount, and what happens to it when I give this person a raise?

❌ The unlicensed supplier

A staffing firm supplies 25 workers without a CLRA licence. The principal employer, you, inherits the wage liability when the firm folds mid quarter. The question: show me your CLRA licence and your last two quarters of PF challans for the staff you supply.

❌ The ghost payroll

The vendor invoices you for CTC plus statutory but remits PF late or not at all. The employee discovers it when they check their UAN passbook, and their trust in you, not the vendor, takes the hit. PF and ESI are due by the 15th of the following month, TDS by the 7th. The question: give me read access to the monthly challans. A vendor who hesitates has a reason to.

❌ The time zone mirage

A team is sold as overlapping with US hours, then quietly works 9 to 6 IST with a two hour overlap and a scrum call at someone's midnight. Burnout follows attrition follows a restaffed project. The question: write the guaranteed overlap hours into the agreement, and ask the candidates, not the salesperson, what hours they actually intend to keep.

❌ The IP that never moved

Contractor agreements under Indian law do not automatically vest IP the way employment does. A three line assignment clause in a template invoice is not the same as an employment contract with confidentiality, assignment and non compete provisions enforceable in the employee's own jurisdiction. The question: who holds the signed IP assignment, and under which country's law would you enforce it?

The thread through all six: contract staffing fails on the boring operational details, never on the headline rate. The vendors worth keeping are the ones who answer these questions with documents instead of assurances.

If contract staff sit on a compliant Indian payroll, somebody is running this calendar every month. If nobody you can name is running it, it is not being run. That is the entire audit, one sentence long.

🧾 Why the 15th matters more than the 7th

TDS penalties are annoying. PF penalties are structural: the 12 percent interest is annual and automatic, the damages scale with delay, and EPFO's systems now flag defaults without a human inspector involved. A vendor who has ever been casual about the 15th will eventually be casual with your people's retirement money. This is also the simplest vendor test in the industry: ask for the last six months of PF challans for the team they run. Clean vendors send a folder within a day.

🚧 The state layer

Professional tax, Shops and Establishments registration, and leave rules all vary by state. A team split across Bengaluru, Pune and Gurgaon is a three state compliance surface, not one. This is where India native operations beat a global platform's India module: the state layer is exactly the part that generic playbooks flatten. We keep this current across 28 states so the variation is our problem, not yours.

The wider statutory picture, PF mechanics, ESI thresholds and what the Labour Codes changed, is covered in depth on our EOR services in India page, including the employer cost calculator most founders actually came for.

There are exactly three triggers, and the honest answer is that most companies hit the first one months before they act on it.

⏰ Trigger one: the six month mark

If a contractor has worked for you, and effectively only you, for six months, the control test from chapter two is already decided. Every additional month adds to the arrears that a reclassification would back date. Six months is the natural review point: convert, or genuinely re-scope the engagement to project based work with other clients in the mix.

💰 Trigger two: the retention wobble

Contractors get no PF, no gratuity, no health cover, no paid leave, and they know it. When a person you rely on starts interviewing, matching the salary is rarely the fix, because the gap is security, not cash. Employment on a real Indian entity, with a UAN accruing and ESI or group health in place, is what Indian candidates weigh against your competitors' offers. Conversion is a retention tool priced at roughly the statutory load you were already implicitly paying inside the invoice.

🚀 Trigger three: the team stops being an experiment

One contractor is a test. Four contractors on your core roadmap is a team, and teams need the boring machinery: appraisal cycles, leave policies, insurance, exits handled inside the 48 hour full and final window. That machinery only exists on an employment stack. The moment India headcount appears in your next year's plan, the experiment is over and the structure should catch up.

🤔 Entity or EOR at conversion time

Converting onto your own Indian entity means first incorporating one, which takes about six months and roughly 15,000 to 20,000 dollars a year to keep compliant. The break even against an EOR sits around 10 to 15 hires by pure cost, and closer to 20 to 30 once you price your own attention. Under that line, converting contractors onto an EOR's entity gets you every benefit of employment this quarter without owning a company in India. We wrote the full decision framework in EOR vs entity in India, including the crossover math.

Whichever side of that line you land on, the sequencing is the same: decide the structure first, then convert, then never let a keeper sit on an invoice past month six again.

Salary data is where India staffing conversations go vague, so here are the bands we actually see offers land in. These are annual CTC figures for full time staff in 2026, converted at roughly 83 INR to the dollar. Contractors invoice 10 to 20 percent above these numbers because they price in the benefits they are not receiving.

💰 Read the bands like a local

Two things make these numbers move. First, company brand: a funded US startup paying in the 60th percentile of these bands gets a better response rate than an unknown services firm paying the 80th, because candidates price stability and stock upside into the decision. Second, the Basic plus DA rule from the Labour Codes: since Basic must be at least half of CTC, two offers with identical CTC can differ meaningfully in take home once PF is computed. Good candidates now ask about salary structure, not just the headline.

📇 The city question

Bengaluru remains the deepest pool for product engineering and commands a 10 to 20 percent premium over the rest of the country. Pune and Hyderabad offer 85 to 90 percent of the talent depth at 80 to 90 percent of the price, with noticeably better retention on senior hires. Chennai is the quiet winner for data and QA. NCR suits fintech and anything needing proximity to enterprise clients. Fully remote widens the funnel by roughly a third and adds the multi state compliance surface from the calendar chapter.

Our honest default for a first India pod: hire remote first within India, anchor on one or two cities for optional office days, and let the talent decide the map. Insisting on a single city in 2026 is paying a premium to shrink your own shortlist.

The deeper dive on why India remains the default destination for this kind of team sits in our piece on outsourcing development to India, with the vendor landscape mapped in the software development outsourcing guide.

Every contract engagement ends. That is the point of the model. Yet almost nobody plans the ending at the start, and the endings are where the legal and relationship damage concentrates. Three exit paths exist, and each has its own mechanics.

🔁 Path one: conversion

The happy ending. The contract employee becomes a permanent one, either on your future India entity or by staying on the staffing partner's rolls under a permanent letter. The mechanics matter more than they look. Continuity of service should carry over, because gratuity eligibility builds from the original start date under a fixed term letter, and a break in service resets protections the employee has already earned. A clean conversion letter states the original joining date, carries the leave balance forward, and keeps the PF account, via UAN transfer, unbroken. Ask your provider how they handle each of those three before you sign, not after month five.

⏰ Path two: planned completion

The engagement runs its term and closes. Under the Labour Codes the discipline is specific: full and final settlement is due within 48 hours of the last working day, wages, leave encashment, and pro rata gratuity where the fixed term crosses the eligibility line. A staffing partner that runs settlements weekly, in batch, is structurally unable to meet that window. Ask to see a real F&F statement from a recent exit, with the dates visible. The document either exists or it does not.

⚠️ Path three: early termination

The uncomfortable one. Performance did not land, the project died, the budget moved. The notice period in the employment letter governs, typically 30 days for junior roles and 60 for senior, and the employer of record or staffing partner runs the process because they are the legal employer. What you should expect from a serious provider: a documented performance conversation trail if the exit is for cause, notice pay computed on the Labour Codes wage definition, and zero improvisation. What you should never do is instruct an abrupt cutoff of a contractor-style worker who has been doing employee shaped work for a year, because that is exactly the fact pattern that turns a quiet exit into a misclassification claim at $25,000 to $40,000 a head.

🧾 The handover checklist

IP assignment should already sit in the employment agreement from day one, signed at joining, not chased at exit. Device return, access revocation and repository handover want a written checklist owned by one named person on your side. The single most common gap: nobody revokes cloud console and code repository access on the last day, and the audit that finds it happens during your Series B diligence. Boring process, expensive omission.

None of this is a reason to avoid the model. It is a reason to pick a partner who treats endings as part of the service. The good ones volunteer their exit process unprompted, because they know the ending is the part you will remember.

🤔 Can I start with one person, or is there a minimum?

One person is fine, and it is how most engagements start. The economics of a flat monthly fee do not depend on volume, and the first hire is usually the audition for the next five. Minimum seat requirements are a vendor revenue policy, not an operational necessity, and we do not have one.

🤔 Who owns the IP a contract hire produces?

If the person is employed through an EOR, the employment contract carries assignment and confidentiality clauses under Indian law, with IP flowing through to you under the service agreement. That chain is enforceable in the employee's own jurisdiction, which is the property that matters. If the person is a raw contractor, you own what the signed agreement says you own, under whichever law the agreement chose, which for many template agreements is the wrong one.

🤔 What happens if I want to end the engagement early?

During a C2H trial, notice periods are short by design, typically 15 to 30 days, and the exit runs through the employing entity: notice, handover, and full and final settlement inside the 48 hour statutory window. You make one decision and write zero paperwork. What you should not do is ghost a contractor mid invoice cycle, which is both poor form and, if the person was employee shaped, the start of a labour complaint.

🤔 Can contract staff work my time zone?

Partially, and it should be negotiated per person, not promised by a salesperson. A four hour overlap with US Eastern is sustainable for most Indian engineers; a full US shift is not, whatever anyone claims. Write the guaranteed overlap window into the role brief, confirm it with the candidate directly in the interview loop, and treat any vendor guarantee of full US hours as the red flag it is.

🤔 How is this different from just using Deel or a global platform?

Global platforms run India as one country module among 150, usually through a local partner entity, with support routed through a ticket queue. An India native EOR runs its own entity, its own payroll team, and nothing else. The difference shows up in the state level edge cases, the speed of a notice period question at 11pm IST, and the FX line: platforms commonly add a spread on the transfer, we settle at the RBI reference rate with none. The comparison across providers is in our review of EOR services in India for 2026.

🤔 Can we interview and pick the people ourselves?

Yes, and you should. The model changes who signs the employment letter, not who chooses the human. You run the technical rounds, set the bar, and make the call; the staffing partner or employer of record handles sourcing if you want it, then employment, payroll and compliance once you say yes. Our own rhythm is a shortlist in 9 days and onboarding in 5 once you pick, and the candidates you reject never know the difference. The one thing to insist on: direct access to the people you are evaluating, no gatekeeping through account managers. If a provider resists that, they are selling you a bench, not a hire.

⭐ Here is the position, without the hedging. Use raw contractors for genuinely short engagements with a hard end date, and put an end date on the arrangement itself, not just the project. Use contract to hire when the role matters and the fit is unproven: 90 days on someone else's compliant payroll, convert at day 90 with the fee due only if the person stays. Put anyone you expect to keep past six months on proper Indian employment, on your entity if you are past 20 to 30 heads, on an EOR's entity if you are not.

Judge every vendor on four numbers: days to shortlist, days to onboard, the fee structure's shape over three years, and the PF challans they will or will not show you. The rate card is the least informative page in the deck.

And the part where I say what we do. I run Versatile, an India native EOR and staffing operation. We shortlist in 9 days, onboard in 5, employ your people on our own registered Indian entity at 149 dollars a month flat, convert C2H hires at 12 percent of CTC billed on day 90, and settle payroll at the RBI reference rate with zero FX spread. The first month is free, there are no setup or exit fees, and the statutory calendar from chapter six is our job, not yours. If contract staffing in India is on your roadmap this quarter, see how the EOR side works or use the form on this page and I will reply personally.