What to Say When a Client Refuses to Pay a Deposit

You send the proposal, the client is excited, and then the deposit line lands and everything goes quiet. Or worse, they reply immediately, just not with a yes.

Every guide on this topic gives you one script for one version of this conversation, usually the polite "we don't do that" version. Real deposit pushback comes in at least five different flavors, and they do not call for the same answer. Some are a client protecting their own cash flow. Some are the clearest signal you will get, for free, before you have done any work.

The short answer: sort the objection into legitimate or red flag before you respond, because the two get opposite replies, then use a script that trades the word "deposit" for structure the client can say yes to. This article gives you the triage table, five scripts for the objections you will actually hear, the scenario every other guide skips (a client who signs the contract, then stalls when the actual invoice arrives), and a plain rule for when the right move is to walk. Everything below was checked in July 2026.

If you have not settled on a percentage yet, start with our guide to how much deposit to charge, which covers the decision table and the clause. This one picks up exactly where that one leaves off: the client has seen the number, and they are pushing back.

Sort the objection first: legitimate caution and a red flag sound almost identical#

The same sentence, "I don't pay deposits," can mean a careful business owner or a client who never intended to pay you at all, and the fastest way to tell them apart is asking what specifically they are proposing instead. A legitimate objection comes with an alternative. A bad-faith one comes with pressure to just start.

Run every deposit pushback through this table before you decide how to respond.

The single question that clarifies most of these fastest: "What would work better for you?" A client with a real constraint answers with a structure (a PO, a payment schedule, a smaller first phase). A client testing you answers with more pressure to skip payment protection entirely, not a workable alternative.

Five scripts for the objections you will actually hear#

Five scenarios cover almost every deposit conversation. Each script keeps the protection (money changes hands before the next phase of work) while dropping whatever word is making the client dig in.

1. "We've never paid a deposit to anyone, and we're not starting now"#

This is company policy stated as if it were law. Sometimes it is real. Sometimes it is the first test of whether you will fold.

"Totally understand, and it's a reasonable policy to have. Here's how I handle it on my end: I don't start a project without some payment reserving the time, because I turn away other work to make room for it. If a straight deposit doesn't fit your process, I can invoice the first phase as its own line item once we agree on scope, that way you're only ever paying for defined work, not a percentage."

You have not asked them to break their policy. You have offered a structure their policy can say yes to.

2. "Our accounts payable can't cut a check before work is delivered"#

With a genuine mid-size or enterprise client, this is frequently true. Their system pays invoices against a purchase order on a fixed cycle, and there is no field in it for "deposit." Fighting the AP department wastes the goodwill you will need later.

"No problem, that's common with larger companies. Can we treat phase one as its own deliverable with its own invoice and PO number? I'll send that invoice the day we kick off so it can start moving through your cycle while I get to work."

Confirm their actual payment terms (net 30, net 45) before you sign anything, and price the wait into your schedule. A PO-based first milestone gets you most of what a deposit gets you: money committed before you have sunk real hours into an undefined scope.

3. "I was burned by a freelancer who took a deposit and vanished"#

This objection deserves a different tone than the others, because the client is describing something that actually happened to them, probably more than once. Arguing that you are different is exactly what the freelancer who vanished also said.

"That's a fair thing to be cautious about, and honestly a smart lesson to have learned. Instead of one deposit up front, let's split this into three milestones: you approve and pay for each phase only after you've seen it. The first one is small, it covers [discovery and a first draft], so you're never funding work you haven't seen yet."

Milestones solve their actual fear (paying for nothing) without you giving up the thing that protects you (never carrying more than one unpaid phase at a time). Our milestone billing guide has the full structure if this is the option you end up using most.

4. "I don't have that kind of money right now"#

Said about a deposit before the project has even started, this is the clearest version of the red flag, not because people cannot have a rough month, but because the final invoice, for the full amount, will land on that same client at a moment you do not control.

"I get it, cash flow is real. Let's shrink the first step instead of skipping it: a smaller kickoff milestone of [$400] covers [the discovery phase], and we can time the next payment to when it works better for you. If the timing genuinely doesn't work at all right now, I'd rather push the start date than begin without it."

Notice what this script does not do: it does not waive payment protection and hope things improve by the time the final invoice is due. If a client cannot fund a modest first milestone, the full balance later is not more likely to arrive, it is less.

5. "No one else asks me for that" / "Can't you just trust me?"#

This is pressure dressed as a reasonable question, and the tell is that it offers no alternative structure at all, just an appeal to your discomfort with saying no twice.

"I hear you, and I get that it can feel like an extra step. It's just how I run every project, not something specific to you, so I keep it consistent. Happy to talk through the payment schedule if that would help, but the deposit itself isn't something I skip."

State it once, warmly, and stop. Repeating the justification signals that the policy is negotiable if pushed hard enough. If the client escalates rather than proposing an actual alternative, you have your answer, and it did not cost you anything to get it.

The scenario every other guide skips: the client signs, then stalls at invoice time#

Every deposit-refusal guide online assumes the pushback happens before signature, while you are still negotiating. In practice, a lot of it happens after: the contract is signed with a deposit clause in black and white, and then the actual invoice arrives and the client goes quiet, or suddenly discovers an objection they never raised while reviewing the contract.

This gap exists because most freelancers run signature and invoicing as two separate steps, days apart, in two different tools. A signed contract with no invoice attached is an easy thing to quietly deprioritize.

The fix is structural, not conversational: collapse acceptance and payment into the same action, so there is no gap for a second thought to live in. If the client's "yes" and the deposit charge happen on the same page, in the same click, the stall-at-invoice-time problem mostly stops existing, because there was never a moment where the deal was agreed but unpaid.

(Disclosure: this is our product, but it is exactly what Raoura is built to do. The deposit line lives inside the proposal itself, so accepting the proposal and paying the deposit are the same click, by card or Apple Pay, straight into your own Stripe account. Raoura is $17 a month flat, with no cut of your payments.)

!A proposal pricing summary in Raoura showing line items totaling $3,450 with a 25% deposit of $862.50 due on acceptance

The deposit is a line in the document the client is already accepting, not a second ask that arrives after the fact.

If a client already stalled on a signed contract before you read this, do not send a bigger ask, send a smaller one: re-send the same invoice with a short, specific note ("just following up, want to make sure this didn't get buried") and a real due date. Our guide on asking a client for payment politely has the exact wording for that first nudge and every excuse that tends to follow it, and our payment reminder email templates cover the full sequence if the first nudge does not land.

The sunk-cost trap: the more free work you do, the harder this gets#

Nobody frames this part clearly, and it matters. The harder a deposit conversation feels, the more likely it is that free work already happened before the money was discussed, mockups, a discovery call that turned into a working session, a "quick draft" to show good faith.

Every hour you spend before the deposit is agreed is an hour that makes walking away later feel more expensive than it should, which is exactly backwards: the work you already gave away for free is already gone whether you continue or not.

The practical fix is upstream of any script: stop doing unpaid creative or strategic work before the deposit conversation happens, even a "quick" one. If a client wants to see your thinking before committing, that is what your portfolio and past work are for.

This is also where knowing a client's actual history pays off. A returning client with a clean record of on-time payments earns a lighter deposit; a new client with no track record does not, whatever their opening tone.

!A client detail page in Raoura showing outstanding balance of $2,400, lifetime revenue of $3,000, and relationship stage set to Active

Outstanding balance and payment history sit on the client record itself, so the deposit decision is based on their actual pattern, not a gut read from one conversation.

When to walk away#

Walk away when a client meets two or more of these at once: no workable alternative to a straight deposit, escalating pressure instead of a proposed structure, and no verifiable business information you can find. Any one of these alone is common and often fine. Two or more together, on a client you have never worked with, is a pattern, not a coincidence.

Concretely, that looks like:

1. You offered a smaller milestone or PO-based structure, and they rejected that too, not just the original percentage.
2. Every reply adds new pressure ("I thought you wanted this job") rather than a new option.
3. A basic search turns up no verifiable business name, no reviews, and no digital footprint that matches what they told you (worth a proper 20-minute check before any high-value contract, not just a gut feel).
4. They want to start "today" or "this week" with no room to even finish the conversation.
5. This is the second or third objection in the same conversation, not the first.

If that is where you land, the exit script is short and does not require an argument:

"I understand this isn't going to work for both of us. I'll hold off on the project for now, best of luck with it."

You are not owed an explanation for declining unpaid work. The freelancers in the source threads for this piece who said "I just dropped him" were, without exception, glad they did. If you want the fuller picture of what else should make you walk before signing anything, our client red flags database covers 50 more of them, ranked by severity.

Is refusing to start work without a deposit even legal?#

Yes. As an independent business, you can set your own payment terms, including declining to begin work until a deposit is received, and no US law requires you to extend credit to a client who has not paid you anything yet. This falls under ordinary freedom of contract, the same principle that lets any vendor set its own terms; it is not a special freelancer carve-out, and no source we found points to a specific statute granting it because none is needed.

One distinction worth knowing: what you are calling a "deposit" as a freelancer is a contract term you set, not the kind of regulated security deposit that shows up in landlord-tenant law or, in a few states, licensed home-improvement contracting. California, for example, caps the down payment a licensed contractor can collect on a residential home-improvement job at $1,000 or 10% of the contract price, whichever is less, under Business and Professions Code section 7159.5, enforced by the Contractors State License Board. That cap applies to licensed contractors doing residential remodeling work. It does not apply to freelance creative, marketing, or technical services, where deposit terms are simply whatever you and the client agree to in the contract.

This is general information, not legal advice for your specific situation. If you are structuring deposits on consistently large contracts, an hour with a contract lawyer is cheap insurance against a badly worded clause, not against the basic right to require payment before you start. And if a client cites a specific state law at you during this conversation, our freelance payment laws by state guide will tell you fast whether they are right.

What the numbers actually tell you#

There is no reliable, sourced statistic anywhere on what share of deposit refusals turn out to be bad faith versus genuinely cautious clients. Several sites publish specific-sounding percentages here ("40% default rate," "70% of disputes prevented"), and none of them link to an actual study. Treat any number like that as decoration, not data, and do not repeat it in your own client conversations.

What is real and sourced: 56% of US small businesses currently have unpaid invoices outstanding, averaging $17,500 each, per Intuit QuickBooks' 2025 Small Business Late Payments Report, which surveyed more than 2,000 US small businesses. The same report found 47% have invoices overdue by more than 30 days. Separately, a 2025 report from collections firm CashInUSA put the number even higher industry-wide: 55% of all US B2B invoiced sales are currently past due, with the average business waiting 43 days for payment.

Neither of those studies is about deposit refusal specifically. But here is the arithmetic worth sitting with, and it is ours: if roughly half of small-business invoices in the US run late regardless of who the client is, a 50% deposit does not just reduce your risk, it converts half of every project's payment risk into money that is already resolved before you have written a line of the final invoice. The remaining balance still faces the odds above. The deposit portion does not, because it was never exposed to them.