The Client Who Asked Me to Prove My Hours

The email arrived on a Tuesday afternoon. A client I had worked with for almost two years. Good relationship. Paid reliably.

The email was polite. It said the hours on my latest invoice seemed high and asked if I could walk them through how I had arrived at the total.

I read it three times.

Then I opened my notes to find the breakdown.

There was no breakdown.

What I Had Instead of a Record

I had a rough number I had written in a project folder. I had some emails I could use to show roughly when work had happened. I had my own memory of how long things had taken.

None of that was a record. It was a reconstruction. And reconstructions always favor the person doing the reconstructing, which made mine feel suspect even to me.

I spent most of that afternoon trying to piece together a justification for my own invoice. I found enough to send a reasonable reply. But I knew it was not airtight. And the client knew it too, because they came back and asked me to just take twenty percent off the total.

I did. Not because they were right. Because I could not prove they were wrong.

That was $480 I lost to a conversation I should have been able to end in two minutes.

The Problem Was Not the Client

I spent a few days being irritated at the client. That was easier than being honest with myself.

The real problem was that I had built a billing process with no foundation. I was sending invoices based on estimates and memory and hoping no one would look too closely. That works until it does not. And when it stops working, you are the one who absorbs the loss.

A client questioning an invoice is not unusual. Invoices get questioned. What matters is whether you can answer the question.

If your answer is a detailed time log with task descriptions and timestamps, the conversation is short. If your answer is a folder of notes and a vague memory, the conversation is expensive.

What I Set Up After That

I started using a time tracker the following week. Desktop app, running timer, and automatic screenshots at random intervals so there was a visual record of what I had been working on.

The screenshots felt strange at first. I was not used to having that kind of documentation. But within a month I stopped thinking about them and just worked.

A few months later a different client questioned a line item on an invoice. I pulled up the time log, sent them a summary with task descriptions and hours broken down by day, and offered to send the full report if they wanted it.

They wrote back within an hour. Paid the invoice in full. Said the breakdown was helpful and appreciated.

Same situation. Completely different outcome. The only thing that changed was that I had actual records.

The Shift That Stuck

I stopped thinking of time tracking as an administrative chore after that second conversation. It became something else. Evidence. Not because my clients are adversarial. Because questions happen, memory is unreliable, and the only thing that holds up under scrutiny is a real log.

The floating timer I run now takes almost no thought. I start it when I start. I stop it when I stop. At the end of a project I have a complete record instead of a folder of guesses.

When I send an invoice now I am not hoping nobody looks closely. I am fine if they do. I have the receipts.

That shift, from hoping to knowing, is the actual value of tracking your time. It is not about the software. It is about being able to stand behind your own numbers without flinching.

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