The Client Project That Taught Me Every Hard Lesson at Once

I took the project in September. Website redesign, modest scope, friendly client. She had worked with a designer before me who had apparently been disorganized. She wanted someone reliable and communicative. I said that was me.

I was not ready for what reliable and communicative would actually cost.

The Beginning Looked Fine

We kicked off quickly. I had a rough estimate in an email, nothing formal, and a deposit that covered about a third of what I expected to bill. The client was responsive. Feedback came fast. The first few weeks felt smooth.

I wasn't tracking time. I had a loose spreadsheet I updated maybe twice a week from memory. I told myself it was fine because I had a rough sense of where things were.

I did not have a sense of where things were.

Where It Started Falling Apart

The additions came in gradually. A new page here. A different layout for the mobile version. Could we also do a blog template while we're at it? Each request was small. Each one felt like the kind of thing a good collaborator says yes to.

I said yes. Every time. Without logging it. Without a change order. Without even a reply email that said "sure, that's extra."

I told myself I'd sort it out at invoice time.

Invoice time came. I was staring at a number I had no way to defend. I knew the project had gone long. I did not know by how much. I tried to reconstruct from my calendar and my email history. I came up with an estimate I wasn't confident in, and I already knew the client was going to push back because the project had stretched past her original timeline expectations.

She did push back. I didn't have screenshots. I didn't have a log. I had my word against her memory of what we had agreed on.

I wrote off about eight hours to close it out. She paid. I felt terrible.

The Part That Actually Hurt

I ran the numbers afterward as honestly as I could. Including the unbilled hours, the written-off time, and the original deposit that never scaled with scope, I had worked that project for roughly forty percent below my standard rate.

That project took time away from other clients I could have served better. It ran into November. I was distracted for two months.

The loss was not just money. It was opportunity, energy, and the kind of confidence that erodes slowly when you let things slide.

What I Run Now

Every project gets a timer from day one. Before the contract is signed I'm logging discovery call time and pre-project setup. That time has a category. It shows up somewhere.

Every scope addition gets a reply email at minimum. Most get a change order. The small ones at least get a message that says "happy to do that, noting it will add X to the invoice." That message is a time-stamped record.

I use automatic screenshots during work sessions now. Not because I want surveillance on myself but because when a client questions how long something took, I can show them what the work actually looked like. That has ended two potential disputes before they started.

The Thing I Wish I'd Known Earlier

Friendly clients are not safe clients in the billing sense. Friendly clients are often the ones where you relax your systems because the relationship feels good. That's exactly when the systems matter most.

The invoice doesn't care whether you liked working with someone. The hours are the hours. You either recorded them or you didn't.

I didn't. Once. That was enough.

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