Freelance Web Developer Rate Calculator
The rate that matches your old salary is not the rate that replaces your old salary. Put in the hours a project really takes and the costs you carry between projects, and see what it has to be worth.
Freelance developers pricing calculator
Recommended selling price
$0.00
per unit, before sales tax
Where the price goes
- Costs $0.00 0%
- Fees $0.00 0%
- Profit $0.00 0%
| Line | Per unit | Order total |
|---|---|---|
| Materials / product | $0.00 | $0.00 |
| Labor | $0.00 | $0.00 |
| Other costs | $0.00 | $0.00 |
| Overhead | $0.00 | $0.00 |
| Total cost | $0.00 | $0.00 |
| Payment processing fee | $0.00 | $0.00 |
| Profit | $0.00 | $0.00 |
| Base selling price | $0.00 | $0.00 |
| Sales tax | $0.00 | $0.00 |
| Customer pays | $0.00 | $0.00 |
- Profit margin0%
- Markup on cost0%
- Cost per unit$0.00
- Quantity1
Show the math
Results are estimates based on the information you enter. Actual taxes, fees, and business expenses may vary.
How to price a development project
Your salary divided by 2,080 is the wrong number
The arithmetic everyone starts with — take the salary you want, divide by 2,080 hours — assumes every working hour is a paid hour. It is not. Sales calls, proposals, invoicing, code that has to be thrown away, the three weeks between contracts, holiday, sick days and the afternoon lost to a client who went quiet are all real and none of them bill. A solo developer working hard typically bills between 1,000 and 1,400 hours a year, not 2,080. Divide by the smaller figure and the honest rate is roughly sixty to eighty percent higher than the one the salary arithmetic gave you.
Price the project, quote the project, but cost it by the hour
Clients prefer a fixed number and so should you: a fixed price rewards you for being fast, where an hourly rate quietly punishes it. But a fixed price you arrived at by feel is a coin toss. Estimate the hours honestly, including the parts nobody enjoys estimating — content wrangling, browser testing, the review round that turns into three — cost those hours at your real rate, add what the project costs you in software and services, then apply the margin. The number that comes out is your floor. What you quote can be higher; it should never be lower.
Scope creep is a pricing problem before it is a discipline problem
Most developers who feel underpaid are not underpriced, they are under-scoped. If the quote says “a website” and the client believes that includes copywriting, a logo, a migration, three rounds of design and training, the hours you costed were never the hours you were going to work. Write the deliverable down to the page, name the number of revision rounds, and price anything beyond it separately at your hourly rate. The calculator gives you a defensible floor; a written scope is what stops the floor being eaten from underneath.
Overhead is not optional just because it is invisible
Hosting, a design tool subscription, an IDE licence, error monitoring, a laptop amortised over three years, an accountant, liability insurance, a domain, a mailbox, a password manager, professional development. None of it is billable to a client and all of it is a cost of being able to take the work. Add it up for a month, divide by the number of projects you realistically complete in a month, and put that figure in the overhead field. Developers who skip this step are the ones who find they are busy all year and no better off.
The formula behind the calculator, including why the margin is divided rather than multiplied, is written out step by step on the pricing calculator.
What freelance web developers have to price in
A price that leaves any of these out is not a price, it is a subsidy. Put each one into the calculator above, even where it feels too small to matter — small and recurring is exactly how costs escape notice.
- Development hours at your real rate
- Not the salary-equivalent rate. The rate that accounts for the hours you cannot bill.
- Discovery, scoping and proposal time
- Hours spent winning the work are hours the work has to pay for, whether you itemise them or bury them in the rate.
- Project management and client communication
- Calls, emails, chasing content, status updates. On a fixed-price build this is routinely ten to twenty percent of the total.
- Testing, QA and browser fixes
- The tail end of a build where estimates go wrong most often. Cost it explicitly rather than hoping.
- Revision rounds
- Name the number in the quote and cost that number. Rounds beyond it are new work at your hourly rate.
- Third-party licences bought for the job
- A premium plugin, a font licence, stock imagery, a paid API tier. Job costs, not overhead, because the project caused them.
- Hosting and domains you carry
- If you host the client during the build, or carry a staging environment, that is your money until it is billed.
- Your own software subscriptions
- Editors, design tools, monitoring, repositories, a password manager. Monthly overhead, divided across the projects in a month.
- Hardware, amortised
- A laptop and a monitor spread over the years they will last, not expensed entirely in the month you bought them.
- Insurance and professional fees
- Liability cover, an accountant, any registration your jurisdiction requires. Overhead, and non-negotiable overhead at that.
- Payment processing
- Card and platform fees come off the top. On a five-figure invoice a 2.9% fee is a meaningful number, and a bank transfer often avoids it entirely.
- Late payment and bad debt
- Some invoices land ninety days out and a few never land at all. A margin that assumes perfect collection is a margin you will not keep.
A cost you leave out does not disappear — it comes out of your profit instead. Put every one of these into the calculator above, even the ones that feel too small to bother with.
A worked example: a small business website build
A five-week build quoted as a fixed price: roughly 38 hours of actual work at a rate that reflects billable reality rather than a salary calculation, plus the licences bought for this job and a month’s share of the overhead that never stops.
| Hours | 38 | Build, project management, testing and two revision rounds. The honest number, not the optimistic one. |
|---|---|---|
| Hourly rate | $95.00 | Set against roughly 1,200 billable hours a year rather than 2,080. |
| Job costs | $180.00 | A premium plugin, a font licence and stock imagery bought for this project. |
| Overhead share | $640.00 | One month of software, insurance, accounting and amortised hardware, carried by one project. |
| Target margin | 25% | What is left after every cost above, including your own paid hours. |
| Payment processing | 2.9% | Card payment. A bank transfer would remove this line entirely. |
| Labor | $3,610.00 | Hours on the job at your own rate. Charge for it or fund it yourself. |
|---|---|---|
| Other job costs | $180.00 | Travel, consumables, subcontractors, anything bought for this job alone. |
| Overhead | $640.00 | The share of running the business that this job has to carry. |
| Total cost | $4,430.00 | What the job costs you before you have made a penny. |
| Payment processing | $178.18 | Taken off the top by the processor, so the price has to cover it. |
| Profit | $1,536.06 | What is actually left, at the margin you asked for. |
- Price per unit $6,144.24
- What the customer pays $6,144.24
- Profit margin 25%
- Equivalent markup 34.67%
The hours alone come to $3,610, which is the number most developers quote and then wonder where the year went. Adding job costs and one month of overhead takes the real cost to $4,430; the margin on top brings the price to $6,144.24. Notice that the $1,536.06 of profit is what pays for the weeks between contracts — it is not a bonus, it is the buffer, and a 10% margin would not provide one.
Run your own figures through the calculator above — the numbers here are an illustration, not a benchmark, and local rates vary enormously.
Freelance developers pricing questions
What should a freelance web developer charge per hour?
There is no single right number, but there is a right method. Start from the annual income you need, divide by the hours you can realistically bill — 1,000 to 1,400 for a full-time solo developer, not 2,080 — and you have a floor rate before overhead or profit. Add a per-project share of your overhead and the margin you want to keep, and the calculator above turns that into a project price. Then sanity-check it against what your local market and your specialism support. Method first, market second: a rate you cannot justify is a rate you will discount under pressure.
Should I quote hourly or fixed price?
Quote fixed, cost hourly. A fixed price is easier for a client to approve, protects you from having to justify every hour, and rewards you for getting faster at work you have done before — an hourly rate penalises exactly that. What makes fixed pricing dangerous is arriving at the number by feel. Estimate the hours, cost them at your real rate, add job costs and overhead, apply the margin, and quote the result. Keep the hourly rate published for work outside the agreed scope, which is where fixed-price projects actually go wrong.
How do I raise my rates without losing clients?
Raise on new work first. Quote the new number to every new enquiry for a quarter and watch the acceptance rate rather than guessing at it — if nobody hesitates, the old rate was too low by more than you raised it. For existing clients give notice well ahead, apply the increase at a natural boundary such as a new project or a contract renewal, and state the new rate without a justification paragraph; explaining at length invites negotiation. Expect to lose your most price-sensitive client and price the work so that losing them is affordable.
Put this calculator on your own site
Free to embed on any site, no attribution fee and no sign-up. The frame loads nothing but the calculator itself — no tracking, no cookies, no third-party scripts — so it will not slow your page down or complicate your own privacy policy. Copy the code below and paste it into any HTML block.