Time and materialsFixed priceBudgetPricingChoosing a vendor
Software developer day rates in 2026: sourced benchmarks, and what a day rate does not tell you
10 min read
In 2026, the public benchmarks for freelance software developer day rates sit in a wide band. In the UK, the median rate for software developer contracts advertised over the six months to 6 November 2026 was £525 a day, according to ITJobsWatch. In France, a full stack developer working directly with clients declared €409 a day on average on Free-Work at the same date. The gap between those two figures already tells you most of what you need to know: a day rate depends on the market, the experience, the specialism and the source. Above all, it says nothing about how many days the job will take, or who pays if that number grows.
This article gives sourced, dated benchmarks, explains what a day rate actually pays for, then shows why, for a business commissioning software, the real question is not the rate but the buying model: time and materials or fixed price.
What a day rate is, and what it pays for
A day rate is the price, before VAT or sales tax, of one working day. It is charged by an independent contractor, a consultancy, an IT services firm or an agency. In North America, contractors more often quote hourly; across Europe, the day rate is the usual unit. What counts as a "day" is not universal: seven, seven and a half or eight hours, defined in the contract or the statement of work, and worth checking.
For a freelancer, a day rate is not a daily salary. It has to cover:
- income tax and social contributions;
- holidays, sick days and public holidays, which nobody pays for;
- time spent finding work, keeping skills current and running the business;
- equipment, software licences, professional insurance and an accountant.
That is why a rate that looks high next to a salary often is not. A contractor who prices correctly is not more expensive than an employee; they simply carry costs that an employer would normally carry.
The 2026 benchmarks, with their sources
There is no official statistic for developer day rates. Published figures come from job boards, contractor platforms and recruitment firms, each with its own method. Here are primary sources you can check yourself, with their dates.
| Source | What is measured | Figure | Date |
|---|---|---|---|
| ITJobsWatch, UK software developer | Median day rate in advertised contract roles | £525 | Six months to 6 November 2026 |
| ITJobsWatch, UK software developer | 10th and 90th percentile of the same adverts | £363 / £625 | Six months to 6 November 2026 |
| Free-Work, France, full stack | Average rate declared by users, working directly | €409 | Checked on 6 November 2026 |
| Free-Work, France, full stack | Same average, through an intermediary | €430 | Checked on 6 November 2026 |
| Free-Work, France, full stack, 5 to 10 years' experience | Average declared, Paris region / other French cities | €539 / €423 | Checked on 6 November 2026 |
| Kicklox 2025 survey, France, "IT and software" | Average declared rate, online survey of tech freelancers | €629 | Survey run in June and July 2025 |
Read them with three precautions.
- They measure different things. ITJobsWatch reports rates in job adverts, which is what clients offer. Free-Work and Kicklox report what freelancers declare. Neither is a record of invoices.
- The populations differ. "Software developer", "full stack developer" and "IT and software" are not the same group. The broader the category, the more senior and specialist profiles it mixes in.
- An average is not a price. It blends junior and senior, capital city and regions, short and long assignments. A given profile can sit well away from it, as the UK spread between the 10th and 90th percentiles shows.
Be wary of pages quoting an "average developer rate" with no source and no date. Many recycle figures from earlier years, or from another country.
What moves a day rate
Experience. It is the first factor. Free-Work's French figures for full stack developers outside Paris climb from €312 a day at 3 to 4 years' experience to €423 at 5 to 10 years and €472 at 11 to 15 years. The same progression shows up in every market.
Specialism. Rare skills, such as architecture, security, data engineering or applied AI, command more than general web development.
Location. London pays more than the rest of the UK, Paris more than the French regions, and Western Europe more than Central and Eastern Europe. Remote work narrows the gaps without closing them.
The intermediary. A consultancy, platform or umbrella company adds its margin or fees. Free-Work shows a gap between direct and intermediated rates but does not say who keeps it.
Contract status. In the UK, whether a contract falls inside or outside the IR35 off-payroll rules changes the tax treatment, and so the rate a contractor needs. Other countries have their own rules on disguised employment. Either way, ask how the engagement is classified before comparing rates.
The assignment itself. Length, urgency, on-site presence and on-call duties: a long, predictable assignment is negotiated differently from a three-week emergency.
Freelancer, IT services firm, agency: you are not buying the same thing
Comparing day rates between a freelancer, a staffing consultancy and an agency usually means comparing different products.
| Supplier | What you buy | Who manages the work | What is included |
|---|---|---|---|
| Freelancer | One person's skills | You, usually | Development; the rest depends on the person |
| Staff augmentation firm | One or more profiles for a period | You, day to day | Days of work; replacement if the contract says so |
| Agency or studio, fixed price | A defined result | The supplier | Design, development, testing and deployment, as the contract states |
An experienced freelancer, well chosen and well directed, is often the most efficient answer to a precise need. The difficulty is not the freelancer; it is handing them a whole project when nobody in your company can act as project manager, product owner and technical lead. Our comparison of agency, freelancer and no-code helps you choose for your situation.
What a day rate does not tell you
A day rate answers one question: what does a day cost. For a business commissioning software, the important questions stay open.
The number of days. It decides the budget, and nobody knows it in advance. Two developers on the same rate can take very different times on the same feature. A low rate times many days costs more than a high rate times few.
What is included. Screen design, testing, deployment, documentation, project management: depending on the supplier, these are inside the rate, billed separately or left to you.
Management time. On time and materials, someone has to set priorities every week, answer questions and approve the work. That time comes out of your company, and it never appears on an invoice.
Overrun risk. If the estimate was optimistic, extra days are billed. This is the central point.
What comes after. Hosting, maintenance, new features, continuity if the person leaves: none of it shows in a day rate.
Time and materials or fixed price: where the risk sits
On time and materials (T&M), you buy time. The supplier commits to skills and availability, not to a result. The final budget is known at the end. If the project takes twice as long as planned, you pay twice as much.
On fixed price, you buy a defined result at an agreed price. Scope and amount are written into the contract before development starts. If the work takes longer than planned, the supplier's margin shrinks; your invoice does not grow.
| Criterion | Time and materials (day rate) | Fixed price |
|---|---|---|
| What you buy | Days of work | Defined software |
| Budget | Known at the end | Agreed before development |
| Overrun risk | Yours | The supplier's |
| Day-to-day direction | By you | By the supplier |
| Condition for success | In-house technical leadership | A scope that has been defined and validated |
| The day rate is used to | Calculate the invoice | Nothing, for you: only the total price matters |
T&M has its logic: it suits a company that already has a technical team and wants to reinforce it. Fixed price, for its part, is only solid if the scope was genuinely pinned down before pricing. Our article on fixed price vs time and materials goes deeper, and if you want a fixed price without freezing every detail, read how agile works on a fixed-price contract.
From day rate to budget: the honest calculation
If you start from a day rate to estimate a project, do the whole sum:
- Estimate days per feature, not for the project as one block, and ask who made the estimate.
- Add the roles the rate does not cover: design, testing, deployment, project management.
- Add your own internal time for direction and acceptance testing.
- Add a contingency, wider the vaguer the scope.
- Add what comes after: hosting, maintenance and changes over several years.
The result is almost always higher than "days × rate". That is normal: it is the real cost. Our guide to estimating a software project details the method, and our breakdown of custom business application cost lists the cost items.
Comparing two quotes without being led by the rate
When you receive one T&M quote and one fixed-price quote, do not compare day rates. Ask each supplier the same four questions: what is delivered, by when, for what total amount, and what happens if it overruns? A T&M quote that cannot answer the last one is not comparable with a fixed price. Our method for comparing software development quotes takes these points one by one.
Common mistakes
- Picking the lowest rate. It says nothing about productivity, and nothing about the final budget.
- Handing a whole project to T&M with nobody to direct it. The meter runs and the decisions do not get made.
- Ignoring your own unbilled days. Meetings, testing, answering questions: that time has a cost.
- Negotiating the rate instead of the scope. Saving 10% on the day rate weighs little against a vague scope that doubles the number of days.
- Quoting an "average rate" without a source. The numbers in circulation are often years old, or from another market.
Our position: no day rate, a price for a result
LPR Studio does not sell hours or staff: we publish no day rate and we do not do staff augmentation. That is not a judgement on those who do. It follows from what we sell: software that is delivered, deployed and maintained, with the build risk carried by us.
In practice, the scope is made visible before any commitment, through a free visual prototype presented on a video call within 5 working days. Then there are three formulas: fixed price development; a subscription where you do not pay for the build but a monthly amount covering hosting, maintenance and changes; or a SaaS edition. In all three, you judge a product, not a timesheet.