The Estimate I Gave Without Looking at My Calendar

The Number That Sounded Right

A new client asked how long a project would take. I thought about the scope. I thought about the deliverables. I did not think about my calendar at all.

Four weeks, I said. Maybe three and a half if the feedback comes back clean.

I believed it when I said it. The work itself probably could be done in four weeks if it were the only thing on my plate. But it was not. I had two active clients already, a retainer that took Tuesday mornings, and a website refresh I had promised a former client for almost nothing because I felt guilty about a delay from the year before.

Four weeks turned into nine.

What Went Wrong

Nothing dramatic. No single crisis. Just constant interruption.

I would block time for the new project and then a revision request would come in from another client. I would shift the block to the next morning and then the retainer would run long. The new project kept getting pushed to the slot right after the current urgent thing, and the current urgent thing never ran out.

I was busy the whole time. That was the problem. Being busy felt like working. But when I looked at my hours at the end of each week, the new project was getting maybe four or five hours when it needed fifteen.

The Time Log Told the Story

I use Time-Trak for everything. Not because I am disciplined by nature but because having the floating timer visible makes it harder to pretend I worked on something I did not.

When I pulled the report at the end of week three, I had logged eleven hours on the new project. The estimate assumed about forty-five by that point. The gap was not subtle.

Seeing it in the report made me stop pretending I would catch up. I had to have a conversation with the client. That conversation was uncomfortable. Not because they were angry, though they were frustrated, but because I had nothing to blame except my own planning.

I had not overcommitted on purpose. I had just quoted without any data.

What Quoting Without Data Actually Costs

The obvious cost is the relationship friction. A missed timeline damages trust in a way that good work does not fully repair. The client finishes the project knowing you were late. That is the memory they carry.

But there is a financial cost too. I had to rush the final two weeks to minimize the damage. Rushing meant evenings and a weekend I had not planned to work. Those hours were not in my estimate, so they were not in my rate. I essentially worked overtime at my normal rate to fix a planning problem I caused.

When I added it up, the effective hourly rate on that project came out well below what I charge. Not because the project was hard. Because I could not give it the time it needed when it needed it.

The Fix Is Boring but It Works

I now check two things before I give any timeline estimate. First, I look at the scope and estimate the hours honestly. Not the hours if everything goes perfectly. The hours if things go normally.

Second, I open my actual calendar and count how many of those hours I can realistically fit into the next few weeks without cutting into existing commitments.

That second step is the one I skipped. It takes about ten minutes. It would have saved me six weeks of stress and one very awkward client call.

Timelines are not just about the work. They are about capacity. And you can not know your capacity if you are not tracking where your hours actually go.

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