The Project I Priced on a Good Day
I sent the quote when I was feeling fast and sharp. The project arrived six weeks later when I was neither of those things.
I quoted it on a Friday after a great week. Everything had gone smoothly, I was ahead of schedule on two projects, and I felt like I could do anything in half the time it normally took.
That is a terrible headspace for pricing work.
The Quote I Sent
The scope was clear enough. A content project, defined deliverables, a client I had spoken with twice. I had done similar work before.
I estimated twelve hours. I would do it in ten if the brief was solid. I charged accordingly.
The client came back six weeks later, ready to start. By then I had a new big project, a minor personal situation that was eating mental energy, and the kind of mental load that makes everything take longer than it should.
I finished the project in nineteen hours.
What I Got Wrong
I quoted based on my best-case self. The version of me who is rested, focused, with a clear desk and no competing deadlines.
That version of me exists sometimes. But projects do not always arrive when I am at my best. They arrive when they arrive.
The twelve-hour estimate was not wrong for a perfect week. It was wrong for a real one.
What Actual Data Would Have Shown
If I had pulled up my time log for similar projects before sending the quote, I would have seen that my average on this type of work was closer to sixteen hours. Not twelve. The twelve was a good run. The average was sixteen.
I did not have that habit yet. I was quoting from memory and mood, not from records.
After this project, I started doing one thing before every quote: I open the logs from the two or three most comparable projects I have completed and I look at the actual hours, not what I estimated, the real logged time. Then I average them and add ten percent.
That ten percent is not padding. It is the cost of being human. Interruptions happen. The brief is never quite as clear as it looked. The client asks for one more thing. The ten percent covers the gap between the project as described and the project as it actually unfolds.
The Client Side of This
The client on this project was happy. They had no idea it took me nineteen hours. The deliverable landed on time and matched what they asked for.
But I had effectively cut my rate by a third. And the worst part was that I had done it to myself, voluntarily, by quoting without data on a day when I felt invincible.
Feelings are not a pricing system.
What I Do Now Before Any Quote Goes Out
Three things. First, I look at logged hours from similar past projects. Second, I note which project phase tends to run longest for me, usually the revision rounds and the final delivery polish. Third, I add time for client communication, because every project has more of that than the brief suggests.
This process takes about fifteen minutes. It has never made a quote worse. It has made several of them more accurate in ways that protected months of income.
I also try not to send quotes on Fridays after great weeks. That sounds irrational. But your pricing should reflect the median version of your work, not the peak. The client is buying your average, not your highlight reel.
The Real Cost of Optimistic Quoting
This one project cost me around seven hours of uncompensated work. Not because the client was difficult. Not because the scope changed. Because I priced it on a feeling instead of a number.
The time log does not care how good of a week you are having when you open it. It just shows you what things actually took. That is the number to quote from.
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.
Download Time-Trak →macOS + Windows · Floating widget · Auto screenshots