The Client I Underquoted Because I Forgot Discovery
I lost thousands on a project that should have been profitable, and the culprit was the work I did before the work started.
The project looked simple on paper. A website rebuild. Clear scope. Reasonable deadline. I quoted six weeks and felt good about it.
What I forgot to quote was the three weeks before that.
The Work Before the Work
Every project has a discovery phase. Calls to understand the brief. Time spent reviewing the old site. Questions back and forth over email. Competitor research the client mentioned casually like it was nothing.
I never tracked any of it. It happened in the gaps between real work, so it felt like overhead. Not billable. Just part of the process.
By the time I started the actual build, I had already put in eleven hours I would never invoice for.
Where the Money Went
I only figured this out because I started tracking everything that quarter. Not just deep work sessions. Every call. Every email thread I had to re-read to get context. Every time I opened a shared doc to review notes.
At the end of that project I pulled up my logs. Eleven hours in discovery. Four hours of revision calls. Two hours fixing a miscommunication that happened because I hadn't documented a decision properly in week one.
Seventeen hours gone. At my rate that was close to two thousand dollars I had worked for free.
The project wasn't a loss on paper. My invoice got paid. But my effective hourly rate on that job was embarrassing.
The Pattern I Couldn't Unsee
Once I saw it on that project, I checked the three before it. Same pattern every time. Discovery work, admin overhead, pre-project alignment calls. None of it tracked. None of it billed.
I had been treating setup time as a gift to every client I worked with.
The worst part is that the projects I had felt best about, the ones that felt smooth and well-managed, were the ones with the most discovery time upfront. I was being rewarded for good preparation with lower effective earnings.
What Changed
I started a timer the moment a project entered my world. Not when the contract was signed. Not when the deposit came in. When I first opened an email that required a substantive response.
That felt aggressive at first. But when I reviewed a month of data, it just looked like the truth. That time existed. It had always existed. I had just never made it visible.
Some of that time I bill directly now. Discovery calls are on the clock. Competitive audits are scoped and quoted. Pre-project documentation is a line item.
Some of it I absorb but I do it knowingly. If I choose to give a client two hours of free strategy time because the relationship is worth it, that's a decision I'm making with my eyes open. Not something that happens to me by accident.
What a Timer Actually Catches
A floating timer you can hit the moment a task starts doesn't just track the obvious work. It trains you to notice when you're working at all. That shift matters more than any individual entry.
Before I tracked everything, I had a fuzzy sense of what projects cost me. After a few months of real data, I could see exactly where my time went on every job type I took. Discovery-heavy projects got quoted differently. Clients with complex internal processes got a buffer built in.
My quotes started reflecting my actual experience instead of my optimism.
The Honest Version
I didn't lose this money because I was careless. I lost it because I had a blind spot about what counted as work. I thought billing started when the real work started.
It doesn't. It starts when your brain is on the problem.
Track it all. Review it honestly. Then decide what to charge. That order matters.
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