The Day a Client Asked How Long Something Took

It was a routine check-in call. We were about six weeks into a project and things were going fine, or so I thought.

About ten minutes in, the client asked a simple question.

"How long did the research phase end up taking? We're trying to budget the next stage."

I should have been able to answer in five seconds. Open my tracker. Read the number. Done.

Instead I said, "Let me pull that together and send it over."

What Happened Next

I spent an hour after the call trying to reconstruct the research phase from calendar entries, email timestamps, and a rough log I'd been keeping in a notes app. The notes were incomplete. The calendar entries didn't capture the actual working time, just the meetings. The emails helped a little but not enough.

I came up with a number. I have no idea if it was accurate. I sent it over and hoped.

The client came back an hour later and said the number seemed lower than they expected. They asked if I was sure.

I wasn't sure. I told them I was. That was the beginning of a trust problem I never fully repaired.

The Actual Issue

I had been tracking time on and off throughout the project. Some days I remembered to run the timer. Some days I meant to log it manually afterward and didn't. Some tasks I tracked in detail. Others I skimmed past because they felt too small to bother with.

The result was a time log full of holes. Useful in a vague sense. Useless when someone asked a specific question.

The research phase alone probably had eight to twelve hours of real work in it. I could account for maybe five hours in my logs. The rest existed somewhere between my memory and a handful of incomplete entries.

What That Question Cost Me

The client didn't fire me over it. But things shifted after that call. They started asking more questions. Checking in more often. The energy changed.

I think they decided I wasn't as organized as they'd assumed. Which was fair. I wasn't.

Three months later, when the project ended, they didn't ask me to quote the next phase. They went with someone else. I never asked why. I didn't need to.

A single question I couldn't answer confidently had planted a seed of doubt that grew over the rest of the engagement.

The Problem with On-and-Off Tracking

Partial tracking is almost worse than no tracking. Because it gives you the illusion of data without the substance.

You feel like you have records. You feel like you've been responsible. Then someone asks a real question and you realize the records are too thin to hold weight.

Consistent tracking means running the timer on everything. Not just the big tasks. Not just the billable work. Everything. Because you never know which entry someone is going to ask about.

Screenshots help too. When a client asks what you were doing during a specific window, being able to show timestamped screen captures of actual work in progress changes the conversation completely. It's not about surveillance. It's about having evidence when evidence matters.

What I Do Now

Every phase of every project gets its own tag from day one. Research, strategy, execution, revision, communication. All of it labeled and logged.

When a client asks how long something took, I can answer before they finish the sentence.

That might sound like a small thing. It isn't. Clients notice when you know your own numbers. It reads as competence. It reads as honesty. It builds the kind of trust that makes them want to hire you again.

I lost a client because I couldn't answer one question. Not because I did bad work. Because I didn't have my data clean.

Never again.

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