← All guides

How to Plan a Revenue Operations Overhaul

Plan a revenue operations overhaul with a project timeline covering tech stack audit, process redesign, CRM optimization, and cross-functional alignment.

How to Plan a Revenue Operations Overhaul

RevOps Overhauls Fail When They Start With Technology

The most common RevOps failure pattern: the company buys a new CRM, spends six months migrating data, and discovers that pipeline management is still inconsistent, forecasting is still unreliable, and sales reps still hate the tool. The technology changed; the process didn't.

Effective RevOps transformation starts with process and data — not the CRM. The tool serves the process. If you don't know what stage criteria define a Commit deal versus an Upside deal, no CRM configuration will make your forecast accurate. Fix the process definitions first, then configure the technology to enforce them.

Here's how to structure the project.

Phase 1: Revenue Diagnostic (Weeks 1–3)

Establish a data-driven baseline before recommending any changes.

Pipeline metrics:

  • Pipeline coverage ratio by quarter: pipeline ÷ quota. Healthy is typically 3–4x.
  • Win rate by pipeline stage: what % of opportunities that reach Stage 3 eventually close?
  • Average sales cycle length by segment and deal size
  • Stage conversion rates: what % of Stage 1 opportunities advance to Stage 2, 3, etc.?

Revenue efficiency metrics:

  • Customer Acquisition Cost (CAC) by channel and segment
  • CAC payback period: CAC ÷ (ACV × gross margin)
  • Lead-to-close conversion rate by source
  • Net Revenue Retention (NRR) and Gross Revenue Retention (GRR) by cohort

Process metrics:

  • Lead response time: median time from lead creation to first sales contact
  • SDR-to-AE handoff conversion rate
  • Forecast accuracy: actual vs. committed forecast at quarter close
  • Deal slip rate: % of deals that slide from one quarter to the next

These metrics establish the baseline and reveal where to focus. A pipeline coverage problem and a win rate problem require completely different interventions.

Phase 2: Process Mapping and Gap Analysis (Weeks 3–5)

Map the current lead-to-cash process end-to-end with specific attention to handoffs.

Handoff points to examine:

  • Marketing → SDR: what defines a Marketing Qualified Lead? What triggers SDR outreach? What does the SDR do if the MQL doesn't respond?
  • SDR → AE: what defines a Sales Qualified Opportunity? What information must the SDR pass? How is the meeting booked?
  • AE → Close: how is the deal progressed? What are the stage exit criteria (not definitions — exit criteria)?
  • Close → CS: what triggers customer success handoff? What information does CS receive?

Sales process audit:

  • Document current stage definitions
  • Identify whether stage definitions are consistently applied across reps (check CRM data: are all Stage 4 deals actually at the same point in the sales process?)
  • Document current forecasting methodology: how do managers translate pipeline to a quarterly number?

Compensation plan review:

  • Does the comp plan incentivize the right behaviors? (If AEs are paid on bookings, they may sandbag; if CSMs are paid on expansion, they may over-promise at renewal)
  • How are commission disputes resolved? How often do they occur?

Phase 3: Tech Stack Audit (Weeks 4–6)

Map every revenue tool and how data flows between them.

Tools to audit:

  • CRM: Salesforce, HubSpot, Pipedrive
  • Marketing automation: Marketo, HubSpot Marketing, Pardot
  • Sales engagement: Outreach, Salesloft, Apollo
  • Revenue intelligence: Gong, Chorus, Clari
  • Customer success: Gainsight, ChurnZero, Totango
  • CPQ and billing: Salesforce CPQ, Chargebee, Stripe Billing

For each tool, document:

  • Primary use case and user group
  • Data that flows in (source, method, frequency)
  • Data that flows out (destination, method, frequency)
  • Data quality issues: missing fields, duplicate records, stale data

Identify:

  • Redundant tools (two tools doing the same thing)
  • Data gaps (information that users need but no system captures)
  • Broken integrations (data that should flow between systems but doesn't)
  • Tools with low adoption (licensed but rarely used)

Phase 4: CRM Redesign (Weeks 6–14)

The CRM is the system of record for revenue data. Redesign it to reflect the process you've designed, not the one you inherited.

Object model:

  • Account: company-level data, industry, size, territory, health score, ARR
  • Contact: individual record, role, relationship to opportunity
  • Lead: net-new individual, before account/contact conversion
  • Opportunity: revenue event with amount, close date, stage, products, competition

Stage redesign:

Define stage exit criteria, not stage definitions. Instead of "Stage 3: Demo Complete" — write "Stage 3 exit criteria: Champion identified, business case confirmed, next step accepted with a date." Reps advance stages only when criteria are met.

Forecasting categories:

  • Closed: revenue recognized this quarter
  • Commit: rep is confident this closes this quarter. Missing this number is a coaching conversation.
  • Best Case: could close with continued progress
  • Pipeline: active but earlier stage
  • Omit: not expected to close this quarter

Configure forecast rollup so managers and RevOps can see pipeline by category, owner, segment, and quarter in real time.

Territory and account assignment:

  • Define territory model: geographic, industry, account size, or named accounts
  • Configure automatic routing rules in CRM
  • Define rules for account conflicts and exceptions

Phase 5: Reporting and Analytics (Weeks 10–16)

Revenue leaders cannot manage what they can't see. Build the reporting infrastructure.

Metric definitions (document these first, configure second):

  • ARR: Annual Recurring Revenue — annualized value of active subscription contracts as of period end
  • NRR: Net Revenue Retention — (beginning period ARR + expansion − contraction − churn) ÷ beginning period ARR
  • Pipeline: total open opportunities by stage, weighted and unweighted
  • CAC: fully-loaded sales and marketing expense ÷ new logos acquired in the period

Dashboards to build:

  • Pipeline dashboard: open pipeline by rep, segment, stage, age, and quarter
  • Forecast dashboard: committed forecast vs. quota by rep and manager, trend
  • Activity dashboard: calls, emails, meetings by rep vs. quota
  • Customer health dashboard: NRR, churn risk, expansion opportunity by CS owner

Phase 6: Enablement and Change Management (Weeks 14–20)

New process and new CRM only work if reps use them correctly.

Training:

  • Sales rep training: new CRM workflow, new stage criteria, new forecasting process
  • Manager training: how to run a pipeline review with the new data
  • SDR training: new handoff process and MQL definition

Cadences to establish:

  • Weekly pipeline review: each rep reviews pipeline with manager using CRM data (not a slide deck)
  • Biweekly forecast call: managers roll up committed forecast to VP
  • Monthly RevOps review: RevOps team reviews pipeline health, win rates, cycle time vs. targets

Build the RevOps overhaul project plan in gantt-chart.io with workstreams for process, technology, and enablement. The technology workstream (CRM redesign) has a hard dependency on the process workstream (stage definitions, forecasting methodology) — if process design isn't complete, configuring the CRM will lock in the wrong process. Visualizing that dependency prevents the most common RevOps mistake: buying technology before the process is ready for it.