How to Price a Freelance Project
Learn how to estimate, scope, and price fixed-bid freelance projects.
A client asks for a quote on a project. You know your hourly rate. But what's the right number for a fixed-price project?
The biggest mistakes in project pricing happen before you do any math. They happen when the scope isn't clear, when revisions aren't discussed, and when you underestimate the work. Here's a practical approach to avoid those mistakes.
Start with scope
A fixed-price project needs a clearly defined scope. If the client can't define what they want, don't give a fixed price. Bill hourly instead.
A clear scope includes:
- What you'll deliver (the actual work)
- What you won't deliver (to prevent creep)
- How many revision rounds are included
- What happens if the scope changes
Estimate hours
Break the project into tasks and estimate hours for each. Be realistic about how long each step takes. Then add a buffer.
For example, you estimate 45 hours for a web project. You add a buffer for uncertainty.
- Estimated hours: 45
- Buffered hours: 45 × 1.5 = 68 hours
That 1.5 multiplier is just an example. A well-defined project may need a smaller buffer, while unfamiliar or poorly defined work may need a much larger one. The right buffer depends on how well you know the work and how clearly the client has defined the scope.
Apply your rate and adjust for complexity
If your hourly rate is $80 (example):
68 hours × $80 = $5,440
Then consider complexity. A simple project might stay at that number. A complex project with custom functionality or tight deadlines might justify a higher price.
| Complexity | What it means |
|---|---|
| Low | Well-defined, similar to past work |
| Medium | Requires some problem-solving or new skills |
| High | Complex scope, unfamiliar domain, multiple stakeholders |
Add project costs
Include anything you'll pay for specifically for this project:
- Software licenses
- Stock assets
- Subcontractor fees
- Platform or payment processing fees
Include these costs in your project price. If appropriate, list them separately in the proposal so the client can see what they're paying for.
Consider risk
Some projects are riskier to quote fixed-price:
- The client is new and hasn't built trust yet
- Requirements are still being defined
- The timeline is aggressive
- The work involves an unfamiliar technology
For risky projects, add a risk buffer. For low-risk, well-defined projects, you might not need one.
Complete example
Scenario: Website redesign for a local business.
- Estimated work: 40 hours
- Time buffer: ×1.5
- Buffered estimate: 60 hours
- Hourly rate: $85
- Base price: $5,100
- Project expenses: $200 (stock photos, plugins)
- Complexity adjustment: ×1.1 (medium complexity)
- Risk adjustment: ×1.05 (new client)
Calculation:
- $5,100 × 1.1 = $5,610
- $5,610 × 1.05 = $5,890.50
- $5,890.50 + $200 = $6,090.50
Final quote: $6,100 (rounded)
If the project takes 42 hours, your effective rate is approximately $145/hour. That's the benefit of project-based pricing when you estimate well — you earn more than your standard hourly rate for efficient work.
When to choose project pricing
Project pricing works well when:
- The scope is clearly defined
- You've done similar work before
- The client values predictable costs
- You want to earn more than your hourly rate for efficient work
When to choose hourly instead
- The scope is vague or exploratory
- The project involves ongoing iteration
- The client expects frequent changes
- You're working in an unfamiliar area
Common mistakes
Underestimating time
Most freelancers do this. Add a serious buffer, especially on first projects with a client.
Not defining scope clearly
"Build a website" isn't a scope. "Five pages, contact form, two revision rounds" is a scope.
Forgetting to include client communication
Meetings, emails, and feedback loops take time. Include them in your estimate.
Skipping the risk review
Fixed-price projects carry risk. If something goes wrong, you absorb the cost. Review each project's risk level before quoting.
Estimate your project price
Use the calculator to get a quick, structured estimate.
Related Guides
Frequently Asked Questions
How do I price a project I've never done before?
Break it into smaller parts. Estimate each part. Add extra time for learning. Consider charging hourly if the work is truly unfamiliar.
How many revisions should I include?
Two rounds is common. More than that usually costs extra.
What if the scope changes mid-project?
Document the original scope. If the client asks for something new, agree on a change order with additional cost.
Should I add a rush fee?
If a client needs the project delivered faster than your standard timeline, charging more is reasonable. A rush fee can be a percentage increase, a fixed fee, or a higher project price based on the additional scheduling constraints. For example, you might add 20% for a moderately compressed timeline.
How do I present my price to a client?
Show what they're getting, not just a number. Use a proposal with deliverables and timeline. Our Proposal Generator can help.
What if the client says my price is too high?
Ask about their budget, then consider adjusting scope instead of lowering your rate. Fewer deliverables, not a lower rate.
Is project-based pricing always better than hourly?
Not always. Project pricing works well for well-defined work. Hourly works better for ongoing, exploratory, or iterative work. Many freelancers use both depending on the project.
Related Tool: Try our Freelance Project Pricing Calculator