The Client I Never Said No To

She was a good client. Paid on time. Friendly on calls. Never argued about invoices.

So I never said no to her.

Need a quick revision? Sure. Want to hop on a call before I'd logged off for the day? Absolutely. One more round of edits before we go live? Of course.

I told myself she was low-maintenance. I told myself the work was easy. I told myself I liked working with her, which was true, and used that to justify every single yes I handed over without thinking.

Then I looked at my time logs.

What the Numbers Said

I had been working with her for four months. I'd invoiced her for twenty-two hours across that stretch. Clean, round numbers because I was billing from memory and memory is optimistic.

My tracker told me the real number was closer to forty-one hours.

Not because I was lying on invoices. Because I genuinely did not know. I'd never added up the quick calls. Never counted the revision loops. Never billed the email threads where she'd ask a question that took forty-five minutes to answer properly.

Nineteen hours. Gone. Not stolen. Just never counted.

Where the Hours Actually Went

I went back through my logs and sorted by entry type. It was uncomfortable.

Calls I never billed: six hours. I had a habit of not billing calls under thirty minutes. I told myself it was goodwill. Turns out goodwill is expensive.

Email and Slack: four hours. I'd convinced myself this wasn't real work. It absolutely is.

Revision rounds: five hours. I built one revision into my quotes. She usually wanted three. I never adjusted the rate or the scope.

Miscellaneous admin and prep: four hours. Pulling assets, formatting documents, chasing approvals. None of it billed.

I didn't have a scope problem. I had a billing blindspot problem.

The Part That Stung

The worst part wasn't the money. It was realizing I'd built a mental model of this client that was completely wrong.

I thought she was low-touch because every individual request felt small. A quick call here. A short email there. But the requests were constant. They never stopped.

I was thinking in hours per task. I should have been thinking in hours per month.

When you see the full picture in a time log, the pattern becomes obvious fast. One project with forty-one hours billed as twenty-two isn't a one-off. It's a relationship with a systematic leak.

What I Changed

I didn't fire her. I didn't raise her rate dramatically overnight. I just started tracking everything.

Every email thread over ten minutes. Every call, no matter how short. Every revision round, labeled clearly so I could see the pattern at the end of the month.

I also set a simple rule for myself: if I'm working, the timer is running. Not because I planned to bill every minute. But because I needed to know what I was actually doing.

After one month of honest tracking, I had a real picture of what the relationship cost me. I went back to her and explained that I'd been underquoting and needed to adjust how I structured the work going forward. She didn't flinch. She said she'd always assumed I was tracking properly.

She thought I knew what I was doing. I just wasn't looking.

The Lesson That Stuck

Saying yes to everything doesn't make you a good partner. It makes you an invisible one. You quietly absorb work the client doesn't even realize they're creating, and then you resent a situation you never measured.

Nice clients will take as much time as you give them. That's not a character flaw. That's just how work expands.

Your job is to know where the hours go. Not guess. Know.

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