How Much Deposit Should Freelancers Ask For?
You blocked two weeks for a rebuild. Kickoff was Monday. The client went quiet until Wednesday, then asked to "sync on vision" again. Thursday they wanted a different stack. Friday you still had not been paid, and another lead wanted a start date you no longer had.
That is what zero-deposit freelancing feels like. You are the bank, the PM, and the engineer — and the only one taking risk.
Deposits fix that. The question is not whether to ask. It is how much, and how to say it without sounding like you do not trust them.
What a deposit actually buys
A deposit is not a tip. It covers:
- Calendar commitment — you declined or delayed other work
- Early cost — discovery, architecture, repo setup, design review
- Relationship signal — serious clients pay to start serious work
If they will not fund the first milestone, ask whether they would hire a contractor to order materials without a draw. Same logic.
Typical deposit ranges for freelance developers
There is no universal law, but these patterns hold for web work:
| Project shape | Common deposit | Notes | | --- | --- | --- | | Small fixed build ($3k–$8k) | 50% upfront | Simple scope, short timeline | | Mid-size project ($8k–$25k) | 30–50% upfront | Often tied to discovery or phase one | | Phased engagement | 25–33% per phase | Each phase starts after prior payment clears | | Retainer | First month in advance | Ongoing access to your week | | Hourly / advisory | Prepaid hour block | 10–20 hours paid before work begins |
Pair the number with a proposal that already explains milestones. Deposits feel normal when the document shows where the money goes.
When to ask for more than your default
Go higher when:
- The client is new and you have no payment history
- You are booking exclusive time during a busy month
- Custom design or backend work starts before anything visible ships
- They need rush delivery
- The scope is fuzzy and you are pricing risk into phase one
You are not punishing them. You are matching terms to uncertainty.
How to ask without sounding defensive
Clients hear "50% upfront" better when it is tied to output.
Scripts that work:
- "To hold your start date of Oct 3, I take 40% to open phase one — discovery, architecture, and staging setup."
- "My standard terms are 50% to begin and 50% at launch. Happy to split into three milestones if that is easier for your AP cycle."
- "I can start once the deposit clears — that is how I protect the slot I quoted you."
Confidence beats apology. You are describing how you run a business, not negotiating your worth.
Deposits protect the week you sold.
Once a client is funded, delivery wins repeat work. WorkFocus helps freelance developers see today's priorities across every active project.
Deposits and scope control belong together
A deposit without clear scope just prepays chaos.
Write what phase one includes in the same email as the invoice. Tie the deposit to named deliverables in your statement of work. When "one small addition" appears in week one, you already have a document and a change-order path — the same habits that help you avoid scope creep.
Red flags when a client resists any upfront payment
Some pushback is normal — finance teams batch payments. Patterns to watch:
- "We never pay until the end" on custom work with no trust history
- Pressure to start immediately before paperwork
- Refusal to sign anything but enthusiasm to access your calendar
You can flex on milestone shape. You cannot flex on taking 100% of the risk forever.
After the deposit clears
Send a short kickoff note repeating:
- What you are building first
- What you need from them by when
- How to request changes
The deposit opened the project. Clarity keeps it profitable.
The bottom line
Most freelance developers should ask for 25–50% upfront on fixed-price web work, or the first phase paid before deep work begins. Match the percentage to risk, write it into the proposal, and tie it to real milestones.
If your bigger problem is keeping funded projects visible while new pings compete for the same week, try WorkFocus free — so the work you sold stays at the top of today, not buried under the last urgent message.
Plan today across every client.
WorkFocus is a daily command center for freelance developers — today's tasks, client projects, and bugs in one place.
Related posts
- Problem-awareNov 25, 2026 · 3 min read
How to Build Confidence as a New Freelance Developer
Imposter feelings are normal. Confidence for new freelance developers comes from systems that make delivery predictable - not from pretending you have ten years of agency experience.
- Problem-awareNov 24, 2026 · 3 min read
How Freelancers Can Avoid Burnout With Multiple Clients
Multiple clients do not cause burnout by themselves. Oversold capacity, invisible switching cost, and no off switch do. Here is how freelancers stay sustainable.
- Problem-awareNov 23, 2026 · 3 min read
How to Turn a One-Off Project Into a Retainer
Launch is not the end of the relationship. Here is how freelancers propose retainers that clients accept instead of calling someone new for every bug.