Milestone Billing: How to Build a Payment Schedule That Works
Milestone billing ties a payment to a defined project checkpoint, often a delivered and accepted phase. A milestone payment schedule sets out the deliverable, amount, review step, and payment term. A signing deposit or calendar installment can appear in the same schedule, but it is not itself a completed-work milestone.
This guide covers how the model works, how it can overlap with progress billing, three useful payment-schedule examples, and a step-by-step method for building your own.
TL;DR
- Tie each completed-work payment to a clear deliverable and agreed review process.
- Progress, milestone, and calendar billing describe useful triggers that can coexist in one agreement.
- Price the whole project from its scope and costs before allocating payment amounts.
- A signing deposit can fund early work; it does not guarantee cost coverage.
- Invoice timing does not determine accounting treatment. Ask a CPA about complex or audited work.
Table of Contents
- What milestone billing is
- How a milestone payment schedule works
- Milestone vs. progress vs. periodic billing
- Three payment-schedule examples to learn from
- How to build your own schedule
- Milestone billing for software and web projects
- What the accountants care about
- Benefits and pitfalls
- Our perspective
- From brief to a phased quote
- FAQ
- Sources
What milestone billing is
Milestone billing connects an agreed payment to a project checkpoint. Usually that means delivering a defined phase, getting the review called for in the agreement, and then invoicing. The parties agree on the deliverable, amount, review process, and payment term before work starts.
On Upwork, a milestone divides a fixed-price contract into work with a set payment. Its own process requires funding before work and has platform-specific review and release rules. For a direct client project, the signed agreement controls instead. That distinction matters for designers, consultants, copywriters, and studios working outside a marketplace.
What counts as a milestone
Useful completed-work checkpoints include an approved strategy document, delivered design concepts, a reviewed architecture phase, final video files, or a tested site handoff. Name the output so both sides can tell when it has been delivered. Our guide to milestones and deliverables with templates for project managers gives more examples.
A signing deposit is a payment event, not completed work. A calendar installment may also sit beside deliverable checkpoints in a broader schedule. Make the trigger explicit for each payment.
How a milestone payment schedule works
Build the schedule from the project plan, then check whether the payment dates fit the effort and the client's review cycle:
- Define the scope. Identify deliverables, revision rounds, assumptions, and exclusions so the payment checkpoints refer to actual work.
- Choose reviewable checkpoints. A brand strategy, storyboard, or construction document set is easier to assess than "mostly done."
- Assign amounts. Use fixed amounts or shares of the agreed total, and make sure they add up.
- Agree the trigger. State what is submitted, who reviews it, how feedback is given, and how long review may take.
- Set payment terms. Write down when an invoice may be issued and when payment is due.
- Deliver and document the review. Use the approval method the agreement specifies; do not assume an email or silence has legal effect by itself.
- Invoice under the agreed terms. Keep the delivered work and approval record with the invoice.
The platform guidance illustrates the value of agreeing scope, deliverables, dates, feedback, and revisions before work. Its funding and release rules apply to that platform, not every client contract.
Milestone vs. progress vs. periodic billing
These labels describe common invoice triggers. They are not mutually exclusive; an agreement can combine them.
| Billing trigger | Illustrative use | What to specify |
|---|---|---|
| Accepted deliverable or phase | Pay when a brand guide or design phase reaches the agreed checkpoint | Output, review, amount, and payment term |
| Measured progress | Bill for an agreed share of work completed | How completion is measured and approved |
| Calendar interval | Bill monthly for a retainer or ongoing services | Period, included work, and amount |
Stripe describes several billing models, and Procore discusses progress measurement in construction. In architecture, AIA describes percentage completion, monthly fee schedules, and milestone fees as distinct options. A studio might combine a signing amount, deliverable payments, and monthly maintenance. Choose triggers that the client can understand and the team can document.
Three payment-schedule examples to learn from
These documents show how payment checkpoints can follow different kinds of work. Compare their triggers with your own deliverables, effort, and review cycle.
A website project: $35,100 in six payments
An SEC-filed website development agreement totals $35,100. It lists $4,980 at signing, followed by $9,280 after website-development completion, $12,880 after demo API and UI completion, $2,200 after QA completion, $2,160 after deployment and setup, and $3,600 after documentation delivery. Its listed completion payments are due within 30 calendar days after the relevant milestone. The useful lesson is its specificity: each later payment names a distinct output.
A marketing schedule sample: $20,000 with a signing payment
A University of Nebraska-Lincoln example payment schedule exhibit shows a $20,000 total and a $4,000 signing amount. This university-hosted sample mixes strategy, brand, advertising, press, and social deliverables with monthly and quarterly payments. It specifies a five-business-day review period and 30-day invoice terms. Use it to see how deliverable and calendar triggers can share one schedule.
An architecture fee: 100% or 80/20
The American Institute of Architects' best practices on charging for services describe a fee paid in full on phase completion and acceptance, or 80% on work completion with the remainder on acceptance. This is an architecture practice example. It shows why the agreement should distinguish delivery from acceptance when those dates may differ.
A worked example you can adapt
Consider this illustrative $12,000 brand identity project:
| Milestone | Deliverable | Share | Amount |
|---|---|---|---|
| 1. Kickoff | Signed agreement and deposit | 30% | $3,600 |
| 2. Concepts | Three logo directions presented | 25% | $3,000 |
| 3. Refinement | One direction developed through two agreed revision rounds | 25% | $3,000 |
| 4. Handoff | Final files and brand guide delivered | 20% | $2,400 |
The kickoff payment is a deposit rather than payment for completed work. The four amounts add to $12,000. Adjust the shares to the project's estimated effort, cash needs, and agreed review cadence.
How to build your own schedule
Start from a real scope, not a round number
Estimate tasks, roles, hours, direct expenses, overhead, contingency, and the margin target before dividing the quote into payments. Our guide to turning a messy brief into a clear project quote covers that sequence, while creative project pricing beyond spreadsheets discusses why revision and dependency assumptions matter.
Review the calculated margin when changing price or cost assumptions. The guide to project margin for small agencies explains the calculation; a favorable figure still depends on the inputs and the work actually delivered.
Weight payments to your cost curve
Compare planned effort and cash outlays with each proposed invoice date. A project that uses most of its hours before the first review may need a different deposit or interim trigger. A deposit can reduce the time you carry early work, but its adequacy depends on the actual terms and payment.
Write the acceptance rule into the contract
For each deliverable, specify what the client receives, who reviews it, how feedback is consolidated, the review period, revision scope, and the payment term. Agree what happens when feedback is late. The agreement, rather than a generic rule, determines whether silence pauses the schedule or has another effect. For consequential default or acceptance language, seek legal advice.
Cap the revisions
State how many rounds the amount includes and how extra work is proposed and priced. This gives the client a clear choice if the direction changes after review.
Keep a time record anyway
Track hours against the estimate even on fixed-price work. It shows which phase took longer and gives you better evidence for a future quote. Our guides on time tracking for quote continuity and time tracking software for creative teams explore that comparison.
Milestone billing for software and web projects
A web or integration project may have reviewable design, build, QA, and handoff stages. Define what each stage delivers and how a client tests or accepts it. Tie each proposed payment to that output and review. For a software-specific cost context, these software project cost benchmarks offer a comparison point alongside your own estimate.
Our guides to software integration scope and estimates and web and app studios show ways to break down such work before choosing payment checkpoints. The same principle applies to packaging, motion, and architecture briefs: start with the deliverables the client can review.
What the accountants care about
The date a client pays an invoice is a commercial term. It does not, by itself, decide when revenue is recognized in accounts. For audited, grant-funded, or otherwise complex work, ask a CPA how the current rules apply to the agreement.
For some U.S. Department of Energy EERE financial-assistance awards, reimbursement follows submitted deliverables and agency verification or acceptance. Check the specific award terms when planning those invoices.
Benefits and pitfalls
Well-defined checkpoints can make the work and payment expectations easier to discuss. Staged invoices may reduce how long a freelancer carries project costs, depending on the amounts, due dates, and whether the client pays on time. Clients can review a real output before the next phase begins.
Stripe highlights the challenge of choosing realistic milestones and clear invoice triggers. Watch for work added inside a phase without a revised agreement, long gaps before the next invoice, and feedback delays that shift the schedule. Document changes and their price rather than assuming the original amount covers them. Our guide to proposal timelines for agencies and freelancers helps account for review time.
For a short, simple job, an agreed deposit and final balance may be enough. Add checkpoints when they make the deliverables, review, and payment schedule clearer.
Our perspective
The Roadbase site explains the planning workspace behind this approach.
A tidy payment schedule begins with a believable work breakdown. If a studio has not mapped the deliverables, review rounds, roles, and hours, percentages alone cannot show whether a checkpoint fits the work. Draft the plan, review the estimate, and then agree the payment triggers with the client. As actual time accumulates, compare it with the estimate to inform later quotes.
From brief to a phased quote
Have a real brief, notes, or a PDF? Bring it into Roadbase to generate an editable draft of phases, tasks, roles, hours, and timing. Review and adjust the breakdown, add your role costs and rates, and consider labor, overhead, direct expenses, contingency, and target margin while building the quote. Then export the reviewed plan and quote as a proposal PDF. Use that breakdown with the client to agree on payment checkpoints and terms.
See the Roadbase pricing page, or explore from the Roadbase homepage. If you are comparing approaches, best project roadmap tools for one-sitting proposals offers criteria to consider.
FAQ
What is a milestone payment?
A milestone payment is an agreed amount linked to a defined checkpoint, commonly completion and review of a deliverable or phase. A signing deposit can appear in the same schedule, though it is not payment for completed work.
How many milestones should a project have?
Choose the number from the project's length, deliverables, review cadence, and cash needs. A simple job may need only a deposit and final balance; a longer project may benefit from several clear checkpoints. Each extra trigger should make the schedule easier to understand, not merely divide the total into smaller numbers.
What percentage should the deposit be?
There is no universal percentage. The Nebraska sample includes a $4,000 signing amount on a $20,000 example. For your project, compare early effort and expenses with the proposed amount, then negotiate the balance across later phases.
What if the client does not approve a milestone?
Follow the agreement's review process: identify the requested changes, document feedback, and agree how the work or schedule moves forward. The contract should say what happens if the client does not respond within the agreed period. Get legal advice on a consequential acceptance or default clause.
Is milestone billing the same as progress billing?
They can overlap. Milestone billing commonly ties an invoice to a defined phase or deliverable; progress billing commonly uses an agreed measure of completed work. A contract can use both triggers, so define the method and approval step for each payment.
Sources
For historical background, see the 2010 Topic 605 milestone-method text; current accounting questions call for current guidance and a CPA.
- Understanding milestones on fixed-price contracts, Upwork
- Types of billing: A guide for businesses, Stripe
- Construction Progress Billing, Procore
- Website development agreement, SEC filing
- Example Exhibit B: Payment Schedule, University of Nebraska-Lincoln
- AIA Best Practices: Charging for services
- 2010 Topic 605 milestone-method text, PwC Viewpoint (historical)
- EERE 336.5: Recipient Guidance for Invoicing, U.S. Department of Energy
- Software project cost benchmarks, Vicedomini Softworks