The Three Thousand Dollar Lesson I Learned Too Late
I didn't lose that money to a bad client. I lost it because I had no idea how long anything actually took.
I found out I was missing roughly three thousand dollars about six weeks after the project ended.
Not because a client stiffed me. Not because I forgot to send an invoice. Because when I added up what I'd actually worked versus what I'd billed, the gap was real and it was ugly.
The project was a website and content package for a mid-sized consulting firm. I quoted it at a flat rate based on gut feel and two similar projects from memory. I'd done those in about forty hours each. This one, I figured, was the same size.
It wasn't.
The Gap I Didn't See Coming
I had no timer running during that project. I never did back then. I worked, I finished, I invoiced. That was my system.
After it wrapped, something felt off. The project had taken longer than expected but I couldn't say how much longer, because I had no data. So I did something I should have done during the work: I reconstructed my hours from calendar blocks, Slack messages, and email timestamps.
The rough total was eighty-three hours.
I had billed for forty-five.
At my rate at the time, that gap was about three thousand dollars in work I did and never charged for. Three thousand dollars I handed to a client who had no idea I was doing it, and who would have paid it without blinking if I'd priced the project correctly.
That number sat with me for a few days.
The Lie I Was Telling Myself
I had always told myself that flat rates were better for clients, easier to sell, and simpler to manage. And maybe that's true sometimes. But the version of flat-rate pricing I was doing wasn't based on anything real. It was based on optimism and fuzzy memory.
The memory piece is what gets most freelancers. You remember a past project as taking a certain number of hours, but you remember the focused hours. The good stretches. You don't remember the extra revision round that ate a Tuesday. You don't remember the three calls that weren't in the original scope. You don't remember the week the client went silent and you had to restart mentally when they came back.
Memory compresses work. A timer doesn't.
What I Changed
After that project, I started running a timer on everything. Not to become more productive. Just to know what was true.
The first month of tracking was uncomfortable. I saw exactly how long certain tasks took, and the numbers did not match the story I'd been telling myself. Discovery calls I thought ran forty-five minutes were often ninety. Revision rounds I mentally filed as quick fixes were sometimes two to three hours each.
Once I had a few months of data, I repriced my flat packages. Not arbitrarily. I looked at average hours per deliverable type and built rates from there. If a project type consistently took sixty hours, I stopped quoting it like a forty-hour job.
I also started breaking bigger projects into phases with separate billing checkpoints. That alone changed how clients engaged with scope. When they knew each phase had a price, the casual add-ons slowed down.
The Client Was Not the Problem
This is the part I had to sit with longest. The client on that project was fine. They communicated well, they paid on time, they were happy with the work.
I was the problem. I had no system for knowing what anything cost me in time, so I made up numbers and hoped they were close enough. They weren't.
Three thousand dollars is a lot to lose to a process problem. But it was also the last time I lost it, because after that I ran a timer on every project I took.
Time-Trak has a floating timer widget that stays visible while you work. That visibility matters more than it sounds. When you can see the clock running, you don't forget to stop it. And you don't finish a project six weeks later wondering where the hours went.
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