The Project That Finished in Phases and Billed as One

The project had three clear phases. Discovery, build, launch. Each one had its own work, its own decisions, its own hours.

But you invoiced it all at the end. One lump sum. One invoice date.

By then, the first phase was two months old. The client barely remembered it. The invoice felt big because they had mentally moved on from half the work it covered.

Why Single Invoices Hurt Multi-Phase Work

When a client receives one invoice for a long project, they evaluate it against what they see right now, not what the full engagement looked like.

Phase one was research, planning, and strategy. That work shaped everything that came after. But it is invisible by invoice day. The client sees the final deliverable and wonders why the number is so high.

You are not overcharging. You just made the early work disappear by waiting to invoice it.

The Phase Billing Structure That Fixes This

Bill at the close of each phase, not the close of the project. This is not just about cash flow, though that matters too. It is about keeping the work visible.

When you invoice at the end of discovery, the client has just gone through it. They know exactly what they got. The invoice makes sense. They pay it and move into the build phase with a clean ledger.

When you invoice for the build at the end of the build, same thing. The work is fresh. The scope is recent. The number matches what they just experienced.

What Tracking Makes Possible

Phase billing only works if your time is tracked by phase from the start.

If you are logging everything under one project, you cannot easily split out what belongs to discovery versus build versus launch. You have to go back and reconstruct it, which means guessing.

Set up your tracker before the project starts. Create separate entries or project codes for each phase. When you close a phase, pull the report, review the hours, and send the invoice. The data is already organized.

This takes about five minutes to set up at project kickoff. It saves a much longer conversation later when a client pushes back on a large end-of-project invoice.

The Hours That Fall Into No Phase

Every project has in-between time. Handoff calls from phase one to phase two. Emails that reference the old scope while planning the new one. Re-reading notes before a phase kicks off.

Decide in advance which phase those hours belong to. Assign them at logging time, not invoice time. If you wait until invoice time, you will either forget them or struggle to justify which bucket they go in.

A simple rule: assign transition time to the phase that just closed. That work existed because the previous phase needed a proper handoff. It belongs there.

When the Client Asks Why There Are Multiple Invoices

Some clients prefer one invoice per project. That is fine to accommodate. But still track by phase internally.

Even if you send one invoice, you want your own records to show what was spent where. That breakdown helps you quote the next similar project more accurately. It also gives you backup if a client disputes a line item.

"The discovery phase ran fourteen hours. Here is the log. The build phase ran twenty-two hours. Here is that log. That is where the total comes from."

That answer is simple when you have the data. It is almost impossible to reconstruct when you do not.

The Invoice That Pays for Good Setup

The projects that go sideways on billing are almost always the ones that were set up loosely at the start. No phase structure, no rate agreement per phase, no tracking categories.

Five minutes at kickoff, before the first billable minute, is the cheapest investment in a clean invoice you will ever make. Build the structure first. The tracking takes care of itself after that.

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