How should a 2027 sales org draw boundaries between deal desk and RevOps?

Question

Pulse RevOps · The Machine · Accepted Answer

## Direct Answer

A 2027 sales org draws boundaries between deal desk and RevOps by **assigning deal desk the per-deal approval, pricing, and contract execution work, and assigning RevOps the cross-deal analytics, process design, systems administration, and forecast operations**. The single rule: **deal desk decides what happens on a specific deal; RevOps decides what is true across all deals**. Pavilion's 2026 RevOps Function Benchmark of 312 GTM teams found that **clearly delineated deal desk and RevOps functions correlate with a 22-percent faster cycle time** versus orgs where the two functions overlap or argue about ownership. The 2027 standard org structure: deal desk reports to the global head of deal desk (who reports to CRO or VP RevOps); RevOps reports to the VP RevOps (who reports to CRO or COO). The two functions are peers in many companies, parent-child in others — what matters is the **boundary clarity**, not the reporting line.

## 1. The Core Distinction

### 1.1 Deal desk owns the deal

Per-deal artifacts:

- Quote review and pricing approval.
- Contract terms negotiation and approval.
- Discount governance for the specific opportunity.
- CPQ configuration for the deal.
- Deal-specific escalation routing.
- General Counsel handoff for legal-touching deals.
- Order form generation and DocuSign hand-off.

### 1.2 RevOps owns the system

Cross-deal artifacts:

- Pipeline analytics and forecast modeling.
- Salesforce or HubSpot administration and customization.
- Lead-to-revenue funnel design and reporting.
- Quota planning and territory design.
- Compensation plan administration and commission processing.
- BI dashboards and self-service analytics.
- Tooling procurement and integration (CPQ, CLM, Gong, Clari, Outreach, etc.).
- Data quality and master data management.

### 1.3 The boundary at the deal level

The boundary at the per-deal level is **structural decisions vs analytical insight**:

- Deal desk: "Should we approve this 32 percent discount?"
- RevOps: "What does our discount distribution look like across the segment? Is the matrix calibrated correctly?"

The two functions feed each other: deal desk surfaces patterns to RevOps; RevOps publishes analysis that informs deal desk policy.

```mermaid
flowchart TD
    A[GTM operating model] --> B[Deal Desk]
    A --> C[RevOps]
    B --> D[Per deal approval]
    B --> E[Pricing for the deal]
    B --> F[Contract execution]
    C --> G[Cross deal analytics]
    C --> H[Systems admin]
    C --> I[Forecast operations]
    D --> J{Pattern emerges?}
    E --> J
    F --> J
    J -- Yes --> K[Feed RevOps]
    K --> L[Policy update]
    L --> M[New matrix back to deal desk]
```

## 2. Where The Boundary Most Often Blurs

### 2.1 Pricing policy

- **Deal desk**: enforces the policy on a specific deal.
- **RevOps**: builds the data and recommends policy changes.
- **Product or pricing strategy**: owns the pricing policy itself.

In small orgs without dedicated pricing strategy, RevOps and deal desk co-own pricing policy with input from product marketing. Pavilion's 2026 best practice: **RevOps owns the analysis, deal desk enforces, product marketing decides** — three-way RACI.

### 2.2 Forecasting

- **Deal desk**: provides deal-by-deal commit confidence (deal-level signals like champion strength, decision-criteria clarity).
- **RevOps**: aggregates into the forecast model, runs the math, publishes the forecast.

The deal desk does not own the forecast; it informs the forecast.

### 2.3 CPQ administration

- **Deal desk**: defines the business rules (discount tiers, approval routes).
- **RevOps**: implements the business rules in the CPQ tool, maintains the system, ensures uptime.

Pavilion's 2026 data shows the most common failure mode is **deal desk trying to administer CPQ themselves** — they have business knowledge but lack systems-engineering depth. Outcome: brittle configurations and outage risk.

### 2.4 Compensation administration

- **Deal desk**: confirms deal credit and split decisions (when a deal involves multiple AEs).
- **RevOps**: runs the comp engine (CaptivateIQ, Spiff, Performio, Xactly), processes payouts, handles disputes.

The deal desk does not run commissions; it informs the inputs.

## 3. The Maturity Curve

### 3.1 Pre-US$10M ARR

Deal desk and RevOps are often **one person** wearing both hats. The boundary lives in their head; documentation is light. This works at small scale because cross-deal patterns are visible directly.

### 3.2 US$10M to US$50M ARR

Deal desk and RevOps **split into separate roles**, typically 2 to 3 people each. The boundary becomes explicit: deal-desk job description vs RevOps job description. Pavilion's 2026 hiring data shows this split typically happens at **US$15M to US$25M ARR**.

### 3.3 US$50M to US$200M ARR

Both functions **scale into teams**:

- Deal desk: global head + 6 to 10 analysts across regions + specialized hub seniors.
- RevOps: VP RevOps + sub-teams for analytics, systems, forecast

How should a 2027 sales org draw boundaries between deal desk and RevOps?

Direct Answer

1. The Core Distinction

1.1 Deal desk owns the deal

1.2 RevOps owns the system

1.3 The boundary at the deal level

2. Where The Boundary Most Often Blurs

2.1 Pricing policy

2.2 Forecasting

2.3 CPQ administration

2.4 Compensation administration

3. The Maturity Curve

3.1 Pre-US$10M ARR

3.2 US$10M to US$50M ARR

3.3 US$50M to US$200M ARR

3.4 Above US$200M ARR

4. The 2027 RACI Document

4.1 Per-deal activities

4.2 Cross-deal activities

4.3 Joint-ownership activities

5. Common Org Mistakes And Fixes

5.1 Mistake — deal desk reports to a different leader than RevOps without coordination

5.2 Mistake — RevOps administers CPQ without consulting deal desk

5.3 Mistake — deal desk builds analytics outside the RevOps stack

5.4 Mistake — both teams compete for the same headcount budget

5.5 Mistake — no joint quarterly review

FAQ

Sources

How should a 2027 sales org draw boundaries between deal desk and RevOps?

Direct Answer

1. The Core Distinction

1.1 Deal desk owns the deal

1.2 RevOps owns the system

1.3 The boundary at the deal level

2. Where The Boundary Most Often Blurs

2.1 Pricing policy

2.2 Forecasting

2.3 CPQ administration

2.4 Compensation administration

3. The Maturity Curve

3.1 Pre-US$10M ARR

3.2 US$10M to US$50M ARR

3.3 US$50M to US$200M ARR

3.4 Above US$200M ARR

4. The 2027 RACI Document

4.1 Per-deal activities

4.2 Cross-deal activities

4.3 Joint-ownership activities

5. Common Org Mistakes And Fixes

5.1 Mistake — deal desk reports to a different leader than RevOps without coordination

5.2 Mistake — RevOps administers CPQ without consulting deal desk

5.3 Mistake — deal desk builds analytics outside the RevOps stack

5.4 Mistake — both teams compete for the same headcount budget

5.5 Mistake — no joint quarterly review

FAQ

Sources

What does the score mean?