Every guide to milestone payments gives you the same answer: 30% upfront, 30% at the midpoint, 40% on delivery. That's fine for a four-week project. It's the wrong shape for a four-month one, and nobody says so.
If you have a $149,000 project running seventeen weeks, or a two-month visualization job, or a consulting engagement with six deliverables, the useful question isn't what the standard split is. It's how many payment points you need, and what a given schedule costs you if the client stops paying halfway through. That second number is calculable, and it's the one that should decide the schedule.
The Number That Matters: Peak Exposure
Peak exposure is the largest gap between work you've delivered and money you've received at any single point in the project. It's what you actually stand to lose.
Take a $60,000 project on the standard 30/30/40 split. You collect $18,000 upfront, then work for weeks. Just before the midpoint payment lands you've delivered roughly half the work — $30,000 worth — against $18,000 received. Exposure: $12,000. Then it grows again through the back half, and just before final delivery you've delivered everything — $60,000 — against $36,000 received. Peak exposure: $24,000, or 40% of the fee.
Now the same $60,000 with five milestones — 25% deposit then four payments of $11,250. Your delivered-versus-paid gap never exceeds about 15% of the fee. Same total, same deposit ratio, peak exposure cut by more than half, purely from spacing.
This is why "how many milestones" isn't a matter of taste. Each extra payment point buys down the maximum you're carrying, at no cost to the client, who pays the same total on roughly the same timeline. It's the cheapest risk reduction available in a freelance contract.
Milestone Count by Project Length
The workable heuristic is one payment point roughly every three to four weeks. Below that you're generating admin for its own sake; above it, exposure climbs faster than most people realise.
Scroll sideways to see all columns
| Project length | Payment points | Typical shape |
|---|---|---|
| Under 2 weeks | 1–2 | 100% upfront, or 50/50 |
| 2–8 weeks | 3 | 30 / 30 / 40 — the standard actually fits here |
| 8–16 weeks | 4–5 | 25% deposit, then equal stages |
| 16+ weeks | 6+ | 20–25% deposit, then every 3 weeks |
Two adjustments to that grid. If the client is new and unproven, move up a row — more, smaller payments. If a single deliverable genuinely dominates the project (one big build with little to show until it's done), you may not be able to attach payments to intermediate deliverables, in which case the deposit has to carry more weight instead.
Work Out Your Schedule and Exposure
Enter the total and the duration. This lays out the dated schedule and shows what each option leaves you carrying at the worst point.
Milestone Schedule + Peak Exposure
Assumes work is delivered at a steady rate across the project. Estimate only.
Peak exposure assumes even delivery and payment on the milestone date. Real projects front-load or back-load effort, so treat it as a comparison between schedules rather than a forecast.
Don't Divide the Total by the Number of Months
A common request on long engagements is to just split the fee into equal monthly payments. It looks like a milestone schedule and behaves like something much worse.
Monthly billing decouples payment from delivery. You're now invoicing for elapsed time rather than accepted work, which means a client who is unhappy with progress has nothing concrete to approve — and you have nothing concrete to point at when they delay. It also removes your natural stopping point, because there's no deliverable boundary to pause at.
If a client's finance process genuinely requires monthly invoicing — which happens, especially with larger companies — the fix is to keep the deliverable triggers and align the milestone dates to their billing cycle, rather than replacing triggers with dates. The payment is still "on approval of X," it just happens to fall near month end.
Deliverable Triggers, With One Backstop
Date-based milestones break the first time the timeline shifts, and timelines usually shift for reasons on the client's side: late feedback, delayed materials, an approver on holiday. A deliverable trigger keeps payment attached to work actually handed over.
The failure mode of deliverable triggers is the opposite one — the client simply doesn't respond, so the deliverable is never "approved" and the payment never falls due. A deemed-acceptance clause closes that:
That last sentence is the one that does the work. Without it, a client can stay one milestone behind for the entire project. With it, the project stops while the unpaid amount is still one milestone's worth — which is exactly what the count was chosen to limit. The same suspension logic applies to ongoing work, though the mechanics differ; see what to do when a retainer client stops paying.
Non-Freelance Contexts: Same Math, Different Names
Progress payments in fabrication, construction and engineering run on the same arithmetic under different labels — schedule of values, progress billing, retainage. Two differences worth knowing if you're crossing into that territory:
- Retainage. Many industrial and construction contracts hold back a percentage (often 5–10%) of each progress payment until final acceptance. That withheld amount is pure additional exposure, and it needs adding on top of the peak figure above.
- Materials versus labour. Where a milestone covers materials you've purchased, the exposure includes your outlay, not just your time. Front-load those payments rather than spreading them evenly.
If your client is a government agency, note that the payment timing may be set by a prompt payment statute rather than your schedule — see the note on government contracts.
Turn the schedule into something you can send. The milestone calculator splits the fee across named deliverables and dates, ready to paste into a proposal.
Open Milestone Calculator →What to Do Before the Schedule Matters
A milestone schedule limits damage; it doesn't prevent it. The upstream decisions do more: what deposit you require, whether the scope is written down, and which state's law governs if it goes wrong. Freelance payment terms explained covers deposits and net terms, the discovery call questions cover surfacing the client's payment process before you quote, and the contract generator builds the schedule and suspension clause into an agreement.
Frequently Asked Questions
How many payment milestones should a long project have?
Pick the count from how long the project runs rather than from a default. A useful rule is one payment point roughly every three to four weeks: three milestones for a project under eight weeks, four to five for eight to sixteen weeks, and six or more beyond that. The reason isn't tidiness. Each additional milestone reduces the largest amount of delivered-but-unpaid work you're ever carrying, which is the number that determines what you actually lose if the client stops paying. Going from three milestones to six on a seventeen-week project typically halves that exposure without changing the total fee at all.
How do I split a project fee across a fixed number of weeks?
Take the deposit off the top first, then divide the remaining balance across the payment points that follow. For a $149,000 project running seventeen weeks with a 25% deposit, the deposit is $37,250 and the remaining $111,750 splits across the later milestones: four further payments of $27,937 each at roughly weeks 4, 8, 12 and 17, or five payments of $22,350 at shorter intervals. Don't simply divide the total by the number of weeks and bill monthly, because that decouples payment from delivery and leaves you invoicing for time rather than for accepted work.
What is peak exposure on a milestone schedule?
Peak exposure is the largest gap between work you've delivered and money you've received at any single point in the project. It's the practical measure of what a payment schedule is worth, because it's what you stand to lose if the client stops paying at the worst possible moment. A schedule with a small deposit and a large final payment can look reasonable while carrying very high peak exposure. Two schedules with identical total fees and identical deposits can differ enormously on this number, which is why the count and spacing of the middle milestones matters more than most freelancers assume.
Should milestones be tied to dates or to deliverables?
Tie them to deliverables, and use dates only as a secondary backstop. Calendar-based milestones break as soon as the timeline shifts, which it usually does — and often for reasons on the client's side, such as late feedback or delayed materials. A deliverable trigger keeps payment attached to work actually handed over. The one refinement worth adding is a deemed-acceptance clause, so that if the client doesn't respond within a set number of business days the milestone counts as approved and payment falls due, which prevents an indefinite wait for sign-off.
What happens if a client misses a milestone payment mid-project?
Stop before starting the next stage, and make sure your contract says you may. A suspension clause stating that work on the following milestone doesn't begin until the preceding invoice is settled turns a difficult conversation into the agreement operating as written. Without it, a client can stay one milestone behind for the entire project and you have no natural stopping point. This is exactly the situation that milestone count is meant to limit: on a schedule with more, smaller payments, one missed payment stops the project while the unpaid amount is still small.
Pick the count from the calendar, not from a template. Then check what the schedule leaves you carrying at the worst moment — if that number is bigger than you'd be willing to write off, add a milestone. It costs the client nothing.