The Project Where I Said Yes to Everything

He Was the Kind of Client You Want to Help

He ran a small company. He was building something real and he cared about it. Every request he made came with a reason that made sense. Could I look at this one extra page? Yes, obviously. Could I jump on a call Thursday to talk through the nav structure? Sure, no problem. Could I take a quick look at his competitor's site and give him a few thoughts? I mean, it would only take twenty minutes.

Except it did not take twenty minutes. It rarely does.

I helped because I wanted to help. He was a good person working on something he believed in and I liked being the person who came through. I was not tracking any of those small moments carefully. They felt too small to bother.

Two Months Later

When the project wrapped, I sat down to invoice and tried to understand why I felt so worn out. The core deliverables were done. The work had not been technically difficult. But I was drained in a way that did not match the scope I had quoted.

I pulled together my time logs. The structured work, the design sessions, the formal revisions, all of it tracked reasonably well. But I had gaps everywhere. Calls that ran over and I had not logged the extra time. Quick questions that turned into thirty-minute conversations. Reviews I had done as favors that took a real chunk of afternoon.

I estimated what I had given away. It was close to eighteen hours over the two months. At my rate, that was significant money. More than that, it was time I had pulled from other work, from my own projects, from the parts of my week I had mentally reserved for thinking.

The Part That Surprised Me

I did not resent him for it. That is the part I had to sit with. He had not taken anything I had not offered. Every yes was my choice. He never pressured me. He just asked, and I said yes because saying yes felt easier than explaining what was in scope and what was not.

The problem was not the client. The problem was that I had no system for knowing when I was over the line. Without logged time I could point to, I had no moment where I could see clearly that things had shifted.

If I had been tracking those calls and quick reviews from the start, I would have seen it building. I might have had a natural opening to say, hey, I've put in a few extra hours on this that weren't in the original scope, let's talk about how to handle that going forward. Clients who are decent, and he was, respond to that kind of honest conversation. What they cannot respond to is a freelancer who says nothing and then disappears after the project ends.

What I Do Differently Now

I track everything. Including the stuff that feels too small to track. A fifteen-minute call gets a log entry. A quick review gets a log entry. Not because I bill for every minute in isolation, but because I need the data to understand what a project actually costs me.

I use Time-Trak for this because the floating timer makes it frictionless enough that I actually do it. When a call ends, I stop the timer. When I finish a quick review, I stop the timer. The habit is easier to maintain when the tool is always visible.

At the end of a project I can look at real numbers and make a real decision. Did I go over because the client added scope? Did I go over because I underestimated? Did I go over because I kept saying yes to things that should have been a different conversation?

Those are three different problems with three different solutions. You can only find the right answer if you have the actual data.

I still help good clients. I still go the extra mile sometimes. I just do it with my eyes open now.

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