The Project I Thought Was Going Well Until I Looked

The project was fine. That was my read on it. The client was happy, deliverables were moving, nobody was complaining. I had no reason to open my time data and check.

So I did not. Not until the project was almost over.

When I finally ran the numbers, two things happened. First, I felt sick. Second, I understood why I had been so tired.

What the Data Showed

I had quoted 40 hours for a brand identity project. Research, concepts, two revision rounds, final files. A scope I had done before. A scope I thought I understood.

My timer showed 67 hours logged.

Not because the client was difficult. Not because there was scope creep I could point to and invoice. Just because I had quoted the work based on a best-case version of the project and delivered it in the real-case version where things take longer than you expect.

At my rate, I had worked 27 hours for free.

Why I Missed It Mid-Project

Because everything felt okay. That is the trap with flat-rate projects. There is no natural moment where the overrun announces itself. The client does not see your hours. You are not sending weekly time reports. The invoice amount is already agreed on. So you just keep working.

If I had done a mid-project billing check at the halfway mark, I would have seen I was already at 38 hours with half the work still to do. That would have been the moment to have a conversation about scope, or at minimum to protect myself on the back half.

I did not look. So I did not see it. So I said nothing.

The Check I Do Now

Every project, I set a budget in hours before the kickoff call. Then I check it at the midpoint without fail. I do not wait until something feels wrong. Feeling wrong comes too late.

When I hit 50 percent of my budgeted hours, I open the project in my time tracker and look at what is left on the scope. If the math does not work, I have a conversation then, not at the end.

Clients do not love that conversation. But they handle it better at the midpoint than they do when the project is done and you are suddenly asking for more money as you hand over the files.

What I Changed About Quoting

I stopped quoting from memory and started quoting from data.

My time tracker has history. Every project I have completed is logged. So now when I get a brief that looks like something I have done before, I go look at what that similar project actually took. Not what I thought it would take at the time. What the timer recorded.

Those two numbers are almost never the same.

Projects take longer than estimates for predictable reasons. Client feedback cycles, unclear briefs, revisions to work the client approved and then changed their mind on, time spent on communication that nobody budgets for. All of it shows up in the logged hours. None of it shows up in a gut estimate.

The Margin That Disappeared

I quoted that project thinking I would make a decent margin. By hour 67, I was below minimum wage for the last stretch. Not because I worked slowly. Because I did not look at the numbers until it was too late to do anything about them.

The project still finished well. The client was happy. I have done more work for them since.

But I will never take that as a sign the project was profitable. Happy clients and profitable projects are not the same thing. I know that now because I have the hour logs to prove it.

Looking at your data mid-project is not paranoia. It is the only way to find out if you are actually making money before it is too late to protect any of it.

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