How to price a freelance project
Pricing a freelance project is one of the hardest skills to develop, and most freelancers undercharge for years before getting it right. The reason is that it is not a maths problem — it is a combination of cost awareness, market positioning, and communication. Getting each of those three pieces right is what separates a sustainable practice from one that burns out.
Start with your costs, not with the market
Many freelancers start by googling what other people charge and anchoring to that number. The problem is that those numbers tell you nothing about whether you will be profitable at that rate. Start with your own numbers instead.
Work out your minimum viable day rate first. Take your target annual income, add business costs (software, equipment, insurance, accountancy), then divide by your estimated billable days. Most freelancers have fewer than 200 truly billable days per year once you subtract holidays, sick days, business development, and admin. Use the Day Rate Calculator to get this number precisely. That is your floor — do not take projects below it.
Break the project into phases, not a single lump sum
A single-line estimate ("Website: £5,000") gives the client no way to understand what they are paying for, and gives you no protection when scope changes. A phase-based estimate solves both problems.
Common phases for a web project might be: Discovery and requirements (8 hours), Wireframes and design (16 hours), Development (40 hours), Content integration (8 hours), Testing and launch (8 hours). When a client asks to add a feature, you can point to a specific phase, explain what it displaces, and quote an additional amount — instead of having an abstract argument about whether the feature was "included."
Even if you do not show the client the full breakdown, building it for yourself forces you to think the project through. You will catch tasks you would have forgotten to price in, and you will be less likely to underestimate a phase you glossed over.
Account for fixed expenses separately
Third-party costs — stock photography, licensed fonts, cloud hosting, API fees, printing — are not included in your hourly rate. List them explicitly in the estimate so the client understands that these are pass-through costs, not markups. Failing to list them upfront leads to awkward conversations when you invoice for them later.
It is reasonable to add a handling fee (typically 10–15%) on third-party costs if sourcing and managing them takes time. Make this transparent in the estimate rather than burying it.
Use a markup for contingency and margin
Even experienced freelancers misjudge how long things take. Client feedback takes longer than expected. Revisions multiply. Technical problems appear. A contingency markup of 10–20% on the total is a reasonable buffer. If you do not use it, it becomes margin. If you do, it means you do not have to go back to the client cap-in-hand.
Agencies typically apply a higher margin (20–35%) because they are managing the project, carrying risk, and building in time for account management that is not directly billable. Solo freelancers doing straightforward work can use a lower margin — but something is almost always better than nothing.
Fixed-price vs time-and-materials
Most project estimates implicitly promise a fixed price: the client expects to pay what is written on the estimate, not more. This is fine if the scope is clearly defined. But if the deliverables are vague, a fixed price transfers all the risk to you — every extra hour you spend is money you do not get back.
For projects with undefined scope, time-and-materials (billing actual hours at your agreed rate, up to an agreed cap) is fairer. You invoice what you actually spend, and the client pays for actual work rather than your estimate of future work. The trade-off is that clients find it harder to budget. A common middle ground is a fixed price for clearly defined phases (like discovery and design) and time-and-materials for implementation.
Present the estimate as a document, not a number
A single-number quote invites clients to negotiate on price, because price is the only thing visible. A detailed estimate with named phases and named line items shifts the conversation to scope: if the budget is lower than the quote, which phase gets cut or reduced? That is a much more productive discussion, and one where you are in control.
When presenting an estimate, give a brief narrative alongside the numbers: one paragraph on what you understand the project to be, one on your approach, and one on what is not included (exclusions). These three things answer the questions clients ask most often and prevent the most common disputes.
What happens after the estimate is approved
Once a client approves your estimate, it becomes the basis of the project contract. Convert it to a formal statement of work or use it as the line items in your first invoice. Use the Quote Generator to turn your estimate into a professional PDF document with your business details, an expiry date, and terms. When the project is complete, create the final invoice using the Invoice Generator.
Tip: Save the PDF estimate before the project starts. If scope disputes arise later, the estimate is your record of what was agreed. Courts and arbitrators give weight to written estimates when they are produced promptly and the client accepted them without objection.