Fixed fee or hourly for extra client work?
Choose fixed-fee or hourly pricing for a client change request using a worked comparison, an uncertainty checklist and clear approval language.
The best pricing model for extra work depends on what you can define before you start. A fixed fee is easier to evaluate when the result and dependencies are clear. Hourly work can fit an investigation whose outcome is uncertain. The mistake is choosing either model without saying what the client is approving and what happens when the assumptions change.
Classify the uncertainty before choosing a price
An extra service page based on an existing layout may be straightforward: approved copy, one image, one review round and a known publishing process. Debugging an unfamiliar integration is different. You may know the symptom but not the cause, the quality of the documentation or whether the vendor will cooperate.
Write down what is known and unknown. For each unknown, ask whether you can resolve it cheaply before quoting. A short inspection can turn a vague task into a defined deliverable. If it cannot, quote the inspection separately and use its findings to propose the implementation.
This is a useful way to avoid both extremes: hiding a large risk allowance inside a fixed fee or offering an hourly arrangement with no meaningful limit. The client needs a decision they can understand, and you need a boundary you can manage.
- Known result and stable inputs: consider a fixed fee.
- Unknown cause or dependency: consider a bounded investigation.
- Changing priorities: consider hourly work with a budget and review point.
Compare the same work under both models
Consider an illustrative request expected to take ten hours, with a plausible range of eight to fourteen. At a selling rate of $120 per hour, hourly billing would be $960, $1,200 or $1,680 at those three outcomes. A fixed quote of $1,400 stays $1,400 if the agreed scope stays the same. It transfers more estimating risk to the provider and offers more price certainty to the client.
That comparison says nothing about whether $120 or $1,400 is right for your business. It simply makes the trade-off visible. A fixed fee can be commercially sensible when your process is repeatable. An hourly arrangement can be sensible when the client controls changing inputs and wants flexibility.
Do not confuse a selling rate with a delivery cost. Use actual planning costs when checking margin, and use the pricing guide to separate your estimate from the amount you ask the client to approve.
Scroll sideways to see all columns.
| Actual effort | Hourly at $120 | Fixed fee |
|---|---|---|
| 8 hours | $960 | $1,400 |
| 10 hours | $1,200 | $1,400 |
| 14 hours | $1,680 | $1,400 |
Use a paid discovery step when the work is unclear
For an unfamiliar integration, propose an investigation with its own output. For example: inspect the current setup, reproduce the problem, identify the likely cause and deliver an implementation recommendation. The deliverable is the diagnosis, not a promise to fix every possible issue within the investigation budget.
An illustrative approval could read: “Authorize up to four hours at the agreed rate to investigate the form-to-CRM failure. I will stop at the limit and send findings, remaining uncertainties and a separate implementation proposal.” State whether unused time is billed and whether the limit includes the written handoff.
This approach only works if you honor the stop point. Put the review on your calendar, record the time and contact the client before going beyond the authorization. If access is missing, use the remaining time carefully rather than treating the cap as a target to spend.
Write the approval in terms of control
A fixed-fee approval should name the deliverable, included review, required inputs, exclusions and delivery assumption. An hourly approval should name the work category, rate, budget limit and reporting cadence. Both should explain how a new request will be handled. “We will see how it goes” is not a useful budget control.
For hourly work, distinguish an estimate from a cap. An estimate predicts likely effort. A cap is a stop-and-review boundary. If a client approves an estimate but assumes it is a cap, the disagreement arrives exactly when the project is already under pressure. Use those words deliberately.
The client change request email provides a practical way to present options. Keep the explanation short enough to answer, but attach enough detail that the selected option can be reconstructed later.
- Fixed fee: “This amount covers these named outcomes.”
- Hourly estimate: “This is the expected effort; it may change.”
- Hourly cap: “Work pauses before exceeding this authorization.”
Review the model when the evidence changes
A pricing model is not a commitment to ignore new information. If an approved third-party dependency changes, explain its effect and propose a decision. If your own estimate was simply too optimistic for the agreed fixed scope, distinguish that from a client-requested addition. The client should not have to diagnose your internal estimating error.
After delivery, compare the predicted range with actual effort. Track which work packages are repeatable enough to quote confidently and which deserve discovery. Over several projects, this gives you a better basis for choosing a model than a universal rule that all client work should be fixed or hourly.
Use Clearcut to record the baseline and the proposed change, then check the calculation with the free scope change calculator. If you need saved online records and client review links, the plan comparison explains the account options.