The Project I Quoted Fast and Paid for Slowly
I gave a number off the top of my head, won the project, and spent the next three months watching that decision unravel.
The Quote That Took Four Minutes
The client sent a brief. It was clear enough. I had done similar work before. I read it twice, did some loose mental math, and sent a number.
Four minutes. Maybe less.
They said yes the same day. I felt good about it. Fast close, interesting project, decent-sounding rate. I started the following Monday.
The First Sign I Missed
About two weeks in, I noticed I was spending more time in the discovery phase than I had budgeted for. But I told myself that was normal. Projects take time to get rolling. I would make it up later.
I did not write that observation down. I did not log it anywhere. I just noted it mentally and moved on.
That was the mistake.
When you notice something is off and do not record it, it does not go away. It just becomes invisible. And invisible problems compound.
What Tracking Revealed at the Halfway Point
I had recently started using Time-Trak seriously for another client and decided mid-project to apply the same discipline here. I went back and reconstructed what I could from my calendar and task notes. Then I started tracking forward in real time.
At the halfway point by deliverables, I had used sixty-three percent of the hours I had mentally budgeted for the whole project.
That number sat in my stomach.
I had been working efficiently. I had not been procrastinating. The project itself was just bigger than I had estimated when I sent that four-minute quote.
Where the Hours Were Going
When I looked at the breakdown, it was not one area. It was all of them, slightly.
The research phase took longer because the client's industry had more regulatory nuance than I had accounted for. The revision cycles were not excessive, but they were thorough. The client was communicative, which was actually great, except that I had not built in any time for the communication itself.
Calls. Email threads. Shared document comments I needed to respond to. That layer of back-and-forth was real work. I had not priced it. I had not even thought about it when I quoted.
By the final week, I had worked almost double the hours I had used to generate my price.
The Dollar Amount
I went back and calculated what I had actually earned per hour on this project.
It was painful. I had effectively charged less than half my standard rate once the full hours were counted.
I finished the work. The client was happy. I sent the invoice and they paid it without a question.
And I sat there knowing I had left a significant amount of money on the table, not because I had been treated badly, but because I had not done the work of estimating before I sent that number.
What Changed After
I now have a rule. No quote leaves my desk until I have broken the project into phases and assigned estimated hours to each one.
It takes longer. Sometimes clients are waiting. I let them wait.
Because the alternative is what I did on this project. I said yes to a number that felt right, and then I spent three months working against it.
I also track every project from day one now, before I am even sure the work will be complex. The floating timer runs. The hours log. I do a check at the end of each week to see where I am against my estimate.
If I am drifting, I catch it early. Early enough to have a conversation. Early enough to revisit scope. Early enough to do something other than absorb the cost quietly.
The Real Lesson
Four minutes is not enough time to quote a project. It never was.
I knew that before. I just did not respect it until I saw the hours in front of me and could not argue with them.
Data does not negotiate. It just shows you what actually happened.
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