The Fixed-Fee Project Where I Tracked Anyway

Fixed-fee projects feel clean. You quote a number, the client says yes, you do the work, you collect the payment. No hour-by-hour justification. No time report. Nobody watching your clock.

I used to think tracking time on those projects was unnecessary overhead. The client was not paying per hour, so why log hours at all?

Then a friend who had been freelancing longer than me asked a simple question.

"How do you know if a fixed-fee project was actually profitable?"

I said I knew roughly how long things took.

She said roughly is a business plan for slowly losing money.

The Project I Decided to Actually Track

I took a fixed-fee branding project, a client I had worked with before, and I ran my timer the whole time. Every task. Every call. Every email thread that ran longer than five minutes.

I was not going to invoice from those hours. I just wanted to see the number.

The project was scoped for what I estimated would be about twenty-five hours of work. I had priced it based on that estimate with a small buffer.

The final tracked time was thirty-nine hours.

The Breakdown That Surprised Me

I had estimated the core deliverables pretty accurately. Logo concepts, brand guide, final files. That came in close to what I expected.

What I had completely underestimated was everything around the deliverables.

Client calls: four and a half hours. I had mentally budgeted two.

Revision rounds: eight hours across three rounds. I had budgeted four.

Admin and file handoff: two hours. I had not budgeted anything.

Back-and-forth email on approvals: almost three hours across the project. I had never counted this as work before.

The deliverables themselves were fine. The surrounding work was double what I had planned for.

What This Changed in My Quoting

I started treating communication and revision time as real line items in my mental scoping, not afterthoughts.

For a project with a lot of client touchpoints, I now add a communication buffer that is proportional to the project length. Not a vague gut feeling buffer. An actual estimate based on what similar projects have cost me in tracked hours.

I also started looking at revision allowances differently. One round of revisions and two rounds of revisions are not the same project. They are priced differently now because I have the data to prove they take different amounts of time.

Why You Should Track Fixed-Fee Projects in Time-Trak

The client never sees the hours. That is fine. The hours are for you.

Every fixed-fee project you track gives you a data point for quoting the next one. Over a year, you build a real picture of what different project types actually cost in your time. You stop quoting from optimism and start quoting from evidence.

Time-Trak makes this easy because you can mark hours as non-billable or run reports just for internal review. The data exists even if it never goes on an invoice.

I also started reviewing my logged hours at the midpoint of fixed-fee projects. Not to panic, but to check whether I was tracking toward the planned hours or already past them. If I am at fifty percent of the budget at thirty percent of the timeline, that is useful information. I can have a scope conversation before it becomes a crisis.

The Number I Use Now

For every project type I quote regularly, I have a real tracked average from past work. Not a memory. Not a feeling. An actual number pulled from my logs.

When a client asks how I priced something, I can tell them. When a project comes in that looks similar to something I have done before, I know what it actually took.

Fixed-fee projects without time tracking are guesses wrapped in confidence. At some point the guess gets expensive enough to hurt.

Track the hours even when the client never asks for them. You are asking. Your next quote depends on the answer.

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