.png)
How to Set Milestones for Per-Hour Hired Developers in India
- Saransh Garg
- 3 days ago
- 10 min read
Across the hourly billing contracts we have structured for HR teams over the last decade, unstructured per hour arrangements run over budget by roughly 20 to 25 percent by the third month. It is rarely because the developer is slow. It happens because there is no checkpoint tied to a deliverable. That is why we insist every client sets milestones for per hour hired developers in India before the first invoice is raised, not after the first dispute. This article walks through how to do it properly, including the labour law behind it, current market rates, and one client scenario where skipping this step almost ended a partnership.
Why Hourly Developer Contracts in India Fail Without Clear Checkpoints
Hourly billing sounds simple. You pay for hours worked, nothing more. In practice, we have watched this model break down repeatedly for HR managers running distributed teams out of Bengaluru, Pune, and Hyderabad. A developer logs 45 hours in a sprint. The HR manager approves the invoice because the contract does not specify what those 45 hours were meant to produce. A few sprints later, the client asks where the promised module is, and there is no paper trail linking hours to output.
This is not a talent problem. India's tech hubs produce some of the most cost efficient engineering hours globally, which is exactly why HR teams choose hourly hiring over full time hiring in the first place. It is a governance problem. Clients who set milestone checkpoints every 10 to 15 working days report almost no billing disputes past the second review. Clients who skip this step average one serious dispute per quarter, usually right when trust in the working relationship should be building instead.
HR managers who have only ever handled full time payroll often assume hourly contracts run themselves once signed. They do not. Hourly hiring without milestones shifts the entire tracking burden onto whoever reviews the invoice, and that person is rarely technical enough to judge whether 45 hours of backend work was reasonable for the task at hand. This is one reason more HR teams are now setting milestones for per hour hired developers in India as a standing part of the onboarding checklist, rather than an afterthought added once a dispute has already happened.
Which Indian Cities Have the Right Talent for Milestone Based Hourly Work
Not every developer adapts well to milestone gated hourly billing, and the city you hire from matters more than most HR teams expect.
Pune and Bengaluru have the deepest bench of engineers already comfortable with Agile, sprint driven product teams, meaning they are used to being judged against a two week deliverable rather than a monthly appraisal. Many come from Indian product companies or global capability centers where sprint demos and story points are routine. If your milestone plan will follow a sprint cadence, this is where we source first.
Hyderabad has strong depth for enterprise and platform focused hourly work, where milestones tend to follow project phases such as requirements sign off, build, and user acceptance testing, rather than sprints. Chennai and the Delhi NCR region round out the talent pool for full stack and QA heavy hourly roles, and both cities have seen a steady rise in outsourcing demand from mid size global teams looking to scale project work without committing to full time headcount.
What Indian engineers bring to this model consistently is strong written documentation, comfort with asynchronous updates given the overlap with European mornings and US East Coast hours, and a long standing habit of writing status reports for clients who are not in the room, a carryover from years of onsite offshore delivery models.
What they often lack is disciplined, task linked time logging rather than a general weekly hours total. Developers coming from salaried full time roles are used to logging hours for internal appraisal, not client facing billing accuracy. Before recommending anyone for a longer hourly contract, we run a paid two week trial sprint with a real milestone and a real timesheet review, since it is the fastest way to catch anyone who under documents or pads hours.
Contract Hiring vs Full Time Hiring: What HR Teams Should Understand Before Setting Milestones
Contract hiring and full time hiring solve different problems, and confusing the two is where most milestone plans go wrong.
Full time hiring brings a developer onto fixed monthly pay, statutory benefits, and long term retention expectations. Milestones here typically feed into performance reviews rather than payment decisions, since salary is not tied to deliverable completion.
Contract hiring, especially hourly contract hiring, ties payment directly to logged time, which is exactly why milestone structure matters so much more. Without it, HR has no reliable way to judge whether the hours billed reflect the deliverable expected, since there is no fixed monthly output to compare against. Many HR teams we work with run a hybrid model, hiring core team members full time and scaling with hourly contract developers for defined, milestone bound project work, which keeps overhead flexible while protecting the core roadmap.
How to Set Milestones for Per Hour Hired Developers in India: The Legal Framework
This is the part HR managers skip most often, and it is the one that causes the most damage later.
Per hour developer contracts in India, whether run directly or through an Employer of Record, sit at the intersection of the Payment of Wages Act 1936, now largely folded into the Code on Wages 2019, the Contract Labour Regulation and Abolition Act 1970, and the relevant state Shops and Establishments Act. None of these laws mention the word milestone, but together they form the compliance layer that any milestone plan needs to sit on top of.
The Payment of Wages Act governs when payment must be released once work is completed, and it does not allow indefinite withholding of pay for hours already worked, even if a milestone was not met. This is the most common HR mistake we see, writing a milestone clause that says no payment until sign off, which is not enforceable against wages already legally due. The correct approach separates two things, hours worked, which must be paid within statutory timelines, and a milestone linked holdback or bonus, which can fairly be tied to deliverable quality.
The Contract Labour Act becomes relevant the moment developers are routed through a staffing partner rather than hired as direct payroll employees, since it requires proper vendor licensing and clean documentation of the working relationship. Companies without a registered India entity usually need an Employer of Record structure here rather than trying to manage contract labour compliance independently, and this is one of the areas where getting milestones for per hour hired developers in India wrong can turn into a legal exposure rather than just a billing headache.
A Ready to Use Milestone Framework for Hourly Developer Contracts
This is the framework HR clients screenshot and hand directly to finance. It works for one developer or a fifteen person hourly pod, and it is built directly around setting milestones for per hour hired developers in India rather than a generic project management template borrowed from full time hiring.
Phase | Typical Duration | Hours Allocation | Required Deliverable | Payment Release |
Onboarding and discovery | 3 to 5 working days | 5 to 8 percent | Environment access, task breakdown, codebase walkthrough notes | Full hours paid, no holdback |
First sprint or phase | 10 to 15 working days | 20 to 25 percent | Working demo of agreed feature set, hours logged against specific tasks | Full hours paid, 10 percent quality holdback released on sign off |
Mid project review | One checkpoint around day 20 to 30 | 25 to 30 percent | Code review, updated documentation, burn down against estimate | Full hours paid, holdback released after review call |
Final phase | 15 to 20 working days | 20 to 25 percent | Feature complete deliverable, handover documentation | Full hours paid, final holdback released on acceptance |
Closure and handover | 2 to 3 working days | 5 to 10 percent | Knowledge transfer session, access removal | Full hours paid |
Wages for hours already worked are never withheld, since that would breach Indian wage law. A modest holdback, typically 8 to 12 percent, tied to milestone quality gives HR teams real leverage without legal exposure. Every milestone needs a named deliverable rather than a date alone. Two weeks of work is not a milestone. A working authentication module with a test coverage report is.
Our Hiring Process and a Client Story
Our standard timeline for setting up milestone based hourly hiring runs about 12 to 18 working days, covering role scoping and assessment design, shortlisting and technical interviews, contract and EOR paperwork, and a short onboarding sprint before hours start counting toward the first milestone. At AnjuSmriti Global, every technical assessment mirrors the client's actual first milestone rather than using a generic coding test, so candidates are scored on both code quality and how accurately they log hours against specific tasks.
One case from our mandate history involved a mid sized European fintech client with around 60 employees, who came to us after hiring three backend developers hourly through a different vendor with no milestone structure at all. Four months in, their finance team flagged a 140 hour gap between invoiced time and expected scope, with no documentation to dispute it. The client was ready to terminate all three contracts.
We rebuilt the engagement around the framework above, re baselined the current sprint as the first milestone, and required deliverable linked time logs going forward. Disputed hours dropped to zero over the following two quarters, and the client extended two of the three contracts by another year. That mandate is part of why the AnjuSmriti team now treats milestone planning as a mandatory step for every hourly contract we place, not an optional add on requested by cautious clients.
What Per Hour Developers in India Actually Cost
Current INR hourly rates across our network, before Employer of Record or agency fees are added, break down as follows.
Mid level developer, 3 to 5 years experience, typically bills at 900 to 1,400 rupees per hour. Senior developer, 6 to 9 years experience, typically bills at 1,600 to 2,600 rupees per hour. Lead or architect level talent with 10 or more years of experience typically bills at 3,200 to 4,800 rupees per hour.
Equivalent roles in the US and Western Europe bill at 35 to 55 dollars per hour for mid level talent, 60 to 90 dollars for senior talent, and 110 to 160 dollars for lead level talent. Even after adding statutory employer contributions, EOR fees, and agency costs, India based hourly developers usually land at 55 to 65 percent of destination market cost, not a vague percentage claim.
This is also where the contract versus full time question resurfaces for most HR budgets. Full time hiring carries fixed monthly cost regardless of workload, along with notice period and severance exposure. Contract hiring on an hourly basis lets budgets flex with actual project volume, but only stays predictable if milestones are governing the hours billed. Most HR clients reinvest the savings from milestone governed hourly hiring into a second reviewer, often a part time technical QA resource, since the framework only works as well as the person verifying the deliverable against the invoice.
What Is Changing in Hourly Tech Hiring Right Now
Hourly hiring in India is shifting fast. AI assisted coding tools are compressing delivery timelines, which means milestone scopes need re calibrating more often than they used to, since a task that took forty hours a couple of years ago may realistically take twenty five now. Cloud and platform engineering skills are converging, with developers expected to handle deployment and infrastructure basics alongside application code, which changes what a fair milestone deliverable looks like for backend roles.
Outsourcing patterns are shifting too. More HR teams are moving away from large, loosely managed offshore vendor pools and toward smaller, milestone governed hourly pods that sit closer to an in house extension of the team than a traditional outsourcing arrangement. We are also seeing a clear workforce shift toward fractional and hourly arrangements even for senior talent, as companies build leaner core teams and scale project work through contract hiring rather than expanding full time headcount.
In the mandates we are running right now, nearly every new HR led hourly engagement asks for a milestone clause built into the contract from day one, not added later. Getting milestones for per hour hired developers in India right early is quickly becoming standard practice, not an optional add on, for any HR team managing distributed hourly talent.
If your team is ready to structure an hourly engagement properly, start here.
Interesting Reads:
FAQs
1.Can HR teams withhold payment until a milestone is approved?
No. Indian wage law requires payment for hours already worked within statutory timelines, regardless of milestone status. What is legally sound is a small holdback, typically 8 to 12 percent, released after milestone approval, paid on top of base wages rather than deducted from them.
2.How do we verify hours actually match the milestone deliverable?
Tie every logged hour to a specific task or ticket ID in your project tool, reviewed at each checkpoint rather than only at invoice time. HR teams without a technical reviewer should pair with a part time QA lead to check deliverables against billed hours before approving payment.
3.Do we need a registered India entity to run milestone based hourly hiring?
No. An Employer of Record becomes the legal employer for compliance purposes, handling wage law and statutory contributions, while your HR team manages the milestone review process. This is the standard route for companies without a local India entity.
4.What happens if hours are logged accurately but a milestone is missed?
The hours must still be paid in full. What changes is the holdback release and, depending on contract terms, whether the engagement continues. A two strike structure, review call after the first miss and exit option after a second, works well in practice.
5.How do time zones affect milestone review calls with India based teams?
India sits several hours ahead of Europe and roughly half a day ahead of the US depending on coast, so most HR clients schedule reviews in the late afternoon IST, which lands as morning in Europe and early morning on the US East Coast.
6.What documentation should developers submit at each milestone?
At minimum, a task linked time log, a short written summary of completed work, and any code review or QA sign off relevant to that phase. A brief recorded demo for technical milestones also helps non technical HR reviewers assess progress quickly.
7.How does IP ownership work with milestone based hourly contracts?
IP assignment should sit in the base contract as a standing clause covering all billed hours, rather than transferring milestone by milestone. Tying IP transfer to milestone completion creates ambiguity over unfinished work if the contract ends mid phase.
8.Is contract hourly hiring cheaper than full time hiring for Indian developers?
Usually yes on total cost, since it avoids benefits, notice period, and severance exposure tied to full time hiring, though hourly hiring needs tighter milestone governance to stay cost predictable. Full time hiring still suits long term core roles better than short project scopes.
Comments