Why This Decision Matters More Than Your Rate
Most freelancers obsess over their hourly rate. Should I charge $75 or $100? But the pricing model — hourly vs. project-based — has a bigger impact on your income than the number itself.
Here's why: A designer who charges $80/hour and takes 20 hours on a website earns $1,600. That same designer, pricing the project at $3,000 and finishing in 15 hours, earns $200/hour effectively. Same skill, same work — completely different outcome based on the pricing model.
Hourly Pricing: The Complete Breakdown
When Hourly Works Best
- Undefined scope — The client doesn't know exactly what they want, and requirements will evolve
- Ongoing retainers — Maintenance, support, or advisory work with variable hours
- New clients — You don't yet know how they work, how many revisions they'll request, or how responsive they'll be
- Technical consulting — Strategy sessions, audits, code reviews where time = value
The Pros
- Zero scope creep risk — extra work = extra pay
- Simple to explain and invoice
- Fair when requirements are fuzzy
- Easy to track and report
The Cons
- Income ceiling — You can only earn more by working more hours
- Speed penalty — Getting faster at your craft actually reduces your income
- Client anxiety — Clients watch the clock and second-guess every hour
- Administrative overhead — You need to track time meticulously
Project-Based Pricing: The Complete Breakdown
When Project Pricing Works Best
- Clear deliverables — Both sides agree on exactly what “done” looks like
- Repeatable work — You've done similar projects before and can estimate accurately
- High-value outcomes — The result is worth much more to the client than your time cost
- Established clients — You know the communication style, revision patterns, and process
The Pros
- Rewards efficiency — Finish faster, earn more per hour
- Predictable income — Both you and the client know the total cost upfront
- No time tracking needed
- Value alignment — Clients focus on results, not hours
The Cons
- Scope creep — “Can you also...” requests eat your margin
- Estimation risk — Underestimate and you lose money
- Requires clear contracts — You need to define exactly what's included and what costs extra
The Decision Framework: 4 Questions
Ask yourself these four questions before pricing any project:
| Question | If Yes → Hourly | If Yes → Project |
|---|---|---|
| Is the scope clear? | No | Yes |
| Have you done this before? | No / first time | Yes, multiple times |
| Is the client known to you? | New client | Established relationship |
| Is the outcome high-value? | Moderate / unclear | Yes, clearly valuable |
3-4 answers in one column? Go with that model. Mixed results? Consider a hybrid approach (see below).
The Hybrid Approach: Best of Both Worlds
Many experienced freelancers use a hybrid model:
- Discovery phase (hourly) — Charge hourly for the initial consultation, research, and scope definition. This protects you from unpaid pre-project work.
- Execution phase (project) — Once scope is defined, quote a fixed price for the deliverables. You benefit from efficiency, the client gets predictable costs.
- Changes & extras (hourly) — Any work outside the agreed scope is billed hourly. This prevents scope creep without rigid change-order processes.
This is the same model architecture firms, law offices, and consulting companies use — and it works just as well for solo freelancers.
Real-World Examples
| Project | Model | Why |
|---|---|---|
| 5-page website | Project | Clear scope, repeatable, you control the speed |
| Ongoing WordPress maintenance | Hourly | Variable tasks, unpredictable hours |
| Brand identity + logo | Project | Defined deliverables, high perceived value |
| Strategy consulting call | Hourly | Time = value, no deliverable to scope |
| E-commerce store build | Hybrid | Discovery hourly, build project, extras hourly |
| Blog writing (regular) | Per piece | Each article is a mini-project with clear scope |
5 Pricing Mistakes That Cost You Money
- Using hourly for everything. If you've done 20 websites and can build one in 15 hours, charging hourly means you earn less as you get better. Switch to project pricing for repeatable work.
- Project pricing without a scope document. No written scope = guaranteed scope creep. Always define deliverables, revisions included, and what costs extra — in writing.
- Underestimating project time. Add a 20-30% buffer to your time estimates. Client communication, revisions, and unexpected issues always take longer than expected.
- Not tracking time on fixed projects. Even on project-based work, track your hours internally. This data helps you price future projects accurately. Use our hourly rate calculator to find your baseline.
- Charging the same for every client. A logo for a local bakery and a logo for a tech startup have different value to the client. Adjust your project prices based on client size, budget, and the value they'll get from your work.
How to Calculate Your Project Price
Start with your hourly rate, then adjust:
- Estimate hours: How long will this realistically take? Include meetings, revisions, and communication.
- Add buffer: Multiply by 1.25 (25% buffer for unknowns).
- Apply hourly rate: Hours × your rate = base price.
- Value adjustment: Is this project worth more to the client than your base price suggests? If a $2,000 website will generate $50,000 in revenue for the client, your price should reflect that value.
- Round up: Present clean numbers. $2,800 becomes $3,000. Clean numbers feel more professional.
Not sure about your rate? Use our Hourly Rate Calculator to find the right baseline, then use our Project Price Calculator to build a detailed quote with margins and rush fees.
Track Every Project's Profitability
Second Brain helps you track income and expenses per client, create professional invoices, and see your financial health at a glance — so you always know if your pricing model is working.
Try Second Brain Free