Milestone
A significant checkpoint in a project, usually marking the completion of key deliverables and often tied to a payment or approval.
For example, a website project might set three milestones - approved designs, a working staging build, and launch - each releasing a third of the fee. Hitting a milestone gives both sides a clear, shared marker that progress is real.
Why it matters to agencies: milestones break a long project into visible, fundable stages, which protects agency cash flow and keeps clients confident that work is moving. Tying payment to milestones also means you are never far ahead of what has been invoiced and approved.
- Milestones with no clear acceptance criteria.
- Too few, so problems surface late.
- Not tying payment or sign-off to them.
What is a milestone in a project?
A significant checkpoint in a project, usually marking the completion of key deliverables and often tied to a payment or approval.
What is the difference between a milestone and a deliverable?
A deliverable is a specific output; a milestone is a checkpoint in the timeline, often reached by completing one or more deliverables.
Why tie payments to milestones?
It protects cash flow and reduces risk - the agency is paid as agreed stages are completed, rather than waiting until the very end.
How many milestones should a project have?
Enough to mark real progress and fund the work - often three to five - without so many that they become admin overhead.