How to Set Payment Milestones for a Software Project
Software development payment milestones should connect each delivery payment to work you can inspect against agreed acceptance rules. Examples include an approved prototype, a working user journey, a tested release and a completed handover. Treat any deposit separately as an advance with a stated purpose, and choose amounts around the project's scope and risks rather than a universal payment split.
What makes a payment milestone verifiable?
A useful milestone describes an outcome, the evidence needed to review it and the rule for accepting it.
“Backend complete” leaves too much open. “An authorised user can create, edit and retrieve a booking, with the agreed access checks passing in the review environment” gives both sides something concrete to inspect.
Write each milestone with these details:
- Deliverable: What the supplier will provide, including documentation.
- Acceptance criteria: Observable results that distinguish passing from failing.
- Evidence: A working build, test results, design files or another inspectable output.
- Dependencies: Access, content, decisions or external services the work needs.
- Reviewer: The person authorised to accept or reject delivery.
- Review process: How feedback is submitted, the review window and what happens if it is missed.
- Payment trigger: Whether invoicing follows submission, written acceptance or another expressly agreed event.
Keep the acceptance criteria within the supplier's agreed scope. If delivery depends on access the buyer must provide, record that dependency and how delays will be handled.
What are some software development payment milestones examples?
Choose a structure that fits how much is known about the work. These are suggested structures, not standard terms.
| Project situation | Example delivery sequence | What to verify |
|---|---|---|
| Defined, fixed-scope build | Scope baseline → prototype → working workflows → release candidate → handover | Each agreed output meets its written acceptance criteria |
| Product with uncertain requirements | Paid discovery → separately agreed build increments → handover | Discovery answers the agreed questions; each increment delivers its agreed outcome |
| Existing product improvement | Reproduced problem → implemented change → release validation → documentation | The change passes the agreed checks without breaking named existing workflows |
| External integration | Interface agreement → controlled demonstration → end-to-end validation → handover | Both systems exchange the agreed information and handle specified failures |
For an evolving product, agree the scope and price of each increment before work starts. Avoid describing an open-ended backlog as a fixed-price milestone.
For discovery, define outputs such as a prioritised scope, prototype and list of unresolved assumptions. Payment should relate to those outputs, without implying that discovery guarantees a particular build cost.
The choice also connects to your delivery method. See waterfall vs agile: which is best for your project?.
How could a payment schedule work in practice?
Consider a small booking application with agreed customer and staff workflows.
The amounts below are illustrative, expressed in US dollars, and total $24,000. They demonstrate how triggers can differ; they are not a pricing benchmark or a recommended split.
| Stage | Illustrative amount | Agreed payment trigger |
|---|---|---|
| Deposit | $3,000 | Agreement signed and advance invoice issued |
| Scope and prototype | $4,000 | Written acceptance of the specified workflows, exclusions and prototype |
| Working booking journey | $7,000 | Customer booking and staff management checks pass |
| Release candidate | $6,000 | Agreed release checks pass and blocking defects are resolved |
| Final handover | $4,000 | Agreed files, access, instructions and walkthrough are delivered and checked |
Attach a short acceptance sheet to each delivery stage. For the booking journey, it might require a customer to select an available slot, receive confirmation and see a cancellation reflected in the staff view.
Also specify failure cases: an unavailable slot cannot be booked, and an unauthorised user cannot view another customer's booking. A successful demonstration of the happy path alone would not satisfy those criteria.
Record what each invoice covers so the deposit and later payments cannot be counted twice.
How should you handle the deposit?
Describe the deposit as an advance, not as proof of completed delivery.
Before paying it, agree:
- What it funds, such as initial planning or reserved delivery capacity.
- Whether it forms part of the total project price.
- How it is credited against the payment schedule.
- How any unused balance is calculated if work stops.
- What work and records the buyer receives on termination.
Ask for a reasoned amount tied to the actual start of work. Avoid choosing it solely because a particular split sounds familiar.
If substantial discovery is needed before the build can be priced, consider a separate discovery engagement with its own deliverables and acceptance rules.
How do you write acceptance rules that prevent guesswork?
Replace broad adjectives with observable conditions. “Easy to use”, “fast” and “production-ready” need definitions before they can serve as payment triggers.
For each important workflow, state the starting conditions, action and expected result. Specify the supported devices, test data and review environment. Where speed matters, agree a measurable target and the conditions under which it will be tested.
Define defect severity through impact. For example, you might classify an inability to complete the agreed booking journey as blocking acceptance, while allowing a minor spacing issue to remain on a dated correction list.
Require written agreement for those exceptions. A list of unfinished work should identify an owner, a correction deadline and any payment affected.
Use software testing and quality assurance practices to help plan the evidence that accompanies each delivery.
What happens when a deliverable is rejected?
Agree a correction and resubmission process before the first delivery.
A rejection should identify the unmet acceptance criterion, the observed result and enough detail to reproduce it. Screenshots or a short recording can support the report, but connect each issue to the agreed requirement.
The supplier should then respond to each item: confirm a defect, request missing information or explain why it appears to be new scope. Record unresolved disagreements explicitly.
Use the same agreed criteria when reviewing the corrected delivery. If the buyer requests different behaviour, handle it through a written scope change with its own price and schedule implications.
Set a review window and an escalation route for missed feedback. Do not leave silence to imply acceptance unless both parties expressly agree that rule and its consequences.
How should disputed invoices be handled?
Make the disputed amount and reason explicit. Identify the invoice, milestone, acceptance criterion and evidence in question.
A proposed dispute process should cover:
- Who reviews the disagreement on each side.
- How supporting evidence is exchanged.
- Whether an agreed, undisputed portion can be paid separately.
- Whether affected work continues or pauses, and on what terms.
- How revised acceptance or payment decisions are recorded.
Distinguish a delivery dispute from an invoice error. An incorrect amount needs a corrected invoice; an unmet requirement needs a delivery decision.
These are points to settle in the agreement, not assumptions about either party's legal rights.
What should the final handover include?
Define handover as a deliverable with its own checklist. A demonstration does not establish that the buyer has everything needed to operate and maintain the product.
Depending on scope, request the agreed source code, design assets, account access, build and deployment instructions, configuration guidance, dependency information and operating documentation. Include a walkthrough in which the receiving person follows the instructions.
Agree which accounts should be buyer-owned from the start. Keep credentials out of ordinary documents and specify a secure transfer method.
State when ownership or licence rights take effect, what third-party restrictions apply and how support begins. Coordinate final payment and transfer steps so each party knows exactly what happens next.
What common mistakes should you avoid?
Paying for elapsed time while calling it delivery. “End of month” is a calendar event. If you intend to pay for time or reserved capacity, describe that arrangement directly.
Making the last milestone cover every unresolved issue. Review evidence at each stage so final acceptance has a defined scope.
Treating launch as entirely supplier-controlled. Name buyer approvals and external dependencies, then agree how they affect acceptance.
Leaving handover until the invoice discussion. Include its contents and checks in the original schedule.
Using milestones where capacity billing fits better. For ongoing support or exploratory work, a time-based arrangement may fit better. Agree reporting, spending limits and review points instead of inventing fixed delivery outcomes.
What questions do founders ask about payment milestones?
Should every milestone release the same amount?
Only if that matches the work and exposure. Explain the basis for each amount and check that the schedule still supports correction and handover.
Can a milestone be accepted with minor defects?
You can agree this in advance. Define which defects are acceptable, record each exception and specify the correction commitment and payment treatment.
Should the final payment wait until after launch?
Choose the trigger deliberately. You might use release readiness, completed deployment or a defined observation period. State the checks, dependencies and end condition.
What if requirements change during development?
Record the change before adding it to a milestone. Agree the revised deliverable, acceptance criteria, price and schedule, while preserving a clear record of work already accepted.
Milestones work best when the scope behind them is written down; see what a software statement of work should include.
*This post is general information, not legal advice. Check your own agreement and consult a qualified lawyer where rights or obligations are unclear. Last reviewed: October 2026.*