Payment Milestones

What This Clause Does

A milestone-based payment structure links each payment to a specific deliverable — a completed prototype, a design review, a working module. This protects both sides: the client only pays when they receive something, and you get paid incrementally rather than waiting until the end of the project.

The risk for freelancers is that milestone definitions can be vague, leaving the client room to claim a deliverable wasn't met and delay payment. Be specific: define exactly what each milestone consists of, what 'completion' means, and how long the client has to accept or provide feedback before the milestone is considered complete.

What This Looks Like in a Contract

"Client shall pay Contractor according to the following milestone schedule: (1) 30% upon execution of this Agreement; (2) 40% upon delivery and approval of [Milestone 2]; (3) 30% upon delivery and approval of final deliverables. Approval shall not be unreasonably withheld; Client has [5/10] business days to approve or provide written feedback."

Red Flags to Watch For

• Milestones defined by vague criteria like 'client satisfaction' rather than objective outputs
• No deadline for client to accept or reject a milestone — they can delay indefinitely
• No mechanism to resolve disputes about whether a milestone was reached
• Final payment withheld until after launch or deployment, outside your control

Negotiation Strategies