Client Ghosted After Final Delivery? How to Get Paid
By RemoteSWE ·
Short answer: change the order of operations, not the paperwork. Almost every ghosting story ends the same way — the freelancer sent the final files and then asked for the money. Once the deliverable is in the client’s hands, you have no leverage and they have no deadline. The fix is a deposit up front, a watermarked or low-resolution proof for approval, and working files released only after the final payment lands. One designer had five clients disappear this way in a single year. This post covers the payment ladder by project size, what to do when a client refuses a deposit, and the escalation sequence when it has already happened.
The short answer: the payment ladder
Match the structure to the size of the job. The smaller the project, the more of it should be paid before you start.
| Project size | Structure | Files released |
|---|---|---|
| Under $500 | 100% up front | On delivery |
| $500 to $3,000 | 50% deposit, 50% on approval | After final payment clears |
| $3,000 to $15,000 | 3 milestones: 30 / 40 / 30 | Per milestone, final assets last |
| Over $15,000 | Monthly or fortnightly invoicing | Rolling, work stops on non-payment |
| New client, any size | Deposit non-negotiable | Proof first, working files on payment |
The last row is the one that matters. A deposit is not a sign of distrust — it is what every business that survives does, and treating it as optional is the single most expensive habit in freelancing.
Why the ghosting happens where it happens
Look closely at the sequence in a typical case. Work is completed without a down payment. Final files are delivered. Payment is requested afterwards. At that moment the client has everything they wanted and you have a polite email.
Nothing about that outcome is surprising, and it is not really about dishonest clients. It is about incentives. A client who intends to pay pays anyway. A client who is disorganised, broke, or unhappy now has no forcing function, so your invoice joins a queue behind things with consequences. You removed the consequence when you sent the files.
There is also an uncomfortable diagnostic hidden in the frequency. One ghost a year is bad luck and a paperwork problem. Five in a year is a channel problem — it says something about where those clients are coming from, and it is worth checking whether people are going quiet before delivery too. If they are, the issue may be the work or the communication rather than the payment terms.
The delivery order that removes the problem
Send a proof, not the deliverable. Watermarked images, a low-resolution export, a staging URL you control, a video walkthrough, a build that expires. The client can review, approve and give feedback on all of these. They cannot ship any of them.
Release working files on payment, not on approval. Approval and payment are two separate gates, and collapsing them into one is where the money disappears. "Great, this is approved" is not a bank transfer.
Say it up front, once, without apology. Put it in the proposal: deposit to start, proof for approval, files on final payment. Stated at the beginning it reads as professional. Introduced halfway through, it reads as suspicion.
The pushback rate on this is far lower than most freelancers expect. In practice the clients who argue hardest about deposits are disproportionately the ones who were going to be a problem anyway, which makes the term a useful filter as well as a protection.
A worked example: two versions of the same $3,200 project
| Stage | No structure | With payment gates |
|---|---|---|
| Kickoff | Work begins on a handshake | $1,600 deposit clears, then work begins |
| Mid-project | Full effort, nothing invoiced | Progress shared on a staging link you own |
| Review | Final files sent for feedback | Watermarked proof sent for approval |
| Approval | Client approves, invoice sent | Client approves, final invoice sent |
| Payment | Silence. $3,200 at risk | $1,600 paid, working files released |
| Worst case | Lose the whole fee | Lose half, keep the deliverable |
The second column is not more work. It is the same project with two extra emails and one export setting changed. The difference in exposure is the entire fee versus half of it, and in practice the deposit alone prevents most of these situations from starting.
What to do when it has already happened
Work the ladder in order and do not skip steps — each one is cheap, and skipping to the end costs you the relationship and usually the money too.
- Day 1 after due date: a neutral nudge. No accusation, no emotion. Invoice attached, one line, assume it was overlooked. A surprising share resolve here.
- Day 7: a second email with a consequence. State plainly what happens next — work pauses, licence to use the files is not granted until payment, late fee applies if your terms include one.
- Day 14: change the channel. Phone, or a message to a different person at the company. Email is the easiest thing in the world to ignore; a colleague asking about an unpaid invoice is not.
- Day 21: formal demand. A written notice referencing your terms and a final date. Many countries let you add statutory late interest — say so.
- Day 30+: escalate or write it off deliberately. Small claims, a collections service, or a conscious decision to stop spending time on it. What you must not do is leave it open indefinitely and call that pursuing it.
Then close the loop: whatever happened, the next client gets a deposit. The lesson is only worth what you change.
Chargebacks: when you were paid and then unpaid
A different failure mode with a better outcome rate than most people assume. A client pays, then months later disputes the charge with their card issuer and the money vanishes from your account.
The issuer usually credits the cardholder provisionally, at their own risk, and then decides based on the evidence both sides submit. This is why documentation wins these. Freelancers who forward their agreed terms, the record of work in progress, and — most powerfully — written sign-offs, frequently get the decision reversed. A client email saying "this is approved" is close to conclusive.
Which means the same habits protect you twice. Written scope, written approvals, dated progress records and a paper trail of delivery are not bureaucracy; they are the evidence file you will need if a payment is ever reversed. Keep them for every project, including the ones that go well.
FAQ
What if a new client refuses to pay a deposit?
Reduce your exposure instead of abandoning the term: split the deposit smaller, break the project into a paid first phase, or take the whole fee up front on a job small enough that they risk little. A client who will not commit any money to a stranger is asking you to take a risk they are not willing to take themselves.
Should I take 100% up front?
On small projects, yes, and plenty of experienced freelancers do it on everything. Above a few thousand it starts to be a genuine ask, which is where milestones do the same job with less friction. The principle is unchanged: never let the amount of unpaid work exceed what you are willing to lose.
Does a contract actually prevent ghosting?
Not by itself. A contract determines who wins an argument; the delivery order determines whether the argument happens. Have both, but if you only change one thing this month, change the order in which you send files.
Five clients ghosted me this year. Is that normal?
No, and it is worth treating as a signal about where the clients are coming from rather than only as a paperwork failure. Check whether prospects are also going quiet before delivery. If they are, look at the channel and the fit — the warning signs are usually visible before signing.
You do not need better clients to fix this. You need the money to arrive before the files do. Deposit to start, proof for approval, working files on final payment — stated up front, once, in the proposal, and applied to everyone including the ones who seem lovely. Keep written approvals for every stage, because they are also your evidence if a payment is ever reversed. Then look upstream at where these clients are coming from, using the channel comparison here and the pricing filter here. If marketplace bidding is part of that mix, the proposal reviewer will tell you whether your opening lines are doing their job before you spend Connects finding out.