The Project That Split Into Two Without Warning

It started as one thing

The original scope was clear. Brand identity work for a new product launch. I had a rate, a timeline, and a project set up in my tracker.

Two months in, the client came back with a request. Could I extend the same visual system to a second product? A spin-off. Different name, different market, but the same team.

I said yes. And I just kept logging everything under the original project.

That was the mistake.

How two becomes one billing problem

When you log hours for two distinct bodies of work under the same project label, you lose the ability to see either one clearly.

You cannot tell how much the original scope cost. You cannot tell how much the extension cost. You definitely cannot tell if the second product justified its own fee.

At invoice time, I had a pile of hours with no clean way to separate them. I made an educated guess at the split. It was probably wrong. I invoiced based on a guess, not a record.

What the client was really asking for

When a client asks you to extend work to a new product, a new market, or a new context, they are starting a new project. Even if it feels like a natural continuation. Even if it uses work that already exists.

The thinking, the iteration, the client calls, the revisions: those are all billable hours for the new thing. If they do not get their own project in your tracker, they get buried.

Clients do not always frame these requests as new projects. They present them as small additions. Your job is to recognize what they actually are.

The tracker setup that protects you

As soon as a project expands into genuinely new territory, create a new project entry. Even if the client name is the same. Even if the rate is the same.

This takes thirty seconds. It means every hour after that point goes to the right place. At invoice time you have two clean records instead of one blurry one.

If the second body of work warrants a new quote, you now have the data to build it. If you need to show the client how time was allocated across both workstreams, you can.

Neat project structure is not bureaucracy. It is billing accuracy.

Scope creep versus scope split

These are different problems.

Scope creep is the gradual expansion of an existing project. Extra revisions, additional features, more review rounds. The project grows but stays roughly the same thing.

A scope split is when one project becomes two. A second product, a second phase with a different deliverable, a second team involved.

Both cost you money if you do not handle them. But scope splits are easier to catch because there is usually a clear moment when the client says something that signals new territory.

That moment is when you open a new project in your tracker.

What I did differently after this

I started treating any request that involved a new deliverable, a new product name, or a new context as a trigger to set up a new project entry.

I also started flagging it in the conversation. Not in a dramatic way. Just a short note: I will set this up as a separate project so we can track it cleanly and invoice it separately.

Most clients actually appreciate that. It shows you are organized. It tells them they will get a clear picture of what each thing costs.

And it means you will never again invoice a client for one project when you actually did two.

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