The Project I Finished Proud Of Until I Ran the Math
The deliverable was great, the client was happy, and I made less than minimum wage. Here's how I found out.
The testimonial was glowing. The client posted it on LinkedIn. I screenshot it and felt good about myself for a week.
Then I actually looked at what the project had paid me per hour.
I try not to think about that number for too long.
The Setup
It was a website copywriting project. Fixed fee, $4,200. Scope was clear: eight pages, one round of revisions, four-week timeline.
I've done that project a dozen times. I quoted it from memory. Felt confident. Signed the contract.
What I didn't do was check my data from the last time I'd run a project like that. I just assumed I remembered correctly.
What I Found When I Finally Counted
I had started tracking time more consistently earlier that year, so I had logs. I went back after this project closed because something felt off. The project had taken longer than expected and I couldn't say exactly why.
When I added everything up, I had logged 67 hours.
The fee was $4,200.
That's $62 an hour before taxes, before software, before the forty minutes I spent on admin for the project that I hadn't even logged.
My target rate at the time was $110 an hour. I had signed a contract that paid me 56 cents on every dollar I thought I was earning.
Where the Hours Actually Went
This is the part that was genuinely useful, even though it was uncomfortable.
I broke the logs down by task. The writing itself was close to my estimate. Strategy and structure were a bit over. But the revision round, which the contract defined as one round, had quietly become something else.
The client had sent feedback in five separate emails over nine days. I had responded to each one. I had made small adjustments. None of it felt like a second round in the moment. Each email seemed minor. But together they added up to nearly 14 hours of work I had priced as if it would take four.
I had absorbed the cost of a client who communicated in fragments.
What Tracking Actually Fixed
I didn't track that project perfectly. But I tracked it well enough to see the pattern clearly after the fact.
The next time I quoted a similar project, I added a line to my contract about what revision rounds meant, specifically. And I added time to my estimate for async feedback management, which I had never done before because I had never seen how much it was costing me.
I also started logging client communication as its own category. Not to charge for every email, but to see it. When you can't see a cost, you can't price for it.
The Testimonial Is Still Nice
I don't regret doing good work. The client was happy and that matters.
But being proud of a project and being paid fairly for a project are not the same thing, and I had been confusing them.
The feeling of finishing something well can cover a lot of financial reality if you let it. I was letting it.
Your time log doesn't care about the testimonial. It just shows you what happened. Sometimes what happened is that you did excellent work for a rate you would never have agreed to if someone had put it in front of you at the start.
Now I run the numbers before I feel proud. The pride is better when it holds up to math.
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