How to Price a Freelance Project

Turning a brief into a fixed price you can defend, with a buffer for the things you can’t see yet

Published Oct 27, 2026•By Mubarak, Software Developer & Marketing Specialist

Fixed-price projects reward good estimators and punish optimistic ones. The method below starts from your hourly rate, builds the estimate from the bottom up, adds a buffer sized to the real uncertainty, and finishes with a check against what the work is worth to the client. A worked example runs through every step.

Open the Quote Generator tool

The short answer

To price a freelance project, break it into tasks, estimate the hours for each, multiply by your hourly rate, and add a risk buffer: around 10–20% for work you have done many times, more for unfamiliar work. Then compare the result with what the outcome is worth to the client and with what similar projects sell for, and quote the deliverables at that fixed price with a clear scope and revision limit.

What do I need before I can price a project?

You need two things: your own hourly rate and a scope detailed enough to list the deliverables.

Your hourly rate is the floor under every fixed price. It has to cover your income target, taxes, business costs and the hours you cannot bill. If you do not have one yet, work it out with the freelance rate calculator or the freelance rate formula. Clients never see this number on a fixed-price quote, but you use it to check that the quote pays you properly.

The scope comes from the discovery conversation. If you still cannot say how many pages, screens, articles or revisions are involved, you are not ready to fix a price. Ask more questions (the discovery questionnaire has a list), or send an estimate instead, as explained in quote vs estimate vs proposal.

What are the main ways to set a fixed project price?

There are four common methods. The strongest quotes use the first two to build the price and the last two to check it.

MethodHow it worksBest forWeak spot
Bottom-up hoursEstimate hours per task × hourly rateMost projectsForgets meetings, admin and revisions
Three-point estimateBest, likely and worst case per task, weightedTasks with real uncertaintyTakes longer to prepare
Comparable projectsWhat similar past projects cost and tookRepeat workNeeds records of past hours
Value-based checkPrice relative to the result’s worth to the clientWork tied to revenue or savingsHard when the value is vague

How do I estimate the hours bottom-up?

List every task, including the ones that do not produce a deliverable, and estimate each separately. Small tasks are easier to estimate accurately than one large lump.

  1. Break each deliverable into tasks of roughly half a day or less.
  2. Add the hidden work: kickoff and check-in calls, emails, project management, file preparation, handover and training.
  3. Add revision time for the number of rounds you will include. A round is not free just because the quote says it is included.
  4. Total the hours and multiply by your hourly rate.

The hidden work is where most underpricing comes from. On a small project, meetings and admin can be a large share of the total. If you track your time, look at a past project and compare hours spent producing work with total hours logged; the billable hours calculator helps with that.

How do three-point estimates work?

For each uncertain task, estimate an optimistic, a most likely and a pessimistic number of hours, then take a weighted average that leans toward the most likely case.

Expected hours = (optimistic + 4 × most likely + pessimistic) ÷ 6

This is the PERT formula, used in project management for decades. Its value for freelancers is that it forces you to think about the pessimistic case for every task instead of quoting the hopeful one. If a task is 4 hours at best, 6 most likely and 14 at worst, the expected time is (4 + 24 + 14) ÷ 6 = 7 hours, not 6. The long tail on the pessimistic side pulls the number up, which is usually what happens in practice.

How much should I pad a quote for risk?

Add a buffer that matches how uncertain the work is: small for familiar work, larger for new types of work, new clients or dependencies you do not control.

There is no official percentage. The ranges below are starting points that many freelancers use; your own history is a better guide (see the next section).

SituationStarting buffer
Work you have done many times, known client10%
Familiar work, new client15–20%
New tools, new type of project, or many stakeholders25–35%
Depends on third parties, legacy code or unknown contentQuote a paid discovery phase first

Put the buffer into the line items, not as a visible “contingency” line. A contingency line invites the client to ask you to remove it, and it implies you expect to go over. Splitting it across the line items keeps each price honest about the real work involved.

Calibrate the buffer from your own projects

After each fixed-price project, divide the hours you actually spent by the hours you estimated. If your last five projects came in at 1.1, 1.3, 1.25, 1.0 and 1.35, your average overrun is 20%, and that is your buffer before any extra allowance for new risks. Freelancers who do this for a year usually find their buffers were too small.

Worked example: pricing a website project

A freelance developer with an $85 target hourly rate is pricing a five-page marketing site for a new client.

TaskOptimisticLikelyPessimisticExpected
Discovery & sitemap4686.0
Design, 5 pages15203121.0
Development & CMS28365638.0
Content entry, QA, launch4686.0
Calls, email, admin5797.0
Total567511278.0
  1. Expected hours: 78. At $85, that is 78 × $85 = $6,630.
  2. Buffer for familiar work with a new client, 15%: $6,630 × 1.15 = $7,624.50.
  3. Round to a clean number: $7,600.
  4. Comparable check: the developer’s last two similar sites sold for $6,800 and $7,500. $7,600 is in line, slightly higher to reflect the new client.
  5. Value check: the client expects the site to support a sales team selling contracts worth several thousand dollars each. One extra contract a year from better enquiries would cover the fee. The price is defensible.

Notice what the three-point method did here. The likely total was 75 hours, but the long pessimistic tail on design and development pushed the expected figure to 78. Quoting the likely case at 75 × $85 = $6,375 would have left $1,225 less to absorb surprises than the final $7,600.

The quote then shows deliverables, not hours: discovery $650, design $2,000, development $3,800, launch $550, project management $600 (total $7,600). If the project takes the likely 75 hours, the developer earns about $101 an hour; at the pessimistic 112 hours, about $68. To see that effective rate as you build the quote, enter the hours in the pricing check in the quote generator.

How do I use value-based pricing as a check?

Ask what the result is worth to the client in money, and make sure your price is a small enough share of that value to be an easy decision.

Value-based pricing works when the client can put a figure on the outcome: more leads, fewer support tickets, hours saved per week. If a workflow automation saves a team 10 hours a week and their time costs $50 an hour, that is roughly $26,000 a year. A $6,000 fixed price is easy to approve against that; a $1,500 price based only on your hours undersells it. When the value is vague (a brand refresh, a portfolio site), lean on hours and comparables instead.

Value is a ceiling and a sanity check, not a reason to drop below your hourly floor. If the value to the client is lower than your cost to do the work, the project is not a good fit at any price you should accept.

What are the most common project pricing mistakes?

Most underpriced projects fail in the same few ways, and almost all of them are about leaving work out of the estimate rather than charging too little per hour.

  • Estimating only the production work. Calls, email, file preparation and handover are real hours. Leave them out and the effective rate drops on every project.
  • Quoting the optimistic case. The hours you would spend if nothing went wrong are a best case, not an estimate. The three-point method fixes this.
  • Unlimited revisions. An open promise of changes turns a fixed price into an open-ended one.
  • Pricing to the client’s budget first. Starting from what the client said they could spend and fitting the work around it usually means quietly absorbing the gap. Price the work, then adjust the scope to meet the budget.
  • Discounting to win. A 10% discount on a project with a 15% buffer leaves almost no margin for surprises. If you must discount, take something out of the scope.
  • Forgetting pass-through costs. Fonts, stock images, plugins, hosting and software seats either go into the price or into the exclusions; they should never come out of your fee.
  • Never checking afterwards. Without comparing estimated and actual hours, the same mistake repeats on the next quote.

How do I protect a fixed price once it is agreed?

Fix the scope as firmly as the price. The price is only fixed for the work described.

  • List inclusions and exclusions in the quote.
  • Limit revision rounds and price additional ones.
  • Tie the timeline to client inputs (“launch 2 weeks after final content is received”).
  • Take a deposit and milestone payments so cash arrives as the work does; see how much deposit to charge.
  • Handle extra requests through a change request with its own price, as described in how to handle scope creep.

If you want market context for your hourly floor, compare it with average freelance rates for your field, and look up any unfamiliar pricing terms in the freelance pricing glossary.

Frequently asked questions

How do I calculate a fixed price for a freelance project?

Break the project into tasks, estimate hours for each, multiply by your hourly rate, add a risk buffer for uncertainty, then sanity-check the result against the value of the outcome to the client.

How much buffer should I add to a fixed-price quote?

Many freelancers add 10% to 20% for work they have done many times and more for unfamiliar work. Better still, base the buffer on how far over your past estimates ran.

Is it better to charge hourly or per project?

Hourly protects you when scope is unclear; a fixed price rewards you for working efficiently and is easier for clients to approve. Many freelancers fix the price of well-defined phases and bill open-ended work hourly.

What is value-based pricing?

Pricing based on what the result is worth to the client rather than on your hours. It works best when the client can put a number on the outcome, such as extra revenue or time saved.

Should I show my hours in a fixed-price quote?

Usually not. Show deliverables and prices. Listing hours invites the client to haggle over each one and ties you to time rather than results.