Fixed-fee projects that run longer than a few weeks need to be billed in stages, or you end up funding the client's project with your own cash. Milestone billing splits the fee into payments tied to real progress: a deposit to start, a payment when the design is signed off, another when the build is done, and the balance on launch. Clients like it because they pay for what they can see. You like it because cash comes in while the work is happening.
The trouble is that each milestone invoice on its own looks like a random fragment of a bigger number. This template solves that by printing the whole schedule on every invoice, marking which stage is being billed, what approved it, and what is left.
TL;DR
The milestone invoice template bills one stage of a fixed-fee project and prints the full schedule every time: each milestone, its percentage and amount, status (paid, billing now, upcoming), the approval that triggered this payment, any change orders, a [TAX RATE]% placeholder and the remaining balance. Send it the day a milestone is approved. Three to five milestones suit most projects of a few weeks to a few months.
What's inside
- Project block — contract and SOW references, total project fee.
- Payment schedule table — every milestone with deliverable, percentage, amount and status.
- This milestone — what was delivered, when it was approved and by whom.
- Change orders — approved changes that adjust the schedule, with references.
- Totals — this milestone amount, tax placeholder, paid to date, remaining balance.
- Payment terms — due date and what happens to the next stage if payment is late.
When to use it
Use it for any fixed-fee project with a defined payment schedule: website and app builds, brand identity projects, video productions, consulting engagements with phase gates, event planning, interior design. It works best when your contract or statement of work lists milestones with clear deliverables.
The first payment is usually better sent as a deposit invoice, since nothing has been delivered yet. For time-based work, use an hourly invoice instead. If scope changes mid-project, capture it on a change order form before it shows up here.
Designing milestones that get paid
A good milestone has a deliverable the client can see and approve. "Design phase complete" is vague. "Homepage and two inner page designs approved in writing" is clear.
Common schedules look like this:
| Project length | Typical split |
|---|---|
| 3 to 6 weeks | 50% deposit, 50% on delivery |
| 1 to 3 months | 30–40% deposit, 30% mid-point, 30–40% on delivery |
| 3 months or more | 20–25% deposit, then three or four equal milestones |
Keep the last milestone modest but meaningful. If 60% of the fee sits on the final delivery, the client holds most of the cards at the end, and small issues can stall a big payment.
Approval triggers and delays
The weakest point in milestone billing is approval. Some clients take weeks to sign off. Your contract should set a review window and a deemed-approval rule, such as approval assumed after five business days with no written feedback. On the invoice, note the trigger: "Approved by [name] on [date]" or "Deemed approved on [date] per clause 4.2." The how to scope a fixed-fee project post covers defining approvals at the scoping stage.
Customize it in your COLO workspace
In COLO you can send a proposal with line items for each stage, have the client accept it in the client portal, and convert it into an invoice. Invoices support partial payments, so each stage payment you record reduces the balance. You can email invoices or download a PDF, and clients pay by card through Stripe or by PayPal. See Invoicing and Payments.
Deliverables, approvals and feedback can live in the project's tasks, comments and files, which gives you a dated record when you note the approval on the invoice.
Common mistakes
- Vague milestones. If nobody can say when it is done, nobody can say when it is due.
- No schedule on the invoice. The client cannot see how this payment fits the whole.
- Back-loading the fee. A large final payment invites delay.
- Absorbing scope changes. Every change belongs on a signed change order and on the schedule.
- Starting the next stage unpaid. State that the next milestone starts when this invoice is paid.
FAQ
Q: What is a milestone invoice?
A milestone invoice bills one stage of a fixed-fee project when that stage is complete. It shows the full payment schedule, the milestone being billed, the approval that triggered it, and the remaining balance.
Q: How many milestones should a project have?
Three to five is common for projects of a few weeks to a few months. Too few and you carry the cost of long stretches of work; too many and admin starts eating your margin.
Q: What triggers a milestone payment?
Define it in the contract: usually client approval of a deliverable, or delivery plus a set number of days without written objections. Avoid triggers that depend on things outside your control.
Q: What if the client delays approving a milestone?
Include a deemed-approval rule in your contract, for example approval is assumed if no written feedback arrives within five business days. Then invoice on that date and note it on the invoice.
Q: Can milestone amounts change during the project?
Only through a signed change order. When scope changes, update the schedule in writing and reflect the new amounts on the next milestone invoice.