Cost guide
Freelance developer rates in India (2026): hourly, fixed price, retainer and dedicated
By Samuel Marndi · Updated
The short answer
For an Indian client in 2026, a freelance web developer charges roughly ₹500–₹2,500 an hour, a mobile app developer ₹600–₹2,800, a senior cloud or DevOps specialist ₹1,500–₹3,500, and applied AI and LLM work ₹2,500–₹5,000. The same people quote roughly two to three times those figures to overseas clients, which is why a rate quoted without a currency and a market tells you nothing.
But the hourly number is the least useful thing on this page. There are four ways to buy a developer's time, they carry the risk differently, and the one you choose changes the total far more than a few hundred rupees an hour does.
Four ways to buy the same time
This is the decision that determines whether you end up paying for outcomes or for hours. Both can be fair; only one of them aligns what the developer wants with what you want.
| Model | Good for | Where it goes wrong | Who carries the risk |
|---|---|---|---|
| Hourly | Open-ended work where nobody can scope it yet: debugging, audits, advice | Long builds — the meter rewards slowness and you pay for the learning curve | You |
| Fixed price per milestone | Anything describable: a website, an app, an integration | Scope that is still moving, where every change becomes a negotiation | The developer |
| Monthly retainer | A steady trickle of changes, plus someone who already knows your system | There is not really enough work, and you are paying for availability | Shared |
| Dedicated days or weeks | A big push with an unclear end: a migration, a rescue, a rebuild | Used as a substitute for scoping something that could have been scoped | Shared |
Rate bands by discipline, for an Indian client
These are published 2026 market bands, not my rate card — mine is on the pricing page. Read them as what the market charges, which is what you need in order to tell a fair quote from an opportunistic one.
| Discipline | Indian client, per hour | Overseas client, per hour |
|---|---|---|
| WordPress, basic front-end, junior work | ₹300 – ₹800 | ₹800 – ₹2,000 |
| Web developer, general | ₹500 – ₹2,500 | ₹1,500 – ₹4,000 |
| Mid-level full-stack (React, Node, APIs) | ₹800 – ₹2,000 | ₹2,500 – ₹5,000 |
| Mobile app developer | ₹600 – ₹2,800 | ₹1,800 – ₹4,500 |
| Senior cloud, DevOps, data | ₹1,500 – ₹3,500 | ₹4,000 – ₹8,000+ |
| AI / ML and applied LLM engineering | ₹2,500 – ₹5,000 | ₹6,000 – ₹12,000+ |
Why hourly is usually the wrong default
Hourly feels safe because it looks like you only pay for what you get. In practice it hands you three problems. It pays for the learning curve: the hours spent working out your system are billed to you at the same rate as the hours spent improving it. It penalises the fast: someone who solves in two hours what another takes ten to solve earns a fifth as much, which is exactly backwards. And it makes your invoice unpredictable, which is the thing you were trying to avoid.
Fixed price per milestone inverts all three. The developer now carries the estimate, so they have a reason to understand the problem before quoting and a reason to work efficiently afterwards. You get a number you can budget against, and a date you can hold.
Where hourly genuinely is right: diagnosis. When nobody knows yet why the site is slow or where the cloud bill is going, a fixed price is a guess dressed as a commitment. Buy a few hours of investigation, get a written finding, then buy the fix at a fixed price against it.
What a day rate means, and what it does not
A day rate is not eight hourly units. It is a block of uninterrupted attention, which is worth more than the same hours scattered across a fortnight, and it usually prices in the fact that a booked day cannot be sold to anyone else.
Expect a day rate to work out below eight times the hourly figure and above six times it. Below that, check what you are getting: a "day" that means four hours is a half-day with a day's name on it. And ask what happens if the day runs out mid-problem, because the answer separates a professional arrangement from a meter.
- Ask what a day is. Hours, and in which time zone — it matters on remote work.
- Ask what happens to unused time. A booked day that finishes early should roll over or be spent on something useful, not vanish.
- Ask about cancellation. A day booked and cancelled the night before cost someone a day they could have sold. 48 hours' notice is a fair line.
- Ask whether travel is inside or outside the day. For on-site work in Bengaluru this is the difference between six productive hours and eight.
Fixed price: the only version of it that works
A fixed price is only safe for both sides if three things are true, and it is the absence of these — not the price — that makes fixed-price projects end badly.
First, the scope is written down, including what is excluded. Second, the money is tied to milestones, each with a deliverable you can actually look at. Third, there is a stated change process: changes are normal and expected, and what matters is that they are priced and agreed rather than absorbed in silence until someone is resentful.
| Milestone | Share of the total | What you should have in your hands |
|---|---|---|
| Scope and design signed off | 20 – 30% | A written scope, the page or screen list, and the designs |
| Core build working | 25 – 30% | A staging link you can click through, on your own hosting |
| Feature complete | 25 – 30% | Everything in scope working, in your repository, reviewed against the list |
| Launch and handover | 20 – 25% | Live, every account in your name, documentation, and the code assigned to you in writing |
Retainers: what you should actually get for one
A retainer is the most commonly mis-sold thing in this trade, because "₹40,000 a month" can mean a guaranteed number of days or it can mean nothing at all. The question that settles it: what do I get if I use none of it, and what happens if I need more than it covers?
- Get the number of hours or days in writing. A retainer without a quantity is a subscription to goodwill.
- Agree what happens to unused time. Carry-over for one month is the common fair answer; "use it or lose it" every month is a reason to buy a smaller retainer.
- Agree the overflow rate before you need it, not during the month you blow through the allowance.
- Agree what counts. Is a twenty-minute phone call billed? Is thinking about your architecture in the shower? Say so now and nobody feels cheated later.
- Agree the notice period. One month either way is normal and keeps both sides honest.
| Retainer shape | Typical monthly | What it should include |
|---|---|---|
| Keep-it-alive | ₹8,000 – ₹25,000 | Updates, backups, uptime monitoring, security patches, small text and image changes |
| Steady improvement | ₹25,000 – ₹60,000 | The above plus a defined number of development hours a month, with a stated carry-over |
| Embedded capacity | ₹60,000 – ₹1,50,000 | Named days per month, a response-time commitment, and participation in your planning |
How a freelance rate compares with a salary
A ₹2,000 hourly rate reads as ₹32 lakh a year if you multiply it by a 2,000-hour working year, and that comparison is wrong in both directions. No freelancer bills 2,000 hours — a realistic figure is 55% to 70% of available time, with the rest going to sales, admin, invoicing and the gaps between projects. And a salary is not what an employee costs you either: statutory contributions, equipment, recruitment and management load sit on top of it.
The honest comparison is cost against utilisation, and it is worked through properly in freelancer, agency or a full-time hire. The short version: below roughly half-time, sustained, a freelancer is cheaper on every axis. Above it, a full-time hire starts to win on cost — and begins to lose on breadth, because one employee is one skill set and a project usually needs four.
Project prices, if that is what you actually came for
Rates are for buying time. If what you want is the price of a finished thing, those are set out properly elsewhere on this site, with itemised breakdowns rather than per-hour arithmetic:
- What a website costs in India — by type, with what inflates each quote
- What a mobile app costs in India — by complexity, including the year-one running bill
- What an AI chatbot or agent costs — with a working estimator and the monthly bill most quotes omit
- What the cloud costs in India — monthly bill bands and migration cost
- My own indicative pricing — ranges, not a rate card, with a written itemised quote after scoping
FAQ
Related questions
How much does a freelance web developer charge per hour in India?
₹500–₹2,500 an hour for an Indian client in 2026, with junior WordPress and basic front-end work at ₹300–₹800 and mid-level full-stack at ₹800–₹2,000. The same developers quote roughly two to three times those figures to overseas clients. Seniority moves the number more than the technology does.
What is a fair hourly rate for an AI developer in India?
₹2,500–₹5,000 an hour for an Indian client on applied AI and LLM work, and ₹6,000–₹12,000 or more for overseas clients. It is the steepest premium in the Indian market right now, because the supply of people who have actually shipped a working retrieval system is much smaller than the number who have built a demo.
Is it better to pay a developer hourly or a fixed price?
Fixed price per milestone for anything describable, hourly only for work nobody can scope yet — debugging, audits, investigation. Hourly pays for the learning curve, penalises the developer who is fast, and leaves your invoice unpredictable. The sensible hybrid is to buy a few hours of diagnosis, get a written finding, then buy the fix at a fixed price against it.
What should a monthly retainer for a developer include?
A quantity, in writing: a number of hours or named days, a response-time commitment, what carries over if you do not use it, and the rate for anything beyond it. A keep-it-alive retainer at ₹8,000–₹25,000 covers updates, backups, monitoring and small changes. A retainer with no stated quantity is a subscription to goodwill.
Why do Indian freelancers charge overseas clients more?
Because the rate tracks the client's market, not the developer's cost of living, and because overseas work carries real extra cost: time-zone overlap outside normal hours, currency conversion and payment-gateway fees, longer payment cycles, and the risk of chasing an invoice across a border. It is not opportunism; a domestic project at the overseas rate would not sell.
How many hours a month can a freelancer actually give me?
Plan on 100 to 130 billable hours a month from someone working full-time on client work, because 30% to 45% of any freelancer's time goes to sales, scoping, admin and invoicing. Anyone promising 180 billable hours a month, sustained, is either not doing their own admin or not telling you about the other clients.
Should I pay a developer a deposit?
Yes — 20% to 40% at the start, with the balance against delivered milestones. A freelancer committing a month to your project has no bench to absorb a client who disappears, and refusing any deposit tends to get you the people with nothing else booked. What you should not do is pay in full upfront, which removes every incentive that was protecting you.
Do freelance rates in India include GST?
Ask, because it changes the number by 18%. A freelancer registered for GST will usually quote excluding it and add it on the invoice; one below the registration threshold will not charge it at all. If you are a registered business the GST is input credit rather than cost, which sometimes makes the registered freelancer cheaper in real terms despite the larger invoice.