
The Six-Month Client I Never Actually Analyzed
I worked with the same client for half a year before I sat down and looked at what that relationship actually cost me.
They Were a Good Client
Paid on time. Friendly on calls. Clear about what they wanted, usually. Never screamed about deadlines or sent emails at midnight.
I liked working with them. I renewed the arrangement every month without thinking about it. It felt stable. After a year of unpredictable project work, stable felt like success.
The Analysis I Kept Not Doing
I told myself I would sit down and review the numbers eventually. Every month I invoiced them, I thought about it, and then I didn't do it because things were busy and the relationship felt fine.
Fine is not a number. Fine is a feeling. And feelings, I have learned, are almost always optimistic when money is involved.
After six months I finally forced myself to look.
What I Found
I had been invoicing a flat monthly rate. What I had not done was track how many hours that flat rate was actually consuming.
When I went back through my rough notes and calendar entries, the number was bad. The effective hourly rate I had been earning from this good, stable, friendly client was lower than anything I would have agreed to upfront.
I was doing somewhere between fifty and sixty hours of work for them each month. I had priced the retainer assuming around thirty.
That gap, multiplied by six months, was the kind of number that makes you sit very still for a few minutes.
The Part That Stung
I had turned down two other projects during that period because I was at capacity. Those projects had higher rates. I said no to them to protect my bandwidth for a client I was serving at a significant discount.
I was making a business decision every time I said no to new work. I just didn't know what that decision was actually based on. I thought I was protecting a good deal. I was protecting a bad one.
What Tracking Would Have Shown Me
If I had been running Time-Trak from month one and logging hours to that client's project, I would have seen the drift within thirty days. Maybe sooner.
The hours log doesn't lie. It shows you when a thirty-hour relationship quietly becomes a fifty-hour one. It shows you the week the scope started expanding. The month the requests doubled. The pattern you can't see when you're in the middle of it.
The invoicing side matters too. When you can look at actual hours logged against what you invoiced, the effective rate calculation is automatic. You don't have to go digging through old notes. You just open the report and read it.
The Conversation I Had to Have
I went back to the client with data. Not accusations. Not frustration. Just the hours, broken down by month, and a note that the arrangement had evolved significantly since we originally scoped it.
They were surprised. Not defensive. They genuinely hadn't realized how much the workload had grown. We renegotiated to something closer to what the actual hours warranted.
That conversation went well because I had numbers. If I had gone to them with just a feeling that things had gotten heavier, I don't think it would have landed the same way.
What I Track Now
Everything. Every retainer. Every fixed project. Every small add-on request that feels too minor to track.
I check the hours-to-revenue ratio on every active client at the end of each month. It takes about ten minutes. It tells me whether stable is actually good or whether I've built a comfortable-feeling situation that doesn't survive contact with a spreadsheet.
Stable clients are worth keeping. But only if you know what you're actually trading to keep them.
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