Freelance deposits: how much to ask for

Asking for money before you've done any work feels backwards. It isn't: contractors, photographers, agencies, and lawyers all collect something before they start. Freelancers skip it not because it's a bad idea, but because asking feels awkward. Here's how much to ask for, how to structure it, and how to say it without the conversation getting weird.

Why a deposit actually protects you

A deposit does three concrete things, and none of them are about distrust.

It filters out clients who were never going to pay anyway. A client who balks at putting down 30% before you've written a line of code or delivered a single session is telling you something: maybe they're broke, maybe they're shopping five freelancers at once, maybe they just don't take the arrangement seriously. Either way, you want that information before you've spent a week on their project, not after.

It covers your actual upfront costs. Most projects have real costs before invoice-worthy work starts: software licenses, subcontractor time, materials, or hours spent on discovery calls and scoping a client never sees itemized. A deposit means those costs don't come entirely out of your pocket while you wait weeks for a first invoice to clear.

It caps your downside if the project falls apart. Projects die mid-way more often than anyone likes to admit: budgets get cut, priorities shift, the client's business changes. If a project ends after week two with nothing invoiced, you've worked for free; with a deposit collected first, you've at least been paid for something before things went sideways.

Where you land depends on the project: a two-week logo package might sit at 50%, since total exposure is small and you want it resolved fast, while a four-month website build might sit closer to 25-30%, split across milestones instead of front-loaded into one payment.

How much to ask for, by project type

There's no universal number, but a few patterns hold across most freelance work:

• Short, single-deliverable projects (under 2 weeks): 50%, sometimes 100% upfront. The project is short enough that a deposit alone covers most of your risk, and full upfront payment isn't unusual for small design, writing, or one-off consulting work.
• Medium projects (a few weeks to a couple months): 30-40% upfront, with the rest tied to milestones or a final payment. This is the most common range for web builds, branding packages, and multi-session coaching engagements.
• Long or ongoing projects (three-plus months, or retainers): 20-25% upfront, then monthly or milestone-based billing after that. A large upfront chunk stops making sense here; smaller, more frequent payments keep exposure low throughout.
• New clients with no history: lean toward the higher end of whatever range fits the project size. Once someone's paid on time for a few projects, you can reasonably lower the deposit or drop it entirely.
• Referral or repeat clients: a smaller deposit, or none, is often fine, since the risk that justified it in the first place is lower once you already know the client pays.

The exact percentage matters less than picking one and stating it consistently. A number that changes project to project with no logic behind it is hard to defend if a client asks why, and makes you look like you're improvising rather than running a real business.

Structuring the deposit, milestones, and final payment

A deposit by itself only solves half the problem: it protects the start of a project, not the middle or the end. For anything longer than a couple of weeks, pair it with a payment structure that spreads risk across the whole timeline:

1. Deposit at signing. Due before any work starts, tied to the signed quote or contract, not to a specific deliverable: the client committing to the project, full stop.
2. Milestone payments during the work. For a three-phase project, that might mean a payment due at the end of each phase (discovery, build, revisions) rather than one lump sum at the very end, so you're never more than one phase deep unpaid.
3. Final payment at delivery. The remaining balance, due at or shortly before the final handoff. Some freelancers hold the final files until this clears; others invoice on delivery and rely on clear terms. Understanding standard freelance payment terms covers how firm to be about timing here.

For projects too short to justify multiple milestones, a simple deposit-plus-final split works fine: 30-50% at signing, the rest on delivery. Don't overcomplicate a two-week project with a three-payment schedule just because it feels more professional. It isn't; it's just more invoices for both sides to track.

Whatever structure you land on, write it into the same document where you lock in scope. If you're sending a quote rather than an invoice at this stage, the difference matters for how enforceable the payment terms are, and quote vs. estimate vs. invoice covers which document actually commits a client to the numbers you're proposing.

How to word the ask without it feeling awkward

The awkwardness of asking for a deposit almost always comes from treating it like an exception, instead of a standard part of how you work. The fix is in the framing, not the amount.

Say it early, not after a client has already mentally started the project. Say it right after scope is agreed, in the same message where you send the quote or contract, not as a separate ask that shows up later out of nowhere.

State it as policy, not negotiation. "My standard terms are a 30% deposit to begin, due before I start" reads as simply how you operate; "Would it be okay if I asked for some money upfront?" reads as a request you're not sure you're entitled to make.

Put it in writing alongside the scope, not as a verbal aside on a call. A deposit mentioned once in conversation is easy to forget or misremember; one written into the same document as the deliverables and timeline is much harder to dispute later.

This also belongs in your client onboarding process. A client onboarding checklist that includes payment terms up front means the deposit conversation happens once, not re-justified for every new client.

What to do when a client pushes back

Some pushback is normal and worth accommodating. Some is a signal to walk away.

If a client asks to lower the percentage or split it into two smaller payments, that's usually fine: it's a negotiation over structure, not a refusal to pay anything upfront. Plenty of freelancers will drop a 40% ask to 25% for a client who's otherwise solid, in exchange for a shorter payment window on the balance.

If a client argues that deposits aren't standard in their industry or that they "never pay upfront," ask what they'd propose instead, and be willing to hold firm. A milestone schedule with a smaller first payment can often satisfy both sides without you working entirely on credit.

A client who refuses to pay anything before work starts, full stop, is telling you how the rest of the relationship is likely to go: slow payments, disputes over scope, or worse. It's reasonable to say no to the project rather than start it uncompensated on the hope that the final invoice goes smoothly.

The one thing not to do is quietly drop the deposit requirement because a single client pushed back hard. Once it's known you'll waive it under pressure, it stops functioning as a policy and starts functioning as an opening offer.