The Client Who Added One Deliverable Per Week

The first extra thing was reasonable. A second page on the site. Fine. The second extra thing was also reasonable. A revised bio section. Sure. By week six you were managing a full rebrand and still charging the original flat rate.

This is how scope creep actually works. Not a dramatic ask. A slow accumulation.

One Addition Does Not Feel Like Scope Creep

The problem is that each individual request sounds small. And it probably is small, taken alone. Five extra minutes here. Fifteen there. A quick revision that turns into a full structural change.

None of it triggers alarm bells in the moment. You say yes because it feels rude not to. You move on because you have other work waiting.

But you are building a debt you will eventually pay out of your own pocket.

Your Time Log Sees What You Do Not

If you are tracking time per project and per task, something interesting happens over weeks. The hours start looking wrong relative to your estimate.

Not dramatically wrong. Maybe you budgeted 20 hours and you are sitting at 22 after three weeks with a lot of work still left. That gap is a signal. It means something shifted.

Without a time log, you would not catch it until invoice day. By then, you have already done the work. You have two options and neither is good. Bill for the real hours and have an uncomfortable conversation. Or swallow the loss and send a number that does not reflect reality.

With a time log, you catch it at 22 hours. You still have the conversation, but now you have it before more work piles on.

How to Use Your Data in That Conversation

Clients are not always aware they are adding scope. Most are not doing it deliberately. They just have ideas and you are the person who makes them happen.

When you show up to that conversation with actual time data, the dynamic changes. You are not complaining or estimating. You are reporting.

"Here is what we agreed on. Here is what has been added since. Here is where the hours currently stand." That is a factual conversation. It is much easier than "I feel like this project has grown."

Time-Trak lets you pull this kind of summary without digging through notes. You see the hours by project, broken down by task. You can show exactly where the time went. That is a very different thing than a vague feeling that things have expanded.

Build the Habit Before the Next Project Starts

The real fix is not just catching scope creep mid-project. It is building the tracking habit before kickoff so that you always have the data when you need it.

Start the timer on the first call. Log discovery. Log the back-and-forth emails if they are billable. Log every revision round separately so you can see the pattern.

When a client adds something new, log it under a separate task. Call it something clear. "Scope addition, week 4." Over time you will be able to look back at your logs and see exactly which clients add scope regularly and how much it typically costs you.

That changes how you quote them next time. Or whether you quote them at all.

The Invoice Is Not the Place to Solve This

If you wait until invoice day to address scope creep, you have waited too long. The work is done. The leverage is gone.

Track early. Check your hours mid-project. Set a personal rule that if actual hours hit 80 percent of your estimate, you review the scope before going further.

One deliverable per week sounds manageable until it is twelve deliverables and one original fee.

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