The Deposit That Saved the Project

Priya once sent her biggest invoice of the year to a client who had already stopped answering email. It was never paid. This is the story of the rule she made afterward, and why it works.

The $6,000 handshake

A quick disclosure first: Priya isn't a real customer. She's a composite, stitched together from stories we've heard from many freelancers. That's exactly why she's worth writing about — this happens all the time.

Priya is a freelance web developer. Two years ago, a local business owner asked her to build a new website: design, development, content migration, launch. They agreed on $6,000.

The client seemed great. Responsive, friendly, genuinely excited about the work. When it came time to talk payment terms, Priya thought about asking for a deposit — and didn't. It felt awkward. Distrustful, even. He'd been so nice. She didn't want to open the relationship by implying he might not pay.

So the project started on a handshake and a plan to "invoice at the end."

For five weeks, everything went well. Weekly check-ins, warm feedback, small revisions. By her estimate the site was about 80% done: design finished, most pages built, launch checklist drafted.

Then the client stopped answering.

There was no falling-out, no complaint about the work. Just silence. Emails went unanswered. Calls went to voicemail. A month passed, then two. She later heard the business had hit money trouble, and the website had quietly dropped off its list of priorities.

Priya had put roughly six weeks into the project. The site never launched. At 80% complete on a $6,000 job, she ate about $4,800 in unpaid work — plus the paying projects she'd turned away to make room for it.

The part that stung most: the client never actually refused to pay. There was simply never a moment where paying was required.

The new rule: money moves before work does

After that, Priya made one rule. Every project starts with a payment schedule, and no work starts until the deposit clears.

Here's what that looks like in practice, using The Invoicer App.

Every project now begins as an estimate. Priya writes up the scope and the price and sends it over, and the client approves it online — no printing, no scanning, no "looks good!" buried in an email thread.

The moment the estimate is approved, she converts it into an invoice. That invoice carries her standard payment schedule:

• 40% deposit before any work begins
• 40% at design sign-off
• 20% at launch

The deposit isn't a request; it's a gate. The invoice includes a secure Stripe payment link, and each installment can be paid by card on its own. The client pays the deposit before Priya so much as opens her editor, and the money lands directly in her own Stripe account — The Invoicer App takes no cut of it.

From there, the schedule runs itself. As payments arrive, installments are checked off automatically, earliest first. The client gets an emailed receipt showing what they paid and exactly what's still owed. Priya gets a "you got paid" email, which she calls the best notification in her inbox. And at any moment, either of them can open the invoice and see what's paid and what's next — no spreadsheet, no "wait, did I send that?"

(Online card payments are part of the Business plan. The free plan covers estimates and invoicing, and whatever price you sign up at is locked forever.)

A deposit isn't distrust

The mental shift that took Priya longest was this: asking for a deposit is not an accusation.

Your electrician takes deposits. Your wedding photographer takes deposits. Your landlord takes one before handing over the keys. Nobody reads any of that as an insult. It's simply how professionals structure work that takes time and carries risk.

A deposit doesn't say "I don't trust you." It says "I do this for a living."

There's a second, quieter benefit. A deposit is a filter. A client who genuinely intends to pay for a website rarely objects to paying 40% of it up front. A client who balks at any money before work begins — who wants to "see how it goes" using your unpaid weeks — is showing you who they are, for free, before you've built anything.

Since making the rule, Priya has lost exactly two prospects over the deposit conversation. She counts both as money saved.

How big should the deposit be?

Typical deposits for freelance work run 25–50% of the project price. Where you land in that range depends on a few practical things.

Project length matters: the longer the job, the more a deposit protects, and the more milestones you can place between the deposit and the final payment. Client history matters too — many freelancers ask 50% from first-time clients and relax to 25–30% once someone has a track record of paying on time. And if you buy anything up front — stock assets, plugins, subcontracted help — the deposit should at least cover those out-of-pocket costs.

Priya's 40/40/20 split works because no single unpaid milestone can ever cost her more than 40% of a project, and the final 20% is small enough that no client has a reason to stall a launch over it.

The same project, one year later

Last spring, in our composite story, Priya quoted another $6,000 website for another friendly, enthusiastic local business owner.

She sent the estimate on a Tuesday morning. The client approved it online before lunch. The estimate became an invoice with her 40/40/20 schedule attached, and the $2,400 deposit was paid by card within the hour — before she'd written a single line of code.

The site launched on schedule. The final installment was paid the day it went live. Total time spent chasing payment: zero.

Same price. Same kind of client. Same friendly emails. The only difference was a rule, and a payment schedule that enforced it so she didn't have to.

That's the real return on a deposit. It doesn't just save you money on the projects that go wrong. It lets you relax on the ones that go right.