Sales teams are designed to win business. Pricing is designed to protect the business. When the same people are responsible for both, without structural constraints, the plant pays for it later — through margin leakage, unstable demand signals, and commercial relationships built on informal terms that no one can now unwind. This is not an indictment of sales teams. It is a description of what happens when a structural problem is solved with a people solution. Asking sales reps to balance win rates and margin protection simultaneously, without systems to support either, is asking them to optimise two conflicting variables with no feedback on how they are performing on either. The solution is not to remove pricing authority from sales teams. It is to give them a system that calculates the right price automatically, routes exceptions to the appropriate authority, and provides margin visibility at the point of quote so that commercial decisions are made with full information rather than estimation. --- Why Pricing Decisions Should Not Live in Rep Judgment The case for moving pricing decisions into systems is not ideological — it is practical. It is based on what rep-level pricing judgment produces at scale and over time. Approach Price Source Margin Outcome Audit Capability Rep judgment Memory, old quotes, customer pressure Inconsistent — varies by rep and deal None — no record of basis Approval-based Rep proposes, manager approves Better — but dependent on manager context Partial — approval recorded, basis not System-configured Rules applied from validated data Consistent — same inputs produce same output Full — every price traced to its rule Rep-level pricing judgment produces inconsistent outcomes not because reps make bad decisions but because they make decisions with different information, under different pressures, and against different customer relationships. The rep who has managed an account for three years knows its pricing history. The rep covering for them does not. The price offered in their absence reflects the coverage rep's knowledge, not the account's commercial history. This inconsistency compounds. Over a year, the same product may be sold to the same customer at five different prices by the same rep, each one a reasonable response to the specific commercial situation at the time, and together producing a pricing history that the customer can use to negotiate every future deal by cherry-picking the lowest rate as their reference. --- What a System-Configured Pricing Model Looks Like A system-configured pricing model does not remove sales judgment from the commercial process. It channels it appropriately. The system handles the routine: calculating the right price based on validated inputs, applying approved discount parameters, enforcing margin floors, and generating a quote that the rep can review and send. The rep handles the exceptional: situations where the standard parameters do not apply, where competitive pressure justifies a below-standard price, or where a strategic relationship warrants treatment that differs from the norm. These situations are routed through an approval workflow that provides the approver with the context needed to make a good decision. The customer's margin history, the competitive rationale, the margin impact This division of labour — system for routine, workflow for exceptional — is not only more consistent than pure rep judgment. It is also faster for the rep in routine situations, because the price is calculated automatically rather than requiring manual estimation and informal approval. --- The Three Capabilities That Pricing Systems Must Have Not all pricing systems deliver the benefits described above. The capabilities that determine whether a pricing system actually shifts decision quality — rather than just digitising the existing process — are specific. Live cost integration. A pricing system that calculates prices from a cost base that is updated quarterly is no more accurate than a spreadsheet-based process. The system must be connected to current cost data. Live ingredient costs, current freight rates, actual overhead absorption Configured rule sets that reflect actual commercial logic. The pricing rules in the system must reflect the actual commercial policy of the business. Not a simplified version of it. Customer tier definitions must reflect how customers are actually segmented. Volume break thresholds must reflect the economics of scale that actually apply at different order sizes. Regional rate variations must reflect genuine market differences rather than arbitrary geographic boundaries. Margin visibility at the point of quote. The single most important feature of a pricing and promotion management system for changing sales behaviour is showing the rep the margin at the point of quote. Not after approval. Not in a monthly report. At the moment the price is being set. When reps can see that a 10% discount on this SKU takes the deal below the margin floor, and can see the specific margin impact in pounds and percentage, the commercial conversation with the customer changes. --- The Transition: From Rep Judgment to Configured Rules The transition from rep-level pricing judgment to system-configured rules does not happen overnight, and forcing it too fast creates resistance that undermines adoption. The practical sequence begins with visibility rather than control. In the first phase, the pricing system is deployed in advisory mode: it shows reps the configured price and the margin, but does not prevent them from overriding it. This phase generates the data that reveals where rep judgment diverges from the configured rules. And whether that divergence is systematically upward (reps pricing above the configured rate) or downward (reps pricing below it). In the second phase, soft guardrails are added: the system requires a documented justification for any price below the configured rate, but does not block the transaction. The justification requirement alone. The act of having to state why a below-rate price is appropriate In the third phase, hard floors are enforced: prices below the margin minimum require formal approval through the configured workflow. Prices within the approved range process automatically. The rep's role in routine pricing is to review the system-generated price and send the quote, not to calculate the price themselves.