Hourly billing charges the client for time at an agreed rate. Fixed price billing charges a set fee for a defined scope, whatever the hours turn out to be. For example, 60 hours at $150 an hour is a $9,000 invoice; a $9,000 fixed-price project stays $9,000 whether it takes 45 hours or 100, unless a change order is approved.
Worked billing example (hypothetical): the same website project billed both ways
| Hourly at $150 | Fixed price at $9,000 | |
|---|---|---|
| What the proposal says | "Estimated 50-70 hours, billed monthly at $150/hour, with a weekly hours report" | "$9,000 for the agreed pages and two revision rounds; changes outside scope by change order" |
| Invoice 1 | Month 1: 38 hours = $5,700 | 40% at signing = $3,600 |
| Invoice 2 | Month 2: 30 hours = $4,500 | 30% at design approval = $2,700 |
| Invoice 3 | None (work finished) | 30% at launch = $2,700 |
| Total billed | 68 hours = $10,200 | $9,000 |
| Who absorbed the 8 hours over the 60-hour estimate | The client paid $1,200 more | The agency earned $1,200 less margin |
Neither is always better. Hourly suits work where nobody can define the scope yet; fixed price suits defined deliverables you know how to estimate. The right choice depends on how clear the scope is, how good your estimates are, how much budget certainty the client needs, and the kind of work. This guide compares the two models, works through the profit math, and ends with a checklist you can apply to your next quote.
Key takeaways:
- Fixed price rewards efficiency but punishes poor estimation; hourly removes estimation risk but ties revenue to hours worked
- The right model depends on scope clarity more than client preference
- Hybrid models (fixed for defined scope + hourly for overflow) capture the strengths of both
- Documenting scope matters in both models; it is your main protection against margin loss
- Mid-sized agencies typically run a portfolio of both, applied selectively to project type
For broader pricing context, see agency pricing models and retainer vs project pricing.
Side-by-side: how each model works
Before diving into when to use each, here is the core comparison across the dimensions that matter most.
| Dimension | Hourly Billing | Fixed Price Billing |
|---|---|---|
| Revenue calculation | Hours logged x hourly rate | Fixed fee regardless of hours |
| Scope flexibility | High (client pays for changes) | Low (changes require change orders) |
| Estimation risk | Carried by client | Carried by agency |
| Efficiency incentive | Negative (faster = less revenue) | Positive (faster = more margin) |
| Cash flow pattern | Monthly invoicing based on hours | Milestone-based, often front-loaded |
| Scope creep impact | Revenue grows | Margin erodes |
| Required documentation | Time tracking, transparent reporting | Detailed scope, change order process |
| Client perception | Transparent but can feel uncertain | Predictable but can feel adversarial |
| Best for | Uncertain scope, ongoing work | Well-defined deliverables |
| Common pitfall | "Padding" accusations, scope drift | Underestimation, margin erosion |
How each model calculates profit
The profitability math is fundamentally different. Understanding it changes how you think about which model to choose.
Hourly profitability math
Revenue = hours logged x billable rate
Cost = hours logged x internal cost per hour
Margin = (billable rate - internal cost) x hours logged
Profit scales linearly with hours billed. Margin per hour is fixed. To grow:
- Raise rates
- Reduce internal cost (efficiency, offshoring, automation)
- Bill more hours (more people, more projects)
Fixed price profitability math
Revenue = fixed fee (agreed in advance)
Cost = actual hours x internal cost per hour
Margin = fixed fee - (actual hours x internal cost)
Profit depends entirely on how accurately you estimated hours. Better estimation = better margin. Faster delivery = better margin. Scope creep without change orders = direct margin loss.
Profit scenario comparison
Consider the same hypothetical project, a website build estimated at 60 hours, under both models.
| Scenario | Hourly @ $150/hr | Fixed Price @ $9,000 |
|---|---|---|
| Project takes exactly 60 hours | $9,000 revenue / $5,400 margin | $9,000 revenue / $5,400 margin |
| Project takes 45 hours (efficient) | $6,750 revenue / $4,050 margin | $9,000 revenue / $6,300 margin |
| Project takes 80 hours (scope creep) | $12,000 revenue / $7,200 margin | $9,000 revenue / $4,200 margin |
| Project takes 100 hours (underestimated) | $15,000 revenue / $9,000 margin | $9,000 revenue / $3,000 margin |
| Project takes 160 hours (badly underestimated) | $24,000 revenue / $14,400 margin | $9,000 revenue / -$600 margin (loss) |
(Assumes $60/hour internal cost.)
Notice the asymmetry. Under hourly billing, margin per hour is fixed and total margin grows with hours (as long as the client keeps paying). Under fixed price, finishing faster raises margin, but every extra hour comes out of it: at a $60 internal cost, this project breaks even at 150 hours and loses money after that. In practice the bigger risk is not the loss itself but the slow erosion, where a 60-hour project quietly takes 100 and earns half the planned margin.
The implication
Fixed price rewards estimation skill, scope discipline, and operational efficiency. Hourly eliminates estimation risk but transfers it to revenue volatility. New agencies tend to do better on hourly until their estimation discipline matures.
Pros and cons in detail
Hourly billing
Pros:
- Eliminates estimation risk. You get paid for every hour worked, even if the project balloons.
- Simple to explain. Most clients understand hourly rates intuitively.
- Accommodates flexibility. Unclear or evolving scope? Hourly is built for it.
- Lower barrier for new services. When you have not yet learned how long something takes, hourly is safer than fixed.
- Transparent billing. Clients can verify exactly what they are paying for if reports are detailed.
- Fair for exploratory work. Consulting, strategy, discovery and research, where the outcome is not defined in advance.
Cons:
- Penalizes efficiency. The faster and better you get, the less you earn for the same outcome. This is a real disincentive over time.
- Caps growth. Revenue is bounded by the number of hours your team can bill.
- Client skepticism. Some clients distrust hourly billing inherently, suspecting padded hours.
- Drift to discussions of effort. Conversations focus on hours rather than outcomes.
- Administrative burden. Tracking time, generating reports and justifying invoices all take time.
- Difficult to scale. Scaling means adding billable people. Linear, not exponential.
- Compensation challenges. Hard to pay junior staff well when their hours are billed at lower rates.
Fixed price billing
Pros:
- Rewards efficiency. Get faster, earn more margin on the same fee.
- Predictable for clients. Budget certainty builds trust and removes friction.
- Outcome-focused conversations. Discussions center on deliverables, not hours logged.
- Scalable. Revenue is not tied directly to hours, so better processes raise profit without raising headcount.
- Professional positioning. Fixed pricing signals confidence in your ability to deliver.
- Better cash flow management. Milestone payments structure revenue predictably.
- Margin upside. Operational improvements directly improve project margins.
Cons:
- Estimation risk. Underestimate and you eat the loss.
- Requires scope discipline. Vague scope + fixed price = certain margin disaster.
- Harder for new agencies. Reliable estimates need history on similar work.
- Can feel adversarial. Change orders sometimes create tension if not framed well.
- Demands strong documentation. Every detail needs to be specified upfront.
- Risk concentrated upfront. Wrong quote at month one affects the entire engagement.
Risk allocation: who carries the downside
A useful frame for choosing between models: who is best positioned to absorb the risk of being wrong?
| Risk Type | Hourly | Fixed Price |
|---|---|---|
| Scope expansion | Client (more hours billed) | Agency (margin erosion) |
| Estimation errors | Client (project costs more) | Agency (margin loss) |
| Efficiency improvements | Agency (less revenue) | Agency (margin upside) |
| Technical complexity surprises | Client (more hours needed) | Agency (more hours, same fee) |
| Client decision delays | Agency (less billable activity) | Agency (project drags) |
| Quality requirements creep | Client (more revisions billed) | Agency (revisions absorbed) |
Hourly transfers most risk to the client. Fixed price transfers most risk to the agency. The question is which party is in the better position to manage and absorb that risk.
For well-defined work the agency has done before, fixed price is fair: the agency is best placed to manage the risk. For exploratory or uncertain work, hourly is fair: neither side knows the answer, so paying for actual effort is more equitable.
Scope creep dynamics
Scope creep affects both models, but differently.
Scope creep under hourly
Scope creep still happens; the agency just gets paid for it. The risk shifts from margin to client satisfaction. When invoices exceed the budget the client had in mind, trust erodes quickly, even if every hour was real.
Mitigations:
- Provide budget estimates upfront ("we estimate 40-60 hours")
- Send weekly burn-down updates
- Set hour caps that trigger renegotiation conversations
- Bill in defined increments (15 or 30 minutes) with line-item detail
Scope creep under fixed price
Scope creep comes straight out of margin. Every "small" change you absorb without a change order is a gift, and small changes add up.
Mitigations:
- Documented scope of work with explicit inclusions and exclusions
- Written change order process for anything outside scope
- Revision limits ("two design rounds, anything beyond is at change order rate")
- Strong contract language tying acceptance criteria to scope
Use a scope of work generator to standardize scope documentation. See preventing scope creep for tactical approaches.
The universal rule
Whatever the model, document scope: what is in, what is out, what triggers additional billing and how changes are handled. It is the best protection you have.
When to use each model
Use hourly when
- Scope is genuinely unclear or exploratory (strategy, discovery, consulting, research)
- Project has high uncertainty (R&D, novel work, integration with unknown systems)
- Client explicitly prefers hourly transparency
- You are doing staff augmentation or ongoing flexible support
- Work is ad-hoc and difficult to define in advance
- You are new to a service category and still developing estimation skill
- Client wants the ability to redirect priorities mid-engagement
Use fixed price when
- Scope is well-defined (website with clear pages, branding deliverables, defined campaign)
- You have meaningful experience and reliable estimation in this work category
- Client wants budget certainty for procurement or internal approval
- You want to incentivize efficiency improvements on your team
- Project has clear milestones and deliverables
- You have strong scope documentation and change order discipline
- The work has been done before in similar form
Hybrid models that capture both strengths
Most mature agencies do not pick one model. They run a portfolio.
Model 1: fixed core plus hourly overflow
The main project is fixed price. Anything outside agreed scope is billed at an hourly rate documented in the SOW.
- Example: $35,000 fixed for the website build; out-of-scope requests billed at $175/hour
- Captures scope creep as revenue without aborting the fixed price
- Requires clean scope documentation to define what is "out of scope"
Model 2: hourly with a cap
Hourly billing with a maximum cap that triggers renegotiation if exceeded.
- Example: $175/hour, capped at 100 hours for $17,500 total before review
- Eliminates estimation risk while giving client budget certainty
- Useful for projects with moderate uncertainty
Model 3: hourly discovery, fixed implementation
Charge hourly for discovery and scoping; quote fixed price for implementation once scope is clear.
- Example: $4,500 hourly discovery (20-30 hours); fixed quote of $48,000 for execution
- Aligns both models with their best fit (uncertain discovery, defined execution)
- A structure procurement teams often find easy to approve
Model 4: milestone-based fixed price
A fixed price split into phases, each invoiced when its milestone is approved.
- Example: $48,000 build billed as $14,400 at signing, $14,400 at design approval, $19,200 at launch
- Keeps the client's budget certainty while bringing cash in as work progresses
- Lets you re-scope later phases (with a change order) if earlier phases reveal new requirements
Model 5: performance plus base hourly
Base hourly retainer plus performance bonuses for hitting outcomes.
- Example: $150/hour up to 40 hours/month; bonus payments for hitting quarterly KPIs
- Combines effort billing with outcome incentive
- Works for ongoing engagements (retainers) more than one-off projects
For pricing scenario modeling, use the project pricing calculator.
Client perception and sales dynamics
Different clients respond differently to billing models. Reading this correctly improves close rates.
Hourly tends to win with
- Technical buyers who value transparency
- Procurement-driven enterprise clients with hourly rate cards
- Clients who have been burned by fixed-price scope disputes
- Engagements with truly variable scope
- Risk-averse buyers who prefer paying for effort
Fixed price tends to win with
- Owner-operators and founders making fast decisions
- Buyers focused on outcomes and ROI
- Clients with budget approval processes that need a fixed number
- Smaller projects where total cost matters more than effort detail
- Clients who view hourly as "uncapped" risk
Track it yourself
Record the billing model on every proposal you send, along with the client type and the outcome. After a few quarters you will see which model wins with which kind of client in your own pipeline, which is more useful than any general rule.
Common mistakes that sink profitability
- Fixed price with vague scope. A very common cause of unprofitable projects. Define deliverables, exclusions, revision counts and acceptance criteria in writing.
- Hourly without estimates or caps. "We will bill as we go" leads to invoice shock and client disputes. Always provide a range and update the client when trending high.
- No change order process. Verbal "sure we can add that" erodes margin. Every scope change needs a written change order with price and timeline.
- Underestimating to win work. Lowballing fixed-price quotes to close the deal usually backfires. You resent the client and the work. Quote fairly; walk away if budget does not fit.
- Mixing models confusingly. If you start hourly, do not switch to fixed mid-engagement without explicit agreement. If you quoted fixed, do not start invoicing hourly for "extras" without a documented change order.
- Inadequate time tracking. Without disciplined time tracking, hourly billing becomes a guess, and you cannot tell whether fixed-price projects are profitable either.
Transitioning between models
Switching billing models mid-engagement requires careful communication. Clients react poorly to surprise changes.
Hourly to fixed price
This typically happens when a recurring engagement has enough data to scope cleanly. After several months of hourly work you have solid data on what tasks actually take.
How to propose:
- "Based on the last quarter, we average 30 hours per month on your account. We'd like to offer a fixed monthly fee of $X covering the same scope, with overflow priced at $Y/hour."
- Show the client the historical data
- Position as budget certainty for them and operational efficiency for you
- Lock in the fixed model with a defined term (6-12 months)
Many clients welcome this because it gives them budget certainty.
Fixed price to hourly
This shift usually signals that scope has become too unpredictable for fixed pricing. If change requests are constant and your margin keeps eroding despite change orders, hourly may be more sustainable.
How to propose:
- "We're seeing a lot of priority shifts each month, and we want to give you the flexibility to redirect work without formal change orders. Moving to hourly gives you that flexibility while making the engagement sustainable for our team."
- Frame as benefit to client
- Set hour ranges and budget guardrails so the client is not exposed to runaway billing
Mid-project model changes
Avoid switching mid-project. Finish the current phase under existing terms, then propose the new model for the next phase or renewal. Changing terms mid-stream breeds distrust even when objectively fair.
Decision framework: which model for your next quote
Run this checklist for any new engagement:
| Question | If Yes | If No |
|---|---|---|
| Is the scope clearly defined with measurable deliverables? | Lean fixed | Lean hourly |
| Have you done this exact type of work 3+ times before? | Lean fixed | Lean hourly |
| Does the client have hard budget approval requirements? | Lean fixed | Lean hourly |
| Will scope likely evolve significantly mid-engagement? | Lean hourly | Lean fixed |
| Is your team experienced enough to estimate accurately? | Either works | Lean hourly |
| Do you have strong scope and change order documentation? | Either works | Avoid fixed |
| Is the work mostly strategic, exploratory, or advisory? | Lean hourly | Lean fixed |
| Is total project value above $25K? | Either works | Lean fixed (simpler) |
If 4+ answers point to one model, use that model. If split, consider a hybrid structure.
Frequently asked questions
Which model is more profitable for agencies?
Fixed price typically has higher margin upside but also higher downside risk. Hourly has more predictable margins but caps revenue. Over a year, either model can be profitable when scope is well managed. Scope discipline is a bigger lever than the choice of model.
How do I avoid hourly padding accusations?
Three habits eliminate them: detailed time entries with task descriptions (not just "client work, 4 hours"), weekly invoice transparency rather than monthly surprise bills, and proactive communication when hours are tracking higher than estimated. Clients distrust hourly billing when they feel surprised, so remove the surprises.
Can I charge fixed price without doing detailed discovery first?
You can on small, familiar projects, but not on larger ones. Skipping discovery on a large fixed-price project is a common route to underestimation. For bigger projects, sell a paid discovery phase first; it filters out unserious buyers and gives you the information to quote accurately. See our client discovery process.
What hourly rate should I charge?
Start from cost, not from competitors. The freelance rate calculator helps you work out your true cost base (salaries, overhead, taxes) and add your target margin. Then check the result against what agencies in your specialism and market publish. Scarce specialist skills command higher rates.
When does a hybrid model make more sense than picking one?
Whenever the work has both defined and undefined components. Discovery plus implementation, a base retainer plus project work, or fixed deliverables plus flexible overflow all suit a hybrid structure. The cleanest hybrid is fixed price for clearly scoped work plus hourly for explicit overflow defined in the SOW.
Choose the right billing model for your next engagement
Hourly vs fixed price is not about one being universally better. It is about fit: to the project, the client, your operational maturity and your risk tolerance. Hourly suits uncertain, flexible, and ongoing work where estimation is hard. Fixed price suits defined projects where you can estimate well and want to reward efficiency.
Whatever you choose, document scope, communicate openly about budgets and use contracts that protect both sides. Matching the billing model to the work, rather than using one model for everything, is an advantage in itself.
AgencyPro supports fixed-price and recurring services with invoicing on every plan, and hourly and credit-based services with time tracking on the Pro plan. Book a demo to see how it handles hourly, fixed-price and hybrid engagements.
