Many Pricing leaders know they need more support and struggle to get the business to see it the same way.
They are doing too much manually. They are stuck reviewing every deal. They have strategy ideas they cannot execute. And they are one project away from burning out the only Analyst they have. But when they ask for headcount, the response is some version of: "We already have a pricing person. Why do we need another one?"
This article is for the VP or Director who has built credibility, earned trust, and still hears no. It is a framework for making the case more effectively with business logic, not burnout symptoms.
Speak in outcomes, not capacity
The biggest mistake I see is asking for support based on volume. "We have too many quotes." "We're reviewing too many deals." "I'm spread too thin."
Those things might be true, but they don't resonate. Executive teams don't add headcount to reduce someone's calendar load. They add it to unlock new value.
Instead of framing the ask around what is broken, frame it around what is stuck. "We cannot move forward with a segmentation model until we have someone to own the analysis and system build." Or: "Field pricing adoption is low because we cannot dedicate resources to training or follow-through." Or: "Quote velocity has dropped because we are still manually managing the logic in CPQ and do not have capacity to rework it."
Tie every gap to a business lever: margin, speed, growth, governance.
Use the headcount to build leverage
When a Pricing leader asks for help, the instinct is to give them "a person." But a single generalist rarely solves the problem. Strong cases focus on leverage: what will this person take off your plate that allows you to do higher-impact work?
If you are doing Analyst work as a Director, show what gets unblocked when you step back into strategy. If you are doing Sales enablement reactively, show what shifts when someone owns proactive pricing adoption. If you are firefighting exceptions, show what changes when you can focus on upstream logic.
A good Pricing hire doesn't just "fill a gap." They increase the reach and credibility of the function. That's leverage.
Build your case like you'd price a product
The business wouldn't greenlight a price increase without understanding cost, value, and risk. Treat headcount the same way.
Cost: Show what this role would require: base, bonus, and systems access.
Value: Quantify what it unlocks: margin lift, faster quotes, cleaner governance, better field adoption.
Risk of inaction: Lay out what happens if the role is not added: talent loss, failed implementation, stalled initiative.
You do not need a 30-slide deck. A one-page business case built around five sections is enough.
Current state: What Pricing covers today and where it is stretched.
The gap: What is not getting done and what that costs the business.
The proposed role: Scope, reporting line, and how it integrates with existing functions.
Expected value: The margin, speed, or governance improvement the hire would unlock, quantified where possible.
Risk of inaction: What happens in the next two quarters if the role is not added.
That structure mirrors the same logic you would expect a GM to present when asking for resources. It works because it speaks the language of the business, not the language of workload.
Common objections and how to preempt them
"We already have someone doing pricing."
"Right now, we're covering execution and governance. But we aren't staffed to drive strategy or deliver the improvements we've identified."
"Can't you just make the system do more?"
"The system can do more. But system logic is only as good as the analysis behind it."
"Let's hold off and revisit in Q3."
"By Q3, the CPQ redesign will be underway. If we don't have headcount in place by then, we'll either delay it or cut corners again."
Bottom line
If you are in a Pricing leadership role, you are already used to explaining the value of logic, structure, and margin control. Making the case for headcount is no different. Frame it around what the business could be capturing, and the conversation changes.
You've already built the credibility. Now it's about connecting the dots between what Pricing does and what the organization needs next.