Why Your Pricing Team Can't Be All Strategy or All Execution And how to spot when it already is
Most Pricing teams don't fail because of bad intent or lack of effort. They fail because they're lopsided. Either they overthink and never ship, or they ship nonstop without ever improving. Leaders feel it before they can explain it. Everything is reactive, or nothing ever quite sticks.
Teams often don't realize they have a gap until a Pricing leader quits, a system breaks, or Sales starts ignoring the playbook. This isn't a headcount issue. It's a structure issue.
What strategy-heavy Pricing teams get wrong
Strategy people usually have great slides. They've got frameworks, benchmarks, and long-term roadmaps. But when there's no one to translate that into systems, processes, or field behavior, all that thinking gets stranded.
I've seen teams design gorgeous pricing architectures: ideal segmentation, new discount tiers, waterfall redesigns. Nothing makes it into the quoting tool. Nothing lives in the system logic. The pricing policy might be technically correct, but it's two steps removed from what reps are doing in Salesforce.
It sounds good in meetings. Until someone asks: "Okay, but where has this been implemented?"
What happens when it's all execution
Execution-heavy teams have the opposite problem. They're fast, responsive, and deeply plugged into Sales workflows but they can't get out of the loop. Same quote exceptions. Same margin issues. Same urgent requests, week after week.
I've seen teams where Analysts are buried in deal support and price overrides, spending the majority of their time reacting with little left for fixing root causes. They're essential, but exhausted. They keep the engine running, but they don't get to rewire it.
At some point, senior leadership notices. And the team that's been praised for hustle suddenly gets asked: "What's your long-term plan for reducing this?"
What causes the imbalance
It usually starts with who got hired first. A VP from a top-tier strategy background builds a team of consultants. Sharp thinkers but weak systems. A legacy Pricing Analyst gets promoted into leadership and hires more operators who know the tools but don't challenge the model. A company prioritizes tools over structure by rolling out a CPQ or dashboards before anyone's defined how pricing decisions are supposed to be made.
Then the business scales. The volume goes up. The pain shows up. And the team that was "good enough for now" stops being good enough. The assumption is usually that the fix is more Analysts, when the real gap is a systems owner or a policy lead who can stop the work from sliding into chaos.
What a balanced team looks like in practice
The best Pricing teams often aren't big. But they're shaped intentionally.
There's someone who can analyze patterns and spot trends. There's someone who owns tools and automation, the glue between pricing logic and quoting behavior. And there's someone who defines policy, not in a vacuum, but with real understanding of what will hold up in the field.
Sometimes that's three people. Sometimes it's one person with depth in two lanes and support in the third. But when those lanes are missing altogether, things start breaking. Slowly at first, then visibly.
How to tell what you're missing
The signs are usually right in front of you but they don't always show up in a dashboard.
If strategy is missing, you'll see the team chasing noise. They'll be busy, responsive, and buried in exceptions but no one's asking the harder questions about pricing structure, segmentation, or deal design. Sales is still running the show, and Pricing is just cleaning up after them.
If systems are missing, everything slows down. Good ideas never scale. Quote logic lives in spreadsheets or Slack threads. Analysts build the same report five different ways, and no one's sure what made it into the CPQ or the ERP. The feedback loop breaks.
If analytics is weak, the team is flying blind. There's a lot of opinion, a lot of back-and-forth, but not much insight driving the decisions. The group might be operationally sound but they're optimizing yesterday's logic, not asking whether it still holds.
Most Pricing leaders know something's off. What they need is a way to name it and a plan to fix it without throwing bodies at the problem.
How this gets diagnosed
A common trap is assuming the Pricing team needs more horsepower when the real gap is coverage. The resume isn't the issue. It's role design, or misalignment between who's in the seat and what the function needs.
The fix depends on the situation. Sometimes it's a net-new hire. Sometimes it's replacing a generalist with a deeper operator. Sometimes it's reshaping responsibilities so policy, systems, and analytics stop operating as separate lanes. Most of the time, the problem is visible. It just isn't named clearly.
Bottom line
A Pricing team that's all strategy and no execution burns credibility.
A team that's all execution and no strategy burns out.
The best teams flex across both. Not with superheroes, but with balance. They don't just think. They build. They don't just build. They fix. And when something breaks, they know whether it's a logic issue, a tool issue, or a design issue because they've got someone thinking in each lane.
If you're stuck in quote support, stalled on strategy, or unsure why nothing's landing, you don't need a bigger team. You probably need a more balanced one.