Every few months, somebody publishes "the definitive pricing framework for audio engineers." Sometimes it's a tier system. Sometimes it's an hourly calculation. Sometimes it's a formula based on years of experience times complexity times genre.
I read them. I respect the effort. But I don't recommend any of them, and I won't be publishing my own.
Here's why.
The variables that matter are not the ones in the framework
Most pricing frameworks operate on visible variables. Years of experience. Project complexity. Local market. Hours per project.
The variables that actually move pricing in real businesses are mostly invisible. The engineer's willingness to lose the gig. The strength of their positioning. The depth of their pipeline. The state of their savings. The client's specific budget reality. The relationship history. The leverage in the room. Whether the engineer is hungry or full this month.
A framework can't see any of that. So it averages. And the average is wrong for almost every individual case.
"Right" is a moving target inside one person
I've watched the same engineer charge $400 a song one month and $2,500 a song six months later, for the same kind of work, and have both numbers be the right number for the moment they were charged.
When $400 was right, they had two months of expenses in savings, a slow pipeline, and a relationship-building project where the artist would refer them later. When $2,500 was right, they had eight months of runway, a positioning shift that made them harder to substitute, and the same artist coming back for a paid follow-up.
A pricing framework can't account for the fact that "right" depends on where you're standing. The number is downstream of the context. The context changes faster than any framework can update.
Frameworks make the answer feel safer than it is
Here's the actual harm I see when engineers adopt a published pricing model.
They feel like they've solved pricing. They quote the framework number. The conversation goes badly. The work doesn't come. They blame the market. They go back to underpricing.
The framework gave them an answer instead of helping them build the muscle. The muscle is being able to look at a specific inquiry, weigh the actual variables, and price it. Frameworks substitute for that muscle. They don't build it.
Useful pricing thinking is messier than people want it to be
When I work through pricing with engineers, the conversation is almost never about a number. It's about:
- What does your runway actually look like? How desperate are you?
- What's the inquiry actually worth, including non-cash value?
- What does your closed-rate history say about the gap between what you quote and what you accept?
- What does your positioning support? What does it not support?
- Who else is in the room? What's their leverage? What's yours?
The output of that thinking is a number, but the thinking itself is what's portable. The number isn't.
What I will offer instead
I'll share patterns. I'll share what I've noticed across thousands of conversations. I'll point at the variables that tend to matter and the ones that tend to be distractions.
But the actual price you should quote on the actual inquiry sitting in your inbox right now? I genuinely don't know. Neither does any framework. The honest version of this work is that pricing is a judgment call, not a calculation, and the judgment has to be built one decision at a time.
The frameworks are popular because they promise to skip the judgment. The reason I don't publish one is that there isn't one to publish.
If pricing keeps coming back as the thing that's stuck in your business, the Strategy Call is where we work through the actual variables in your situation. Not a framework. The specifics.
