How do you price a freelance project?
Price a freelance project from three things at once: your real costs, your market position, and how clearly you communicate the scope. Work out a minimum day rate from your costs, break the job into phases with hours, add fixed expenses and a contingency markup, then present it as a document. The estimator above totals it as you go.
Pricing well is one of the hardest skills to develop, and most freelancers undercharge for years before getting it right. Cost awareness, market positioning, and communication each pull their weight, and getting all three right is what separates a sustainable practice from one that burns out.
Should you start from your costs or the market?
Start from your costs. Googling what others charge tells you nothing about whether you will profit at that number. Take your target annual income, add business costs like software, equipment, insurance, and accounting, then divide by your realistic billable days. Most freelancers have fewer than 200 a year. That figure is your floor, and you should not go below it.
Your billable days drop fast once you subtract holidays, sick days, business development, and admin, which is why the count lands below 200. Use the Day Rate Calculator to pin down your minimum viable day rate precisely, then hold it as the floor you do not take projects below.
Why break the project into phases?
A single-line quote like Website: £5,000 gives the client no way to see what they are buying and gives you no cover when the scope shifts. Splitting the work into named phases, each with its own hours, fixes both. When a client wants to add a feature, you point to the phase it affects and price it cleanly.
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.
How do you handle fixed expenses?
List third-party costs on their own, separate from your hourly rate. Stock photography, licensed fonts, hosting, API fees, and printing are pass-through costs, and naming them upfront avoids an awkward invoice later. If sourcing and managing them takes real time, it is fair to add a handling fee of around 10 to 15 percent, shown openly in the estimate.
Failing to list these costs upfront leads to awkward conversations when you invoice for them later, so keep them visible and keep the handling fee transparent rather than buried.
Should you add a markup for contingency?
Yes. Even seasoned freelancers misjudge how long work takes. Feedback drags, revisions multiply, and technical problems surface. A contingency markup of 10 to 20 percent on the total absorbs that. If you do not need it, it becomes margin. Agencies often run higher, between 20 and 35 percent, to cover project management and unbillable account time.
Keeping a buffer means you do not have to go back to the client cap-in-hand when a phase runs long.
Agencies sit at the higher end because they manage the project, carry risk, and build in account-management time that is not directly billable. Solo freelancers doing straightforward work can use a lower margin, though something almost always beats nothing.
Fixed price or time and materials?
Choose a fixed price when the scope is clearly defined and you can name the deliverables. Choose time and materials, billing actual hours up to an agreed cap, when the scope is vague, so every extra hour is still paid. A common middle path fixes the price for discovery and design, then bills implementation by the hour.
Most project estimates implicitly promise a fixed price: the client expects to pay what is written on the estimate. That works when the scope is clearly defined. When the deliverables are vague, a fixed price transfers all the risk to you, since every extra hour you spend is money you do not get back.
With time and materials you invoice what you actually spend, and the client pays for real work rather than your estimate of future work. The trade-off is that clients find it harder to budget, which is why the discovery-fixed, implementation-billed split tends to keep both sides comfortable.
How should you present the estimate?
Present it as a document, not a bare number. A single figure invites haggling on price, because price is all the client can see. A breakdown with named phases and line items shifts the talk to scope: if the budget is tight, which phase gets trimmed? Add a short narrative covering the goal, your approach, and the exclusions.
That kind of discussion is far more productive, and one where you stay in control.
Keep that narrative to a paragraph each: what you understand the project to be, how you will approach it, and what falls outside the scope. Those three notes answer the questions clients ask most often and head off the most common disputes.
What happens after the client approves the estimate?
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.