The Client I Invoiced From Memory and Regretted It

The project wrapped up on a Thursday. The client was happy. I was tired. I told myself I'd log everything properly over the weekend.

I didn't.

Monday came and I sat down to write the invoice. I had a few notes in a notebook, some emails, a Slack thread I half-remembered. I did the math in my head, rounded up a little to feel safe, and sent it.

She replied within ten minutes.

"This doesn't match what we discussed. Can you send me a breakdown?"

I couldn't. Not a real one. I had nothing that added up to anything defensible.

The Number I Made Up

I had estimated around 22 hours. That felt right. That was the number I invoiced.

When I actually tried to reconstruct the work, pulling calendar blocks and email timestamps and browser history, I got to maybe 14 hours I could prove. There were definitely more hours in there. I knew I'd worked late twice. I knew there was a full afternoon lost to a round of revisions she'd requested verbally on a call.

But I couldn't show her those hours. I just had a number I'd made up and a memory I couldn't back up.

We settled on 17. I called it a discount. She called it fair. I called it a lesson I was going to pay for every time I thought about it.

What I Lost Was More Than Money

The direct loss was five hours at my rate. That stung. But the worse part was the conversation.

I had to negotiate with a client over whether I was telling the truth. That's not a position you ever want to be in. She wasn't hostile about it, but the trust shifted. She hired me one more time after that, paid promptly, and then went quiet.

I've thought about that a lot. Not the invoice. The trust.

When you can't show your work, you're asking someone to take your word for it. Some clients will. Some won't. And even the ones who do start wondering.

The Habit I Built After That

I started using Time-Trak the following week. Not because I read a review or someone recommended it. Because I needed something that would stop me from ever being in that position again.

The thing that changed everything wasn't the timer. It was the screenshots.

Time-Trak takes random screenshots while the timer is running. Not every five minutes on a rigid schedule, randomly, so the record feels natural and complete. When a client questions your hours, you're not arguing about trust. You're showing them a timeline of what happened.

The client who questions your invoice at 22 hours shuts down the conversation immediately when you can show her screen captures from every work session with timestamps attached.

The Part I Had Wrong

I used to think time tracking was for big agencies. For people billing 80-hour weeks across a dozen clients. Not for a freelancer running three projects at once and trying to stay sane.

That was wrong. Time tracking matters most when your memory is the only other option.

Memory is not a billing system. It's not a legal record. It's not something you can attach to an invoice and call documentation.

You will remember the hard afternoon. You will forget the two-hour call that ran over. You will lose the revision cycle that happened over a weekend when you were half-checked-out.

That's not negligence. That's just how memory works. It's not built to log billable hours.

What I Do Now

Timer goes on when work starts. Timer stops when it stops. I write a quick note in the entry before I close the session. Takes maybe 15 seconds.

At invoice time, I open the report, review the entries, and build the invoice from real data. It takes less time than the argument I had with that client over five disputed hours.

I've never had a client question an invoice since. That's not luck. That's what a paper trail does.

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