Demo-itis Is Killing Your Mixes. Here’s How to Beat It.

You spent two days on the mix. The kick is finally hitting. The vocal sits where it should. The low end is tight. You bounce it, send it, and wait.

Then the email comes back. “Something feels off. Can we make it sound more like the rough?”

This is demo-itis mixing in its purest form, and every working engineer runs into it. The client isn’t wrong on purpose. They’re not trying to make your life harder. Their brain is doing exactly what brains do: defaulting to whatever it heard first. If you don’t have a system for handling it, you’ll burn hours chasing notes that take the mix backward, and your client will still leave the project unhappy.

Demo-itis mixing isn’t a personality flaw or bad taste. It’s a predictable cognitive pattern, and once you understand the pattern, you can build a process that stops it from blowing up your projects. This post breaks down what’s actually happening, how to spot it before it derails the project, and the conversations that pull a client out of it without making them feel stupid.

What Demo-itis Mixing Actually Is

Demo-itis is a slang term, but the mechanism behind it is real. When someone listens to the same rough mix dozens of times during writing, recording, and demoing, their brain locks onto that version as the “correct” sound. Anything different feels wrong, even when it’s objectively better.

This isn’t taste. It’s wiring. Psychologists call it the mere-exposure effect: repeated exposure to a stimulus increases preference for it, regardless of quality. Robert Zajonc documented this in the 1960s and it’s been replicated across music, food, art, and even abstract symbols.

For your client, the rough mix has weeks of head-start on yours. It played in their car on the drive home from rehearsal. It was the version they sent their friends. It was the version they fell in love with. Your final mix has had ten minutes.

This is why “your mix sounds different” gets confused with “your mix sounds wrong.” The client genuinely cannot tell the two apart in the moment. Their feedback is real, but the cause isn’t what they think it is.

How to Spot Demo-itis Mixing Before It Derails the Project

Demo-itis mixing has a vocabulary. Once you learn it, the warning signs become obvious. Watch for any of these in revision notes:

• “It feels different from how I’m used to hearing it”
• “Can the vocal feel more like the rough?”
• “I miss something about the original”
• “It’s cleaner but I liked the old one better”
• “My friend said the demo had more energy”
• “The rough just felt more like me“

These aren’t technical notes. They’re emotional ones. The client isn’t asking you to change a frequency or adjust a level. They’re asking you to bring back a feeling. If you treat that feedback as literal mix instructions, you’ll undo your own work and end up with a duller version of the demo.

The trick is naming what’s happening before you touch a fader. Reply with curiosity, not defensiveness. Ask what specifically feels different. Most of the time, the client can’t pinpoint it. That’s the tell.

Why Clients Don’t Know They Have It

Here’s the hard part: people with demo-itis are almost never aware of it. They genuinely believe the rough is better. To them, your mix sounds polished but lifeless, and they can’t articulate why. They just know they want their song back.

This is also why arguing doesn’t work. If you tell a client “you’ve got demo-itis, trust me, the mix is better,” you’ll lose the room. They’ll feel patronized, dig in harder, and the relationship gets adversarial. The client owns the song. Your opinion about their hearing isn’t going to override their own ears.

The job isn’t to convince them. It’s to give them tools to hear the new version with fresh perspective. Once they can do that, the resistance usually drops on its own.

The Pre-Mix Conversation That Prevents It

The best moment to handle demo-itis mixing is before the mix exists. Set the expectation during onboarding that the final mix will sound different from the rough, and that this is the point.

Walk the client through what changes and why:

• The balance will feel different because you’re carving space for every element to be heard clearly
• Some parts they’re used to hearing loud will sit further back so the lead can breathe
• The vocal might feel less in-your-face but more present overall
• The low end will be tighter, which can feel “smaller” until they hear it on better speakers

Tell them upfront that the first listen of your mix will probably feel weird. That’s normal. Their ears need a few passes to recalibrate. Ask them not to send notes after one listen.

This single conversation kills 80% of demo-itis battles before they start. Not because it cures the bias, but because it gives the client a frame for what they’re feeling. When their brain says “this feels off,” they remember you said it would, and they slow down before firing off a panic email.

The A/B Test That Beats Demo-itis Mixing

When demo-itis mixing hits anyway, structured comparison is the most reliable way out. Ad-hoc A/B-ing doesn’t work because the client always picks whichever version played last (recency bias) or first (anchoring). You need a setup that minimizes both.

Here’s the protocol that holds up:

1. Have the client listen on a system they trust, not laptop speakers or AirPods. Studio monitors are ideal. A decent pair of headphones works too.
2. Give them a 24-hour break from the rough before the comparison. Time away dilutes the mere-exposure effect.
3. Send the new mix and the rough together, but don’t label which is which. Call them Version A and Version B.
4. Ask them to listen to each one twice, in this order: A, B, A, B. Repetition flattens the order effect.
5. Have them rate each on three things: vocal clarity, low-end punch, and overall energy.

When you remove the labels and force structured listening, the rough usually loses on at least two of the three. The client makes the call themselves, which is the only outcome that sticks.

If they still prefer the rough across the board, that’s useful information too. It means your mix actually moved too far from their reference. Time to find out which specific elements they’re missing.

When to Push Back vs. When to Match the Rough

Some demo-itis cases aren’t fixable, and you have to decide whether to fight it or follow it. The frame I’d recommend is simple: are you mixing for them, or are you mixing for the audience?

If the song is for streaming release and needs to compete with professionally mixed tracks in their genre, your job is to mix for the audience. The client hired you because the demo wasn’t good enough. Pushing back is part of what they’re paying for.

If the song is a personal project, a demo for pitching, or something the client cares about for emotional reasons more than commercial ones, sometimes matching the rough is the right move. You can voice your concerns once, then deliver what they want. Not every project needs to be your portfolio piece.

What you don’t want to do is silently resent the client for picking the demo while delivering exactly what they asked for. That energy leaks into the next project. If you’re going to match the rough, do it cleanly, charge for the work, and move on.

Specific Notes That Mean “I Have Demo-itis”

These are the most common demo-itis disguised as technical feedback. When you see them, slow down before changing anything:

• “The vocal needs to be louder” usually means the vocal sat higher in the rough’s bad balance. Bringing it up in your tighter mix often kills the dynamics.
• “It needs more energy” usually means the rough was clipping or over-limited and felt loud. Your mix has dynamic range, which feels quieter even when it’s not.
• “The drums lost something” usually means the rough had a heavy room sound or a lo-fi character that’s hard to articulate.
• “It sounds too clean” usually means the rough had artifacts (noise, distortion, phase issues) the client got attached to.
• “It needs more vibe” is almost always demo-itis mixing in disguise. There’s no fader for vibe.

Before reacting, ask the client to send timestamps of moments in the rough where they hear what they’re missing. Half the time, they can’t find one. That’s diagnostic.

Build a System That Catches Demo-itis Mixing Early

Most demo-itis mixing fights happen because the engineer didn’t see it coming. The earlier you spot the bias, the easier it is to redirect. A few systems-level fixes that pay off:

Ask for the rough mix and reference tracks at the start of every project. The rough tells you what they’re attached to. The references tell you where they actually want to end up. When those two contradict (and they often do), you know the project will need a demo-itis conversation before mixing starts.

Limit how much access the client has to the rough during the mixing window. If you can, ask them to take a week off from listening to it. The bias weakens with time. This is a hard ask, but suggesting it plants the idea that the rough is part of the problem.

Use a clean intake setup so the rough mix and references arrive in one place, labeled, alongside the session files. When everything lives in one organized space from the start, you can reference the rough deliberately during the mix instead of getting it forwarded over text three weeks later. session.trackbloom.com is built for this. It’s an upload link you send to the client, and stems, references, and roughs come in grouped and ready to work with. That kind of structure pays off the most when demo-itis mixing arguments come up, because you can cite the rough directly instead of hunting through old text threads.

Document your demo-itis conversation in writing. After the pre-mix call, send a short recap email: “Quick recap of what we discussed about why the mix will sound different from the rough. Wanted to put this in writing so we both have it.” When demo-itis hits later, you have something to point to that isn’t just your opinion in the moment.

What to Do When Demo-itis Mixing Hits Mid-Revision

Sometimes you do everything right and demo-itis mixing still shows up on revision two or three. The client signed off on V1, requested a few tweaks, and now suddenly they’re saying the whole thing has lost something. This is the frustrating version, because you didn’t see it coming.

The cause is usually that the client kept listening to V1 between rounds, and now V1 has become the new “rough” in their head. Every change you make from there feels like a step backward, even if the notes were theirs.

When this happens, stop and reset before doing more work. A few moves that help:

Pull up V1 and the latest version side by side and walk the client through what changed. Be specific. “You asked for the vocal to come up 1dB and the snare to crack more. Here’s exactly what I did.” When clients see that the changes are theirs, the demo-itis spiral usually breaks.

If the client can’t articulate what’s missing, send them home with both versions and ask them not to touch it for 48 hours. Tell them to come back with three specific timestamps where they can hear what they want changed. If they can’t find three, the issue isn’t the mix.

Don’t keep accepting vague rounds of revision while a demo-itis pattern is forming. Each round of “I’m not sure, just bring back some of the old feeling” gets you further from a finished mix and closer to a stalled project. Name what’s happening: “I think we might be running into demo-itis here. Can we slow down and figure out what specifically is missing before I make more changes?”

Most clients respond well to that conversation, especially if you’ve already framed demo-itis as a known thing during onboarding. They feel relieved that there’s a name for what they’re feeling, and they appreciate that you’re not just blindly executing notes that are taking the mix backward.

The One-Sentence Reframe That Saves Projects

When a client comes back stuck on the rough, the most useful thing you can say is some version of this: “What you’re hearing isn’t that the mix is wrong. It’s that your ears haven’t lived with it yet.”

That sentence does three things at once. It validates the feeling without agreeing with the diagnosis. It names the mechanism without making the client feel dumb. And it gives them something to do, which is wait and listen again, instead of demanding immediate changes.

Pair that with a 48-hour cooling-off period before the next round of notes, and most demo-itis cases resolve without a single fader move. The client comes back saying “you know what, I listened again, and it’s actually growing on me.” That’s not a coincidence. That’s mere-exposure working in your favor for once.

Demo-itis isn’t a problem you solve once and then never see again. It’s a recurring pattern that comes with the job. The engineers who handle it well aren’t the ones with the best comebacks. They’re the ones who set the expectation early, name the bias when it shows up, and give the client a structured way to hear past it.

That’s the work. It’s not always glamorous, but it’s the difference between getting referred and getting ghosted.