The Deposit Playbook: Asking for Money Up Front Without Losing the Job

Deposits are the least discussed line in a service business. Everybody has an opinion about them — the owner who thinks asking for money up front costs jobs, the office manager who is tired of chasing final payments, the tech who has driven forty minutes to an empty driveway. What almost nobody has is a written rule. So the deposit gets asked for when the customer feels risky and skipped when they seem nice, which is exactly backwards, because likeability is not a credit check. A deposit policy is not a collections tactic. It is a way of finding out, before you spend anything, whether the person on the other end has actually decided.

Know what you are actually protecting against

There are three different problems people try to solve with a deposit, and they call for three different amounts. The first is a no-show: the appointment that vanishes and takes a slot with it. The second is cash exposure: materials you have to buy, permits you have to pull, product you have to order before anyone pays you a cent. The third is commitment: the customer who says yes, keeps the quote open for months, and is quietly still shopping.

Name yours before you pick a number. A med spa booking a ninety-minute treatment is protecting a slot, so a small amount held on file does the whole job — the point is friction, not funding. A roofing company staging materials for a tear-off is protecting real outlay, and the deposit needs to cover the money that leaves your account before work starts. A solar installer is mostly protecting sequence: the design, the permit, the interconnection paperwork all happen weeks before there is anything on a roof.

The mistake is copying a percentage from a competitor without knowing which problem it was designed for. A flat thirty percent is either too much for a treatment or nowhere near enough for a job where materials are most of the cost. Work backwards from what you are exposed to, and the number stops feeling arbitrary to you — which is the first reason it stops feeling arbitrary to the customer.

Ask at the moment of yes, not after it

The best time to collect a deposit is the same conversation in which the customer agrees to go ahead. Not the next morning, not in a follow-up email, not when the crew is confirming the date. Enthusiasm has a half-life, and every hour between the decision and the payment is an hour in which the deposit becomes a second decision to make.

That means the payment link has to exist before the yes does. If asking for a deposit requires someone to build an invoice, send it from a different system, and wait, you will lose most of them to that gap. A saved link, a card on file, a text with a one-tap page — the mechanism matters more than the script.

When you do explain it, explain it as scheduling, not as trust. “The deposit is what holds the date and gets your materials ordered” is true and requires no defensiveness. “We ask for a deposit because people cancel” invites the customer to prove they are not one of those people, and now you are negotiating character instead of confirming a booking. Say the number in the quote too, in writing, before it comes up on the phone. Nobody likes discovering a payment they did not know about.

Apply it consistently. The moment you waive deposits for the customers who push back, you have created a policy that only applies to the people who did not think to argue — and the ones who pushed hardest are usually the ones you most wanted the deposit from.

Decide the refund rule before you need it

The question that decides whether a deposit policy survives contact with reality is what happens when someone cancels. Write that rule down and put it where the customer sees it before they pay. A window in which the deposit is fully refundable, a point after which it converts to credit, and a clear statement of what is non-refundable because it was already spent — ordered materials, a permit fee, a product that was opened.

Be more generous than feels natural at the top of the window and stricter than feels comfortable at the bottom. The generosity costs little and removes most of the reason a hesitant customer says they will think about it. The strictness is what makes the deposit do its job at all. A deposit that is always refunded on request is a formality with a payment step attached.

And expect exceptions. Weather, hospitals, a family emergency. You will refund some deposits you did not have to, and that is fine — the policy exists to set the default, not to remove your discretion. What you should not do is let the exception become the unwritten rule by never recording that you made one.

What to automate, and what stays a human call

Automate the mechanics. Generate the payment link when the quote is accepted and attach it to the same message. Send one reminder if the deposit is unpaid after a few hours and a second the next morning, then stop and flag it for a person. Hold the slot as tentative rather than confirmed until the deposit clears, and release it automatically at a deadline everyone knows about. Send a receipt that restates the refund window in plain language. Log every waived or refunded deposit against the job, with a reason, so the exceptions are countable at the end of the quarter.

Keep the judgement human. Whether a long-standing customer, a landlord who sends you six jobs a year, or a commercial account gets different terms. Whether a hesitation on the phone is a cash-flow problem you can solve with a smaller deposit or a signal that the customer never intended to book. Whether to waive the cancellation charge on a job you would rather not have taken. Those decisions depend on the relationship and on what you heard in the customer's voice, and no rule you write will contain them. Automate the asking, the reminding, and the recording. Decide the exceptions yourself, and count them.