The First Invoice I Was Too Ashamed to Send

The project took 34 hours. At my rate, that was $5,100.

I sent an invoice for $3,200.

I changed the number because I was scared. I'd expected the project to take 20 hours and I didn't want to explain why it took 14 more. So I just absorbed the difference and told myself it was the right thing to do.

It wasn't. It was the easy thing to do. There's a difference.

Why I Changed the Number

I was newer to freelancing. I didn't have a lot of data on how long my work actually took. When I estimated 20 hours, I genuinely believed it. When it ran over, my first instinct was to blame myself.

Maybe I was slow. Maybe I hadn't scoped it properly. Maybe the client would think I was incompetent if they saw how far over I went.

So I hid it. I paid myself less so I wouldn't have to have an uncomfortable conversation.

What the Hours Actually Showed

Here's the thing I couldn't see at the time. I had been tracking my hours on that project. The log was accurate. And when I went back and looked at what those 34 hours actually contained, most of the overrun was legitimate.

Three extra hours of revisions the client requested verbally on a call I hadn't documented as a scope change. Four hours rebuilding a section after they sent new brand guidelines halfway through. Two hours of export and delivery work that wasn't in my original estimate.

That's nine hours that weren't my mistake. They were scope additions and surprise requirements. I had the timestamps. I had the entries. I had the evidence.

I discounted the invoice anyway because I hadn't connected the data to my confidence yet.

What That Pattern Costs Over Time

If you discount every invoice where you go over estimate, you're training yourself to eat overruns as a matter of habit. You also train clients to expect that you'll absorb problems silently.

The next project they'll give you another soft deadline and assume you'll figure it out. Because you always do. Because you never say anything.

I did this for most of my first year. Looking back at my invoicing history versus my tracked hours from that period, I underbilled by somewhere around $8,000 across twelve months. Not because clients pushed back. Because I preemptively cut my own invoices before sending them.

The Review Step I Added

Now I have a rule. Before I generate any invoice, I read through the time entries for that project. Every single one.

I look for two things. Entries that reflect client-requested changes, and entries that show unexpected complexity that wasn't in the original scope.

If I find them, I decide consciously whether to include them, adjust them, or note them as overrun. Sometimes I absorb them. But it's a choice, not a reflex.

Time-Trak makes this easy because all the entries are right there with notes. I can read through the log of a whole project in a few minutes. I can see when the scope shifted and what it cost me.

That review step alone has probably added $15,000 to my invoicing over the last two years. Not because I started padding hours. Because I stopped cutting them out of anxiety.

What I'd Tell Myself Then

The hours don't lie. If the tracker says 34, you worked 34.

You don't owe a client a discount because the project took longer than you estimated. Estimates are guesses. Hours are facts. Learn to present the facts clearly and let the client respond.

Most of the time they pay. And the ones who push back give you a conversation worth having.

Send the invoice.

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