The Scope That Felt Small and Cost Me Six Weeks

It was supposed to be a small add-on to an existing project. Two extra pages, same design system, same client. The kind of work that feels like it should take a day or two.

Six weeks later I was still in it.

How It Started

The original project was a website redesign. Twelve pages, three months, a rate we both agreed on. It went well enough. The client was happy and asked if I could add a resource section before launch.

Two pages, they said. Similar to what we had already built.

I said yes without opening a new project in my time tracker. It felt too small to formalize. I just kept working.

Where the Hours Went

Week one: the resource section required a content structure I had not built before. Two hours of planning and revision before I could design anything.

Week two: the client wanted a filtering system for the resources. That was new. Not in the original two-page description. Four hours.

Week three: the filtering system needed to work on mobile in a specific way the client had not mentioned initially. Three hours.

Week four: a third resource category appeared that needed its own layout variation.

Week five: revisions.

Week six: more revisions, then final approval.

I logged all of this because my tracker was still running. I just never stopped to look at the total until the work was done.

The Total That Ended the Habit

Thirty-one hours. For a two-page add-on.

I had not opened a separate project for it. I had not set a budget. I had not done a mid-point check. I had just kept working because it felt like it was almost done and I did not want to have a difficult conversation about an informal agreement.

I invoiced eleven hours. That was the number that felt defensible based on the original description. I could not go back and charge for thirty-one hours of work the client had understood to be a small favor.

The difference was twenty hours. At my rate, that was real money I did not collect.

The Rule I Made After That

Every piece of work gets a project. Every project gets a budget. No exceptions for things that feel small.

Small things have a way of becoming complicated. The complexity does not announce itself upfront. It reveals itself as you work. The only way to catch it before it becomes expensive is to be watching the hours as they accumulate.

Now when a client asks for something extra, even something that genuinely is small, I open a new project, set a rough hour budget, and tell the client I will check in if the scope starts to run. That conversation takes two minutes. The one I avoided took twenty hours of free work.

What Tracking Actually Protects

People talk about time tracking like it is about billing more. It is not, or not only.

It is about having a record that makes hard conversations possible. If I had checked my hours at the ten-hour mark on that add-on project, I would have known something was wrong. I could have gone back to the client with data. Here is what we scoped, here is where we are, here is what the rest looks like.

That conversation would have been fine. Clients understand when work is larger than expected if you tell them before the work is done.

Instead I waited, absorbed the overage, and learned the lesson the expensive way.

The next time a client said something would be small, I smiled and opened a new project before I typed a single word.

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