The Business of Mixing

Helping mix engineers build sustainable careers.

"Working with Michael has been the best investment I've ever made in my mixing career. Better than any piece of equipment or any tutorial."

Alex Krispin
Mixing Engineer, Miami, FL

← Back to Blog

When to Fire a Client: Setting Boundaries as a Successful Mix Engineer

When to Fire a Client: Setting Boundaries as a Successful Mix Engineer

I'm going to say something that might sound insane if you're a mix engineer who's still fighting for every project: One of the most important business decisions you'll ever make is choosing to stop working with someone.

Not turning down a cold inquiry. Not passing on a project that doesn't fit your schedule. I mean looking at a client you already have — someone who's already paying you — and deciding that the relationship needs to end.

Most engineers never consider this. The idea of voluntarily walking away from revenue feels like career suicide when you're still building. You've spent months, maybe years, trying to get people to hire you. Why on earth would you get rid of one once you finally have them?

Because some clients aren't helping you build. They're keeping you stuck. And the longer you hold onto them, the more damage they do — to your energy, your reputation, your rate structure, and your ability to attract the kind of work that actually moves your career forward.

The Clients Who Cost You More Than They Pay

Let me paint a picture you'll probably recognize.

You have a client. They pay you, say, $300 per mix. That's real money. That's groceries. That's a chunk of rent. On paper, it's a good thing.

But here's what the $300 doesn't tell you:

They send you mixes back with 15 pages of revision notes. They want you on the phone for an hour before you even open the session. They text you at 11pm asking if you got their email. They negotiate the rate every single time, even though you've worked together six times. They want three rounds of revisions for a project that should have been done in one. They question your decisions in ways that aren't about the music — they're about control.

By the time you add up the hours — the mixing, the revisions, the emotional labor of managing someone who doesn't trust you — that $300 project took you 15 hours. You made $20 an hour. Before taxes. Before your overhead. Before your tools and subscriptions and the rent on whatever space you're working in.

That's not a client. That's a job. A bad one.

And here's the part that really hurts: While you were spending those 15 hours on a $300 project, you weren't spending them on outreach to better clients. You weren't working on your systems. You weren't finishing the project for the client who actually respects your process and pays your full rate. You weren't doing the things that grow your business because you were consumed by the thing that's shrinking it.

The real cost of a bad client isn't what they pay you. It's what they prevent you from earning.

The Signs Are Always There

In my experience coaching engineers, the pattern is remarkably consistent. When I ask someone to describe their most difficult client relationship, the signs were always present from the beginning. They just chose to ignore them because they needed the work.

Here are the patterns I see over and over:

They negotiate before they've even heard what you do. The first question is about price, not quality. Not process. Not your approach. Just "what's your rate?" followed immediately by "can you do it for less?" This person will never value your work. They're buying a commodity and they'll treat you like one.

They disrespect your time without realizing it. Late to calls. Slow to send files. But when they need something? It's urgent. They expect you to be available on their schedule while having no respect for yours. The relationship is one-directional from day one.

You dread the notification. This is the big one. When you see their name pop up on your phone or in your inbox, your stomach drops. Not because of the work — you love mixing. Because of them. Because you know that message is going to be a problem, a complaint, a last-minute change, or an emotional drain you don't have the bandwidth for.

They make you worse at your job. I've watched engineers lose confidence because of a single toxic client. The constant second-guessing, the nitpicking that has nothing to do with making the song better, the way they make you feel like you don't know what you're doing — it bleeds into your other work. You start doubting yourself on projects that have nothing to do with this person. That's not a professional challenge. That's corrosion.

They refer people just like them. Bad clients attract bad clients. When your most difficult client refers their friend, that friend is almost always cut from the same cloth. Now instead of one problem, you have two. And you feel obligated because it was a "referral."

If you're reading this and a specific name just popped into your head, that's all the information you need.

The Scarcity Trap

"But Michael, I need the money."

I hear this constantly. And I get it. I really do. When you're building a career and every dollar matters, the idea of voluntarily cutting off a revenue stream feels reckless. Irresponsible, even.

But here's what I've learned from coaching hundreds of engineers through this exact conversation: The scarcity mindset that makes you hold onto bad clients is the same scarcity mindset that keeps you attracting them.

When you operate from "I can't afford to lose anyone," you make decisions that signal desperation. You accept rates below your value. You tolerate behavior you shouldn't. You bend your boundaries every time someone pushes. And the market responds accordingly. You become the engineer who's "easy to work with" — not because you're actually collaborative, but because you'll put up with anything.

The clients who respect your work, pay your rate, and treat you like a professional? They can smell desperation. And they avoid it. Not because they're snobs, but because they've learned that the person who won't hold a boundary with them probably won't hold a standard on their project either.

So the bad clients stay, and the good clients go elsewhere. And the cycle reinforces itself.

Here's what makes this even more painful: Your bad clients know you're operating from scarcity. Maybe not consciously. But they can feel it. That's why they push the boundaries. That's why they negotiate every time. That's why they send revision notes at midnight and expect you to respond by morning. They've learned — through your behavior, not your words — that you'll take it. That you need them more than they need you. And as long as that dynamic exists, it will never improve. It will only escalate.

I'm not telling you to fire a client when you can't make rent. That would be irresponsible coaching. But I am telling you that the fear of losing a client is almost always disproportionate to the actual impact of losing them. You've built them up in your mind as essential revenue when in reality they're a fraction of your income and a majority of your stress.

What Happens When You Finally Let Go

I've coached engineers through this decision dozens of times. And while every situation is different — different finances, different markets, different goals — the outcome follows a remarkably consistent pattern.

One engineer I worked with had a client who paid decently but required so much hand-holding and so many revisions that the effective hourly rate was embarrassing. This client took up roughly 30% of his working hours but only accounted for about 15% of his income. And emotionally? They accounted for about 80% of his stress.

We ran the numbers together. We looked at his pipeline. We talked through his fears. And eventually, he made the call. Not dramatically. Not with a big speech. He just stopped being available for the next project.

Within six weeks, he had replaced that revenue. Not because the universe rewarded him for being brave — because he finally had the time and energy to pursue the opportunities he'd been too exhausted to chase. He started reaching out to artists he actually wanted to work with. He had the headspace to update his portfolio. He took a meeting he'd been putting off for months.

The bad client wasn't just costing him money. They were costing him momentum.

I've seen this happen enough times that I'd call it a pattern, not a coincidence. Another engineer let go of two clients in the same month — both low-rate, high-maintenance relationships she'd been tolerating for over a year. She was terrified. Within three months, she'd replaced both with clients paying 40% more who required half the revision cycles.

She didn't get lucky. She got free.

When you're consumed by a toxic client relationship, you don't realize how much of your capacity it's eating. Not just hours — mental and emotional bandwidth. The cognitive load of dreading someone's feedback. The energy spent managing their expectations instead of doing your best work. The way it colors your entire day when you know you have to deal with them.

Remove that, and you suddenly have resources you forgot you had.

There's a third story I come back to often. An engineer who'd been tolerating a client for two years — not because the money was good, but because they'd become friends. The lines had blurred. The client expected buddy pricing. Expected priority scheduling. Expected the engineer to basically be on-call for their projects while paying below market rate. And the engineer felt guilty even thinking about changing the terms because it felt like betraying a friendship.

We spent three coaching sessions just untangling the business relationship from the personal one. When he finally had that conversation — not firing the client, but restructuring the terms — the client walked. Just left. No negotiation, no counter-offer. And you know what that told him? It was never a friendship. It was someone taking advantage of the fact that he thought it was. That clarity alone was worth more than any project fee.

Difficult vs. Toxic: An Important Distinction

I want to be careful here, because there's a difference between a difficult project and a toxic client, and conflating the two will hurt you.

Difficult projects can be some of the best things that happen to your career. An artist with a strong vision who pushes you to try things outside your comfort zone? That's growth. A project with complex arrangements that forces you to level up technically? That's valuable. A client who gives detailed, thoughtful feedback because they care deeply about the outcome? That's a gift, even when it's exhausting.

Difficult is not the same as toxic.

Toxic is when the difficulty isn't about the music — it's about the person. When the revisions aren't about making the song better, they're about control. When the feedback isn't detailed and thoughtful, it's vague and contradictory. When the communication isn't demanding because they care, it's demanding because they don't respect you.

The test I use with my coaching clients is simple: After a session with this person, do you feel challenged or do you feel drained?

Challenged means you're growing. Drained means you're shrinking.

A difficult client who pushes you to do better work and pays you fairly for the effort? Keep them. Nurture that relationship. Those people make you a better engineer.

A toxic client who grinds you down, underpays you, and makes you question why you got into this business? That's the one we're talking about.

Don't use this post as justification to bail on every client who gives you a tough note. Hard feedback from someone who cares is how you grow. The distinction matters, and being honest with yourself about which category a client falls into is part of being a professional.

Why I Won't Give You a Script

You might be expecting me to give you a template. An email you can copy-paste. A "how to fire a client in three easy steps" framework.

I'm not going to do that.

Not because I'm holding back information — because it would be irresponsible. Every situation is different. Your financial runway, your pipeline, your market, your relationship history with this person, your goals for the next six months — all of it matters. A decision like this requires understanding the full picture of your business, not a generic script from a blog post.

I've seen engineers fire clients too early, before they had the pipeline to absorb the loss. I've seen others wait too long, burning out so badly that they nearly quit the industry entirely. The timing matters. The approach matters. The context matters.

What I can tell you is that the pattern is always the same: The signs are there. The costs are real. The fear is almost always bigger than the reality. And the engineers who make this decision thoughtfully — with a clear understanding of their numbers, their pipeline, and their trajectory — almost always come out better on the other side.

That's not a decision you make from a blog post. That's a decision you make when you understand your full business picture. When you can look at the numbers and the emotions and separate the two. When someone who knows your specific situation can say, "Yeah, based on everything I know about where you are and where you're going, here's what I'd consider."

The Permission You Don't Need

Here's what I really want you to take away from this.

You don't need permission to protect your business. You don't need someone to validate that a client relationship isn't working. You already know. You knew before you opened this post. The name came to mind immediately.

The question isn't whether you have a client you should probably let go of. The question is what's keeping you from doing it, and whether that reason is real or manufactured by fear.

Most of the time it's fear. Fear of the gap. Fear of looking ungrateful. Fear of burning a bridge. Fear of what it says about you if you can't "handle" a difficult client.

But holding onto a client who's actively making your business worse isn't handling anything. It's avoiding a decision. And avoidance has a cost that compounds every single week you let it continue.

The best engineers I work with aren't the ones who never have bad client relationships. They're the ones who recognize the pattern early and act on it before it does real damage. They protect their energy, their standards, and their capacity to do great work — because they understand that those things are the actual product they're selling.

Your talent, your ear, your creative instincts — those are valuable. And every hour you spend being ground down by someone who doesn't respect them is an hour stolen from someone who would.

So here's the question I'll leave you with, and I want you to sit with it honestly:

If you added up all the hours, all the stress, all the emotional labor, and all the opportunities you've missed because you were consumed by your worst client relationship — what has it actually cost you? Not just in dollars, but in the career you're not building while you're busy surviving this one?

That number is almost always bigger than you think. And it's growing.

Great relationships need great systems behind them.

A Strategy Call gives you 90 minutes to build the processes that protect your creative relationships. Scope, revisions, communication, and boundaries.

Book a Strategy Call ($350) Or start with the free Rate Reality Check