The Invoice I Was Too Embarrassed to Send

The Project Ran Long and I Knew It

I took a fixed-fee website project. The quote was based on my estimate of about thirty hours. Halfway through, I knew I was already past that.

I didn't say anything. I told myself I'd absorb the extra time and learn from it. I told myself the client relationship was worth protecting. I kept working.

By the time I delivered the final files, I had logged fifty-four hours.

The Invoice I Should Have Sent

The project was fixed fee, so technically I should have sent the agreed amount and moved on. That's what a clean fixed-fee engagement looks like.

But I had started to feel, somewhere around hour forty, that some of the overrun was genuinely due to scope that had expanded. Three new pages added mid-project. A revision to the navigation structure that required rebuilding two templates. An extra round of copy revisions because the client changed their mind about the tone.

Those felt like real additions. Not my miscalculation. Actual new work.

So I built an invoice that included the original fee plus a line item for the scope additions. I priced the additions based on my hourly rate and the time logged for those specific tasks.

And then I did not send it.

What Was Actually Stopping Me

I was afraid the client would push back. I was afraid they'd say the additions were included in the original brief. I was afraid of a confrontation.

But underneath that, there was something more specific. I was afraid because I had not told them upfront that the additions would cost more. I had just kept working and hoped to sort it out at the end.

That was my mistake and I knew it. So I sat on the invoice for three weeks, sending the original amount, absorbing about eight hundred dollars of real work because I didn't want to explain why I hadn't flagged it sooner.

The Version Where I Don't Lose That Money

Mid-project, when the navigation changes came in, I send a quick message. Something like: this revision will add roughly three hours outside the original scope, I'll track it separately and add a line to the final invoice.

Two sentences. That's it.

The client either agrees or we have the conversation then, when it is easy, when the project is still warm and nobody has paid yet and everything is in progress.

Instead I waited until the project was done and then lost my nerve entirely.

What I Changed

I started flagging scope additions in real time. Not aggressively. Not in a way that made clients feel nickel-and-dimed. Just a quick note when something clearly falls outside what we agreed.

I also started checking my time logs more regularly during projects. When I saw I was at twenty-five hours on a thirty-hour job, I did a quick check on whether I was on track. If the remaining work was going to push me over, I had a decision to make: absorb it, raise it, or flag it.

Making that decision mid-project is infinitely easier than making it after delivery.

The Invoice That Feels Hard to Send

If you are sitting on an invoice right now because the number makes you uncomfortable, I want to say something plainly.

Your discomfort is probably not about the number. It is about the fact that you did not have a conversation you should have had earlier.

You cannot fix that now. But you can send the invoice you can defend, learn from the gap, and handle it earlier next time.

Sitting on it does not help you or the client. It just keeps the money off your books.

Track your time, bill every minute.

Time-Trak is a native Mac and Windows time tracker with a floating timer, automatic screenshots, and one-click invoicing.

Free during beta.

macOS + Windows · Floating widget · Auto screenshots