The Project I Finished in Half the Time and Charged Wrong

I got good at a specific type of project. Genuinely good. What used to take me twelve hours started taking six. I knew the process, I had the templates, I had done it enough times that the rough patches were smooth.

So naturally I started charging less for it.

I did not do this on purpose. I billed hourly. The hours went down. The invoices went down. I thought that was fair.

It took me longer than I want to admit to realize that fair to the client was not the same as fair to me.

What Efficiency Is Supposed to Do

When you get better at something, that is supposed to benefit you. The value you deliver stays the same or goes up. The cost to produce it goes down. The margin widens. That is how skill is supposed to pay off.

What I was doing instead was passing every efficiency gain directly to the client in the form of lower invoices. I was billing for time spent, not value delivered. The faster I got, the less I made per project.

When I Saw It in the Data

I had been tracking seriously for a few months before I ran a report that broke down average hours per project type. The numbers were clear. One category of work had dropped significantly in hours over a twelve-month period.

At first I thought I was looking at easier projects. But the deliverables were the same. The client outcomes were the same. I had just gotten faster.

Then I looked at the revenue per project in that category. Also down. Tracking with the hours, exactly as you would expect when you bill purely on time logged.

I sat with that for a while.

The Math That Burned

Year one of doing this project type: twelve hours average, invoiced accordingly.

Year two: six hours average, invoiced accordingly.

Same deliverable. Same client type. Same market rate for the outcome. Half the revenue.

The clients were not complaining. They were getting the same result faster. Some of them probably did not even notice the invoices had dropped. They just paid what came in.

I had quietly cut my own income by making myself better at my job.

What I Changed

I moved to project-based pricing for that service type. Not across the board, just for the work where my process was mature and the scope was predictable.

I used my tracked hours data to set the price. I knew what the project took. I knew what I needed to earn. I set a number that reflected the value of the outcome, not the minutes I logged.

Time-Trak still runs on every project. The data still matters. I want to know if a project starts taking longer than expected, because that means something changed and I need to know what. But the logged hours inform my pricing decisions, they do not mechanically produce my invoice total.

The Lesson That Took Too Long

Hourly billing is not neutral. It ties your income to your slowness. The more skilled you become, the harder it works against you.

That does not mean hourly is always wrong. For variable work, for projects where scope is unclear, for relationships where transparency about time matters, it makes sense.

But for project types where you have real data on what work actually costs you and what it delivers to clients, that data should inform a smarter number.

I would not have seen this without tracked hours. The report made it impossible to ignore. The trend was right there.

Check your hour logs by project type. Look at whether your rates have kept pace with your skill level. You may find you have been discounting yourself for years and calling it fair.

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