A deposit policy that exists as an informal habit rather than a stated rule tends to survive right up until a client pushes back, and then it quietly gets waived because there was never a firm line to point to. The policy itself was never really the problem, the lack of a consistent, stated one was.
A deposit policy that actually holds isn't a stricter one. It's one that's stated clearly enough that there's nothing to negotiate in the moment.
A deposit policy that only lives in your head gets waived under pressure
An unstated internal rule has no weight in the actual moment a client asks to skip it, because there's nothing concrete to point back to. A policy only holds if it exists somewhere explicit before the conversation happens, not as an improvised response to a request.
State the deposit requirement before you quote a price, not after
Introducing a deposit requirement after a client has already mentally committed to a number feels like a late addition and invites pushback. State it upfront, as part of how pricing and engagement work generally, so it's never a surprise added on later.
In Stelaah, a deposit requirement can be built directly into how an estimate converts to a signed engagement, so it's a standard part of the process rather than a separate ask. See how invoices works.
Make payment a real condition of starting, not a formality
If work quietly begins before the deposit clears, "required" stops meaning anything in practice. Treat the deposit as a genuine gate, work doesn't start until it's paid, not a step that gets skipped when the client seems trustworthy or the timeline feels tight.
Explain the reason behind it, not just the requirement itself
A deposit requirement stated without context reads as arbitrary. Briefly explaining the reason, it reserves capacity, it confirms commitment, makes the policy feel like a reasonable business practice rather than a hurdle aimed at the client specifically.
Have one deliberate, consistent process for exceptions
A policy with no exceptions at all is brittle; a policy with improvised exceptions isn't really a policy. Decide in advance what a legitimate exception looks like and handle every request the same way, rather than deciding case by case under pressure.
A simple checklist
If you do nothing else, do these five things:
- State the deposit requirement before quoting a price, not after.
- Treat it as a real gate to starting work, not a soft formality.
- Explain the reason behind the policy, not just the rule itself.
- Decide your exception process in advance, not case by case.
- Apply the policy consistently, so it never comes down to who pushes back.
Do that, and a deposit policy becomes something clients simply expect, not something you have to defend every time it comes up.
Run your client work in one place. Stelaah keeps projects, clients, contracts, and invoices together, with Aria for the busywork.
Start freeWe build Stelaah, the workspace for client work. We write about running teams, agencies, and venues without the busywork.
