Scope is what kills more mixing businesses than rate ever will.
Scope is the thing that turns a $2,000 mix into 40 hours of work and a quiet kind of resentment. It's the third round of revisions that wasn't actually budgeted. It's the new stems that show up two days before the deadline. It's the friend asking "real quick" for two more mixes, on the same budget.
I'm not going to give you a scope template. I don't believe in those for the same reason I don't believe in pricing templates: scope is downstream of context, and the context is yours, not mine. But what I can share is how I think about scope when I'm working through it with an engineer.
I start by asking what they're actually selling
This sounds obvious. It isn't.
Many engineers, when asked "what does a $2,000 mix include," can't articulate it cleanly. They include things by default that they didn't price for. They exclude things they actually have to do. They don't know what's standard and what's extra because they've never written it down.
The first scope question isn't "what should I charge for this." It's "what am I even agreeing to do." Most of the time, the engineer surprises themselves when they actually answer it.
I look at the gap between what they sold and what they delivered
There's almost always a gap. Engineers don't usually deliver less than they sold. They deliver more. They throw in the stems they didn't include in the quote. They take the extra revision because they don't want to feel petty. They do the editing that wasn't supposed to be included because the client "just assumed."
The gap is the work. Not the scope template. The gap.
If the gap is closing two engineers' projects per month at five extra hours each, that's ten hours a month of unpaid work. Over a year, that's a project's worth of revenue you delivered for free. Multiply by years.
This is usually the moment something snaps. Not at the next scope template. At the realization that the leak is bigger than they thought.
I think about scope in three dimensions
When I'm thinking through scope with someone, I usually find three categories of risk:
- What's included. The actual deliverable. Number of mixes. Stem counts. Reference exchanges. Listening sessions.
- How long it takes. Time bounds. Revision rounds. Response-window expectations from the client.
- What constitutes "done." Sign-off mechanism. Final approval definition. What happens if the artist disappears mid-project.
Most scope failures are in category 3. The work is done but nobody officially called it done, so it stays half-open, and three weeks later the client comes back with a "small tweak."
I'm allergic to scoping by default
A lot of engineers scope by default. They use whatever they did last time. They borrow from a peer's contract. They assume the new client wants the same thing the last client wanted.
This is the source of an enormous amount of scope rot. Default scope is scope you didn't decide. Scope you didn't decide can't really hold a line, because there isn't a line to hold. It's just whatever happens.
Every project worth real money deserves a scoping conversation, even if the conversation is short. "Here's what's included. Here's what's not. Here's what 'done' looks like for this project specifically." Not a template. A choice.
I don't try to make scope airtight
The reason I don't believe in scope templates is that scope is a negotiation, not a contract. The most well-written scope document in the world can't survive a client who decides they're going to ask for one more thing.
What matters more than airtight scope is your willingness to say, in the moment, "that's outside what we agreed. Here's what that adds." That sentence isn't in a template. It's a posture you build by holding the line a few times and noticing the world doesn't end.
The engineers who handle scope well aren't using better contracts. They've just made peace with awkward conversations.
What I won't do here
I won't give you a contract template. I won't give you a scope checklist. The reason isn't laziness on my part. It's that scope only works when it matches what you actually do, what you actually believe, and what you can actually defend. A template you pasted in from someone else's business doesn't qualify.
Scope is one of those things where the right answer for you is specific to your work, your clients, and your tolerance for the conversation. None of which is in a template.
If scope is leaking your time and money in ways you can see but can't seem to fix, the Strategy Call is where we look at where it's actually happening in your specific situation, and what to do about it next.
