Milestone & Progress Billing for Project Work
Module 2: Billing & Invoicing Essentials, Chapter 3
The short answer
Milestone billing invoices a project in stages tied to specific deliverables, rather than on a fixed monthly schedule or all at once at the end. It's the right structure whenever a project has a defined scope, a clear endpoint, and payments that should track actual progress rather than the calendar.
When does milestone billing make more sense than a retainer?
Retainers fit ongoing, open-ended work where the same amount of effort repeats every cycle. Milestone billing fits the opposite case: a defined project with a beginning, an end, and distinct phases. If the engagement has a scope document and a final deliverable, milestone billing usually protects cash flow better than either a single invoice at the end or a retainer that doesn't really match the shape of the work.
What does a typical milestone schedule look like?
| Milestone | Typical % | Triggered by |
|---|---|---|
| Kickoff / deposit | 25–30% | Signed agreement, before work begins |
| Delivery / mid-project | 40% | Major deliverable or phase completion |
| Final acceptance | 30–35% | Client sign-off on completed work |
This isn't a fixed formula, the right split depends on how front-loaded the actual work is. A design-heavy first phase might justify a larger kickoff payment; a project that's mostly execution near the end might weight the final milestone more heavily.
Why does the deposit matter so much?
Because it converts a project from something you're financing on the client's behalf into something the client has real commitment to. For larger projects, a deposit of 25-50% of the total before work begins is common practice, particularly on new client relationships where payment history doesn't exist yet. It also directly protects your cash flow: without it, you're covering weeks or months of costs before seeing a dollar back.
What's the biggest mistake in setting up milestone billing?
Leaving the trigger for each milestone vague. "Invoice 2 upon substantial progress" invites a dispute, since "substantial" means something different to each side. "Invoice 2 upon delivery of the approved wireframes" doesn't, it's a specific, checkable event both sides agreed to in advance. Every milestone needs a trigger clear enough that neither side has to interpret it.
Quick check
Three questions. No email required, this one's just for you.
1. When does milestone billing generally fit better than a retainer?
2. Why is a vague milestone trigger like "substantial progress" a problem?
3. What's a common deposit range for larger project-based work?
Frequently asked questions
Can milestone billing and a retainer coexist on the same engagement?
Yes, some relationships combine a retainer for ongoing baseline work with milestone invoices for larger, discrete projects that come up separately. Keep the two clearly separated on paper.
What happens if a milestone is delayed by the client, not by you?
This should be addressed in the agreement upfront. Many milestone schedules specify that a delayed sign-off doesn't delay the invoice itself, only the start of the next phase.
Should the final milestone always be the largest?
Not necessarily. Weighting too much value into the final payment increases your risk exposure across the whole project. A meaningful deposit and a substantial mid-project milestone both reduce that risk.
Sources
- Worksbuddy, milestone billing and deposit practices for professional services
- Aviy, milestone billing guide
Prefer to have this run for you?
A Receivables Review shows exactly where your own AR process could improve.
Book a Receivables Review