How a fixed fee becomes a loss
A project is agreed for a fixed fee. Then come a few small requests: another revision, an extra version, a quick call, a late change of direction. Each seems minor and each is agreed to politely. By the end, the hours have swelled, and the fee that looked fair at the start has become a poor wage.
Counting the extra hours turns a vague feeling into a figure you can act on.
Record the baseline and the extras
At the start, note the hours you expect the agreed scope to take. As the project proceeds, log time against two columns: planned work and extra work. The extra column captures anything that was not in the original description, however small.
At the end, compare the totals. If planned work took 20 hours and extras took 12, then the project cost 60 percent more time than quoted, and the effective hourly rate fell by about a third.
| Item | Hours | Share |
|---|---|---|
| Planned work | 20 | 62% |
| Extra revisions | 7 | 22% |
| Added requests | 5 | 16% |
Where the extras usually come from
Look for patterns. Some clients habitually request many revisions. Some projects start with unclear briefs, which leads to rework. Some extras arise because a stage was skipped. Knowing the source tells you which part of your process or contract needs tightening.
- Unclear brief at the start
- Open-ended revision rounds
- Decisions made by several people
- New requests added without a new price
Tools for keeping the scope visible
A short written scope listing deliverables and the number of included revisions is the foundation. When a request falls outside it, a courteous note such as that can be added for an extra fee, with the estimated time, keeps the boundary clear without damaging goodwill.
Many clients appreciate the clarity. Those who do not are worth knowing about before the next project.
Pricing the next project better
Use the extra-hour figure when quoting similar work. If previous projects of this kind ran thirty percent over, build a similar allowance into the price or the number of included revisions. A quote that reflects reality is fairer to both sides.
Putting a price on the lesson
After a project overrun, write a one-line summary of what it cost in lost income. For example, twelve extra hours at your target rate equals a given amount. Seeing the money value of unmanaged scope makes the case for firmer boundaries in the next agreement.
Phrases that protect the boundary
Short, neutral phrases are useful: that sits outside the agreed scope, it can be included for an additional fee, or swapped for another item. They state a fact without blame, and most clients understand them. Having them ready removes the discomfort of improvising when a request arrives.
A closing review of each finished project takes five minutes: planned hours, actual hours, main cause of any difference, and one change for next time. After a dozen such notes, the pattern of your own estimating errors becomes clear, and corrections follow almost automatically.
If a client disputes the extra charges, present the log calmly: the dates, the requests and the hours. Facts presented without heat usually produce a fair outcome, whether that is payment, a compromise or an agreement to cap future requests. Either way, the record keeps the discussion grounded.
Learning without bitterness
The goal of counting extras is not to blame clients but to improve your process. Some of the overruns will be your own doing, such as underestimating or avoiding a difficult conversation. Both are fixable once they are visible.
Useful ideas start with a clearer picture of your own spending.
Explore your reports
