A Five-Minute Change Note: Pricing the Mid-Project 'Quick Favour' Without the Awkward Pause

It's Tuesday afternoon. You've just sent the second draft, the client has replied with a thumbs-up, and you're mentally moving on to the next job. Then the phone rings. 'Can you just move the logo to the left, swap the hero photo, and add a little section about the offer?' You say yes because each piece sounds tiny. Three weeks later, eight small yeses have stacked up, the deadline has shifted twice, and the fixed fee now covers about 30% more work than anyone wrote down.

This isn't a story about difficult clients. It's a story about verbal requests having no edges. Nobody knows if the change is included, when it's due, or what it displaces. And because it was never written down, nobody can prove otherwise. The fix isn't a 12-page contract. It's a five-minute habit.

Why the verbal request is expensive

The cost isn't the five minutes. It's the context switch, the re-export, the re-upload, the email trail, and the bit of the original brief you quietly drop to make room. Fixed fees only work when scope has a boundary. A verbal change redraws that boundary in the client's favour without anyone noticing.

That's why the innocent-sounding request is so corrosive. It doesn't look like a commercial decision. It looks like being helpful. And being helpful is not the same as being profitable.

The five-minute change note

Before you touch the file, write four lines in an email or project thread. Not a legal document. A note.

• What is changing: 'Add a fourth product tile to the homepage grid.'
• What it affects: 'One extra design round, plus mobile layout and two image crops.'
• What it costs or displaces: '£X plus VAT, or we swap it for the testimonials section in phase two.'
• When you need a decision: 'If you're happy, I'll book it in for Thursday.'

That's it. Send it. The client can reply 'yes please'. You now have a written variation, a price, and a timestamp. If they say 'I thought that was included', you have a calm place to start the conversation rather than a vague memory and a slightly defensive tone.

Set a tripwire, not a maze

You don't want to send a change note for every comma. Pick a threshold. A workable one for a small studio: anything that takes more than 30 minutes, changes an approved route, adds a new deliverable, or pulls in a third party gets a note. Under that, absorb it and log it — but log it.

Keep a simple variation log in the project folder: date, request, decision, time, cost. After a month you'll see the pattern. Maybe it's a particular client. Maybe it's a particular stage of the project. That's the real value: the log tells you where your fixed fee is leaking, long before the final invoice makes it obvious.

The script for pricing without the flinch

The awkward bit isn't the admin; it's saying a number. Here's a script that keeps it neutral:

'Thanks — that's doable. It sits outside the agreed scope, so I'd treat it as a variation: [one sentence on impact]. I can either add it for £X plus VAT and keep the current deadline, or fold it into phase two at no extra cost if we push the launch by a week. Which works better?'

Notice what it doesn't do. It doesn't apologise. It doesn't call the client unreasonable. It doesn't pretend the work is free. It gives a choice. Most clients take one. The ones who don't were never going to be profitable on a fixed fee anyway.

Make the note part of the handover, not a confrontation

Language matters. Call it a change note, not a warning. Put the template in your onboarding pack, alongside the schedule and the feedback process. When it's normal at the start, it's normal at week six. If you only introduce it mid-project, it feels like a penalty. If you introduce it before the first invoice, it feels like professional housekeeping.

What about goodwill?

Keep some. A small studio runs on relationships. The point isn't to charge for every tweet; it's to stop the cumulative drift that makes you resent the project. If you decide to absorb something, say so: 'I'll fold that in as goodwill this time, but I've noted it so we can see the pattern.' That sentence does two things: it preserves the relationship and it stops the next request from arriving with the same assumptions.

The paper trail is part of the product

Your final files are part of the product. So is the paper trail that explains why the final files look the way they do. A variation log and a few change notes are not bureaucracy; they're the difference between a fixed fee that works and a fixed fee you regret. Next time the phone rings with a 'can you just', you'll have a five-minute habit that keeps the project — and the relationship — on the rails.