Hourly vs project-based vs value-based pricing for freelancers
Three pricing models compared. When to use each one and how to switch.
Hourly pricing bills for time. Project-based pricing bills for a deliverable. Value-based pricing bills for the outcome the client gets. Most freelancers start hourly, move to project-based as they get faster, and eventually adopt value-based pricing for high-stakes work. There is no single right model. The right one depends on your service, your clients, and how predictable your work is.
This guide breaks down all three with real math, comparison tables, and a framework for switching.
The three pricing models at a glance
Before the deep dive, here is the summary.
| Hourly | Project-based | Value-based | |
|---|---|---|---|
| What you charge for | Time spent | Deliverable completed | Business outcome achieved |
| Pricing transparency | High (client sees hours) | Medium (client sees total) | Low (client sees ROI framing) |
| Earning ceiling | Capped by hours available | Higher (efficiency rewarded) | Highest (decoupled from time) |
| Client risk | Low (pay as you go) | Medium (fixed commitment) | Higher (larger upfront investment) |
| Best for | Undefined scope, ongoing work | Clear deliverables, repeatable work | Strategic work with measurable impact |
| Typical freelancer stage | Early career, generalists | Mid-career, specialists | Senior, consultants, strategists |
Every model works. The question is which one fits the work you are doing right now.
Hourly pricing: how it works and when to use it
Hourly pricing is the simplest model. You track your hours. You bill for them. The client pays based on time spent.
The math
If you charge $100/hour and a project takes 40 hours, the client pays $4,000. If it takes 60 hours, they pay $6,000.
Your revenue is a direct function of time. More hours equals more money. Fewer hours equals less money.
When hourly works well
Hourly pricing is the right choice when:
- the scope is undefined. If the client cannot tell you exactly what they need, charging hourly protects you from scope creep. Consulting engagements, technical audits, and ongoing support retainers often work best on an hourly basis.
- the work is unpredictable. Bug fixes, maintenance work, and ad hoc requests are hard to price as a project because you cannot predict the effort.
- you are new to a service. If you have not done enough projects to estimate accurately, hourly pricing prevents you from undercharging on a flat rate.
- the client insists on it. Some corporate clients and agencies require hourly billing because their procurement systems are built around it. Fighting this costs more than accepting it.
When hourly breaks down
Hourly pricing has a structural problem: the faster you get, the less you earn.
A logo that took you 20 hours two years ago takes you 8 hours today because you are more experienced. On hourly billing, your income dropped 60% despite delivering the same quality output.
Hourly pricing also creates a misaligned incentive. The client wants you to work fewer hours. You earn more by working more hours. Neither side is wrong, but the incentive structure pits you against each other.
Real example: hourly pricing for a web developer
Rate: $125/hour Project: marketing website redesign Estimated hours: 80 Quoted range: $8,000 to $12,000 (with a buffer for revisions)
Actual hours: 95 Final bill: $11,875
The client paid more than the low estimate but within the quoted range. This works because the developer communicated the range upfront and tracked hours transparently. The client was never surprised.
Hourly pricing pitfalls
- Not tracking accurately. If you round down or forget to log time, you lose money. Use a timer, not your memory.
- Not setting a minimum. A 15-minute call should not be free. Set a minimum billing increment (30 minutes or 1 hour).
- Not capping the estimate. Saying “$125/hour” with no range is an open checkbook. Always give a range: “I estimate 60 to 80 hours for this project, billed at $125/hour.”
Project-based pricing: how it works and when to use it
Project-based pricing (also called flat-rate or fixed-fee) means quoting one price for the entire deliverable. The client knows the total cost before work starts. You earn the same amount whether the work takes you 10 hours or 50.
The math
You quote $8,000 for a brand identity package. It takes you 30 hours. Your effective rate is $267/hour.
Same project, different month. It takes 50 hours because the client needed more exploration. Your effective rate drops to $160/hour.
Your income is fixed. Your effective rate fluctuates based on efficiency.
When project-based works well
Project-based pricing is the right choice when:
- the deliverable is clear. Website builds, brand identity packages, marketing campaigns, copywriting projects. If you can define the output, you can price it flat.
- you have done this work before. Accurate project pricing requires knowing how long the work actually takes. That comes from experience.
- the client wants cost certainty. Many clients prefer a fixed price because they need to approve a budget internally. A flat rate eliminates the “how many hours will this really take” anxiety.
- your speed is an advantage. If you can deliver a website in 3 weeks that takes most people 8 weeks, project pricing lets you earn more per hour without the client feeling overcharged.
When project-based breaks down
The biggest risk is underpricing. If you quote $5,000 for a project that ends up taking 80 hours, your effective rate is $62.50/hour. That might be below what you need to sustain your business.
Project pricing also struggles with scope changes. If the client adds features, pages, or rounds of revisions beyond what you quoted, you absorb the cost unless you have a change order process.
Real example: project-based pricing for a brand designer
Quoted price: $6,500 for a full brand identity (logo, color palette, typography, brand guidelines PDF) Estimated internal hours: 25 Target effective rate: $260/hour
Actual hours: 22 Actual effective rate: $295/hour
The designer priced based on experience and delivered efficiently. The client paid a fair price for the output. The designer earned more per hour than they would have on an hourly rate. Both sides are satisfied.
Real example: project-based pricing gone wrong
Quoted price: $4,000 for a website redesign Estimated internal hours: 30 Target effective rate: $133/hour
Actual hours: 65 (client kept requesting changes, scope expanded) Actual effective rate: $61.50/hour
The freelancer did not define revision limits or a scope boundary. The project expanded without additional billing. The fix is not to avoid project pricing. The fix is to define the scope tightly and include a change order process.
Project pricing pitfalls
- Not defining scope precisely. “Website redesign” is not a scope. “5-page marketing website with responsive design, 2 rounds of revisions, and content migration for existing pages” is a scope.
- Not including a change order clause. Any work outside the original scope should trigger a separate quote. Build this into your proposal.
- Pricing too low to win the deal. If you discount your flat rate to compete, you absorb the risk on a project that already has thin margins. Price based on your costs and value, not the client’s budget anchor.
- Not padding for revisions. Build 2 to 3 revision rounds into your estimate. If the client uses fewer, you keep the margin. If they use more, you are covered.
Value-based pricing: how it works and when to use it
Value-based pricing sets the fee based on the outcome the client receives, not the time you spend or the deliverable you produce. If a marketing strategy generates $200,000 in new revenue, charging $20,000 for it is 10% of the value created.
The math
The client’s problem: their checkout flow has a 2% conversion rate. Industry average is 4%. Their monthly revenue: $500,000 A 2% improvement in conversion: $500,000/month additional revenue, or $6,000,000/year.
You charge $50,000 for a UX overhaul of the checkout flow.
That is less than 1% of the first-year revenue impact. To the client, this is an obvious investment. To you, this is a project that might take 100 hours at an effective rate of $500/hour.
When value-based works well
Value-based pricing is the right choice when:
- the outcome is measurable. Revenue increase, cost reduction, time saved, conversion improvement. If you can put a number on the impact, you can price against it.
- you have the credibility to command it. Value-based pricing requires the client to trust that you can deliver the outcome. That trust comes from case studies, track record, and reputation.
- the client sees the engagement as an investment. If the client is buying a commodity, they will shop on price. If they are buying a solution to a $500,000 problem, price is secondary to confidence.
- the stakes are high enough to justify it. Value-based pricing does not make sense for a $500 project. It makes sense when the client stands to gain tens or hundreds of thousands from the result.
When value-based breaks down
Value-based pricing requires a specific kind of conversation. You need to understand the client’s business, quantify the problem, and frame your fee as a fraction of the outcome.
Not every client will engage in that conversation. Some just want a website built and do not care about ROI framing. That is fine. Use project pricing for those clients.
Value-based pricing also does not work when:
- the outcome is subjective (brand “feeling”)
- you cannot isolate your contribution from other factors
- the client does not have revenue data to anchor against
- you are early in your career without a track record
Real example: value-based pricing for a copywriter
Client problem: SaaS landing page converts at 1.2%. They want 3%. Client’s monthly ad spend: $40,000 Current cost per acquisition: $333 Target cost per acquisition: $133
If the copywriter hits the target, the client saves $200 per customer. At 120 customers/month, that is $24,000/month in savings, or $288,000/year.
The copywriter charges $15,000 for the landing page rewrite and A/B testing framework.
That is 5% of the first-year savings. The client sees it as a no-brainer. The copywriter earns $15,000 for what might be 40 hours of work ($375/hour effective).
Value-based pricing pitfalls
- Overestimating the value. Be honest about the outcome you can realistically deliver. If the value case depends on best-case assumptions, the pricing will feel dishonest.
- Not tying fees to outcomes. If you charge value-based prices but deliver hourly-style work, the client will feel overcharged. The delivery experience needs to match the pricing.
- Skipping the discovery conversation. Value-based pricing requires deep understanding of the client’s business metrics. If you skip discovery and guess at the value, your pricing has no foundation.
- Using it when project pricing is simpler. Not every engagement needs a value framework. If the client just needs a logo, quote a flat rate. Save value pricing for strategic work.
Comparison: which model earns more
The same project priced three ways.
Scenario: a freelance designer creates a landing page for a SaaS company.
| Hourly | Project-based | Value-based | |
|---|---|---|---|
| Pricing approach | $150/hour x 30 hours | $6,000 flat rate | $15,000 based on projected conversion lift |
| Revenue to freelancer | $4,500 | $6,000 | $15,000 |
| Effective hourly rate | $150 | $200 | $500 |
| Client’s perspective | ”Paying for time" | "Paying for a page" | "Paying for more revenue” |
| Requires from freelancer | Time tracking | Scope definition | Business case development |
The same work. Three different price points. The difference is how the work is framed and what the client believes they are buying.
How to switch from hourly to project-based
This is the most common transition and the easiest to execute.
Step 1: track your hours on the next 5 projects
Even if you are billing hourly, track exactly how long each type of deliverable takes. After 5 projects, you will have reliable averages.
Step 2: calculate your target project rate
Take your average hours for a deliverable type. Multiply by your hourly rate. Add 20% as a buffer for revisions and scope ambiguity.
Example: Average hours for a website: 45 Hourly rate: $125 Base project price: $5,625 With 20% buffer: $6,750 Rounded: $7,000
Step 3: define your scope document
Write a clear description of what is included and what is not. This is the foundation of project pricing. If the scope is vague, you will lose money.
Step 4: quote the next project as a flat rate
Use the project price instead of your hourly rate. Present it in a proper proposal with scope, timeline, and payment terms.
Step 5: track your effective rate
After delivering, divide the project fee by the actual hours. If your effective rate is higher than your old hourly rate, the transition is working. If it is lower, tighten your scope or raise your price.
How to switch from project-based to value-based
This transition is harder and not every project qualifies.
Step 1: identify which clients have measurable outcomes
Look at your current client list. Which ones can point to a revenue number, a cost savings, or a conversion metric that your work affects? Those are your value-pricing candidates.
Step 2: change the discovery conversation
Stop asking “what do you want built?” Start asking “what business result are you trying to achieve?” and “what is this problem costing you?”
Step 3: quantify the value
Work with the client to put a number on the outcome. “If we increase conversion by 1%, that is $X per month.” Your fee should be 10 to 20% of the projected value.
Step 4: present the fee with the value context
Do not say “my fee is $20,000.” Say “the projected revenue impact is $200,000 in the first year. My fee is $20,000, which is 10% of that impact.” The number is the same. The framing is completely different.
Step 5: deliver on the outcome
Value-based pricing only works long-term if you deliver results. Track the metrics. Report on the outcomes. Build case studies. Your credibility for the next value-priced engagement depends on demonstrating results from the last one.
Common mistakes with each model
Hourly mistakes
- Billing in small increments (15 minutes) that add up to less than a fair day rate
- Not enforcing a minimum engagement
- Discounting your rate for “easy” work
- Letting clients negotiate your hourly rate down without reducing scope
Project-based mistakes
- Quoting before you understand the scope
- Not including a revision limit
- Absorbing scope changes without a change order
- Pricing based on what the client says their budget is instead of what the work costs you
Value-based mistakes
- Using value pricing for commodity work that does not have measurable outcomes
- Overestimating the impact to justify a higher fee
- Not documenting the outcome you are pricing against
- Failing to deliver on the outcome and losing credibility
FAQ
Should new freelancers start with hourly pricing?
Usually, yes. Hourly pricing is the safest way to learn how long work takes without undercharging. Once you have enough data to estimate accurately, transition to project-based. You need at least 5 to 10 similar projects before you can price flat rates confidently.
Can I use different pricing models for different clients?
Absolutely. Many freelancers use hourly for maintenance work, project-based for builds, and value-based for strategy engagements. Match the model to the work, not to a philosophical commitment to one approach.
How do I handle scope creep with project pricing?
Include a change order clause in every proposal. When the client requests something outside the original scope, provide a separate estimate and get approval before doing the work. Read our guide on change order templates for copy-paste language.
What hourly rate should I charge as a freelancer?
Start by calculating your minimum viable rate. Take your annual income target, divide by the number of billable hours you realistically have (most freelancers bill 20 to 25 hours per week, not 40). Then factor in taxes, insurance, and business expenses. According to Payoneer’s freelancer income data, rates vary widely by region and specialty, but the global average is around $21/hour. US-based specialists typically charge $75 to $250/hour depending on the field.
Is value-based pricing just overcharging?
No. It is pricing based on what the result is worth, not what the work costs. If a $15,000 engagement generates $200,000 in revenue for the client, both sides benefit. The client would not pay $15,000 for the same work if the outcome were worth $5,000. Value pricing only works when the value is real.
How do I present a project price without the client asking for an hourly breakdown?
Frame the price around the deliverable and outcome, not the hours. “The investment for this project is $8,000, which includes [deliverables], [timeline], and [revision rounds].” If the client pushes for hours, say: “I price based on the deliverable and outcome, not hours. That way you get the result without worrying about the clock.”
What if I am faster than average? Does project pricing reward that?
Yes. That is the primary advantage. If you can deliver a website in 20 hours that takes most freelancers 50, project pricing lets you earn $400/hour effectively instead of $150/hour. Your speed is a competitive advantage that hourly pricing penalizes and project pricing rewards.
How do deposits work with each pricing model?
For hourly, require a retainer deposit (10 to 20 hours prepaid) before starting. For project-based, 50% upfront and 50% on delivery is standard. For value-based, the deposit structure is the same as project-based, but the total is higher. Read our full guide on deposit strategy for specifics.
The practical takeaway
There is no universally correct pricing model. There is only the model that fits your current work, clients, and career stage.
If your scope is unpredictable, use hourly. If your deliverables are repeatable, use project-based. If you can measure the business impact of your work, use value-based.
Most freelancers should aim to move from hourly to project-based within their first year or two, and explore value-based pricing for strategic engagements where the math supports it.
If you want to present any of these pricing models in a professional proposal, GetPaidFirst generates proposals from meeting notes with your pricing, payment terms, and deposit structure built in. The client approves and pays in one step regardless of which model you use.
Further reading:
- Payoneer Freelancer Income Report (Payoneer)
- The Win Without Pitching Manifesto (Blair Enns)
- Freelance pricing guide (GetPaidFirst)
- Value-based pricing for freelancers (GetPaidFirst)
- Freelance proposal guide (GetPaidFirst)
- Deposit strategy (GetPaidFirst)