How to Know If a Project Was Actually Profitable

The number in your invoice is not your profit

You finished the project. You invoiced. The client paid. Feels good.

But do you actually know if you made money on it?

Not rough money. Real money. The kind that accounts for every hour you put in, including the ones you forgot to log, the revision rounds you absorbed, and the three calls that were supposed to be fifteen minutes each.

Most freelancers skip this math. They see payment and move on. That habit is expensive.

What profitability per project actually means

Take your project total. Divide it by the real hours you tracked. That number is your effective hourly rate for that project.

Now compare it to your target rate.

If you wanted to earn $100 an hour and you came in at $60, that project cost you money relative to your goal. You worked below rate and probably didn't notice.

This is why project revenue is a vanity number without hours behind it. A $5,000 project sounds great. A $5,000 project that took 80 hours is $62.50 an hour. That might be below what you need to stay viable.

Where the hours usually go

Profitability problems almost always trace back to a few patterns.

Revisions that weren't scoped. You agreed to two rounds. The client treated that as two rounds per section. You let it happen because you didn't want the friction.

Admin time on a fixed project. Every email, every check-in, every Slack message answering a question that should have been in the brief. That time is real. If it's not tracked, it's invisible.

Scope drift in the middle. The project mutated over six weeks and nobody acknowledged it. You kept working. The invoice stayed the same.

Startup time on unfamiliar work. You estimated based on a project type you hadn't done in a year. It took longer. You ate the difference.

None of this shows up when you just look at what you billed.

How to run the actual calculation

When a project closes, pull the full time log. Not just the task work. All of it: calls, emails, revisions, prep, any admin attached to that client and project.

Add those hours up. Divide your invoice total by that number.

Then ask three questions.

Was my effective rate acceptable? If not, why?

Where did I log more time than I expected?

Would I quote this the same way next time?

That last question is the one that changes your business. If you answer no, you have a pricing problem or a scoping problem. Either way, you now know.

What to do with a bad number

A low effective rate on one project is information. A low effective rate on the same type of project three times in a row is a pattern.

Patterns tell you where your pricing is broken. They show you which client relationships cost more than they earn. They reveal which service offerings you consistently undercharge for.

You cannot fix what you cannot see. That's not a motivational line. It's just true.

If you track time by project and pull this report after every engagement closes, you will have real data within a few months. That data will tell you more about your business than any gut feeling ever could.

The projects that look fine are the ones to worry about

When a project goes sideways, you notice. You adjust. You maybe even have the hard conversation.

But the projects that quietly erode your rate? Those are the dangerous ones. They feel okay. The client is pleasant. The work is familiar. And you're earning $55 an hour on a day you thought you were earning $95.

Track the hours. Run the math. Close every project with a real number, not just a paid invoice.

That habit will change which projects you take next year.

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