Client Ghosted You After Delivery: The Recovery Playbook

There is a specific silence that follows hitting send on final files. The project thread that got replies within hours now gets nothing. The invoice sits unopened, or worse, opened and unanswered. You re-read your last message checking for something offensive in it. There is nothing. The client is just gone.

Before writing this guide we fetched every page ranking on the first page for this query in July 2026, and the field is strange.

• One page reframes your missing money as a "client experience" problem and never mentions the invoice.
• One was last substantively updated in 2021.
• One is a collections agency pitch from 2017.
• The best of them spends most of its words on ghosting before a project starts.

Zero of the four mention the copyright leverage you still hold over delivered, unpaid work, and zero mention the state payment laws passed in 2024 and 2025 that can double what a silent client owes you. This playbook covers both, in the order you should actually use them.

First, confirm it is a ghost and not a delay#

Treat silence as ghosting only after three unanswered contacts on at least two different channels over 14 days; before that, the odds heavily favor an ordinary late payment. Bonsai's analysis of three years of invoices from more than 100,000 freelancers found 29% of invoices are paid late, but over 75% of those late invoices are paid within 14 days of the due date, and about 90% within a month. Statistically, the client who has you drafting angry emails on day 6 will most likely pay by day 14 without ever knowing you were composing them.

A ghost is defined by channels, not by days. One unanswered email is an inbox. Three unanswered contacts across email and phone is a decision.

That distinction matters because the boring explanations are common and unglamorous:

• Your email landed in spam or a "later" pile.
• The person who hired you is on vacation or has left the company.
• The invoice is sitting in an approval queue behind someone else's signature.
• A company card expired.
• Larger clients add a structural one: your contact was never the person who pays, and accounts payable has never heard of you.

So the first 14 days are diagnosis, not war. Your job is to rule the boring explanations out one channel at a time, while keeping every message so professional it could be read aloud in small claims court later. Because if this does go the distance, it will be.

The 21-day recovery sequence#

Run six touches over 21 days and switch channels every second touch: same-thread email, fresh-thread email, phone plus voicemail, a second human at the company, a reissued invoice, and a final closing-the-file email. Repetition on one channel gets filtered by the same habit that ignored the first message. Switching channels is what breaks a ghost, because each new channel re-asks the question "are you really choosing not to answer this?"

Three of those touches deserve exact words.

The day 9 voicemail: "Hi [name], it's [you]. The [project] invoice for [amount] came due on [date] and I want to make sure nothing's stuck on your end. The payment link is in my email from [day]. If something's wrong, call me back today and we'll sort it out." Then the text: "Just left you a voicemail about invoice #142. All good on your end?" You are giving them a face-saving exit at every step; most late payers take it.

The day 13 note to a second person: "Hi, I'm the [role] who delivered [project] for [contact name] on [date]. Invoice #142 for [amount] is now [X] days past due and [contact] hasn't been reachable. Could you point me to the right person for payment status?" No accusations. Companies pay invoices; individuals ghost them. Your goal is to get the invoice back inside a process.

The day 21 closing email is the one that recovers ghosts, and it works by being calm about consequences: "I haven't been able to reach you since [date] despite several attempts, so I'm setting a final date. If invoice #142 ([amount]) isn't paid by [day 30 date], I'll send a formal demand letter by certified mail and pursue the remedies available to me, and I want to flag one of them now: my contract licenses the delivered work upon full payment, so until payment clears, the files I delivered aren't licensed for use. I'd much rather close this the easy way. Here's the payment link." Then stop. No more reminders between day 21 and day 30. Silence from you, for once, does the talking.

If reminders feel impossible to keep up with on top of billable work, that is a systems problem rather than a courage problem, and the fix is covered in our guide to getting clients to pay invoices on time.

The leverage you still hold: the work itself#

Under US copyright law, ownership of freelance work does not transfer automatically: a transfer of copyright requires a written, signed agreement under [17 U.S.C. § 204(a)](https://www.law.cornell.edu/uscode/text/17/204), which means a client who never paid very often never acquired the rights they are using. Freelancers consistently underrate this card. The client has your files, so it feels like they hold everything. Legally, possession of a file and license to use it are different things.

The mechanics, briefly and carefully. Work you create as an independent contractor is yours at creation, it only becomes the client's "work made for hire" in specific categories and only with a signed written agreement, and it only transfers by written assignment.

If your contract conditions the license on full payment (good contracts do, and our contract guide covers the clause), an unpaid client using the work is using it without a license. If your contract is silent, the picture is muddier, because courts can find an implied license once you hand work over voluntarily, which is exactly why the payment-condition clause belongs in every future contract.

What this is worth in practice: one factual sentence in your day 21 email and your demand letter, as shown above. A client who ignores "please pay me" often answers "the site you launched is using unlicensed work" very quickly, especially if their own clients or legal counsel might hear about it.

Two hard warnings.

1. Do not engage in self-help repossession. Logging into their site with credentials you still have and taking the work down can expose you to civil and even criminal liability under computer access laws, and it converts you from creditor to defendant. Say the words, never touch their systems.
2. This section is general information, not legal advice. It covers how US copyright works, not your specific dispute. If real money rides on the licensing question, an hour with an IP lawyer is cheap.

What to do when a ghost has actually published your unpaid work, including DMCA takedowns, is its own topic on our roadmap.

Day 30: silence becomes nonpayment#

At 30 days of documented silence, stop chasing and start enforcing: a certified demand letter, then the state laws that award double damages on contracts as small as $250 in California, $500 in Illinois, and $800 in New York, then small claims court, which handles claims from [$2,500 up to $25,000 depending on the state](https://www.nolo.com/legal-encyclopedia/small-claims-suits-how-much-30031.html) for a $15 to $100 filing fee. From this point on, a ghosted freelancer and a refused freelancer are in the same process, and we maintain the complete version in the unpaid invoice escalation ladder: the demand letter anatomy, the New York, Illinois, and California statutes in detail, and the small claims mechanics state by state.

Two additions specific to ghosts.

1. Confirm the client still exists before spending anything on enforcement. Spend ten minutes searching the state's Secretary of State business registry for their entity, checking whether the website and socials have gone dark, and searching the owner's name plus "LLC" for a new company. A ghost who dissolved their LLC is a different problem from a ghost who is dodging you, and the registry search is free.
2. Let the statute of limitations lower your blood pressure. Written contract debt remains enforceable for 3 to 10 years depending on the state. You have been ghosted, not beaten. The deadline pressure you feel is emotional, not legal.

And you are not an outlier who got uniquely unlucky. A Freelancers Union survey found 71% of freelancers have struggled to collect payment at least once, losing an average of nearly $6,000 a year to nonpayment, and Intuit QuickBooks' January 2025 survey of 2,487 small businesses found 56% are owed money on unpaid invoices, averaging $17,500 each. How late is normal, and how often invoices die entirely, is quantified in our freelance late payment statistics hub.

Ghost-proofing the next project#

The structural fix is to never be owed 100% of anything: a 25% to 50% deposit before work starts, milestone billing so no single payment exceeds one phase, and final files that transfer only when the final payment clears. Every one of those is a norm, not an imposition, and each has its own guide: how much deposit to charge, payment terms that surface problems early, and the late fee clause that makes silence expensive. Milestone billing, the single strongest ghost-proofing structure, is on our roadmap as its own guide.

The delivery mechanics matter as much as the paperwork. A ghosting is only catastrophic when the client already has everything. Deliver watermarked previews or a staging link for approval, invoice the final payment, and release final files on payment. That is not distrust; it is the same order of operations as every store you have ever walked out of.

The honest failure mode of all this advice is that it requires you to notice, on the right day, that an invoice crossed a threshold, and then to do an uncomfortable task instead of billable work, six separate times.

Raoura exists for that gap: it tracks every invoice, runs your reminder sequence automatically on the schedule you set, applies your agreed late fee after the grace period, and keeps delivered files behind a client portal where final versions unlock on payment, so the sequence above happens even when you would rather not think about it. Disclosure: Raoura is our product, and everything in this playbook works the same if you run it from a calendar and a spreadsheet.

!A delivered milestone in Raoura where the preview link is open but the final wireframes file shows a "Pay to unlock" badge, with a note that the file unlocks the moment the milestone is paid

The client can review everything and take nothing: final files unlock themselves when the payment clears, which makes ghosting pointless.