In short
- Every milestone should end in something you can look at.
- Make the first one small, real and soon.
- Split by output, not by week.
- Extra work is a new milestone, not a favour.
A milestone is two things at once: a payment and a checkpoint. Get the split right and a project that is going wrong announces itself in week one, while the amount at risk is still small. Get it wrong and you find out at the end, having funded the whole thing.
Split by output, not by time
"Week two" is not a milestone, because there is nothing to accept. Every stage should end in something a reasonable person could look at and judge: a page, a schema, a working signup, a set of screens, three of the twelve articles.
| By time (weak) | By output (better) |
|---|---|
| Week 1: setup | Project skeleton deployed, one page built to the design |
| Week 2: development | Remaining five pages built and responsive |
| Week 3: extras | Contact form connected to the CRM, with a test submission received |
| Week 4: finishing | Cross-browser pass, handover and access transferred |
The right-hand column tells you what you are paying for and what to check. The left-hand one only tells you time has passed.
Make the first milestone a real test
The first stage is the one doing the most work for you, because it is where you learn how this person communicates, estimates and finishes things. It should be small, genuinely useful, and complete within a week or two.
- Produces something you can judge on its own.
- Is not so small that it proves nothing.
- Touches the risky part of the project, not the easy part.
- Has a deadline close enough that slippage is visible.
Size them so nothing gets big
Long milestones hide problems. Four stages of two weeks each are far safer than two of a month, for both sides: the client sees progress sooner, and the freelancer is paid sooner and is not carrying a month of unpaid work.
- Two weeks is a good default ceiling for one stage.
- If a stage has no output until the end, it is too big or wrongly cut.
- Front-load the risk. Build the uncertain part early, while the budget is mostly unspent.
- Put handover in its own small milestone, so access transfer does not get forgotten at the finish.
What each milestone should say
Four lines is enough: the deliverable, what done means, how many revisions are included, and the amount. Ambiguity in any of those is where an approval turns into an argument.
Weak
Milestone 2: build the rest of the site. $2,000.
Better
Milestone 2: the five remaining pages built to the approved Figma designs, responsive from 375px, reviewed in current Chrome and Safari. Two rounds of revisions included. $2,000.
The second version can be approved or rejected on facts. It also protects the freelancer: revisions are bounded, so a third round is a conversation about price rather than an expectation.
Approving, and what approval means
When work is submitted you can approve it, or request revisions with specific notes. Approval releases the money for that stage, either straight away or after a short clearance period, and if you go quiet it approves automatically after a set time so work cannot be held indefinitely.
Instant release has one consequence worth knowing: a released milestone can no longer be disputed. If you are unsure about the work, ask for revisions rather than releasing and sorting it out afterwards. How freelance escrow works covers the sequence in full.
Handling extra work
New work is a new milestone. Adding it to a running contract keeps it funded, dated and reviewable like the rest, and it keeps the original estimate honest rather than quietly absorbing changes that were never priced.
How many milestones should a project have?
Enough that no single one is longer than about two weeks or larger than you would be comfortable losing. For most small projects that means three to five.
Should I pay a deposit?
On this platform the first milestone being funded into escrow is the deposit, functionally: the freelancer can see the money is committed without you handing it over. A separate upfront payment outside that adds risk for you and nothing for them.
What if a milestone is only partly delivered?
Request revisions with specific notes, which is what the review window is for. If you cannot agree, either side can open a dispute while the milestone is still funded, and mediation can end in full release, full refund or a split.
Can milestones be added later?
Yes. Extra scope is added as new milestones on the existing contract, each funded before that work starts.