No. It realigns discretion with the economic risk of the transaction, which is a different thing. Today your highest paid sellers are probably setting price on every transaction, including thousands of low visibility line items where their time adds no value, while genuinely strategic exceptions get the same casual treatment as a $200 stock order. We build a negotiation corridor, an entry point, a target, and a floor, with clear rules for where each applies. Inside the corridor, sellers move faster than they do today because nothing needs approval. Outside it, exceptions get reviewed by someone accountable for margin, quickly, with a reason code that improves the guidance over time. Most sellers end up with more autonomy on most transactions. What goes away is not discretion. It is unexamined discretion on the small percentage of decisions where real gross profit dollars are at risk.

Because gross margin percentage is an average, and averages are where margin problems hide. A flat number can conceal cost inflation you passed through late, mix shift toward lower value work, quote losses on larger opportunities, and off invoice leakage in rebates, freight, and terms, all moving against each other and netting out to "looks like last year." The questions that actually reveal the condition of your pricing: What is your win rate on quotes above $5,000, and is it falling? How much unexplained price dispersion exists between similar customers buying the same item? What percentage of your revenue actually runs through systematic pricing governance versus being priced by memory, habit, or a spreadsheet from 2016? In our experience, executives who can answer all three usually do not have a problem. Executives who cannot are usually surprised by what the answers show.

A matrix is a rule set. Governance is what surrounds it: who can override it, what happens when they do, how often it is refreshed when costs move, and, most importantly, what share of your revenue actually flows through it. When we run this analysis at distributors, the answer to that last question is routinely a minority of the book. Contract customers, OEM business, systems and project work, and legacy customer specific pricing often sit entirely outside the matrix, priced on methodology nobody has reviewed in years. And inside the matrix, drift accumulates: items within the same size run priced wildly out of proportion to each other, exceptions layered on exceptions, logic ported forward through two ERP migrations because nobody owned rationalizing it. So the honest answer is: a matrix is necessary and not sufficient. The first question worth asking is what percentage of your revenue it actually governs. Most executives have never seen that number. It changes the conversation when they do.

Pricing software optimizes a number. We build the commercial system that determines whether the number ever reaches your P&L. The gap between those two is where most pricing initiatives die: a technically sound recommendation arrives at the quote line, the seller does not trust it, the manager does not inspect it, the compensation plan rewards ignoring it, and eighteen months later the tool is a line item in the budget review. We are technology agnostic by design. If you already own a pricing tool, our job is usually to make the system you already paid for produce the EBITDA it was bought to produce, by fixing the decision rights, workflow, incentives, and management routines around it. If you own nothing, we design the operating model first and recommend technology only where the business case requires it. The result we sign up for is realized gross profit dollars, verified against your financials, not a recommendation deck.

They will fight a black box. They will not fight a transparent system that makes their approvals faster and their commission checks more defensible. Field resistance to pricing programs is usually rational: the data was stale, the guidance was opaque, the approval took three days while the customer waited, and the last corporate initiative made their job harder without making them money. So we design for adoption rather than hoping for it. The logic is explainable, a seller and a manager can see why a given customer and product context has more or less pricing power. Rollout starts with a pilot led by respected field leaders, not a mandate. Override reasons feed back into the model instead of into a compliance report. And we look hard at compensation, because no pricing program survives a comp plan that pays sellers to do the opposite. If your team would genuinely fight a system built that way, that is not a pricing problem. It is an operating model problem, and it is the actual thing that needs fixing first.

Ten business days. That is the standard timeline from usable data to a completed Margin Opportunity Scan: a quantified value pool, a map of where margin is leaking and why, the share of your revenue under real pricing governance, and a CFO grade bridge from identified opportunity to realizable EBITDA. It is a paid diagnostic, deliberately, because it is rigorous enough to support an investment decision, not a proposal exercise. From there, a full transformation typically runs 12 to 16 weeks, and it is structured so the pilot proves the economics on real transactions before anything rolls out broadly, which means the first verified margin capture usually lands inside the first 60 to 90 days rather than at the end. The honest variable is your data. If you can produce 12 to 24 months of line item transaction history with cost, customer, product, and seller fields, the clock starts immediately. If you cannot, that is a finding in itself, and we will tell you before you spend anything.