The album got mastered three weeks ago. You moved on. You’re halfway into a new project when their name lights up your phone again. “Hey, can we just bump the vocal up on track 4? Tiny tweak. Shouldn’t take long.” Welcome to the never-done client: pleasant, complimentary, and somehow always finding one more thing.
You sigh. You open the session. You bump the vocal. You bounce. You send.
Two days later: “Actually, can we go back to the old vocal level but add a bit more reverb on the bridge?”
Every mix engineer eventually gets one of these, and most engineers handle it badly the first three or four times before they figure out a real system. The work creeps out past the contract. The pay doesn’t. The session that should have closed in early March is still open in your DAW in late May. You’re not mixing anymore. You’re babysitting a song that doesn’t want to grow up.
This post is the playbook. We’re going to walk through who these clients actually are, why the pattern keeps repeating, the specific moments where you can break it, and the language that closes a project without closing the door on future work.
What Makes Someone a Never-Done Client
The phrase “never-done client” comes from a Gearspace thread that’s been quietly running for nearly a decade, where mastering engineer Thomas W. Bethe describes an artist who’d been sending him “just one more revision” for over 90 days after the masters were delivered. The term stuck because every working engineer recognized the pattern instantly.
A never-done client is not a difficult client. They’re often pleasant, complimentary, even apologetic. They thank you for your patience. They tell you the mix sounds incredible. Then they send another note. Then another. Then another. The relationship feels collaborative right up until you realize you’re doing your fifth revision on a project that was signed off three months ago.
Three patterns show up almost universally.
The first is decision avoidance. They cannot commit to a finished song because committing means it’s real, and real means it will be judged. Every tweak buys them another week before they have to put the song out into the world. Your DAW is functioning as a safety net for their nerves.
The second is fresh-ear panic. Every time they play the master in a new context (car, AirPods, gym speakers, a friend’s living room) they hear something different and want to chase it. They don’t yet understand that a finished master will always sound slightly different on every system. So they spiral, and they bring you into the spiral with them.
The third is the perfectionist loop. Their reference for the song is a moving target. As they listen, their taste evolves. The mix they approved a month ago no longer matches the version they hear in their head. They genuinely believe each new note will be the last one.
None of these are character flaws. They’re predictable human responses to releasing creative work. But predictability is not the same as acceptability, and the engineer’s job is to recognize the pattern early and structure the relationship so it doesn’t drag on indefinitely.
How to Spot a Never-Done Client Before Sign-Off
Most never-done client situations are preventable if you catch the warning signs before final approval. By the time you’re three “tiny tweaks” deep, you’re already losing. The earlier you spot the pattern, the more options you have.
Watch for these signals during the active mix phase:
- Revisions that contradict the previous round. They asked for less vocal compression. Now they want more. The notes don’t build, they oscillate.
- A growing list of “while we’re at it” requests. Each revision pass picks up a new element that wasn’t in the original brief.
- Pulled-in third parties giving feedback. The manager suddenly weighs in. The drummer’s girlfriend has thoughts. The original decision-maker keeps getting outvoted by people who weren’t on the brief.
- Excessive praise paired with new notes. “It sounds incredible, just one more thing” is the universal cadence. Three rounds of this in a row is diagnostic.
- Hesitation around final approval. You ask if the mix is signed off. They say “almost” or “let me sit with it one more night.” That night becomes a week.
When you see two or more of these in the same project, you’re not dealing with a normal revision cycle. You’re dealing with a client who structurally cannot land the plane, and your job is to land it for them.
The Three-Strike Revision System for Never-Done Clients
The simplest defense against a never-done client is a clear revision policy enforced from day one. Most engineers know this in theory and forget it in practice. Then the third or fourth revision request comes in and they tell themselves it’s just a quick one, and the boundary erodes.
A three-strike system works because it gives you a clean structure for the conversation. Build it into your contract and quote it at intake.
Round one is the first full revision. Anything reasonable. New notes, balance adjustments, EQ tweaks, comp choices. Free, included in the mix fee.
Round two is the second revision. Refinements on what came back from round one. Also included, but flagged in writing as the second of three.
Round three is the final included revision. After this round, the project is signed off. Any further work goes to an hourly recall rate.
When you send the round-three bounce, send it with explicit language: “This is the third and final revision included in the original scope. Once you approve this, the mix is locked. If anything else comes up after sign-off, I can handle it at my hourly recall rate, which is $X per hour with a one-hour minimum.”
That last sentence does the heavy lifting. It doesn’t refuse future work. It just prices it. The never-done client who would have happily sent you eight more “quick tweaks” suddenly has to decide whether each one is worth $X. Most of them aren’t, and the project closes.
The Hourly Recall Rate That Tames Never-Done Clients
The recall rate is the single most useful tool for handling a never-done client, and most engineers don’t have one. They have a per-song mix rate. They have a contract. They have a deposit policy. But they don’t have a number ready for “what happens after the project is signed off.”
Set the number now, before you need it. A good recall rate is two to three times your effective hourly mix rate, with a minimum charge. If you normally bill out at $60 an hour for mixing, your recall rate might be $150 an hour with a one-hour minimum. The higher rate accounts for the cost of reopening a closed session, reloading plugins, finding the right state, and getting back into the headspace of a project you’d already mentally archived.
Put it in your contract. Put it in your final delivery email. The first time you mention it shouldn’t be the first time the client hears it.
When the post-delivery tweak request comes in, the response is short and friendly:
“Happy to do that. Reopening the session counts as a recall, so it’ll come in at my hourly recall rate of $X with a one-hour minimum. Want me to send a quick invoice and get started, or do you want to bundle this with any other tweaks first?”
That last clause matters more than people realize. It does two things at once. It signals that you’ll do the work without complaint. And it nudges the client toward batching their requests instead of dripping them out one at a time. Most clients, faced with the choice, will sit on their note for a few days, decide it wasn’t worth $X by itself, and either let it go or wait until they have a real batch worth paying for.
The Sign-Off Email That Locks the Project
Most never-done client situations start with a soft sign-off. The engineer delivers the final mix. The client says “love it, let me know what’s next” or “amazing, sending payment.” That feels like approval. It isn’t.
A real sign-off is explicit, in writing, and dated. Build it into your delivery workflow.
When you send the final mix, send it with language like this:
“Attached is the final master for [song title], approved at our last revision. Please confirm in writing that this is the final approved version. Once I have your confirmation, I’ll archive the session and consider the project complete. Any further changes after sign-off would fall under my recall rate, which is $X per hour with a one-hour minimum.”
Then wait for the explicit “approved” or “confirmed” before you archive. If the client replies with “sounds great” or “love it” without the magic word, follow up: “Quick confirmation: can you reply with ‘approved’ so I have it in writing for my records?”
This sounds bureaucratic until you’ve been through your fifth post-delivery tweak cycle. After that, it sounds like the most reasonable thing in the world. The friction of typing the word “approved” is tiny for a client who actually intends to sign off. For the never-done client, that friction is the speed bump that forces them to confront the fact that they’re committing.
A written, dated approval is also what protects you if a dispute ever escalates. You have a record of when the project closed. You have a quoted recall rate. The conversation moves from “but I just wanted one more thing” to “the project closed on this date and additional work is billable.”
The “Sit With It” Window
For never-done client patterns specifically, a built-in cooling-off period before final approval can prevent half the post-delivery requests before they happen.
When you send what you think is the final revision, don’t ask for sign-off the same day. Tell the client: “Sit with this for 72 hours. Play it on three different systems. Take notes. Send me everything you want changed in one message. After that, we’ll either run a final round or call it locked.”
Three things happen in that window. First, the mere-exposure effect we covered in the demo-itis post starts working in your favor. The mix becomes familiar instead of new. Second, the client batches their thoughts into a single message instead of firing off panic notes as they come up. And third, the act of waiting forces them to commit to the sign-off as a decision rather than slipping into approval by inertia.
This single workflow change reduces the never-done client risk by a substantial margin. It costs you nothing. It buys the client psychological space to actually land. And it positions the final round as a real ending, not a soft pause.
When to Hold the Line vs. When to Bend
Not every post-delivery request is a never-done client situation. Sometimes a real mistake gets caught. Sometimes a label demands a change after the master goes to distribution. Sometimes the artist genuinely needs an alternate version for sync. The skill is knowing the difference.
Hold the line when the request is creative drift. Notes like “can the vocal feel a bit more intimate” or “I want the chorus to hit harder” are pure tweak territory, no matter how reasonable they sound. The mix was approved. Creative reinterpretation after sign-off is recall work.
Bend when the request is a technical fault on your end. A click in the master, a panning error, a missing harmony you forgot to unmute. These are corrections, not revisions, and you fix them for free as fast as you can. Your reputation depends on this. Never make the client pay for your mistakes.
Also bend, selectively, when the relationship is genuinely valuable. If a client has paid every invoice on time, refers you regularly, and asks for a small tweak six months in, the right answer is sometimes “I’ll knock that out as a favor this time.” Not every situation needs to be billed. But that’s a deliberate choice on your part, not a default. The never-done client gets the recall rate. The favorite-client-with-one-real-note gets the favor.
The line between these two is judgment, and judgment improves with reps. A useful rule: if you’re feeling resentful before you’ve opened the session, the request is recall work. If you’d genuinely enjoy doing the tweak, it’s a favor.
What to Do When the Pattern Has Already Set In
If you’re reading this with a never-done client already deep into post-delivery tweak rounds, you don’t get to apply the prevention playbook. You have to reset the relationship mid-flight.
The reset conversation is uncomfortable but short. Send an email along these lines:
“Hey [name], wanted to flag something on my side. The session for [song title] has stayed open longer than I usually keep projects active, and I’d like to formally close it out so we can both move forward. I’ve loved the work we’ve done together. Going forward, any additional tweaks would come in at my hourly recall rate of $X with a one-hour minimum. Can you confirm the current version is approved as the final, and I’ll bill any further changes individually?”
That email is hard to send the first time. After that it gets easier. Most never-done clients respond well to it because they’ve also been quietly wishing the project would end and didn’t know how to land it themselves. You’re giving them permission to stop.
A small number will push back. They’ll say “but you usually do these for free” or “the last one was a tiny tweak.” Hold the line. Restate the recall rate. The clients who walk away over a recall fee were never going to refer you anyway, and the clients who pay it become better clients almost immediately. Boundaries don’t lose you good clients. They lose you bad ones.
For new projects starting now, use a clean intake process that surfaces this structure from day one. When clients send tracks through session.trackbloom.com, the project starts with a defined shape: stems organized by instrument, scope captured upfront, final formats agreed before the first fader moves. A structured intake doesn’t fix never-done clients on its own, but it sets the tone that the project has edges. WeTransfer-and-vibes does the opposite.
The Hidden Cost of Every Never-Done Client
Every never-done client costs you more than the unpaid tweak hours. They cost you the next client. They cost you the headspace to start fresh work. They cost you the relief of being able to file a project as truly done.
The math is brutal once you actually look at it. If a never-done client eats four hours of recall work a month for six months, that’s 24 hours of your time given away. At a $150 hourly recall rate, that’s $3,600 in lost revenue. But the real cost is opportunity. Those 24 hours could have been a full mix project for a new client, plus the referrals that project would have generated. The actual lost revenue is closer to $5,000 or $6,000, plus relationship value you’ll never see.
Worse, never-done clients teach you bad habits. After enough of them, you start opening every project with a defensive crouch. You assume revisions will spiral. You quote conservatively because you’ve been burned. The clients who would have been clean projects feel the friction in your communication and assume something is wrong. Bad clients shape how you show up for good ones, and the cost compounds.
Closing the never-done client is therefore not a small relationship problem. It’s a business decision that affects every project that comes after.
The Two Sentences That Solve Most of This
If you take only one thing from this post, take these two sentences. Memorize them. Use them verbatim until they feel natural.
The first is for the moment of final delivery: “Once you confirm this is approved, I’ll archive the session. Any changes after that point would come in at my recall rate of $X per hour.”
The second is for the post-delivery tweak request: “Happy to do that. It’ll come in at my recall rate of $X per hour with a one-hour minimum. Want me to send an invoice and get started?”
That’s the entire playbook compressed into two sentences. The first one closes the project. The second one prices the work that comes after. Together they end 90% of never-done client patterns without a single uncomfortable conversation, because the structure does the work that confrontation would have done.
The remaining 10% are clients who push past even those sentences. For those, the recall rate becomes the firing rate. Quote it. Stand by it. Let the client walk if they don’t want to pay it. You’re not running a charity for people who can’t decide their song is finished. You’re running a business that closes projects, archives sessions, and moves on to the next one.
The clients who pay the recall rate become some of your best long-term clients, because they’ve now experienced what professional boundaries feel like and they respect you more for it. The clients who don’t pay it self-select out of your roster, which is also fine. Either way, the never-done client pattern dies.
That’s the whole job. Not eliminating tricky clients, because that’s not possible. Building a system that handles them automatically, so you spend your real time mixing music instead of refreshing your inbox.