The Flat-Rate Project I Tracked Anyway
The client paid a fixed fee, so tracking hours felt pointless. What I found in that data changed how I price everything.
The client wanted a flat fee. I gave them one. They paid half upfront, half on delivery. Clean, simple, no hourly arguments.
I almost did not track time on it at all. If the rate is fixed, what difference does it make how long it takes?
I tracked it anyway, mostly out of habit. I am glad I did.
What the Hours Actually Showed
I quoted the project at a rate that implied roughly fifteen hours of work. The kind of number you land on from experience and intuition, adjusted slightly for how much you like the client and how busy you are.
I spent twenty-nine hours on it.
The client never knew. The invoice was fixed. I delivered on time and they were happy. On the surface, a successful project. Under the surface, I had charged myself a rate I would never have accepted if someone had offered it to me upfront.
Fifteen hours versus twenty-nine. That is not a rounding error. That is a pricing problem.
Why Flat-Rate Projects Are the Most Dangerous to Ignore
With hourly work, the relationship between effort and income is direct. You work more, you bill more. The tracking matters for the client.
With flat-rate work, the tracking matters for you.
If you do not log hours on fixed-fee projects, you have no data. You will quote the next similar project the same way you quoted this one, by feel, by habit, by whatever number came to mind. And if that number was wrong this time, it will be wrong next time too.
Tracking time on fixed-price work is not about billing the client. It is about knowing your actual costs before you price the next one.
The Pattern I Found After Six Months
Once I started logging hours on every project, fixed or hourly, I could see which types consistently ran over. For me it was anything involving client-side dependencies. Projects where I was waiting on content, waiting on approvals, waiting on feedback. The waiting never felt like work, so I had not built it into my quotes. But the interruptions, the follow-ups, the context-switching back into a project after a ten-day pause? That time was real.
I started adding a buffer to any project where the client controlled the timeline. Not a large one. But a real one, based on what the data said those projects actually cost me.
What Changed When I Had the Data
The next time a client wanted a flat fee for a similar scope, I had a number I could defend. Not to them. To myself.
I knew the project type took between twenty-five and thirty-five hours depending on how responsive the client was. I knew my rate. I could build a flat fee that actually reflected the work.
I also had something useful when the conversation about scope came up. Because on flat-rate projects, scope always comes up. The client adds a section, changes the structure, wants a second round of revisions. When you have logged hours by phase, you know immediately how far outside the original scope you are. That is a real conversation to have. Without the data, you are guessing.
The Habit That Costs You Nothing
Tracking time on a fixed-rate project takes the same effort as tracking it on an hourly one. You start the timer, you stop the timer, you label the entry.
The client never sees it unless you choose to show them. But you see it. And over time, that data becomes the most honest accounting of what your work actually costs.
The project where I worked twenty-nine hours and billed for fifteen paid fine. The client was happy. But I will not make that pricing mistake again. Because now I have a record of what that mistake actually looked like.
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.
Download Time-Trak →macOS + Windows · Floating widget · Auto screenshots