How to Handle Partial Payments Without Losing Track of What's Owed
A client owes you $4,000, and this morning $1,500 landed in your account with no explanation attached — just a transfer and a payment reference you do not recog...
Asking for a deposit rarely costs you a good client — bad timing and apologetic wording do. Here's how much to ask for, when to raise it, scripts you can use verbatim, and clean answers to the three objections you'll actually hear.
You have a new client ready to start. The scope is agreed, the dates are on the calendar, and everything feels good — right up until you have to say the words "I ask for a deposit before we begin." Suddenly you are rewriting the sentence in your head, softening it, wondering if it will make you sound like you don't trust them.
That hesitation is normal, and it is expensive: every project you start with nothing paid up front is a project where you carry all of the risk — your time, your materials, your calendar slot. If the client goes quiet halfway through, you are the one absorbing the loss, and the odds are not especially in your favor. Remote's 2025 Contractor Management Report found that 85% of freelancers have their invoices paid late at least some of the time, and that roughly one in five are paid late more often than they are paid on schedule.
The good news is that a deposit request almost never scares off a good client. What scares people is a request that shows up at the wrong moment, with no explanation, in wording that sounds defensive. This post covers how much to ask for, when to bring it up, the exact language to use, how to handle pushback, and how to keep the rest of the money on schedule once the work begins.
Most of the discomfort comes from a story we tell ourselves: that asking for money up front implies we expect the client to behave badly. It feels like an accusation dressed up as a policy.
But that is not how clients experience it. People pay deposits constantly — to book a venue, hold a rental car, schedule a contractor — and nobody reads those as insults. They read them as a sign that the thing being booked is in demand and the process behind it is organized.
A deposit is not a trust test — it is a commitment device, and it works in both directions.
For the client, paying something up front converts a vague intention into a real project. It moves your work from "something we're planning to do" to "something we've started." That has a real effect on how seriously the engagement gets treated internally — approvals move faster, feedback comes back sooner, and your emails stop sitting at the bottom of an inbox.
For you, it covers the cost of blocking out time and turning down other work. It filters out people who were never going to move forward. And it sets a tone: this is a business relationship with terms, not a favor.
There is no universal number, but there are sensible ranges depending on the kind of work you do and how long the engagement runs.
Pick your number before the conversation, not during it. A figure you decided on calmly, in advance, comes out of your mouth very differently than one you are computing live while someone waits.
The single biggest factor in how a deposit request lands is when the client first hears about it.
Mention it early — in your first proposal, on your pricing page, in the initial scoping call — and it is simply part of how you work, whereas mentioning it after the client has already said yes tends to read as a new condition being added late. It is the same policy in both cases, but the reaction is completely different.
The best sequence is: describe how you work before you talk numbers, put the deposit in writing in the proposal, then reference it as a known fact when it is time to start. By the time the invoice goes out, the client has already seen the terms twice. Nothing about it is a surprise.
The most effective phrasing is short, matter-of-fact, and framed around scheduling rather than trust, and you will notice that none of the examples below apologize for the request.
For a proposal or scope document: "To reserve your start date, I ask for 50% up front, with the balance due on delivery. Once the deposit is received, I'll block the dates on my calendar and send over the kickoff materials."
For a first call, said out loud: "Before we get into dates — the way I work is a 50% deposit to get started and the rest at the end. Does that work on your side?"
Three things make this language work. It ties the deposit to something the client wants — a reserved date. It states the full payment structure, so there is no second surprise later. And "the way I work" sounds less like a rule imposed on them than "my policy" does.
What to leave out: "I hope this is okay," "I know it's a lot to ask," and any explanation of past clients who burned you. Apologizing invites negotiation. Explaining your history makes it personal.
Occasionally someone will push back, and it is usually one of three objections, each of which has a clean answer.
"We don't pay deposits." Some larger organizations genuinely have procurement rules about this. Ask whether they can issue a purchase order instead, or offer to split the work into smaller phases invoiced on completion, so your exposure at any moment stays small.
"Can we do it after we see the first draft?" This is the most common one. A fair response: "I can start on a smaller first phase and invoice at the end of it — that way you see real work before committing to the full scope." You have kept a payment gate and given them the reassurance they asked for.
"That seems like a lot." Often the objection is cash timing, not the principle. Offering to split the deposit across two dates, or to reduce it slightly in exchange for a shorter payment window on the balance, resolves it more often than dropping the request entirely.
And if someone refuses every version of a payment gate on a project of real size, treat that as information. The pattern behind that answer rarely improves after you have delivered.
If you want to prevent friction before it starts, the way you onboard a new client, including when terms are introduced, does most of the work for you.
The fastest way to stop dreading the conversation is to remove the decision from it. When a deposit is a documented part of your process, you are not asking for a favor each time — you are describing how the engagement runs.
Put the terms in three places — your proposal template, your contract, and the invoice itself — and use the same numbers every time, so you are never doing mental math about what to ask this particular client.
A deposit protects the beginning of a project, but the balance is where things usually slip: the work is delivered, the client is happy, and the final invoice quietly ages while everyone involved moves on to the next thing.
Two habits close that gap. First, tie the final payment to a specific event rather than a vague endpoint: on delivery of final files, on launch day, on the last day of the month. Second, decide the follow-up schedule in advance — a short note a few days before the due date, another the day after, then a firmer one a week later. Deciding the cadence ahead of time means you never have to sit and rewrite an awkward email while annoyed.
If those nudges are the part that keeps falling off your plate, a reminder tool like DueDrop can send them for you on a schedule you set, alongside whatever invoicing software you already use.
For a wider look at getting paid on time, our guide to how reliable follow-ups change your monthly cash flow math shows what a steadier follow-up habit does to the numbers.
Yes. Deposits are standard practice in design, development, consulting, construction, photography, events, and most other project-based service work. Clients who hire freelancers or small firms regularly expect to be asked, and many are surprised when they aren't.
For fixed-fee projects, 30–50% is the common range, with 50% being the most frequent. Long multi-phase projects often use 25–33% up front with milestone payments after. If a job includes hard costs like materials or travel, cover those in full plus a portion of your fee.
Frame it around scheduling rather than risk: "To reserve your start date, I ask for 50% up front." Mention it in the proposal before the client says yes, state the full payment structure at once, and skip any apology. Trust never enters the sentence.
Offer an alternative that still limits your exposure — split the project into smaller phases invoiced on completion, request a purchase order, or divide the deposit across two dates. If someone rejects every form of payment gate on a substantial project, treat it as a signal about how the rest of the engagement is likely to go.
Most service providers make deposits non-refundable, because the money compensates for time reserved and other work turned down. Whatever you decide, put it in writing in the contract before the project starts, along with what happens if the client cancels partway through.
Connect your tools in five minutes. Let the first reminder go out tomorrow morning — sounding exactly like you'd write it yourself.
Start my free 14-day trial