The Client I Quoted by Memory and Paid for Twice

I Had Done This Before

That was the problem.

A client came back with a project that looked identical to one I had finished eight months earlier. Same industry, same deliverables, roughly the same scope. I did not look at any records. I did not check how long the original took. I just remembered it as a smooth project and quoted accordingly.

I was off by eleven hours.

Not on the estimate. On my memory of the first project.

What I Thought I Remembered

I remembered the first project as taking about three weeks of light work. Maybe twenty hours total. It felt efficient. The client was easy. I finished ahead of schedule and came away thinking I had finally figured out how to scope this type of work.

When I finally dug up my old invoices after the second project went sideways, I found out the first one took thirty-one hours. I had billed correctly at the time. I just never retained the real number. What I kept was the feeling.

Feelings compress. Hard weeks become smooth in hindsight. The back-and-forth revision rounds fade. What you remember is closing it out and getting paid.

The Second Project Hit Different

The repeat client was friendly. The brief was clear. I started the work feeling confident.

About two weeks in, I realized I was deep into territory I had not accounted for. There was a research phase I had mentally skipped when I estimated. There were two rounds of revisions I had forgotten were standard for this type of client. There was a handoff process that took half a day each time.

None of that was in my quote. All of it was in my original time logs, sitting in Time-Trak, waiting for me to check.

I did not check.

The Number That Hurt

I finished the second project at forty-four hours. I had quoted for twenty-two.

I did not go back to the client and renegotiate. The scope had not changed. The rate had not changed. I had just guessed wrong, and the guess came from confidence built on a memory I had never verified.

At my hourly rate, those twenty-two unbilled hours cost me more than I made on the project.

What Changed After

I started treating every closed project as reference data, not just a receipt.

Now when a returning client comes back with something familiar, the first thing I do is pull up the original project in Time-Trak and read the actual hours by phase. Not the total. The breakdown. Because the total might be close to what I remember, but the breakdown shows me where the time actually went.

Research phase: six hours. First draft: eight hours. Revision round one: four hours. Revision round two: three hours. Handoff and admin: three hours.

That breakdown is the quote. Not my feeling about how the project went.

Repeat Work Is the Easiest Thing to Underprice

New projects feel risky, so you pad them. Familiar projects feel safe, so you shave them. But familiar does not mean fast. It means you have done it before. Sometimes that helps. Often the client knows the process too, and their expectations are higher.

The time logs from past work are the only real protection against optimistic memory. Not because the numbers are always exactly repeatable, but because they give you something concrete to build from instead of a feeling.

I lost real money on that second project. Not because the work was hard. Because I trusted a memory I had never actually checked.

The data was there. I just did not use it.

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