You sent the first pass on Tuesday. They said it was sounding amazing. They had a few notes, you turned them around by Friday. You sent the revision, and then nothing.
A week passes. Two. You check the email thread for the hundredth time, wondering if you missed something. You send a gentle bump. Crickets. The half-finished session is still open on your second monitor, and you still haven’t been paid for the work you’ve done. That’s a client ghosting in progress, and almost every working mix engineer hits one eventually.
Welcome to client ghosting, the silent epidemic of freelance mixing work. It is not rare, it is not your fault, and it has a playbook. Most engineers learn this playbook the hard way, losing money and sleep along the way. This post is the shortcut.
We’re going to walk through what’s actually happening when a client goes silent mid-project, how to handle the first 72 hours without burning the relationship, when to escalate, how to recover payment for work already done, and the specific contract language that makes the next ghost much less likely to cost you anything.
Why Client Ghosting Happens (And Why It’s Not Personal)
Before you spiral into “did I do something wrong,” understand that most client ghosting situations have nothing to do with the mix. Engineers tend to take silence personally because the work is creative and the relationship feels close. But the actual reasons your client disappeared are usually mundane and rarely about you.
The most common cause is money. The artist ran out of budget, the label pulled funding, the manager said no to the second invoice. Instead of telling you that, they hide. Embarrassment is a powerful silencer. A client who can’t pay you would rather avoid you entirely than have the conversation.
The second most common cause is internal band drama. The vocalist quit. The producer and the artist had a falling out. The deluxe edition got shelved. Suddenly the mix you’re working on belongs to a project that no longer exists, and nobody wants to be the one to tell you.
A distant third is genuine life chaos. Death, illness, divorce, a major job change. These do happen, and they do explain temporary silences. But if it stretches past two weeks with zero contact, you’re almost certainly looking at one of the first two causes dressed up as the third.
What Ghosting Almost Never Means
It almost never means they hated the mix. Clients who hate the mix tell you. Loudly, often, and with a lot of adjectives. Silence is the opposite of dissatisfaction with the work. Silence means something else broke.
It almost never means they found a better engineer. If they had, they would either tell you (some clients do this, painfully) or quietly ask for stems before disappearing. A client who ghosts without asking for stems is not switching, they are stuck.
The First 72 Hours: Don’t Panic, Don’t Pursue
Your instinct after the first missed reply is going to be wrong. Either you’ll spiral and assume you ruined the mix, or you’ll fire off three follow-ups in two days that look desperate. Neither helps. The first 72 hours of a possible client ghosting are about pacing, not pursuit.
Here is the protocol for the first three days of silence.
Day 1 (missed reply day): Do nothing. People miss emails. Producers go to sessions, parents take their kids to soccer, founders fly to LA. A single quiet day is not ghosting. Keep working on the mix if you’ve been paid for that stage, or move on to your other projects if you haven’t.
Day 3: Send one short follow-up. Not “are you ok?” Not “did I do something wrong?” Just a casual professional bump. “Hey, wanted to make sure the latest revision came through ok. Let me know what you think when you get a chance.” That’s it. One line, no neediness, no pressure.
Day 7: Send a second message, this one slightly more structured. Reference the timeline. “Following up on the revision I sent on the 15th. Happy to jump on a quick call if it’s easier to talk through. Otherwise, let me know if you need anything else from me to move forward.” Now you’ve created a paper trail and given them an easy off-ramp.
If you haven’t heard anything by day 10, you’re in actual ghost territory. Stop sending casual bumps. Switch gears.
The Two-Week Mark: Time for a Different Conversation
Around the two-week silence point, a client ghosting moves from possible to probable. You need to do two things. First, freeze the project. Second, send a message that explicitly names the situation without being aggressive about it.
Freezing the project means stopping all work. If you were going to do another pass, don’t. If you were going to render alternate versions, don’t. Lock the session, archive it, and move it off your active queue. Continuing to work on something that may never be paid for is one of the most common ways engineers lose money.
The message at this point should sound something like this. “Hey [name], it’s been a few weeks since I’ve heard back, and I want to make sure the project is still active on your end. I have the mix in the state we left it. If you’d like to pick this up again, just let me know and I’ll get back to it. If you need to put it on hold or step away from the project entirely, also fine, just want to know where things stand so I can plan my schedule. Either way, the outstanding balance on the work completed so far is [amount] and is due regardless.”
That last sentence is the one most engineers leave out. Don’t.
You’re not being aggressive. You’re stating a fact. The work you’ve already done has a price tag, and that price tag doesn’t disappear because the client disappeared. Naming the number in writing protects you legally and psychologically.
Recovering Payment After a Client Ghosting
If your message at the two-week mark gets a response, you’re often in negotiation territory. The client might come back with “we’re going on hold, can we pause the project?” That’s fine, but the outstanding invoice for work completed still gets paid before you press pause. Anything else means they walk away with your labor for free.
If they don’t respond, you have a few escalation levels for recovering payment after a client ghosting. They scale with how much money is on the line and how much of your energy is worth spending.
Escalation Level 1: The Formal Demand
Switch from casual email to formal language. Use a different subject line (“Outstanding invoice for [project name]”) and use bullet points. State the amount, the work it covers, the date the invoice was issued, and the date payment is due. Give a deadline, usually seven to ten days from the date of the new message.
This often works on its own. The shift in tone signals that you’ve moved from collaborator mode to business mode, and a lot of clients who were hoping you’d forget about it suddenly remember they have a way to PayPal you.
Escalation Level 2: The Demand Letter
If the formal email gets ignored, the next step is a written demand letter. You can write this yourself or pay a lawyer a small fee to draft one on letterhead. According to the Freelancers Union, formal demand letters often resolve a client ghosting situation without needing to escalate further.
The letter should reference your original agreement, state the amount owed, list the dates and the specific work it covers, and give a final deadline (usually 14 days). It should also mention that you reserve the right to pursue legal remedies if payment isn’t received.
A lawyer-drafted demand letter costs $50 to $200 and has a much higher response rate than emails from you. The letterhead does most of the work.
Escalation Level 3: Small Claims Court
For unpaid balances over $500 and under your state’s small claims limit (usually $5,000 to $10,000), small claims court is realistic. You don’t need a lawyer. Filing fees are typically $30 to $150. You file in the jurisdiction where the client lives, which is sometimes the dealbreaker if they’re across the country.
Bring your contract, the email thread, the invoice, and any evidence of work delivered. Judges in small claims tend to side with the person who has the paper trail, which is almost always the engineer.
For balances under $500, small claims is rarely worth the time. Write it off, learn from it, and move to prevention.
The Contract Clauses That Make Client Ghosting Less Costly
Most of the pain from a client ghosting is preventable with contract language you should already have in place. If you’re working without a written agreement, that ends today. If you have one, audit it for the following clauses.
Deposit clause. Non-refundable deposit of 30% to 50% before any work begins. This single clause filters out 90% of potential client ghosting before it ever becomes a problem. A client who won’t put a deposit down is a client who was probably going to disappear anyway.
Milestone payments. Don’t do all the work and invoice once at the end. Break the project into rough mix, revision rounds, and final delivery, with payment due at each stage. If a client ghosting happens after the rough mix, you’ve at least been paid for the rough mix.
Stale project clause. This is the one most engineers don’t have. It says: if the client doesn’t respond to communication for 30 (or 60) days, the project is considered abandoned, and any outstanding balance is due immediately. The unused portion of the deposit is forfeited.
That clause turns a client ghosting from “I lost a month of revenue and have nothing to show for it” into “the contract ran its course and the deposit covered my time.”
Stem-and-files-on-payment clause. Final stems, project files, and bounced mixes are only released after final payment clears. No exceptions. This clause is what flips a ghost back into a paying client when they finally need the files.
Late fee clause. A 1.5% to 2% monthly late fee on overdue invoices. This doesn’t usually generate much actual late fee revenue, but it gives you grounds to bring up interest accumulation in your demand letter, which adds pressure.
If you’re not sure where to start with any of this, our guide to what to include in a mix engineer contract covers each clause in detail with example language.
How to Spot a Client Ghosting Before It Happens
Some clients telegraph the ghost weeks in advance. Once you’ve been through a client ghosting a few times, you start to see the pattern. Here are the patterns that show up most often.
The client takes a long time to send the original tracks. Not a few hours late, but days or weeks of “I’ll send them tonight” followed by nothing. If they can’t get organized enough to send you the files, they probably can’t get organized enough to pay you on time either.
The deposit conversation gets weird. They ask if they can pay the deposit “next week” or “after the first revision.” They want to negotiate the percentage. They suggest “we’ll just trust each other on this one.” Every red flag here is screaming.
The brief is vague and the references are inconsistent. A client who can’t articulate what they want is a client who’s likely to change their mind, and clients who change their mind on the work are more likely to change their mind on the project entirely. That pattern is a leading indicator of client ghosting risk.
They have a long list of people who need to “weigh in” before approving anything. The manager, the producer, the label, the partner, the cousin who DJ’s. The more decision-makers, the higher the ghost risk, because any one of them can stall the project indefinitely.
For more on the warning signs to catch before they become problems, our post on mixing client red flags goes deeper.
Why Your Intake Process Sets the Tone
Most client ghosting situations happen because the relationship never had a clear shape to begin with. The brief was loose, the timeline was vague, the deposit was “we’ll figure it out,” and the files came in through three different cloud links.
A clean intake fixes most of this before the work starts. When a client uploads their tracks to a structured intake link like session.trackbloom.com, they’re doing more than sending files. They’re signaling that the project is real, they’re organized enough to follow a process, and they’re committing to a defined start. The friction of an intake link weeds out the tire-kickers who were never going to pay anyway. WeTransfer can’t do that. A casual shared drive folder can’t do that. A proper intake process can, and that process is one of the cheapest forms of client ghosting insurance you can build.
If your intake feels like a casual favor, the rest of the project will too. If it feels like a professional service, ghosts become a lot less common, because flaky clients self-select out before they can cause damage.
What to Do With the Time You Get Back
The hardest part of being ghosted isn’t usually the money. It’s the open loop. You spend weeks checking your inbox, wondering, doing nothing about it. That open loop costs more than the unpaid invoice ever did.
The faster you can close the loop, the faster you can move on. Send the formal demand. Lock the session. Write it off on your taxes if it comes to that. Then go book the next client.
Engineers who survive long-term don’t dwell on the ghosts. They learn from each one, tighten their process, and assume that 5% to 10% of clients will flake no matter what they do. They price that risk into their rates and their deposits and stop taking client ghosting personally.
One last thing. Every ghost teaches you something. Maybe it’s that you should have asked for a bigger deposit. Maybe it’s that you should have caught the red flag in the discovery call. Maybe it’s that you needed a stale project clause in your contract. Whatever it is, write it down. Update your intake. Update your contract. Next quarter, when the next ghost shows up, you’ll lose less money and less sleep than you did this time.
That’s the actual win. Not eliminating client ghosting, because that’s not possible. Getting better at it, faster than the engineers around you.