The Deposit Policy Every Solo Founder Needs — Percentages, Exceptions, and Enforcement
A deposit is not a courtesy request — it is the risk-allocation mechanism of your business. It prices the risk that a client disappears, changes their mind, or slow-walks payment, and it instantly sorts serious buyers from curious ones.
This guide turns deposits into a clean policy: percentages by engagement type, the exceptions you allow deliberately, contract language that holds up, and refund rules that avoid the two most common disputes.
The short answer
- Requiring a deposit filters out roughly a third of would-be time-wasters before they reach your calendar.
- 50% upfront is the solo-founder standard for projects; 100% for anything under $1,500.
- Clients who push back hard on deposits show elevated rates of late payment and scope disputes later — the deposit is a diagnostic.
Who this playbook is for
Built for solo founders who start work on trust and have been burned at least once by a client who vanished mid-project.
Step 1: Set a percentage schedule by engagement type
Small fixed work (under $1,500): 100% upfront. Projects ($1,500-$15k): 50% to book, 50% at delivery. Large projects: 40/30/30 across milestones. Retainers: first month upfront, then monthly in advance. Publish this on your services page — a public policy feels like a system, not a negotiating position.
Step 2: Decide your exceptions in advance, in writing
Public sector and enterprises often legally cannot pay deposits — for them, use net-15 with milestone invoicing instead. Trusted repeat clients may move to deposits waived. Write the exception list down; ad-hoc exceptions are how policies erode until they are decorative.
Step 3: Put the deposit in the proposal, not the invoice
The deposit appears in the proposal as part of the payment schedule, before signature. Post-signature deposit requests trigger renegotiation energy; in-proposal deposits are just how you work. Include: amount, what it secures (calendar slot), and refund conditions.
Step 4: Wire deposits to consequences in the contract
Language essentials: deposit secures the start date and is non-refundable if the client cancels within X days of start; work begins on receipt of deposit, not on signature; deposits convert to first invoice credit at project start. One paragraph covers all three — get it into your template once.
Step 5: Handle "why do you need a deposit?" with a confident script
"The deposit books the slot and covers setup — it’s standard for independent specialists, and it’s credited fully to the project. Everyone I work with runs the same schedule." No apology, no paragraph of justification. Hesitancy in your voice costs more deposits than client objections ever will.
Your weekly operating rhythm
| Day | Action | Time |
|---|---|---|
| Per proposal | Payment schedule included with deposit line | in-flow |
| On booking | Deposit invoice sent immediately; start date pinned to receipt | 10 min |
| Monthly | Review exception list — did any waiver hurt? | 15 min |
| Quarterly | Adjust percentages based on write-offs and pipeline strength | 30 min |
KPIs that tell you it is working
| Metric | Healthy target | Why it matters |
|---|---|---|
| Deposit collection before start | 100% (except written exceptions) | Any pattern of "started anyway" means the policy is soft |
| Cancellation non-refund rate | Tracked | This is the policy paying for itself |
| Client objections to deposits | Should trend down | A published policy normalizes itself over months |
| Cash cycle | Positive from day one | The structural point of the whole policy |
Common mistakes to avoid
- Making exceptions verbally. "Just this once" deposits waivers multiply mysteriously; only written exceptions exist.
- Refunding deposits on client cold feet. The deposit compensates your blocked calendar; refunds turn it into a free option for clients.
- Collecting deposits after contracts are signed but before they’re countersigned. Sequence: signature and deposit together, or work never starts.
A tool stack that fits a one-person budget
| Tool | Where it fits |
|---|---|
| Stripe / Wise | Deposit links with card and bank options |
| Dubsado / Bonsai | Proposals with embedded payment schedules |
| Your services page | The public policy that pre-answers objections |
| Notion | The written exceptions ledger |
Keep going
Use these internal references while implementing this guide:
- One Person Company Hub
- How to Start a One Person Company
- Solopreneur Operating System
- A Pro Bono Policy for Solo Founders
- Refund Policies for Services
- Chargeback Defense for Solo Businesses
FAQ
Q: What deposit percentage is too high?
Above 50% upfront, buyers get genuinely nervous unless you are well-known. For big projects, milestone weighting (40/30/30) achieves the same protection with less sticker shock. The goal is risk coverage, not maximum prepayment.
Q: Are deposits refundable if the client cancels?
Non-refundable if cancellation happens inside your start window; refundable (minus a small admin fee) outside it. State both conditions in the proposal. This balances fairness with compensating you for a slot nobody else could book.
Q: How do deposits work with chargebacks?
Deposits paid by card can be disputed like any charge. For large deposits, prefer bank transfer or require signed acceptance of terms at payment. Keep the proposal, contract and payment all timestamped together — that paper trail is your chargeback defense.
Q: Should existing clients pay deposits too?
After 2-3 clean payment cycles, waiving deposits for trusted clients is a reasonable loyalty benefit — but keep it deliberate and written. New services or new project types with old clients still get full deposits.
Get the weekly operating brief
Every Monday: 3 moves, 5 minutes. Actionable strategy for your one-person company — no fluff, no filler.