The Project Where the Budget Was Fine and the Margin Wasn't

You stayed inside the hours. You still lost.

The project was 40 hours. You quoted 40 hours. You logged 38. You sent the invoice, it got paid, and you moved on.

But the margin on that project was bad. And you would not have known that if you had only looked at billable hours.

This is one of the more common profitability blind spots. Staying inside your quoted hours feels like a win. It is only a win if the rate on those hours actually covers your real cost of doing the work.

Overhead is the part most freelancers skip

Every project carries costs beyond the time you billed.

There is the time you spent before the contract was signed. The proposal, the discovery call, the scope document. Those hours are real. They came out of your week.

There is the onboarding time. Setting up the project, getting access to tools, learning how the client works.

There is the admin overhead. The back-and-forth emails, the status updates, the invoice follow-up.

And depending on your setup, there is the cost of tools, subscriptions, and any contractors you brought in.

None of that shows up in your 38 logged billable hours. But all of it affects what you actually made.

How to calculate project margin properly

Start with what you collected. That is your revenue for the project.

Then build a real cost number.

Add up every hour connected to the project, not just billable execution time. If you track non-billable time in Time-Trak under the same project, this is easy to pull. If you have not been doing that, start now, because this is the number that tells you whether a project type is actually worth taking.

Multiply those total hours by your target hourly rate. That is what the project should have cost to deliver at a healthy margin.

If what you collected is less than that, the margin was negative regardless of whether you hit your hour budget.

Why the hour budget lie feels so comfortable

Tracking billable hours only and declaring the project a success is a habit that is very easy to form. The number looks clean. Client paid, invoice matched quote, move on.

But the 38 billable hours were preceded by 6 hours of pre-project work you did not log anywhere. And there were 4 hours of back-and-forth admin during the project that you absorbed because it felt rude to charge for email.

That is 48 real hours for a 40-hour invoice. Your effective hourly rate just dropped by 17 percent.

Do that across every project and it explains a lot about why busy months still feel financially tight.

The fix is in what you track, not just what you bill

You do not have to bill for every hour to benefit from tracking every hour. The data is the point.

Log pre-project time under a non-billable category. Log admin time the same way. When the project ends, pull the full report. Compare total hours to revenue. That is your real margin.

Over time you will start to see which project types are profitable and which ones look profitable until you count everything. That is genuinely useful information for pricing future work.

The one-click invoicing side of your workflow only captures what you decide to bill. The time tracking side captures everything. Both matter, but for different reasons.

Change the benchmark

Stop measuring project success by whether you stayed inside quoted hours. That is a client-side metric, not a business-side metric.

The metric that actually matters for your business is total hours in versus dollars out. If that ratio is good, the project was profitable. If it is not, you need to know why before you quote the next one the same way.

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