The most dangerous invoice in freelancing is the single one at the end. 100% on delivery means you finance the client's project for weeks, then beg for payment when your leverage is zero. Milestone billing fixes the power dynamic: a deposit up front (40% is the professional standard for project work) plus even payments at defined milestones keeps cash flowing while the work is being done — and gives you a clean, pre-agreed pause point if a payment stalls.
Enter the project total, your deposit percentage, and how many milestones the remainder splits across. The calculator returns the deposit amount, each milestone payment, and a plain-English schedule you can paste straight into your proposal or contract.
Milestones also solve the quieter killer: scope creep. When "just one more revision" arrives, a milestone structure gives you somewhere to put it — after the current milestone is approved and paid, as a change order against the next one. Without milestones, extra work dissolves into the single end-of-project invoice and you negotiate from zero leverage. Each milestone boundary is a natural point to say: "that is outside this milestone — here is what it costs as an addition." Pair this with the scope creep calculator to price those additions honestly.
Planning estimate only. This is arithmetic, not legal advice — and note what it deliberately excludes: no interest-based late fees. This tool models enforcement as work-pause clauses (work stops until the milestone clears), which protect cash flow without compounding penalties. Put the schedule in writing before work starts.
Key takeaways
- Never finance the client: a 30–50% deposit (40% default here) means you are never more than one milestone of unpaid work deep.
- Split the remainder into even milestones tied to deliverables, not dates — "on homepage approval", not "on the 15th" — so payment follows value.
- Each milestone is a pause point: if payment stalls, work pauses. Agree this in writing before starting, not during the dispute.
- This tool uses no interest-based late fees — flat work-pause clauses protect you better than penalties that sour relationships and rarely get paid.
- Put the schedule in the contract verbatim: amount, trigger, and what happens on non-payment. Verbal milestone agreements evaporate under pressure.
- Retainers are monthly deposits: 100% up front on the 1st, every cycle. The same schedule math applies — payment before the work it covers.
- Invoice each milestone the day it is approved — "net 30" starts at invoicing, and every day you delay the invoice is a day you delay the cash.
How it works
- Enter the total agreed project value — the full price, not a phase of it.
- Set the deposit percentage with the slider. 40% is the default and the professional standard for project work; 30–50% is the healthy band. Below 30% you are financing the client.
- Choose how many milestones the remainder splits into — typically 2–4, one per major deliverable or project phase.
- The calculator returns the deposit due before work starts, each even milestone payment, and a plain-English schedule: deposit → M1 → M2 → …
- Paste the schedule into your proposal, then define each milestone trigger as a deliverable approval ("on homepage design sign-off"), never a calendar date.
- Add the enforcement clause in writing: work pauses until a due milestone clears. No interest-based late fees — work-pause clauses protect cash flow without poisoning the relationship. Then protect the income stream with the <a href="/freelancer-cash-flow-forecast/">cash flow forecast</a>.
- For retainers, enter the monthly fee with 100% deposit and 1 milestone — payment on the 1st before the month's work. The same math enforces the same discipline.
- When scope creep appears mid-project, park it at the next milestone boundary as a priced change order — the <a href="/scope-creep-cost-calculator/">scope creep calculator</a> prices the addition.
Worked example
Worked example — $10,000 project, 40% deposit, 3 milestones:
- Deposit: $10,000 × 40% = $4,000.00 — due before work starts
- Remainder: $6,000.00 across 3 milestones
- Each milestone: $2,000.00 on deliverable approval
- Schedule: Deposit $4,000.00 (due before work starts) → M1 $2,000.00 (on milestone 1 approval) → M2 $2,000.00 (on milestone 2 approval) → M3 $2,000.00 (on milestone 3 approval)
Why this works: the freelancer collects $4,000 before lifting a finger and is never more than $2,000 of unpaid work deep. If milestone 2 stalls, work pauses with $8,000 already banked or committed — leverage stays with the person doing the work.
Second example — $3,600 project, 25% deposit, 2 milestones: deposit $900.00, milestones $1,350.00 each. The calculator flags the deposit as below 30% and recommends pushing toward 40% ($1,440) — the difference between financing the client and being financed by the client.
Third example — $4,500/month retainer, structured as milestones: retainers are deposits by another name. Enter $4,500 total, 100% deposit, 1 milestone: deposit $4,500.00 due on the 1st before the month's work begins. The "milestone" is the month itself, approved by delivery of the agreed work. Same arithmetic, same principle: payment before the work it covers, every cycle, no exceptions — which is why retainer clients are statistically the best payers freelancers have.
Frequently asked questions
What deposit should a freelancer ask for?
30–50%, with 40% as the professional standard for project work. Retainers and small fixed jobs often take 50–100% up front; large multi-month projects may step down to 30% with tighter milestones. Below 30% you are extending the client interest-free credit — which is exactly what the deposit exists to prevent. New clients and unknown payers: take the higher end.
Should milestones be tied to dates or deliverables?
Deliverables, always. "50% on homepage approval" is enforceable; "50% on the 15th" bills the client for calendar time regardless of progress and invites disputes about what was delivered. Date-based milestones also punish you for client-caused delays — your payment should never depend on their responsiveness.
How many milestones should a project have?
One per major deliverable or phase, typically 2–4. Too few and each unpaid gap is large; too many and you drown in invoicing overhead and approval-chasing. A $10,000 website: deposit + design approval + build approval + launch = 4 payments. Match the money to the moments the client feels value land.
What if a client refuses to pay a deposit?
Treat it as information. Clients who will not put 30–40% down before work starts are statistically the clients who pay late — or never — at the end. Options: hold firm (best), reduce scope to what the deposit covers, or walk away. Discounting your deposit policy to win the project usually just buys you a more expensive lesson.
Should I charge interest on late milestone payments?
This tool deliberately models no interest-based late fees. In practice, penalty interest on small freelance invoices is rarely collected, often unenforceable across borders, and reliably poisons the relationship. The stronger mechanism is the work-pause clause: work stops until the overdue milestone clears. It costs you nothing to enforce and restores your leverage instantly.
What is a work-pause clause?
A contract term stating that if a milestone payment is more than N days overdue, all work pauses until it clears — with timelines shifting accordingly. It is fair (the client controls the remedy: pay), self-enforcing (you simply stop), and it converts "please pay me" into a structural consequence agreed before any tension existed. Write it into the contract, not the invoice reminder.
How do milestones work for hourly or retainer clients?
Adapt the pattern: for hourly, bill weekly or biweekly instead of monthly — shorter cycles are the hourly equivalent of milestones. For retainers, payment is due on the 1st before the month's work begins (a 100% "deposit" each cycle). The principle never changes: never let delivered-but-unbilled work pile up past what you can afford to lose.
Should the final milestone be smaller or larger?
Smaller is safer. Even splits are clean, but many experienced freelancers make the final milestone the smallest (e.g., 40/25/25/10) so the client's incentive to stall at the finish line is minimal — the painful "final 10% held hostage over trivial revisions" scenario. If you use even splits, define "final approval" tightly: what constitutes acceptance, and within how many days silence counts as acceptance.
Do I need a contract for milestone billing?
Yes — milestones without a contract are wishes. The contract needs four things per milestone: amount, trigger (the deliverable), due date after trigger, and the consequence of non-payment (work pauses). A one-page agreement with these beats a ten-page template missing them. This calculator gives you the schedule; a contract turns it into an obligation.
How do milestones help cash flow?
They convert one lumpy end-of-project payment into regular inflows during the work — which is what your expenses actually follow. A 3-month project on 100%-on-delivery pays you in month 3; on 40/20/20/20 you collect in months 0, 1, 2, and 3. Model the difference in the cash flow forecast and watch the "lowest balance" line transform.
What about very small projects — still use milestones?
Simplify, don't skip. Under ~$1,000, use 50% up front / 50% on delivery — two payments, same principle. The admin cost of four milestones on a $500 job exceeds the protection. The rule scales: the smaller the project, the larger the proportion up front, because small projects have the worst late-payment economics.
Is this financial or legal advice?
No. This is payment-schedule arithmetic plus widely used contracting practice — not legal advice and not financial advice. Contract enforceability varies by jurisdiction; for large projects or difficult clients, have a professional review your terms. And note the deliberate design choice: this tool contains no interest, lending, or penalty-interest features of any kind.