Billing and charging

Milestone billing

Milestone billing is a billing approach where invoices are issued upon completion of defined project milestones (e.g. design sign-off, beta launch, final delivery), rather than on a time-based or calendar-based cadence, common in fixed-price design, development, and construction work.

Applies in: Global

Milestone billing matches the cash to the work. Instead of invoicing for hours or on a calendar (monthly retainer), the supplier invoices when something objective happens: a deliverable is approved, a phase is signed off, a stage of construction is verified. The client pays for verifiable progress, the supplier gets predictable cash inflows aligned with the work they have already done.

The structure starts with the milestones themselves. A 4-milestone project might split as 25% on contract signature (deposit), 25% on discovery sign-off, 25% on beta delivery, 25% on final acceptance. The percentages and the milestone definitions need to be specific enough that both sides agree when a milestone is hit. "Beta launched" is testable; "meaningful progress made" is not.

The risk on milestone billing is the partial-completion case. If the project stalls between milestones, the supplier has done work without an invoice trigger. The defence: smaller, more frequent milestones reduce the gap, and a contract clause for time-based interim billing covers stalls. The supplier should also issue invoices the moment a milestone is hit, not at the end of the month, because the milestone hit is the agreed payment trigger.

Common questions about Milestone billing

How do I structure milestones?
Specific, testable, and small enough that the gap between any two is manageable. A 12-week project with 2 milestones leaves you exposed to 6-week cash gaps; the same project with 4-6 milestones smooths the cash flow. Define each milestone in writing ("design sign-off" needs to say what "sign-off" looks like) so neither side can argue when it is hit.
What happens if a milestone is partially complete?
By default, the milestone is either hit or not, and the invoice triggers only when it is fully hit. To avoid being unpaid through long stalls, build in interim time-based billing ("if more than 30 days elapse between milestones, invoice for hours actually worked") or split milestones into smaller pieces upfront. The cleanest model is small enough milestones that partial completion is rare.
Is milestone billing better than time and materials?
Different trade-offs. Milestone billing matches cash to deliverables and is easier for clients to budget; the supplier carries the risk of scope creep within a milestone. T&M bills actual effort and the client carries the scope risk. Milestone billing fits fixed-price projects with clear deliverables. T&M fits exploratory or research-heavy work where the deliverable is the answer.

Use JupiterInvoice for Milestone billing

Milestone billing on a JupiterInvoice invoice is a field, a label, and an audit trail your buyer can act on without an email back-and-forth.

Related terms

Send an invoice that handles milestone billing properly

Free. No signup. Tax labels, payment terms, and PO numbers are first-class fields, not workarounds.

Create an invoice

No signup required. Build now, save later.