RevOps playbook · AI Employee: Rev

Custom Pricing & CPQ Exception

Exception quotes turned around in 24h

Install this playbookBack to marketplace
The problem

Custom pricing requests are the enterprise-deal-specific work that grinds sales cycles. Customer wants ELA (Enterprise License Agreement), tiered volume commit, custom SKU bundle, deferred payment structure, revenue share — each requires deal desk + finance + legal review, custom quote build outside CPQ standard flow, and multiple approval rounds. Weeks lost per deal; enterprise close rates suffer.

At a glance
Trigger
Form
Approvals
Deal desk + finance approval
What it does
Writes to your systems
Systems
Salesforce CPQ · Deal desk · Slack
How it feels in production

An hour-by-hour walkthrough.

AE Kiran works a large enterprise deal that needs custom pricing structure. Rev picks up the pattern (deal >$500K ACV + non-standard structure request) and orchestrates: **Draft the deal desk brief** - Customer: Acme Global, $2.4M ACV, 3-year commit - Ask: tiered volume pricing (5000 seats year 1, ramping to 15000 by year 3), custom bundle (their existing + our new AI product), 45-day payment terms - Precedent: 3 similar-shape deals in past 18 months (details attached) - Financial impact: ARR $2.4M, TCV $8.2M, discount blended 24% - Recommended structure: base tier + step-up commits, single SKU with bundle pricing, 45-day terms with early-pay 2% discount option **Route through approval chain** - Deal desk review (structure + pricing sanity) - Finance review (revenue recognition + payment terms) - Legal review (custom terms language) - Executive sponsor (VP Sales or CRO based on size) Each approver sees the deal desk brief with their scope highlighted. Approvals in 24-48 hours instead of weeks. **Build the custom quote in CPQ** - Custom SKU for the bundle - Tiered pricing configured - Custom payment terms applied - Order form generated Enterprise close velocity restored. Custom-pricing capability without the weeks-of-friction tax.
How it works

Step by step.

  1. 01

    Detect custom-pricing request

    Deal size + non-standard structure signals. Auto-routed to deal desk track vs. standard CPQ path.

    Salesforce · Deal desk workflow
  2. 02

    Draft deal desk brief with structure recommendation

    Customer context, ask, precedent, financial impact, recommended structure. Ready for reviewer decisions.

    Deal desk template · Historical deal data
  3. 03

    Route through parallel approval chain

    Deal desk + finance + legal + executive in parallel where possible. Each sees their scope.

    Approval flow · Multi-approver routing
  4. 04

    Build custom CPQ configuration

    Custom SKU + tiered pricing + custom terms. CPQ configuration for the specific deal.

    Salesforce CPQ · Custom configuration
  5. 05

    Track outcome for future precedent

    Deal close outcome + policy learnings. Future similar deals benefit from precedent.

    Analytics · Precedent library
Systems and wiring

What you connect to make this run.

Salesforce CPQ · DealHub · Conga

read+write

CPQ platform for custom configuration. Custom SKUs + non-standard pricing structures.

Deal desk workflow

read+write

Deal desk review + coordination across finance + legal + executive.

Snowflake · Historical deal data

read

Precedent analysis for similar-shape deals. Structure recommendations grounded in historical outcomes.

Slack · Teams · Approval flow

read+write

Multi-approver coordination + AE + deal desk communication.

What changes

Before and after, honestly.

Time from custom-pricing ask to approved structure
Before
3-8 weeks
After
3-7 business days
AE hours per custom-pricing deal
Before
20-50 hours (chasing approvals)
After
3-8 hours
Enterprise close rate on custom deals
Before
45-65%
After
65-85%
Deal desk hours per custom deal
Before
10-25 hours
After
3-6 hours
Related

Playbooks that pair with this one.

RevOps

Discount Approval Routing

Custom-pricing includes discount logic; approval routing coordinated.

RevOps

CPQ Quote Error Triage

Custom quotes may hit CPQ edge cases; unified troubleshooting.

RevOps

Non-Standard MSA & Redlines

Custom pricing often accompanies custom contract terms.

Frequently asked

Answers about this playbook.

What about deal-specific SKU creation vs. reusable custom SKUs?

Reusable custom SKUs preferred (multiple deals can use). Deal-specific only when truly unique structure not repeatable.

How does it handle usage-based pricing structures?

Usage-based pricing supported with meter definitions + billing integration. More complex than fixed pricing; standardized meter definitions help.

What about revenue recognition complexity for custom structures?

Finance review specifically for rev-rec implications. Some structures (ELA, multi-year prepay) affect recognition schedules; captured in approval.

Can custom pricing become standard offering?

Yes — recurring custom-pricing patterns feed product-marketing consideration for standard offering. Reduces custom work over time.

How does this interact with product-led-growth pricing?

PLG pricing typically standard; custom pricing usually for enterprise sales-led motion. Different flows; both supported.

See it run on your data.

Free plan, no credit card. Connect the systems this playbook needs and run it against a past event first.

Book a demoMore RevOps playbooks