The Proposal I Wrote From Gut Feeling
I sent a quote based on how the project felt, not what similar work had actually taken me. It did not go well.
The client sent a detailed brief. Good scope, clear deliverables, reasonable timeline. I read it, got a feel for the project, and wrote a quote.
I did not look at any past projects. I did not check how long similar work had taken me. I just had a number in my head and I sent it.
That number was wrong by about forty percent.
The Confidence That Wasn't Confidence
I had been freelancing long enough to believe I had a calibrated sense of how long things take. And honestly, for small tasks, I probably do. Quick edits, short briefs, single-pass deliverables. I can estimate those reasonably well.
But this project had layers. A discovery phase I mentally categorized as quick. A revision cycle I assumed would be one round. A final delivery process I didn't account for at all because I never think about it until I'm in it.
I wasn't being sloppy. I was being overconfident, which is worse. Sloppy you can fix by slowing down. Overconfident is harder because you don't even know to slow down.
What Actually Happened
The project started fine. The discovery phase ran long, but I told myself I'd make it up later. The first round of revisions came back with more notes than I expected, but the feedback was reasonable so I couldn't really push back. The delivery process involved three rounds of stakeholder review I hadn't been told about.
By the time I sent the final file, I had logged almost double the hours I had priced for.
I sat with that for a while before I did anything. I pulled up my time log and went through every entry. I wanted to find waste. I wanted to find the place where I had been inefficient or distracted so I could blame myself in a productive way.
There wasn't much. The work just took what it took. I had priced for a version of the project that didn't exist.
What Past Data Would Have Shown Me
After that project closed, I went back through my time logs for similar work. The pattern was clear. Discovery phases on this type of project almost always run fifty percent longer than I expect. Revision cycles are rarely one round when there are multiple stakeholders. Delivery administration is always at least two hours I never price for.
This information was sitting in my own records. I just hadn't looked at it before writing the proposal.
If I had spent twenty minutes reviewing comparable past projects, I would have added hours to my estimate. The quote would have been higher. Maybe the client would have balked. Maybe they wouldn't have. Either way, I would have known what I was agreeing to.
What I Do Now
Before I write any proposal for a project over a certain size, I open my time tracker and filter for similar past work. I look at what I estimated versus what I logged. I look at which phases ran long. I look at the parts of the project I always underestimate.
Then I build the quote from that, not from how the project feels when I read the brief.
The brief always makes the project sound cleaner than it is. Your past data tells you what the messy reality usually looks like.
The Real Cost
I didn't lose the client. I finished the project, delivered good work, and they were happy. But I worked for about half my intended rate when I look at what I actually earned per hour.
That's the quiet version of a bad project. No blowup. No difficult conversation. Just a lot of hours that weren't compensated because I trusted my gut instead of my records.
Your gut has no memory. Your time log does.
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