Ask a B2B SaaS company who owns pricing and watch the room go quiet.

Sales will say Product sets the prices. Product will say Finance approved the model. Finance will say Sales negotiates the actual number. And RevOps will tell you they just build the CPQ fields.

Pricing is the highest-leverage revenue variable in most companies, and it almost never has a clear owner.

That is not an oversight. It is a structural failure. And it is one of the most expensive ones I see inside scaling companies because the damage compounds silently, one deal at a time, until someone finally runs the analysis and realises that effective ASP has dropped 18% in two quarters without a single pricing change on the rate card.

Why Pricing Has No Owner

Pricing sits at the intersection of three functions that rarely collaborate well.

Sales views pricing as a negotiation tool. Their primary concern is deal velocity and close rate. A discount is a lever they pull to reduce friction, and they will always want more room to pull it.

Finance views pricing as a margin variable. Their concern is unit economics, revenue quality, and predictability. They want guardrails, approvals, and controls. They want fewer exceptions.

Product views pricing as a packaging decision. They care about how pricing maps to value, how tiers work, and how feature gating aligns with market segments. They want simplicity and logical structure.

Each function has a legitimate perspective. None of them has a complete one. And because pricing requires all three perspectives to work, it defaults to nobody’s core responsibility.

What fills the gap is usually informal process. A Slack thread to the VP of Sales for approval on a non-standard discount. A spreadsheet that someone in Finance maintains with “approved” pricing exceptions. A Confluence page from two years ago that describes a discount matrix nobody follows.

This is not governance. This is institutional memory masquerading as process.

The Discount Spiral: How One Exception Becomes Policy

I have seen this pattern at every company that lacks pricing governance. It always follows the same arc.

A strategic deal comes in. The prospect is a recognisable logo. Sales asks for a 30% discount, well above the standard 15% threshold. The deal gets approved because the logo matters, the quarter is tight, and everyone agrees it is a one-time exception.

Except it is never a one-time exception.

The rep who closed that deal tells the team about the discount they got approved. Another rep references it on their next deal. A manager uses it as precedent to justify a similar ask. Within 90 days, what was an exception has become an expectation.

Every discount without governance becomes a precedent. Every precedent becomes a norm. Every norm erodes margin.

This is the same dynamic I wrote about in the hidden cost of revenue exceptions. The mechanism is identical. The difference with pricing is that the financial impact is immediate and measurable, yet somehow still invisible until someone does the forensic work.

The reason it stays invisible is that most companies track bookings and ARR, not effective discount rate by segment, by rep, by deal size. Without that instrumentation, margin erosion hides inside topline numbers that still look healthy.

The Three Failure Modes

In my experience, pricing governance breaks in one of three ways. Most companies are living inside one of these modes right now.

Failure Mode 1: Too Loose

This is the most common pattern in growth-stage companies. There is either no approval process or the process is so informal that it functions as a rubber stamp. Reps discount freely. Managers approve without scrutiny. Finance sees the numbers after the deal is closed.

The symptoms: ASP declining quarter over quarter. Wide variance in discount rates across reps. Deals that look great on bookings but terrible on unit economics. Customer Success inheriting contracts priced so aggressively that the account is underwater from day one.

When every rep can set their own price, you do not have a pricing strategy. You have a negotiation culture.

Failure Mode 2: Too Rigid

This is the overcorrection. Leadership sees margin erosion, panics, and locks down pricing with hard approval gates. Every discount above 5% requires VP sign-off. Every non-standard term needs legal review. The CPQ system enforces rigid rules with no override path.

The symptoms: deal velocity collapses. Sales cycle length increases. Reps spend more time navigating internal approvals than selling. Good deals die because the approval process took longer than the prospect’s patience. The best reps leave for companies where they can actually close business.

Rigidity is not governance. It is a different kind of failure, one that makes misalignment feel intentional.

Failure Mode 3: No System At All

This is where most Series A and B companies live. Pricing exists on a slide deck. Discounting is handled conversationally. There is no CPQ, no approval workflow, no tracking. The CEO approves big discounts over lunch. Finance reconciles pricing after contracts are signed.

The symptoms: no two deals are priced the same way. Nobody can explain the discount logic for any given account. Renewal pricing is a negotiation from scratch because nobody documented what was agreed the first time. Revenue forecasting is guesswork because the inputs are unreliable.

What Pricing Governance Architecture Actually Looks Like

Governance is not a policy document. It is an operational system with four components.

First: a pricing framework. This is the source of truth for how your product is priced. Not a rate card, a framework. It defines tiers, packaging logic, discount bands by segment, and the rationale for each. It is maintained by Product and Finance jointly. It is versioned. It is accessible.

Second: approval workflows with tiered authority. Not every discount needs the same level of scrutiny. A 10% discount on a mid-market deal is different from a 40% discount on an enterprise contract. Governance architecture defines who can approve what, at what threshold, with what data required. These workflows live in your CPQ or deal desk tooling, not in Slack.

Third: instrumentation. You cannot govern what you cannot measure. Effective governance requires real-time visibility into discount rates by segment, by rep, by deal size, by quarter. It requires alerting when patterns deviate from norms. It requires dashboards that Finance and RevOps review weekly, not quarterly.

Fourth: enforcement. This is where most companies fail. They define the rules but do not enforce them. A pricing governance framework without enforcement is a suggestion. Enforcement means deals cannot progress past a certain stage without pricing approval. It means CPQ blocks non-compliant configurations. It means comp plans penalise excessive discounting instead of rewarding it.

Deal Desk as a Governance Mechanism

The most effective pricing governance I have seen operates through a well-designed deal desk function.

Deal desk is not an administrative bottleneck. It is a decision-support layer that sits between Sales and Finance. When designed correctly, it accelerates deals by removing ambiguity, not by adding gates.

A strong deal desk does three things. It validates that pricing complies with the framework before the deal reaches approval. It provides reps with pre-approved pricing options so they spend less time negotiating internally. And it captures structured data on every pricing decision so the organisation can learn from its own patterns.

The best deal desks I have worked with reduce average deal cycle time by 15-20% while simultaneously improving discount compliance. That is not a trade-off. That is what good operational design looks like.

The key is positioning deal desk as an enablement function, not a policing function. Reps should see deal desk as the fastest path to getting a deal approved, not the biggest obstacle. That requires investment in tooling, training, and a genuine feedback loop between deal desk and the field.

How AI Can Enforce Pricing Rules at Scale

This is where the conversation gets interesting.

Most pricing governance breaks down at scale because humans cannot review every deal with the same rigour. When you have 200 reps closing 500 deals a month, manual oversight becomes a sampling exercise at best. The deals that slip through are the ones that set the worst precedents.

AI changes the enforcement equation. Not AI as a buzzword. AI as a practical layer in your revenue operating model that does three specific things.

Pattern detection. An AI layer can flag when a rep’s discount behaviour deviates from segment norms. Not after the quarter closes, in real time. It can surface that a particular rep has averaged 28% discounts when the segment benchmark is 14% and route that insight to their manager before the next deal closes.

Compliance gating. AI can evaluate whether a proposed deal structure complies with pricing framework rules before it enters the approval queue. Non-compliant configurations get flagged with specific explanations of what needs to change. This is not about replacing human judgment. It is about ensuring that human judgment is applied to the right deals, not wasted on deals that should never have reached the queue.

Precedent analysis. This is the most underutilised capability. AI can analyse historical pricing decisions and surface when a current request would create a precedent that conflicts with stated pricing strategy. It can quantify the downstream margin impact of approving a specific exception. That context turns a gut-feel approval into an informed decision.

The trap is buying AI wrappers that promise pricing intelligence without integrating into your actual deal flow. The value is not in the model. It is in the workflow integration that makes governance automatic rather than aspirational.

Why Finance and RevOps Must Co-Own Pricing

Here is the structural fix.

Pricing governance cannot live in Sales. Sales has an inherent conflict of interest. They are measured on bookings, not margin. Asking Sales to self-govern pricing is like asking the offence to call their own penalties.

Pricing governance cannot live solely in Finance. Finance lacks proximity to deal dynamics. They do not see the competitive pressure, the buyer behaviour, or the tactical reality of closing a deal at quarter end. Pure Finance governance produces the rigidity failure mode.

Pricing governance belongs to a joint function between Finance and RevOps, with clear input channels from Sales and Product.

Finance brings the economic framework. What margins are acceptable. What discount bands protect unit economics. What pricing changes affect LTV/CAC ratios and revenue quality.

RevOps brings the operational architecture. How rules get encoded into CPQ. How approval workflows are designed and enforced. How data flows from deal execution back into pricing analytics. How governance integrates with the broader revenue architecture.

Together, they create a system where Sales has clear rules and fast paths to approval. Product has confidence that packaging logic is respected in the field. Leadership has visibility into pricing as a managed variable, not an uncontrolled one.

This is not a committee. It is a shared operating responsibility with distinct roles. Finance sets the boundaries. RevOps builds and enforces the system. Both report on pricing health to leadership as a standing agenda item, not a quarterly post-mortem.

Pricing Is a System, Not a Spreadsheet

The companies that scale margin alongside revenue are the ones that treat pricing as a governed system.

Not a rate card pinned to a Confluence page. Not an informal approval chain that depends on who you know. Not a set of rules that get bypassed whenever the deal is big enough.

A system. With ownership. With rules. With instrumentation. With enforcement.

Every company I have worked with that implemented real pricing governance found margin they did not know they were losing. Not because they raised prices. Because they stopped giving away margin through untracked, ungoverned, well-intentioned exceptions.

The discount you approve today without governance is the precedent your team will reference for the next twelve months. That is not a risk. That is a certainty.

The question is whether your company designs for it or discovers it in the post-mortem.