Nobody loses money on a project in one go. It goes an hour at a time: a "quick" copy swap, one more round of tweaks, a format the client forgot to ask for, a call that wasn't in the plan. Each one feels too small to put a price on. That's exactly why they add up.
This guide does two things. It shows you what those small requests cost you over a year, using your own numbers, and it gives you three habits that stop the leak without making you the difficult one.
Why small requests never get billed
If you're not billing them, it's rarely because you forgot. It's usually one of these:
- It feels petty. Charging $60 for twenty minutes of work feels like nickel-and-diming a client who is paying you thousands.
- You have no price ready. Working out a fair number takes longer than doing the job, so you just do the job.
- The file is already open. By the time you've thought about it, it's done.
- You're afraid of the reaction. You'd rather lose an hour than risk an awkward email.
All four are reasonable on the day. The trouble is that they repeat on every project, with every client, all year.
Run your numbers
Put in your hourly rate, how many projects you finish in a year, and a fair guess at the hours per project that you did and never billed. Be honest: count the extra revision rounds, the small fixes after "final", and the calls you didn't plan for.
rate × hours × projects
If the number surprises you, you're in good company. Most people have never added it up, because each piece was too small to notice.
Where the hours actually go
When freelancers go back through a finished project, the unbilled time tends to sit in the same few places:
- Revision rounds past the ones you planned. Round four is rarely in anyone's quote.
- "While you're in there" jobs. Small additions that ride along with a change you agreed to.
- Extra formats and exports. One more size, one more file type, one more version for a different platform.
- Fixing things the client supplied late or changed. New copy after layout, new photos after edit.
- Meetings and calls. A weekly check-in nobody priced in.
None of these are wrong to do. They're wrong to do for free without either of you noticing.
Three habits that stop the leak
1. Write down what's included, in numbers
"Website design" can stretch forever. "Five page designs, two rounds of revisions on each, final files in PNG and SVG" can't. When the scope has numbers in it, both of you can see when a request goes past it, and you no longer have to argue about it. You just point at the agreement.
2. Have a price ready before you're asked
The hardest part of charging for a change is working out the number on the spot. Decide in advance how you price extras: your hourly rate, a fixed price per extra revision round, or a minimum charge for small jobs. Our guide to pricing a change request in 60 seconds walks through it, with a calculator and a reply you can copy.
3. Say yes, with a price
You don't have to refuse anything. You only have to make the cost visible before you start. Something like:
Happy to add that. It's outside what we agreed, so it would be 2 hours, $150. Want me to go ahead?
Most clients say yes. Some say "actually, it can wait", which tells you how much they really needed it. Either way, you stop working for free without anyone getting upset.
What about the ones you've already given away?
Don't try to bill a client for last year's favours. That damages the relationship far more than it recovers. Instead:
- Start counting now. Log extras as they happen, even the ones you decide not to charge for.
- Make gifts visible. If you do something free, say so: "No charge for this one; normally it would be $90." The client learns that extras have a value.
- Use the record at renewal. "The last project included 9 hours of extras at no charge" is a strong opening for a better scope or a higher price next time.
The aim isn't to charge for every minute. It's to decide, each time, whether you're giving something away, instead of finding out at the end of the year that you gave away a month.