Milestone Billing: How to Split a Project Into Payments

The short answer

Most agencies solve the beginning and the end of a project and leave the middle unfunded. A deposit covers the start, a final invoice covers delivery, and the 8 weeks in between are paid for out of your own account.

1. Split the fee into stages, not into a deposit and a balance.

2. Tie each stage to a date, or to something you control, rather than to the client's approval.

3. Invoice the moment a stage is reached, on the same terms as everything else.

4. Define acceptance, including what happens when the client says nothing.

5. Say what happens when a stage goes unpaid, before it does.

The point of staging is not a bigger total. It is a shorter gap between doing the work and being paid for it, which is the number that actually determines whether a profitable project is survivable.

Where the money actually goes wrong

Take a $24,000 project over 10 weeks, with a 30% deposit and the balance on delivery. You receive $7,200 at the start and $16,800 at the end, and if the final invoice runs on net 30 you are paid in week 14.

Your costs do not follow that shape. Salaries, contractors and tools are consumed steadily across the 10 weeks. So you fund roughly 2 months of the project yourself, having been paid for 3 weeks of it. Nothing has gone wrong, nobody is late, and you are still short.

Staging changes the shape rather than the amount. The same $24,000 split across 4 points pays you as the cost is incurred, which is what the deposit does for week 1 and nothing does for weeks 2 to 10.

Tie stages to dates, not to approval

This is the decision that determines whether staging works, and most agencies get it backwards.

A deliverable-based stage sounds fair: you invoice when the designs are approved. In practice it hands the client a lever, because the trigger for your payment is an action only they can take. A client who is slow, distracted or short of cash can defer your invoice indefinitely without ever refusing anything, and you have no grounds to complain, because the stage genuinely has not been reached.

Use dates where you can, and your own delivery where a date feels arbitrary. Where the client insists on approval as the trigger, pair it with a deemed acceptance clause so the trigger cannot be held open forever.

A split that works

For a fixed-scope project of 8 to 12 weeks, 4 points is usually enough. More than that and the admin costs more than it returns:

The front weighting is deliberate. Your risk is highest early, when you have committed the team and hold nothing, and lowest at the end when the work is done and visible. Keeping the last stage relatively small also reduces what is at stake in the final conversation, which is the one most likely to become a dispute.

For longer or open-ended work, monthly billing in arrears of the month worked is simpler than stages, and the structure in the retainer piece applies instead.

Define acceptance, including silence

Wherever approval matters, the contract needs to say what approval is and how long the client has to give it. Without that, a stage stays open by default:

The client will review each deliverable within 5 business days of receipt and either approve it or provide consolidated written comments. Where no response is received within that period, the deliverable is deemed accepted and the corresponding stage becomes payable.

Deemed acceptance is standard commercial drafting and rarely contested at signature, because a client reading it before a project starts sees a reasonable review window rather than a trap. Raising it mid-project is much harder, which is the argument for putting it in at the start alongside your payment terms.

Consolidated comments matter too. Feedback arriving in 11 messages over 3 weeks is what turns a 5-day review into a month, and asking for it in one round is easier to request in a contract than in the moment.

Invoice each stage properly

A staged project multiplies the number of invoices, and each one has to clear the same checks the final one would:

• Invoice on the day the stage is reached, not at month end. A stage invoiced 3 weeks late has given the client 3 weeks of free credit.

• Reference the stage on the invoice, so accounts payable can match it to the contract or the purchase order.

• Check the purchase order covers the whole fee, not the first stage. An invoice above the remaining balance fails silently, as the PO piece describes.

• Keep the terms the same across stages. Different terms on different invoices confuse the payment run and give you nothing.

Watch the payment period as well. In the EU the Late Payment Directive requires businesses to pay within 60 days unless they expressly agree otherwise and the arrangement is not grossly unfair, so a stage invoiced on net 90 by default is worth questioning rather than accepting.

When a stage goes unpaid

Staging gives you something a single balance invoice never does: a decision point in the middle, while your position is still strong and before the exposure is large.

Say in the contract that work on the next stage does not begin until the previous one is paid. It is easier to state at signature than to introduce later, it is proportionate, and it reverses the moment payment clears. The mechanics are the same as pausing work, but a staged contract makes the boundary obvious rather than confrontational.

The alternative is what usually happens: stage 2 goes unpaid, the team carries on because stopping feels dramatic, and by the time anyone acts you are owed 3 stages instead of 1.

What staging does not fix

Stages allocate an agreed fee across a timeline. They do not price work nobody agreed to, so extra requests still need pricing when they arrive, as the scope piece sets out. A staged contract with unpriced additions is the same problem with better cash flow.

They also do not help where the client cannot pay at all. Staging limits how much you lose in that case, which is worth a great deal, but it is a containment measure rather than a cure.

FAQ

How should I split a project into payments?

For a fixed-scope project of 8 to 12 weeks, 4 points works: 30% on signature, 25% at week 4, 25% at week 8 and 20% on delivery. Weight it towards the front, because that is when your risk is highest and you hold the least.

Should stages be tied to milestones or to dates?

Dates, where possible. A stage triggered by client approval can be deferred indefinitely by a client who simply does not approve, and you have no grounds to object because the stage has not been reached. Where approval must be the trigger, add a deemed acceptance clause.

What is deemed acceptance?

A contract term saying a deliverable counts as accepted if the client does not respond within a stated window, commonly 5 business days. It stops an approval-triggered stage from staying open forever, and it is far easier to agree at signature than mid-project.

Will clients object to staged payments?

Rarely, when it is presented as the normal structure rather than as a response to something. Staged payments are ordinary in construction, consulting and software, and many procurement teams prefer them because the spend is spread across periods.

How many stages is too many?

Past 4 or 5 on a typical project the administration costs more than the cash flow gains, and every additional invoice is another chance for something to stall in accounts payable. Fewer, larger stages beat many small ones.

What if the client stops paying mid-project?

Stop before the next stage, which is the point of staging. Say so in the contract at signature, so pausing reads as the agreed process rather than as an escalation, and resume the moment the outstanding stage is paid.

Not legal advice. Contract terms including acceptance, suspension and payment periods depend on the wording you sign and on local law. Have your template reviewed before relying on it.