Should You Ask for a Deposit? Milestone Payments for Freelancers
Worked scenarios are illustrative composites. Our editorial pen name and method.
On this page
Choose a payment schedule from the work you must fund
An upfront payment reduces the amount of work and expense you finance before receiving money. It does not guarantee payment of the balance, prove a client’s reliability, or settle the treatment of a cancellation. The useful question is how much cash and work each party commits before the next payment checkpoint.
There is no universal deposit percentage for freelance projects. Service type, procurement rules, project length, cancellation terms and applicable law can all affect the arrangement. Build a schedule from the project instead of presenting 25%, 30% or 50% as a measured industry norm.
Map the first stage before selecting a percentage
Write down the work due before the next payment, third-party purchases, and the date funds need to be available. Separate actual cash expenses from the value you assign to your own time.
Illustrative $2,000 project: before the first milestone, expect $150 of licensed assets and six hours of work. At a chosen $75/hour planning value, that is $150 + 6 × $75 = $600 of combined cash cost and valued effort.
| Proposed upfront share | Upfront amount | Difference from the $600 planning amount |
|---|---|---|
| 20% | $400 | $200 below |
| 30% | $600 | Equal |
| 50% | $1,000 | $400 above |
Only $150 in this example is an external cash payment. The six hours are an opportunity-cost input, not necessarily an accounting expense. This comparison helps you choose a proposal; it does not determine a legally retainable deposit or the amount a client should accept.
Repeat the calculation for later stages. A large initial payment can still leave a long unfunded interval if most work happens before the final invoice is due.
Compare milestones with a start-and-finish split
Assume a $6,000 website project and $4,800 of total planning cost, including valued work, spread evenly over four stages. Compare these hypothetical schedules:
| Stage | Cumulative planning cost | Payments received before that stage: 50/50 | Payments received before that stage: four $1,500 installments |
|---|---|---|---|
| Discovery complete | $1,200 | $3,000 | $1,500 |
| Design complete | $2,400 | $3,000 | $3,000 |
| Build complete | $3,600 | $3,000 | $4,500 |
| Handoff complete | $4,800 | $3,000 | $6,000 |
Here the 50/50 plan collects the second $3,000 only after handoff. The installment plan assumes each payment is received before its stage begins. If a payment instead becomes due after approval, the timing and exposure change. Neither schedule is inherently correct; the table makes the assumed timing explicit.
A $1,500 invoice is not the same as $1,500 received. Include due dates and expected payment-processing time when deciding whether funds cover the next stage. The invoice generator can record agreed terms, but it does not collect payment or enforce the agreement.
Put the payment triggers in the proposal
Specify the amount, invoice date or milestone, due date, and what deliverable completes each stage. Address delayed feedback, changed scope, cancellation and any agreed condition for starting the next stage. Do not rely on the word “deposit” alone to define those terms.
A proposal might say:
The proposed fee is $2,000: $600 before discovery begins, $700 at the agreed design checkpoint, and $700 at the agreed handoff checkpoint. The attached scope defines those checkpoints, payment due dates and cancellation terms. Please confirm the schedule before work begins.
These amounts are examples. Replace the dates and conditions with terms both parties accept. Whether an advance can be retained, refunded or credited depends on the agreement and applicable rules; describing it as “non-refundable” does not by itself settle that question.
If the client requests different terms
Ask which part is difficult: the upfront amount, approval process, payment timing or uncertainty about the deliverable. Compare a smaller first phase, different milestones or a reduced scope. A refusal may reflect procurement constraints, not unwillingness to pay.
Evaluate the revised schedule against the costs you must cover and the work you would complete before receipt. Accept, counter-propose or decline based on those facts and your commitments. Do not assume that losing a project will automatically lead to replacement work.
Keep accepted terms, invoices, approvals and payment records together. Reconcile each advance against the final balance so the client is not charged twice. Tax and accounting treatment varies by jurisdiction and business structure; obtain appropriate advice for those questions. This guide provides payment-planning arithmetic and communication examples, not legal or tax advice.