The Project I Lost Money On Twice

The First Time I Should Have Learned the Lesson

Two years ago I landed a website build for a small retail client. New to that niche, excited about the work, eager to close. I quoted based on what felt fair. The project ran long. I logged the hours, saw the overrun, felt bad about it, and moved on.

I did not investigate why it ran long. I did not flag the project type as risky. I did not update my quoting process in any way.

I just moved on.

The Second Time

A year later, nearly identical project. Different client, same industry, same general scope. I quoted it the same way I quoted the first one, because that was the number in my head.

You can probably see where this is going.

The project ran long again. Almost exactly the same overrun, almost exactly the same phases. Discovery dragged. The client had no clear vision for the site architecture. Revision rounds multiplied. I tracked everything and watched my real hourly rate drop week by week.

When I finally sat down and compared the two projects side by side, I nearly laughed. The hour breakdowns were nearly identical. I had walked into the same wall twice because I never looked at what the first wall actually cost me.

What the Time Log Showed Me

When I lined up both project logs, the pattern was obvious. The discovery phase on both projects ran nearly double what I had estimated. The revision rounds each hit three or four cycles, not two. And both projects had a long, messy handoff phase I had never thought to budget for at all.

None of this was in my quote. Not once, not twice.

The hours were there, logged faithfully in my tracker, and I just never went back to read them as a lesson. I was using my time log as a billing tool and ignoring it entirely as a learning tool.

The Habit I Was Missing

After the second project I built one new habit: a short end-of-project review focused entirely on hours versus estimate. Not the client relationship. Not the creative quality. Just the hours.

Which phases ran long? By how much? Why? Is this a one-time thing or a pattern?

That review takes maybe twenty minutes. I do it before I close the project file. I write three sentences in my notes: what I estimated, what actually happened, and what I would do differently on the quote.

Small habit. Huge difference.

What Happened the Third Time

When a third retail website project came in, I went back and read both previous reviews before I quoted anything. I saw the discovery overrun pattern. I saw the revision cycle problem. I built both into the new estimate.

The client pushed back slightly on the price. I held the number because I had data behind it, not just intuition. They agreed.

The project came in close to estimate. Not perfect, but within range. My real hourly rate was what I had intended it to be when I wrote the quote.

That had never happened before on this project type.

The Cost of Not Looking Back

Every unbilled hour you log is documentation. But documentation only helps you if you read it.

A lot of freelancers use time tracking defensively, to justify invoices if a client questions them. That is a fine use. But there is a second use that most people skip: reading your own history to get better at pricing what comes next.

Your past projects are the best quoting data you will ever have. They are specific to your working style, your client types, your weaknesses, your revision tendencies. No industry rate card can match that.

I lost money on the same project twice because I never read what I had already written down. The third project paid me fairly because I finally did.

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