How to Structure Client Payments So You Never Chase an Invoice
- Chasing invoices is a structure problem, not a client problem. Fix the structure and the chasing disappears.
- Tie every payment to a milestone the client can see, and collect the last one before final handover.
- Front-load the schedule: never be more built than you are paid.
Chasing Invoices Is a Structure Problem
If you are sending reminder emails and refreshing your bank app, the problem started before the work did. Late payment is almost never about a bad client. It is about a payment structure that let the client receive everything before they paid for it. Once the value is delivered, your leverage is gone and the invoice becomes optional in their mind.
The builders who never chase money are not better at nagging. They set a payment schedule at the start that ties each release of money to a visible step of progress. The structure collects the payment. They never have to.
The Payment Ladder: Tie Money to Milestones
Break the project into a Payment Ladder - a small number of milestones, each with a payment attached, that the client can see and understand. For most builds three rungs is enough. Bigger projects get more rungs, but the principle never changes: money moves when a milestone is hit.
| Milestone | Share | Triggers when |
|---|---|---|
| Deposit to start | 40% | Agreement signed, before any work begins |
| Working version | 30% | The core build is demoed and approved |
| Final handover | 30% | Paid before you hand over final access or files |
A simple three-rung Payment Ladder for a fixed-price build
The exact split can flex, but the shape should not. Each milestone is something the client can point to, so a payment request never feels arbitrary. You are not asking for money because it is Tuesday. You are asking because the thing you both agreed on just happened.
Front-Load So You Are Never Underwater
The golden rule of a payment schedule: never be more built than you are paid. At every point in the project, the money collected should cover the work delivered so far, with a little ahead. A 40 percent deposit means you are never working the first stretch for free, and collecting the final payment before handover means the last rung is never the one that goes unpaid.
Put It in Writing and Automate the Ask
A payment structure only protects you if the client agreed to it before the work started. Put the ladder in the one-page agreement you send up front: the milestones, the amounts, and when each is due. When you request a payment later, you are not introducing a new demand, you are following the plan they already signed.
- Write the milestones and payment split into the agreement before any work begins.
- Collect the deposit and let it clear before you start - no exceptions.
- Send each milestone invoice the moment the milestone is hit, while the progress is visible and fresh.
- Hold final access and files until the last payment clears, then hand over cleanly.
Short, practical drops on offers, outreach, pricing, and closing clients with Claude Code. No spam, unsubscribe anytime.
Frequently asked
How should I split payments on a client project?
For most fixed-price builds, a three-rung split works well: a deposit up front to start, a middle payment when the working version is approved, and a final payment before handover. A common shape is 40 percent, 30 percent, 30 percent, but the exact numbers matter less than the rule that you are never more built than you are paid.
Should I take a deposit before starting client work?
Always. A deposit filters serious clients from time-wasters and means you never work the opening stretch of a project for free. Let the deposit clear before you begin - a client who will not pay to start is showing you how the rest of the invoices would have gone.
How do I stop clients from paying late?
Fix the structure, not the follow-up. Tie each payment to a visible milestone, put the schedule in a signed agreement up front, invoice the moment each milestone is hit, and hold final handover until the last payment clears. When the structure collects the money, you stop having to chase it.
What if a client wants to pay everything at the end?
Decline politely and offer the milestone structure instead. Pay-on-completion puts all the risk on you and removes every ounce of leverage once the work is delivered. Explain that milestone payments keep the project moving and protect both sides, then hold the line - it is a standard, reasonable ask.
Last reviewed July 16, 2026.
Co-founder of the Claude Code Profit Room. Built and sold AI services to real clients; writes about offers, pricing, outreach, and closing with receipts.
More from Duncan Rogoff →
