The Client Who Kept Asking for Small Changes

It Always Starts With One Thing

They asked to tweak the headline. Fine. Then the color. Fine. Then the layout on mobile. Still fine. Each request took twenty minutes. None of them made it to an invoice.

That is how it goes. Small changes feel too minor to log. You knock them out, move on, and think nothing of it. But those twenty-minute windows stack. By the end of the month you have worked a full day on requests that no contract covered and no invoice captured.

This is not scope creep in the obvious sense. There is no big add-on. No dramatic pivot. Just a slow bleed of micro-tasks that each feel too small to mention.

Why You Do Not Track Them

There are two reasons small changes go untracked.

First, you tell yourself it is not worth the friction. Starting a timer for a fifteen-minute fix feels like more effort than the fix itself. So you skip it.

Second, you assume you will remember it later. You will not. By the time you sit down to invoice, the small stuff is gone. Your memory keeps the big work. The tiny edits disappear.

The result is an invoice that reflects maybe seventy percent of what you actually did.

The Fix Is Habit, Not Willpower

You are not going to start remembering small tasks through effort alone. The solution is making tracking the path of least resistance.

A floating timer widget solves this. It sits on your screen. You see the client name, you click start, you fix the thing, you click stop. The log entry exists before you even think about whether it is worth tracking.

That is the only version of this that works long-term. If logging requires you to open an app, navigate to a project, and fill in a description, you will skip it every single time for anything under thirty minutes.

What the Log Actually Shows You

After a few weeks of tracking everything, including the small stuff, the pattern becomes obvious.

You will see one client with forty entries in a month. Half of them are under twenty minutes. Add it up and that client owes you for six hours of work you were never going to bill.

You will also see which types of requests repeat. If a client asks for the same category of revision every week, that is a workflow problem or a scope problem. Either way it is information you can use to reset expectations or renegotiate.

Without the log you just feel vaguely underpaid and cannot explain why.

How to Handle It When You Bring It Up

Most clients do not realize they have been doing this. When you show them the log, the reaction is usually surprise, not defensiveness. The data does the talking.

You do not need to say the project has been mismanaged. You say: here is what the last month actually looked like. You show the time entries. You let them see the pattern.

That conversation is much easier when your data is specific. Client asked to revise CTA copy. 18 minutes. Client asked to adjust mobile spacing. 22 minutes. Client requested new section header options. 31 minutes. That is a bill. It is also a signal that future work needs a defined revision round built into the scope.

Start Tracking the Small Stuff Now

You do not need a policy change or a difficult email. You need a timer running the moment the request comes in.

If you have Time-Trak open, the floating widget is there. Click start when the Slack message lands. Click stop when you send your reply. Do that for thirty days and read the logs.

You will find hours you forgot you worked. You will find a client type you need to reprice. You will find the bill you were already owed.

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