Business

Payment Milestones in a Software Project: How to Tie Money to Results

November 11, 2026 · 5 min read · Etzal Group Team

A project is 70 percent paid and, by the client's estimate, 30 percent built. The vendor's team has thinned out. Every request for progress is met with reassurance. The client has little leverage, because the remaining money is smaller than the remaining work. This situation is almost always created on the day the contract was signed, in the table of payment milestones that nobody examined closely.

What a payment schedule really does

At every point in a project, one party has given more than it has received. A schedule decides which party, and by how much.

  • If payments run ahead of delivery, the client carries the risk that the vendor will not finish.
  • If delivery runs far ahead of payment, the vendor carries the risk that the client will not pay.

A fair schedule keeps the gap small in both directions. Neither side should be able to walk away with a large advantage.

The four rules

1. Pay for results you can verify. "Phase 2 complete" is the vendor's opinion. "Order module passes the agreed acceptance tests in the staging environment" is something you can check.

2. Keep each payment proportionate to the value delivered. If a milestone delivers a fifth of the system, it should release roughly a fifth of the money.

3. Keep milestones close together. Four to eight weeks apart. Long gaps hide problems and create large exposures.

4. Hold something back to the end. A final payment on go-live and a retention through the warranty period keep attention on the last, least glamorous work.

What makes a good milestone

A milestone needs three things written down:

  • A deliverable. Named and specific.
  • An acceptance test. How both sides will know it is done.
  • A time limit for review. For example, the client has ten working days to test and either accept or list defects. Silence beyond that period counts as acceptance. This protects the vendor from a client who delays payment by never reviewing.

Weak milestones: "Design completed", "Development 50 percent", "Testing started". None can be verified by the client.

Strong milestones: "Clickable prototype of all screens approved in writing", "Sales order and invoicing modules deployed to staging and passing test cases 1 to 40", "Data from the old system migrated and reconciled to the agreed totals".

Three example schedules

A. Fixed-price project, about six months

MilestoneShare
Contract signed15%
Requirements and design approved15%
Release 1 accepted on staging20%
Release 2 accepted on staging20%
User acceptance test passed15%
Go-live10%
End of warranty period5%

The client is never more than about one milestone ahead in payment, and 30 percent stays unpaid until the system is tested by its users.

B. Discovery first, then build

MilestoneShare
Discovery phase, paid separately at a fixed feeFixed fee
Build contract signed10% of build
Each of four releases accepted18% each
Go-live13%
End of warranty5%

Paying for discovery separately lets both sides stop after it with something useful: a requirements document the client owns.

C. Time and materials

No milestones in the same sense, but the same principles apply:

  • Invoice monthly or fortnightly, in arrears, with timesheets.
  • Agree a monthly cap that cannot be exceeded without written approval.
  • Review working software at the end of every sprint.
  • Allow termination on short notice, such as 30 days.

The client's protection here is frequency: a month is the most that can be lost.

Clauses that belong with the schedule

  • Acceptance procedure. Who tests, against what, within how many days, and what counts as a defect that blocks acceptance.
  • Defect classes. Critical defects block acceptance. Minor ones are listed and fixed within an agreed time without holding up payment.
  • Late payment. What the vendor may do if an accepted milestone is not paid, typically pause work after notice.
  • Late delivery. What the client may do if a milestone slips, from a revised plan to, in serious cases, termination.
  • Change requests. How additional work is priced and when it is paid, so changes do not blur the milestone table.
  • Ownership. When rights to the code and documents transfer. Tying transfer to payment of each milestone is fair to both sides.
  • Termination. What is paid and what is handed over if the contract ends early.

Warning signs in a proposed schedule

  • More than half due before anything can be tested.
  • Milestones defined by dates alone.
  • Milestones defined by effort, such as "development 50 percent complete".
  • No payment tied to user acceptance.
  • No retention.
  • A final payment so small that the vendor loses little by not finishing.

On the other side, vendors should be cautious of:

  • No deposit at all on a project that needs a team reserved.
  • Acceptance with no time limit.
  • Everything due at the end. It usually means the vendor funds the project, and the price will reflect it.

For the vendor's side of the table

A schedule that is fair to the client is also good for the vendor. Clear acceptance tests end arguments about whether something is finished. A review time limit prevents indefinite delay. Regular milestones give regular cash. We prefer contracts written this way, and we propose them to clients even when not asked.

If you are reviewing a proposal and are unsure whether its schedule is balanced, we are glad to look at it. See how we structure projects in Enterprise Software, or contact us.

Summary

Tie each payment to a deliverable with a written acceptance test and a review time limit. Keep payments in step with value delivered, keep milestones four to eight weeks apart, and hold back a final payment and a retention. Add clauses for acceptance, defects, delay, change and termination. A schedule built this way keeps both sides motivated to the last day of the warranty.

Frequently asked questions

How large should the upfront payment be?

Between 10 and 30 percent is common for custom software. It should cover the vendor's cost of starting, such as assigning a team and doing discovery, without leaving the client exposed for work not yet done. A demand for more than half upfront deserves a question about why.

What is a retention and how much is normal?

A retention is a portion of the price held back until the end of the warranty period or until agreed defects are fixed. Five to ten percent is typical. It gives the vendor a reason to stay responsive after go-live, when most of the money has already been paid.

Should payments be tied to dates or to deliverables?

To deliverables that can be checked. A payment that falls due on a date is owed whether or not anything works. A payment that falls due on acceptance of a named deliverable is owed when the client can see and test the result.

Author

Etzal Group Team

Etzal Group Team, helping businesses grow with technology. Contact us.

Related service

Free consultation

Not sure where to start? We will map the right system for your business, free.