The Project I Priced From Memory and What It Cost

A client came to me with a project that felt familiar. I had done something similar about eight months earlier. Same general scope, similar deliverables, comparable client size. I pulled up that old invoice, saw the number, and used it as the basis for my new quote.

That was a mistake. I know that now.

Memory is not a project management tool

What I remembered about that previous project was the easy parts. The creative work. The calls that went well. The final delivery. What I did not remember clearly was how the middle went. The rounds of feedback. The week where the direction changed. The extra research I did that didn't show up anywhere in the deliverables but took real time.

Memory smooths over the rough parts. It keeps the invoice amount and forgets the hours that made it painful.

When I went back and looked at the actual time logs from that old project, I saw a job that ran about thirty percent over my initial estimate. I had still invoiced the original quote because I didn't want the confrontation. And then I used that wrong quote as the basis for a new one.

I was about to repeat the same mistake with fresh enthusiasm.

The new project confirmed it

Six weeks in, I was over budget. Not by a little. The scope was similar on paper but the client's process was slower. Approvals took longer. Feedback came in pieces. I found myself redoing work I thought was done because something upstream had shifted.

None of this was unusual. Clients are like this. Projects are like this. The problem was that I hadn't priced for it because I hadn't looked at what the last similar project actually cost me in time.

When I finally compared the hours to the quote, the gap was significant. I was looking at a project that paid $3,200 but had cost me closer to $4,800 worth of my time at my actual rate.

What real data looks like versus what memory says

After this project closed, I did something I should have done before I quoted it. I ran a proper review of every similar project in my history using my logged hours in Time-Trak.

I looked at projects by type and compared estimated time to actual time across all of them. The pattern was obvious. This category of work consistently ran over by twenty to thirty-five percent. Every single time. I had just never looked at them together before so I never saw the pattern.

I was systematically underquoting one specific type of work because my memory of doing it was always better than the reality of what it required.

The fix was not complicated

I added a buffer to every quote in this category. Not a random buffer. A buffer based on the actual average overrun I could see in the data. That's not guessing. That's using information you already have.

I also changed how I quote now. Before I send any proposal, I look up the last two or three projects of the same type and check the actual logged hours against what I invoiced. If they don't line up, I find out why before I commit to a new price.

Time-Trak keeps all of that history by project and client, so pulling it up takes a few minutes. The alternative is doing what I was doing before, which is quoting from a feeling and hoping the feeling is right.

The thing about gut feel

Experience is valuable. Pattern recognition is real. But neither of those things is accurate enough to build a quote on without checking the data.

Your gut remembers the projects that went well. Your logs remember all of them. Quote from the logs.

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