Derek used to bill $200/hr for brand strategy work. A typical project took 40 hours, earning $8,000. Then he got better. The same quality work now took him 25 hours. His income dropped to $5,000 per project.
He was literally being punished for getting better at his job.
When he switched to project pricing at $15,000 flat, two things happened: clients stopped questioning his hours, and his effective rate jumped to $600/hr. Same work. Same quality. Better outcome for everyone.
The 5 Traps of Hourly Billing
Hourly billing feels safe. It's not. It just hides the risk.
1. You get punished for being fast
The better you get, the less you earn. A task that took you 10 hours as a junior now takes 3, but you bill 3 hours at the same rate. Your expertise is literally reducing your income.
A consultant who's 3x faster than they were 5 years ago earns 3x less per project on hourly billing.
2. Clients focus on hours, not outcomes
"Why did that take 8 hours?" is a question you should never have to answer. When clients buy hours, they scrutinize hours. When they buy outcomes, they evaluate results.
Every hour-justification email costs 15-20 minutes. Over a year, that's 50+ hours of unpaid administrative work.
3. Scope creep is invisible
On hourly billing, scope creep doesn't trigger a conversation. It just means more hours. The project grows silently and the client gets a surprise invoice.
Projects routinely run 30-50% over initial estimates. Neither you nor the client is happy.
4. Your income has a ceiling
There are only so many hours in a week. At $250/hr × 30 billable hours/week × 48 weeks, your max is $360K. Project pricing breaks that ceiling because it's tied to value, not time.
You're trading the one resource you can't make more of (time) for money. There's always a limit.
5. It creates adversarial dynamics
The client wants fewer hours. You need more hours to do good work. You're on opposite sides of every conversation. Project pricing puts you on the same side: both focused on outcomes.
Adversarial dynamics erode trust. Trust erosion leads to micromanagement, scope disputes, and churn.
4 Project Pricing Models
Each one fits a different type of engagement. Pick the one that matches your work.
Fixed Project Fee
Agree on a flat price for a defined scope of work. Client knows the cost upfront. You manage your time to deliver within the budget.
Best for: Repeatable deliverables with predictable scope: website redesigns, brand identities, strategy decks, audits.
Formula: (Estimated hours × your target hourly rate) × 1.3-1.5 buffer + value premium
Derek prices website projects at $15,000 flat. His average is 40 hours of work. If he finishes in 30 hours, he earns $500/hr effective. If it takes 50, he learns to scope better next time.
Risk: You eat the cost of scope creep. Mitigate with clear scope documents and change-order processes.
Value-Based Pricing
Price based on the outcome value to the client, not the effort to you. If you save them $500K, charging $50K is a 10x return.
Best for: High-impact strategic work: revenue optimization, cost reduction, process redesign, market entry.
Formula: 10-20% of the measurable value you'll create (or a significant fraction of cost savings)
Rachel helped a client restructure their sales process. Expected impact: $800K in additional revenue. She charged $120K, which was 15% of the value. The client was thrilled. It took her 80 hours of work.
Risk: Requires the ability to quantify outcomes. Doesn't work well for exploratory or research-phase work.
Retainer with Deliverables
Monthly fee for a defined set of deliverables or outcomes, not a bucket of hours. The client gets predictable cost and you get predictable revenue.
Best for: Ongoing advisory, content, marketing, or operational support. Any relationship that's continuous.
Formula: Monthly deliverable value + access/availability premium. Minimum 3-month commitment.
James charges $5,000/month for a retainer that includes: weekly strategy call, monthly report, unlimited Slack access, and quarterly planning session. Some months it's 8 hours of work. Some months it's 20. It averages out.
Risk: Retainers can drift into "do everything" territory. Define deliverables explicitly and review quarterly.
Tiered Packages
Offer 3 options at different price points with different scope levels. The client self-selects based on budget and needs.
Best for: Productized services, consulting engagements, any proposal where the client might say "that's more than we budgeted."
Formula: Base package (core deliverable) / Standard (core + enhancements) / Premium (full-service). Price the middle option at your target.
Brand strategy package: Essential ($8K, positioning + messaging) / Growth ($15K, + content strategy + competitive analysis) / Enterprise ($25K, + implementation support + 90-day advisory). 70% of clients pick the middle tier.
Risk: Too many options create decision paralysis. Always offer exactly 3. Make the middle option the obvious choice.
The Math: Hourly vs. Project vs. Value
Same deliverable. Same quality. Very different economics.
| Scenario | Price | Hours | Effective Rate |
|---|---|---|---|
| Current state (hourly) | $200/hr | 40 hrs | $200/hr |
| Fixed fee (conservative) | $12,000 flat | 40 hrs | $300/hr |
| Fixed fee (efficient) | $12,000 flat | 28 hrs | $428/hr |
| Value-based | $25,000 flat | 40 hrs | $625/hr |
The Project Scoping Checklist
Good scoping prevents 90% of project pricing problems. Cover all 6 before quoting.
1. Define the deliverables explicitly
Not "marketing strategy" but "45-page marketing strategy document including competitive analysis, channel recommendations, 90-day execution plan, and budget allocation." The more specific, the fewer disputes.
Common mistake: Vague scope like "consulting support" or "strategic guidance": these mean different things to every person.
2. List what's NOT included
Exclusions are as important as inclusions. "This project does not include: implementation, ongoing revisions after approval, additional research rounds, or third-party tool costs."
Common mistake: Assuming the client knows what's out of scope. They don't. If it's not written down, they'll expect it.
3. Define revision rounds
"Two rounds of revisions included. Additional revision rounds available at $X per round." This prevents infinite revision loops.
Common mistake: Unlimited revisions. There's no such thing. There's just unpriced revisions that eat your margin.
4. Build in a change-order process
"Scope changes beyond the original SOW will be documented in a change order with updated timeline and pricing. Both parties must approve before work begins."
Common mistake: Absorbing "small" requests that add up to 30% more work. Every change, no matter how small, gets documented.
5. Set payment milestones
50% upfront, 25% at midpoint, 25% on delivery. Or 100% upfront for smaller projects. Never start work with 0% paid.
Common mistake: Net-30 on the full amount after delivery. You've done all the work with zero commitment from the client.
6. Include a timeline with dependencies
"Client feedback due within 5 business days of each deliverable. Delayed feedback shifts the timeline by the equivalent number of days."
Common mistake: Committing to a deadline without protecting yourself from client delays.
How alfred_ Makes Project Pricing Sustainable
Project pricing works best when you're efficient. alfred_ makes you more efficient.
- +Automated email triage cuts admin time, freeing more hours for billable delivery
- +AI-drafted replies handle client communication faster, protecting your margins
- +Task extraction from emails ensures no deliverable or deadline gets missed
- +Daily briefings keep you on top of multiple projects without context-switching
- +Meeting prep is automatic: you walk into client calls fully briefed
Try alfred_
Price Smarter. Earn More. Work Less.
alfred_ handles the admin so your project margins stay healthy. Start free.
Try alfred_ FreeFrequently Asked Questions
How do I estimate project hours accurately?
Track your time on 3-5 similar projects. Average the hours. Then add 30-50% buffer for client communication, revisions, and unexpected complexity. Most people underestimate by 30%, and the buffer corrects for that. Over time, your estimates will get tighter.
What if the project takes way longer than I estimated?
That's the risk of project pricing, and it's why the buffer matters. If you consistently go over estimates, your scoping or estimation process needs work. Track actuals vs. estimates on every project and adjust your formula. After 5-10 projects, your estimates should be within 15%.
Should I show the client my hourly rate when pricing a project?
No. The whole point of project pricing is decoupling price from time. When you say "$15,000 for this project," the client evaluates whether the outcome is worth $15,000. When you say "$200/hr × 75 hours," they evaluate whether each hour was necessary.
How do I handle a client who insists on hourly billing?
Some clients have procurement policies that require hourly billing. In that case, set your hourly rate high enough to account for the efficiency penalty, and cap the total at a project-equivalent amount. Or offer a "not-to-exceed" estimate that functions like a project fee with hourly tracking.
When should I still use hourly billing?
Hourly works for: exploratory/discovery work where scope is genuinely unknown, ongoing advisory where deliverables change weekly, and very small engagements (under $2,000) where formal scoping costs more than it saves. For everything else, project or value-based pricing is better.
How do I transition existing hourly clients to project pricing?
At the next project or contract renewal, propose a project-based option alongside the hourly option. Frame it as a benefit: "For this next phase, I can offer a fixed fee of $X. That gives you cost predictability and includes [scope]." Most clients prefer knowing the total cost upfront.