The Project I Billed by Feel and What That Cost Me
I finished a project, made up a number that felt fair, and sent the invoice. It was three thousand dollars short.
The Number I Invented
I finished the project on a Thursday afternoon. The client was happy. I was tired. I opened a blank invoice, thought about how long it had taken, landed on a number that felt right, and hit send.
That number was wrong. Not a little wrong. About three thousand dollars wrong.
I know that now because I eventually started tracking my time and ran the math backward on projects I had already closed. The hours were there in my head. They just weren't in any record. And when I tried to reconstruct them weeks later, I could only account for the obvious stuff. The big working blocks. The long days.
What I couldn't account for was everything else.
What 'Everything Else' Actually Means
The back-and-forth emails that stretched across two weeks. The call we had that wasn't on the calendar but ran ninety minutes. The revision round I did on a Sunday because I wanted it done. The time I spent fixing a file the client sent me broken. The hour I spent tracking down feedback from three different people because no one on their side was coordinating.
None of that made it into my mental estimate. I billed for the work I could picture. Not the work I actually did.
This is how you lose money without anyone stealing from you. You just don't count it.
Why 'Feel' Is a Terrible Billing System
Feeling your way through a bill makes sense when you're new. You don't have data. You go with your gut. The problem is that your gut is optimistic. It rounds down. It forgets the annoying parts. It compresses two hard weeks into a fuzzy sense of 'that took a while.'
Your gut also adjusts for how much the client can pay, whether you like them, whether the project went smoothly, whether you want repeat work. None of those things should change your invoice. They all do when you're billing by feel.
Tracking time kills the feel. That's the point. You log the ninety-minute call. You log the Sunday revision. You log the broken file. Then when you open the invoice, there's a number waiting for you. You didn't guess it. You earned it.
The Backward Math I Ran
A few months after I started using Time-Trak, I got curious about my old projects. I couldn't reconstruct exact hours. But I had notes, email threads, and a rough sense of the timeline. I started estimating what those projects would have looked like if I'd tracked everything.
The gap was consistent. I was billing roughly sixty to seventy percent of what I should have been charging. Not because my rates were wrong. Because I was forgetting thirty percent of the work.
On a five-thousand dollar project, that's fifteen hundred dollars gone. On a larger one, more. Across a year, it's real money. The kind of money that changes whether a slow month feels manageable or terrifying.
What I Do Differently Now
I start a timer when I open a client file. Even if I think I'm just going to spend ten minutes on something. Especially then, actually, because ten-minute tasks have a habit of becoming fifty-minute ones.
I log calls. I log email threads when they turn into something longer than a quick reply. I log the time I spend fixing problems I didn't create. All of it goes in.
When I'm ready to invoice, I pull the report, look at the total, and send it. I don't adjust it down because I feel weird about the number. The number is what it is because the hours were what they were.
The client who hired me is paying for my time. All of it. Not just the parts I remembered to count.
Three thousand dollars is a lot of hours to give away for free. I stopped doing it when I stopped guessing.
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