MonkeeTools

Blog · Client billing

Part of the Client billing guides

Deposits, milestones, and retainers

Monkee · September 15, 2026

The riskiest moment in freelance work is the beginning: you have committed your time, and the client has committed nothing. Deposits, milestones, and retainers are the three structures that fix that imbalance. They are not about distrust. They are about making commitment mutual, so both sides can relax and do good work.

This guide is the structural overview: when each model fits, how to set it up, and the exact language to use. For the invoice mechanics of deposits specifically, see how to invoice for a deposit, which covers the deposit invoice and the final balance invoice step by step.

Deposits: commitment before work starts

A deposit is money paid upfront, before or as the work begins, credited against the final total. It does three jobs at once: it proves the client is serious, it covers your early costs, and it makes ghosting expensive enough that it rarely happens.

When to ask

Always, for new clients. Every time. The clients who balk at a standard deposit are disproportionately the clients who would have been a problem later. For long-standing clients with a clean payment history, you can relax it, but keep it as your default. Project types where deposits matter most: anything with upfront costs (materials, subcontractors, travel), anything longer than a few weeks, and anything custom that cannot be resold if the client walks.

How much

The standard range is 25 to 50 percent of the project total. Where you land depends on the shape of the work:

• 25 to 33 percent for standard project work with a client you have vetted. Enough to matter, easy to say yes to.
• 50 percent for new clients, large projects, or work with significant upfront costs. Half upfront is completely normal in creative and consulting work.
• 100 percent for small fixed-price jobs under a few hundred dollars. Invoicing twice for $200 costs more in admin than it protects.

Never go below 25 percent. A 10 percent deposit is not protection, it is a rounding error the client will forget they paid. For the full breakdown by project type, including when 100 percent upfront is the normal move, see how much deposit you should ask for.

How to ask without the awkwardness

The awkwardness is the whole reason people skip deposits, so make it boring and procedural. It is not a negotiation, it is how you work. Put it in the proposal, repeat it in the invoice notes, and send the deposit invoice the day the project is agreed.

Subject: Deposit invoice for [PROJECT NAME]

Hi [NAME],

Great, we are confirmed for [PROJECT NAME]. As discussed,
I work with a [50]% deposit to reserve your slot and cover
initial work.

Deposit invoice attached: [AMOUNT], due [DUE DATE].
The balance of [BALANCE AMOUNT] will be invoiced on
[DELIVERY / COMPLETION DATE].

I will get started as soon as the deposit lands.

Thanks,
[YOUR NAME]

Milestones: getting paid as the work progresses

For projects too big for a single deposit and a single final invoice, split the work into milestones: phases with defined deliverables, each invoiced when complete. A typical split for a $12,000 project: 25% deposit, 25% at the midpoint deliverable, 50% on delivery. The client never owes too much at once, and you never work too long unpaid.

What makes a milestone work

• Define the deliverable, not the effort. "Homepage designs delivered" is a milestone. "Two weeks of design work" is a timesheet. Milestones are about what the client receives.
• Attach acceptance criteria. One sentence on what "done" means: "Three homepage concepts delivered as Figma files, one round of revisions included." This prevents the milestone from drifting into endless tweaks.
• Invoice on completion, immediately. The milestone invoice goes out the day the deliverable is accepted, not at month end. Momentum is a payment accelerant.
• Keep the count low. Two to four milestones for most projects. More than that and you are running a billing department, not a project.

Billing schedule for [PROJECT NAME], total [TOTAL]:

1. Deposit: [25]% ([AMOUNT]) due before work begins.
2. Milestone 1, [DELIVERABLE]: [25]% ([AMOUNT]) due on
   delivery and acceptance.
3. Final delivery, [DELIVERABLE]: remaining [50]%
   ([AMOUNT]) due within 14 days of delivery.

Acceptance: deliverables are considered accepted 5 business
days after delivery unless written revisions are requested.
Work on the next phase begins when the previous milestone
invoice is paid.

That last line is the quiet power of milestones: each phase funds the next, so a stalled payment pauses the project automatically instead of becoming your problem to chase. For the full playbook, slicing projects, acceptance criteria, and what to do when a milestone stalls, see milestone billing that keeps cash flow steady.

Retainers: predictable income, on purpose

A retainer is a client paying a fixed amount each month for ongoing access to your work. It is the closest freelancing gets to a salary, and it is the best structure for work that never really ends: maintenance, content, marketing, support, advisory.

The two retainer shapes

• Hours-based: "Up to 20 hours per month at $X." Simple to explain, simple to track. Best when the work varies month to month. Keep a simple timesheet so the hours are never a matter of opinion.
• Deliverable-based: "Four blog posts and one newsletter per month for $X." Better when the output is predictable. The client buys outcomes, not your calendar, and unused capacity is your profit, not their refund.

The rules that keep retainers healthy

• Bill at the start of the month, not the end. A retainer is paid upfront for the coming month's availability. This is standard and non-negotiable; it is what makes it a retainer instead of a monthly invoice.
• Set a rollover policy in writing. Unused hours either expire or roll over, and both are fine, but "we'll figure it out" is not. A common setup: up to 25% of hours roll one month forward, then expire.
• Require a notice period. Thirty days' notice to end the retainer, on both sides. It protects your pipeline planning and gives the client a clean exit.
• Review quarterly. Retainers drift: the work grows, the fee doesn't. A standing quarterly check-in ("is this still the right shape?") is where raises happen without awkwardness.

Subject: Proposal: monthly retainer for [SERVICE]

Hi [NAME],

Based on the last few months, I would like to propose
moving to a retainer so you have guaranteed availability
and we both skip the per-project admin.

Proposed: [DELIVERABLES OR HOURS] per month for [AMOUNT],
billed on the 1st of each month for the month ahead.
Unused hours: up to [25]% roll forward one month, then
expire. Either of us can end the retainer with 30 days'
written notice.

Happy to adjust the shape before we start. If this looks
right, I will send the first invoice for [START DATE].

[YOUR NAME]

What to invoice, and when

Each structure maps to a simple invoicing rhythm:

• Deposit: one invoice at project start, described as "Deposit for [project], 50% of total." The final invoice shows the full total, the deposit as a credit line, and the balance due. The mechanics are covered in how to invoice for a deposit.
• Milestones: one invoice per milestone, numbered in your normal sequence, each referencing the project and the milestone name. The final milestone invoice is just the last one, not a special document.
• Retainers: one invoice per month, issued on the 1st for the month ahead: "Retainer, [Month]: [deliverables or hours]." Same number sequence, same format, every month. Boring is the goal.

When a client pays a deposit, send a receipt confirming it. It takes a minute and it removes an entire category of "did you get my payment?" emails. And when project work turns into a long-term relationship, the deep guide on retainer agreements covers pricing, rollover terms, boundaries, and clean exits.

Deposits, milestones, and retainers are not about distrust. They are about making commitment mutual, so both sides can stop worrying about money and do the work.

← Client billing guides