If your founder isn't actively selling but still wants pricing oversight, should CPQ governance shift entirely to a formal deal desk, or is there a hybrid model that keeps founder visibility without slowing down deal velocity in 2027?

The outcome you should expect

The founder who says "I'm not selling anymore, but I still want pricing oversight" is expressing three separate anxieties that get incorrectly collapsed into one request. The first is margin protection — a fear that without them in the path, discounting drifts and the company trains its own market to expect thirty-five percent off list. The second is precedent control — the fear that one rep hands a strategic logo a most-favored-nation clause, an uncapped price lock, or a perpetual grandfather term that quietly becomes the template every future prospect cites in negotiation. The third is strategic-account judgment — the usually-correct belief that the founder still holds irreplaceable context about which five or ten accounts justify bending the model for brand, reference value, or a platform bet.

None of those three anxieties require the founder to approve the seventy percent of deals that are entirely standard. They require a *system* that protects margin, a *gate* that catches precedent, and a *narrow lane* for genuine strategy. The deal-desk-versus-founder framing is a false binary, and the correct unit of analysis is decision rights: which approvals move to automation, which move to a desk, and which stay — in a deliberately constrained shape — with the founder.

What you should expect from a well-built hybrid is a specific set of outcomes, and they are worth stating up front because they are the argument you will make to a skeptical founder. Median approval cycle time typically drops twenty to forty percent, because the majority of deals stop waiting on any human at all. Overall sales cycle time improves eight to fifteen percent, since approval delay compounds into every downstream step — legal review, security questionnaire, signature scheduling. Discount leakage tends to fall two hundred to five hundred basis points within two quarters, and the mechanism is counterintuitive: the improvement comes less from tighter rules than from eliminating the inconsistency of a founder approving deals emotionally between board meetings. Founder time on deals collapses from three to eight hours per week to roughly twenty to forty minutes.

The outcome that surprises founders most is that they end up feeling *more* informed, not less. Per-deal approval only ever shows a founder the deals that happened to route to them, one at a time, with no aggregate view. A weekly pricing scorecard shows discount distribution, band mix, leakage trend, and precedent watch across everything — direct, channel, renewal, expansion. Founders who make this shift routinely discover a discounting pattern in one segment they could never see deal by deal, and fix it with a single rate-card change worth more than a year of individual approvals.

There is a second-order outcome worth naming: the organization de-risks itself. A founder-as-approver company has a single point of failure. The founder takes a two-week vacation, gets absorbed in a fundraise, or gets sick, and the pipeline freezes at the approval step. The hybrid removes that fragility, and it also builds pricing judgment in the sales management layer, which never develops when there is a founder backstop absorbing every hard call.

What drives that outcome

The mechanism is a three-band approval matrix, and getting the band definitions right is roughly eighty percent of the design. Everything else — briefs, SLAs, scorecards, tooling — is scaffolding around this core.

Band 1, standard and auto-approved. Definition: list price or a pre-approved rate card, discount at or below a hard ceiling (commonly fifteen percent, sometimes ten for high-margin software, twenty in competitive low-margin segments), standard contract length, standard payment terms, no non-standard legal clauses, deal size below a routine threshold. Band 1 should auto-approve inside CPQ with zero human touch and cover sixty to seventy-two percent of deals by count. Requiring a human to look at a clean, standard, in-policy deal is pure waste — it is the approval equivalent of having someone sign off on a correctly-filled expense report.

Band 2, managed by the deal desk. Definition: discount between the Band 1 ceiling and a strategic ceiling, modest deviations on term length or payment timing, a single non-standard but pre-vetted clause, deal size in a mid-range. Band 2 routes to the desk with a published SLA — four business hours or same day. The desk works from a written playbook, which is what makes its decisions consistent and fast rather than a matter of who happens to be reviewing.

Band 3, strategic and founder-owned. Definition: discount above the strategic ceiling, multi-year structures with free periods, any genuinely custom legal term, deal size above a material ARR threshold, or — the most important trigger — any deal that would set a new pricing precedent regardless of size. Band 3 routes to the founder, asynchronously only, with a twenty-four-hour SLA and a deal-desk-prepared brief.

Calibrating the thresholds is where most designs go wrong, in either direction. Too loose and Band 3 catches nothing meaningful; too tight and the founder is drowning again within a quarter. Pull the discount distribution for the last two quarters and find the median plus the seventy-fifth and ninetieth percentiles. A defensible structure sets the Band 1 ceiling near the sixtieth to sixty-fifth percentile of historical discounts, so the majority of normal deals auto-approve, and the Band 2/Band 3 boundary near the eighty-eighth to ninety-second percentile, so the founder sees only the genuine tail. If your historical median is twelve percent, your seventy-fifth is nineteen, and your ninetieth is thirty-one, then a fifteen/thirty split is well-calibrated. For the ARR trigger, use two to four times average ACV. For precedent triggers, the threshold is binary rather than numeric: any clause off the pre-approved list, any pricing structure never used before, anything creating an MFN or price-lock obligation.

The second driver is what the founder actually *does* in Band 3, and naming it explicitly is what makes the reduced role feel like a promotion rather than a demotion. The founder is not checking arithmetic — CPQ did the math and the desk validated the structure. The founder does three things. Precedent judgment: will this term, if it becomes the template, be acceptable? A forty-five percent discount to a logo that will never be referenceable is a margin leak; the same discount to a brand-name lighthouse account is a marketing investment, and only someone who owns the go-to-market strategy reliably distinguishes them. Strategic-account context: the founder knows things absent from the CRM — that this prospect's CEO sits on the board of three target accounts, that this segment is a deliberate land grab. Model-evolution signal: when the same exception appears repeatedly in Band 3, that is the cue to change the rate card, not to approve one more time. A quarter of Band 3 reviews should produce a short list of things the pricing model ought to do natively.

The third driver is async-by-default, and it is the single design choice that determines whether the hybrid preserves velocity or quietly destroys it. A live approval meeting, even a five-minute one, requires calendar coordination with a founder who is fundraising and hiring — that is where deals die. Instead, the desk produces a one-page brief and posts it to a dedicated channel the founder checks at fixed times daily. The founder responds approve, reject, or approve-with-condition, in writing, within twenty-four hours. The asymmetry is powerful: the founder batches every Band 3 deal into one twenty-minute window on their own schedule, while reps get a hard SLA they can promise a customer. The written trail compounds into policy. The only carve-out is a rarely-used escalation path for a genuinely time-boxed situation — a competitor offer expiring, a quarter-end signature window — that reps know exists but find socially expensive to invoke.

The brief itself is the artifact most companies skip, and skipping it is fatal: without it the founder either approves blind, defeating the oversight, or digs through the CRM, defeating the velocity. Fix the template so the founder builds pattern recognition. It carries the ask in one sentence, the deal context including the competitor and why the discount is requested, an explicit precedent flag ("this would be our first sub-threshold enterprise deal" or "matches the structure approved for Account X"), the economics — effective ARR, blended margin, payback, comparison to segment norms — the desk's own recommendation, and the single strategic question only the founder can answer. That structure converts founder approval from a thirty-minute archaeology dig into a ninety-second judgment call, and preparing it forces the desk to think, which is itself a quality gate.

Benchmarks and realistic ranges

Concrete targets keep the design honest and give you something to audit against at the two-quarter mark.

Band mix. Band 1 sixty to seventy-two percent of deals by count, Band 2 eighteen to twenty-eight percent, Band 3 eight to fifteen percent. Band 3 will represent a much larger share of ARR — commonly forty-five to sixty percent — which is exactly the point: the founder touches few deals but most dollars. If Band 3 exceeds roughly fifteen percent by count, your thresholds are miscalibrated or reps are structuring deals to escape the desk.

Cycle time. Band 1 instant. Band 2 median under four business hours with a p90 under one business day. Band 3 median under twelve hours, p90 under twenty-four. Track p90 rather than median as the operational number, because reps plan customer commitments around the worst case, not the typical case.

Staffing. Roughly one deal desk FTE per eight to fifteen million in ARR. Below about ten million this is almost always fractional — a RevOps generalist at forty to sixty percent allocation, or a senior sales ops analyst growing into the role. The first dedicated hire typically lands between ten and twenty-five million ARR.

Discipline metrics. Discount leakage down two to five hundred basis points within two quarters. Just as important, discount *variance* down — the standard deviation on similar-profile deals should shrink measurably, since consistency was half the objective. Band 2 playbook exception rate healthy at five to twelve percent; near zero means the desk is rubber-stamping or the playbook is too permissive, well above twelve means the playbook is too rigid and needs rewriting.

Founder metrics. Twenty to forty minutes per week total, split between a daily async batch and the weekly scorecard. Founder override rate on Band 2 deals near zero. Founder SLA compliance above ninety percent — a founder who blows their own published SLA destroys the system's credibility faster than any other single failure.

These are starting reference points rather than universal laws. A high-velocity, low-ACV business will land at the aggressive end of Band 1 coverage; a six-figure-ACV enterprise business will run a smaller Band 1 and a larger founder surface, appropriately. The useful discipline is that a hybrid landing wildly outside these ranges needs a design review, not a rationalization.

Governance evolves with stage, and knowing the trajectory helps you build the next version rather than just the current one. Below roughly three million ARR the founder *is* the deal desk, and that is correct — there is not enough volume to justify a function, and the founder still holds the most market context. The only move at that stage is instrumentation: start capturing approval timestamps and discount data so the eventual transition is data-driven rather than argumentative. From three to ten million, bottleneck pain begins; stand up a fractional desk, codify the matrix, move the founder to async Band 3. From ten to twenty-five million, hire a dedicated desk, ratchet the bands upward, and let a VP Sales or CRO absorb some of what the founder held. From twenty-five to seventy-five million the desk becomes a team of two to five and pricing strategy moves to a pricing function. Above that, a formal deal desk organization and pricing committee govern, and the CEO is out of individual approvals entirely. The invariant across all of it: the founder's surface should shrink monotonically at every stage. If it is not shrinking, governance is not evolving and the next bottleneck is already forming.

Diagnostics for whether you have a problem yet. Before designing anything, run five checks. Pull approval-requested-to-granted timestamps across the last sixty deals; a founder-touched median over twenty-four hours or a p90 over seventy-two indicates a bottleneck. Count monthly deal volume; below fifteen to twenty a founder can plausibly stay close, above thirty to forty it is mathematically untenable. Measure founder calendar load; more than two to three hours weekly on approvals carries a brutal opportunity cost. Check discount variance on similar-profile deals; high dispersion means founder involvement is adding noise, not control. Finally, observe rep behavior — sandbagging asks, timing requests around the founder's mood, or routing to a friendlier VP all mean the process is already broken. Fail two or more and you need the hybrid now.

Risks, edge cases, and failure modes

Hybrids fail in recognizable, recurring ways, and each failure has a signature visible on the scorecard before it becomes cultural.

Band 3 creep. Over two quarters, the founder's share drifts from twelve percent to twenty-five. Either thresholds were never re-calibrated as the business matured, or reps are deliberately structuring deals to escalate past a desk they find stricter than the founder. The diagnostic that separates these: audit whether the founder is approving Band 3 deals the desk would have rejected. If yes, the founder is the leak.

The rubber-stamp desk. Exception rate near zero and leakage flat. Almost always a comp or reporting-line problem — a desk carrying variable comp tied to closed deals will approve freely, and a desk reporting into the VP Sales is structurally compromised because the VP is paid to close and the desk's job is sometimes to say no. The desk belongs under RevOps and should be paid on base plus process metrics: SLA compliance, leakage reduction, scorecard quality. Never on bookings.

The bureaucratic desk. High exception rate, low rep satisfaction, creative deal structures disappearing. The playbook is too rigid and the desk is rejecting things it should escalate. Retrain on the escalate-versus-reject distinction, which is the hardest judgment a desk makes.

The absentee founder. Band 3 p90 repeatedly blows past twenty-four hours. Either get a hard recommitment or remove the founder from the approval path entirely and go scorecard-only. A founder who wants the seat but not the SLA is worse than no founder in the path.

The shadow path. Reps get approvals by direct message, the official dashboards look clean, and they do not match reality. Make off-system approvals structurally impossible: a quote cannot move to closed-won without a logged in-system approval.

Scorecard theater. The founder reviews the weekly scorecard religiously and never changes policy based on it. Require every review to end with an explicit logged decision — policy change, threshold change, or no change.

The founder who intellectually agrees but emotionally cannot let go is the most common edge case and it is a behavioral problem, not a design problem. The symptom is a founder DMing reps, overriding the desk in Slack, and re-approving Band 2 deals the desk already handled — which teaches the org there are two approval paths and kills the desk's authority. The fix has three parts. Structural friction: every founder override logs in CPQ with a written rationale, which alone cuts casual overrides by making them visible, and the override rate appears on the founder's own scorecard. Reframing: the RevOps lead has to say, privately, that every override spends down the desk's authority and you will need that authority next quarter. And a legitimate outlet: let the founder designate three to five "strategic watch" accounts that route to them regardless of band. Channeling the attachment beats trying to eliminate it, and override rates typically fall from around twenty percent to under three within a quarter.

Motions other than new business are where governance quietly develops a hole. A matrix that governs only new logos leaves renewals, expansions, and save deals ungoverned, and that is exactly where leakage reaccumulates. A flat renewal at list or with a contractual escalator is Band 1. A renewal discounted *deeper* than the original deal is a precedent-setting event and belongs in Band 2 or Band 3 by magnitude, because re-discounting teaches your customer base to threaten churn for price. An expansion at the existing per-unit rate is Band 1, but an expansion that resets the entire contract to a new blended rate is a fresh pricing decision. Churn-risk save concessions are the most dangerous category — an account manager facing cancellation under time pressure will request steep terms, and if those route only to a sales manager they leak badly. A *pattern* of save concessions in one segment is a scorecard signal that the product or the original pricing is wrong, not a series of deals to approve one at a time.

Channel, international, and marketplace motions generalize the frame but require separate calibration. Regional Band 1 ceilings matter because a discount that is routine in one geography is a precedent-setter in another. Channel deals govern partner margin against a partner agreement rather than customer discount off a rate card, so the band logic is program-deviation-driven. Marketplace transactions carry the marketplace fee in their net economics and the bands must be set on net, not gross. Co-sell deals are often genuinely Band 3 by nature. The unifying discipline: every motion rolls up to one founder scorecard. A founder with tight direct-deal governance and no channel visibility does not have pricing oversight — they have partial oversight, which is more dangerous than none because it feels complete.

The enterprise objection — "every deal here is strategic, so the founder should see all of them" — is usually an illusion worth testing. Even at two-hundred-thousand-dollar average ACV and six to nine deals a month, most deals follow established patterns. The adaptation is to define Band 1 by *structure* rather than discount percentage: a deal on standard paper, standard term, and within-segment discount auto-approves even at high ACV. The bands shift from discount-magnitude-driven to structure-and-precedent-driven, the founder's surface lands higher than in a velocity business — perhaps twenty percent — and the three-band logic still holds.

The skipped-desk pattern deserves a specific warning, since it looks like the "shift entirely to a deal desk" answer done badly. A company moves from founder-led selling straight to "the VP Sales approves everything," and discounting creeps because the VP is paid on bookings. The founder senses drift and re-inserts, producing a chaotic three-way approval mess. The lesson is that a deal desk is not merely an approver — it is specifically a *neutral, non-bookings-paid* function, and skipping the neutrality is worse than having no desk at all.

A practical rollout plan

Stage the transition over roughly six months. Flipping from founder-on-everything to full hybrid overnight produces founder panic and rep confusion, and the panic is what causes the reversion.

Month zero to one — instrument and get buy-in. Change nothing operationally. Capture the baseline: approval cycle times by approver, discount distribution, founder hours on deals, and a modeled band mix showing what the matrix *would* have produced against the last two quarters. That model is your most persuasive artifact — it lets you tell the founder "you personally approved a hundred and forty deals last quarter, and a hundred and one of them were inside your own stated policy." Separately, secure the founder's explicit agreement on the underlying principle: decision rights versus visibility. Oversight in a scaled organization means you see everything, you set the rules, and you decide only the exceptions to your own rules. Without that agreement the rest is theater.

Month two to three — codify and stand up. Write the three-band matrix with data-calibrated thresholds, write the Band 2 playbook, build the brief template, configure the matrix in the CPQ tool, and stand up the (likely fractional) desk. Run it in parallel first: the desk shadows the founder's existing approvals for three to four weeks so you can compare decisions and tune the playbook against real disagreements. Every gap between what the desk would have done and what the founder did is playbook material.

Month three to four — shift Bands 1 and 2. Turn on Band 1 auto-approval first; it is the high-confidence win and delivers an immediate, visible velocity gain that buys political capital for the harder step. Move Band 2 fully to the desk with live, published SLAs. The founder still sees Band 3 synchronously and receives the first weekly scorecards.

Month four to six — shift the founder to async and scorecard. This is the genuinely hard part: moving the founder from synchronous approver to async-only Band 3 reviewer plus scorecard owner. Coach through the discomfort by pointing at the scorecard every week — the scorecard *is* the oversight now.

Month six onward — tune and ratchet. Re-calibrate thresholds quarterly with accumulated data. As the business matures, what was strategic becomes routine, and the bands should ratchet so the founder's surface keeps shrinking.

Implementation details that decide whether it holds. The matrix must live in the tooling, not a wiki page — a matrix documented in Confluence but not enforced in CPQ is a suggestion. In Salesforce CPQ, that means approval processes and rules where discount fields drive conditional routing, deal-size fields add parallel steps, and a precedent-flag checkbox (set by the rep or auto-set by a validation rule detecting non-standard clauses) forces Band 3 routing regardless of discount. Route via queues with alerting and escalation timers. Modern alternatives — DealHub, Subskribe, Conga — offer native approval-workflow builders that are generally faster to configure and easier to maintain. Choose the tool whose routing logic your team can actually maintain; an elaborate configuration only one departed admin understood is a liability.

Five configuration principles carry most of the weight. Auto-approval must be genuinely automatic, with no "approved" status that still requires a click. Matrix logic lives in the tool with change history, so quarterly re-calibration is a tracked config change. SLA timers and escalation are native, so an unactioned Band 2 deal auto-escalates and logs the breach. The precedent flag cannot be bypassed — it is the one control reps must not be able to route around. Every decision logs timestamp, approver, and a required rationale, which becomes both the audit trail and the raw material for the scorecard. Bad CPQ configuration is the most common practical reason hybrids fail: the policy is sound and the implementation leaks.

The weekly scorecard is the artifact that replaces per-deal approval, and it should take fifteen to twenty-five minutes. It carries discount distribution against a trailing thirteen-week average so drift is immediately visible; leakage in dollars and as a trend; band mix, watching for Band 1 shrinking or Band 3 growing; Band 2 exception rate; cycle time and p90 by band; SLA compliance for desk and founder both; the top five largest or most precedent-setting deals of the week by name; and a precedent watch listing any new term or structure introduced. The founder reads it, asks questions, and adjusts *policy*. The discipline that matters: the scorecard is for pattern detection and policy tuning, never for relitigating a closed deal. A founder who uses it to second-guess an approved deal has re-entered decision rights and broken the system.

What the founder must say, personally. This is an org-design change, and org-design changes fail when RevOps announces them instead of the founder owning them. Five statements, delivered by the founder, in all-hands, repeatedly. "I am not stepping back from pricing — I am stepping up to owning the system," because the org will otherwise read founder withdrawal as founder indifference to margin. "The deal desk speaks for me on Band 2," because without explicit air cover reps will test the desk, appeal past it, and the first casual founder override kills it. "Routing to the desk is not a failure — sandbagging and mis-flagging are." "Here is exactly what still comes to me, and why," which makes the remaining involvement read as deliberate strategy rather than incomplete delegation. And "here is how I will know things are going well," showing the org the scorecard, which signals oversight is real and merely relocated. The single most powerful signal available: being asked to intervene on a Band 2 deal and answering publicly, "that's the desk's call, and I trust it."

Where this goes. Expect AI to absorb much of Band 2 over the next several years — reading a quote, checking it against policy, flagging precedent risk, drafting an approve or reject with rationale, and routing only genuine judgment calls onward. The human desk shifts toward playbook authorship and exception handling rather than per-deal processing, and the brief becomes largely auto-assembled. The founder's Band 3 role is the most durable part of the system, because precedent judgment and strategic-account context require owning the business model and knowing things no system contains. The trajectory is not that the hybrid disappears — it intensifies, and the companies that instrument and codify now are the ones positioned to bolt automation onto a clean system rather than automating a mess.

Related questions

Should the deal desk report into Sales or RevOps?

RevOps, without exception. A desk reporting to the VP Sales is structurally compromised — the VP is compensated on bookings, and the desk's job is periodically to say no. RevOps ownership preserves neutrality, which is the entire source of the desk's credibility with both reps and the founder.

How should a deal desk be compensated?

Base plus a bonus tied to process metrics: SLA compliance, discount-leakage reduction, scorecard quality, playbook currency. Never on bookings or closed deals. Any variable comp tied to deals closing produces a rubber-stamp desk within two quarters, which is functionally the same as having no desk.

What if we have fewer than fifteen deals a month?

You can defer the full hybrid, but instrument now — capture approval timestamps and discount data from day one. The transition is dramatically easier to run proactively at fifteen deals a month than reactively at fifty, because you will already have the data to calibrate thresholds instead of arguing from intuition.

Does the same matrix govern renewals and expansions?

The same three-band frame applies, calibrated per motion. Flat renewals and same-rate expansions are Band 1. A renewal discounted deeper than the original, or an expansion resetting the whole contract to a lower blended rate, is a fresh pricing decision and routes to Band 2 or Band 3 by magnitude.

How often should thresholds be re-calibrated?

Quarterly. What was strategic at one stage becomes routine at the next, and static thresholds cause Band 3 creep — the founder's surface grows instead of shrinking. Treat re-calibration as a tracked configuration change with change history, not an informal adjustment someone makes in the tool.

FAQ

What percentage of deals should reach the founder?

Eight to fifteen percent by count is the healthy range for a direct-sales velocity business, representing perhaps forty-five to sixty percent of ARR. Enterprise-ACV companies with low deal volume can run higher, near twenty percent, because more deals genuinely involve novel structure. If your Band 3 exceeds fifteen percent in a velocity business, your thresholds are too tight or reps are structuring deals to escalate past the desk — audit both before assuming the volume is legitimate.

How do I convince a founder this isn't losing control?

Show them the modeled band mix against their own last two quarters of approvals. Most founders discover that eighty to ninety percent of what they personally approved was already inside their own stated policy — they were doing data entry, not governance. Then show them a sample weekly scorecard. Per-deal approval never gave them aggregate discount distribution, leakage trend, or variance by segment. The honest pitch is that this is the first real oversight they have ever had.

Can we skip the deal desk and let the VP Sales approve instead?

You can, and it reliably produces discount creep. A VP Sales paid on bookings has the wrong incentive for an approval role, and the founder eventually senses the drift and re-inserts chaotically, creating a three-way approval mess worse than either extreme. The desk's defining property is neutrality — a function not paid on closing — and skipping that property is worse than having no desk.

What if the founder keeps overriding the deal desk?

Treat it as a behavioral problem with a structural fix. Require every override to log a written rationale in CPQ, and put the founder's override rate on their own scorecard — visibility alone eliminates most casual overrides. Then give the attachment a legitimate outlet: let the founder name three to five strategic watch accounts that route to them regardless of band. Trying to eliminate the impulse fails; channeling it works.

How long does the full transition take?

Roughly six months done properly. Month zero to one instruments and secures founder buy-in on the principle. Months two and three codify the matrix, write the playbook, configure CPQ, and run the desk in parallel with the founder. Months three to four shift Bands 1 and 2. Months four to six move the founder to async-only plus scorecard. Rushing it produces reversion the first time a deal feels important.

How do we know it worked?

Judge at two quarters against six criteria: median approval cycle time down twenty to forty percent, discount leakage down two to five hundred basis points, discount variance narrowed, founder time down roughly eighty percent, band mix and SLA compliance inside target ranges, and — the qualitative test — the founder reports feeling more informed about pricing patterns than before. If velocity and leakage are both flat and the founder is still in deals, the matrix exists on paper and the real approval path never changed.

Sources

• https://hbr.org/2018/01/a-quick-guide-to-value-based-pricing
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales/our-insights/how-b2b-companies-can-win-with-pricing
• https://www.bain.com/insights/topics/pricing/
• https://www.salesforce.com/products/cpq/
• https://help.salesforce.com/s/articleView?id=sf.cpq_approvals_parent.htm&type=5
• https://www.gartner.com/en/sales/topics/sales-operations
• https://www.forrester.com/blogs/category/revenue-operations/
• https://openviewpartners.com/blog/
• https://www.pwc.com/us/en/services/consulting/business-transformation/library/pricing-strategy.html
• https://sloanreview.mit.edu/article/the-strategy-of-pricing/

Related on PULSE

• How do you structure a discount approval matrix in CPQ?
• When should a company hire its first dedicated deal desk?
• How do you measure and reduce discount leakage?
• Should RevOps or Sales own quote-to-cash governance?
• How do you transition out of founder-led sales without losing deals?
• What belongs on a weekly pricing scorecard?