A Revenue Operations audit should not start with "is Salesforce clean?"

That question is too small.

The better question is: does the go-to-market system turn strategy into consistent, measurable, accountable execution?

If the answer is no, the CRM will show symptoms. But the cause may be unclear strategy, weak definitions, broken handoffs, incentive conflicts, poor data ownership, bad cadence, or customer lifecycle gaps.

An audit should diagnose the system, not just the tool.

Start with symptoms

Common symptoms of a weak revenue motion:

  • Leadership debates whose number is correct
  • Pipeline looks healthy but misses persist
  • Forecast calls produce confidence but not clarity
  • Marketing and sales disagree on lead quality
  • Sales and CS disagree on what was sold
  • Renewals surprise the business
  • Expansion opportunities appear late or randomly
  • Reps do not trust routing or territory rules
  • Compensation disputes require executive arbitration
  • Data quality projects repeat every quarter
  • QBRs explain results but do not change the system

These symptoms are useful because they show where to look. They are not the root cause by themselves.

Audit area 1: Strategy-to-execution translation

Ask:

  • Are target segments and ICP definitions explicit?
  • Do routing, territory, and ownership rules match the strategy?
  • Are goals translated into operating rules?
  • Can managers explain how the strategy changes daily execution?
  • Which strategic priorities are not reflected in systems or cadence?

Red flag: the company has a strategy deck but no operating map.

Audit area 2: Pipeline integrity

Ask:

  • Are stages defined by buyer evidence or seller activity?
  • Are stage entry and exit criteria documented?
  • Are required fields tied to decisions?
  • Are stale opportunities visible and managed?
  • Is pipeline quality reviewed by source, segment, age, and conversion?

Red flag: pipeline reviews are mostly reps narrating deal updates.

Audit area 3: Forecast process

Ask:

  • Are forecast categories evidence-based?
  • Are timing risk and value risk separated?
  • Are slippage reasons tracked and acted on?
  • Does finance trust the forecast process?
  • Does the forecast call produce management actions?

Red flag: commit means "rep feels good."

Audit area 4: Handoffs

Ask:

  • Are marketing-to-sales acceptance criteria clear?
  • Are sales-to-CS handoff requirements enforced?
  • Are finance handoffs complete before billing issues appear?
  • Are rejection and feedback reasons captured?
  • Do exceptions have defined owners?

Red flag: handoffs depend on Slack messages and personal relationships.

Audit area 5: Ownership, routing, and territories

Ask:

  • Are account ownership rules explicit?
  • Can the business explain routing logic in plain English?
  • Are strategic accounts protected?
  • Are territories balanced against opportunity and capacity?
  • Are conflict scenarios documented?

Red flag: routing disputes are solved one executive escalation at a time.

Audit area 6: Incentives

Ask:

  • Do compensation plans reinforce the current strategy?
  • Are renewal, expansion, partner, and multi-product credits clear?
  • Are discounting and bad-fit deals controlled?
  • Is there a documented dispute process?
  • Which behaviors are paid but not actually desired?

Red flag: leadership says customer quality matters but pays only on bookings.

Audit area 7: Data and systems

Ask:

  • Which fields are decision-critical?
  • Does each critical field have an owner?
  • Are validation rules protecting decisions or creating workarounds?
  • Are source, segment, stage, renewal, and ownership data reliable?
  • Which reports are not trusted, and why?

Red flag: everyone wants clean data, but no one owns specific fields.

Audit area 8: Systems architecture

Ask:

  • Which decisions depend on CRM, CPQ, billing, product usage, CS, support, warehouse, enrichment, or finance data?
  • Where do customer, account, contract, product usage, and ownership records disagree?
  • Which integrations are business-critical versus merely convenient?
  • Where does manual reconciliation still drive board, forecast, renewal, or compensation decisions?
  • Are AI or scoring workflows grounded in trusted definitions and clear decision rights?

Red flag: the CRM looks clean, but every important decision still requires a private spreadsheet or manual system stitching.

Audit area 9: Customer lifecycle

Ask:

  • Is closed-won followed by a complete handoff?
  • Are onboarding, activation, renewal, expansion, and churn workflows defined?
  • Are product usage signals connected to customer actions?
  • Are churn reasons specific enough to drive decisions?
  • Are renewal risks surfaced early enough?

Red flag: churn is analyzed after it happens, not managed before it happens.

Audit area 10: Management cadence

Ask:

  • Does each recurring meeting have a decision purpose?
  • Are operating packets prepared before meetings?
  • Are decisions logged and reviewed?
  • Do QBRs inspect operating mechanics, not just results?
  • Are experiments stopped, scaled, or modified based on evidence?

Red flag: the calendar is full, but the system does not learn.

Audit area 11: Adoption and change management

Ask:

  • Do managers enforce the rules RevOps designs?
  • Does the field understand why a process changed, not just what changed?
  • Are exceptions visible enough to improve the rule instead of bypassing it?
  • Are enablement, manager inspection, and executive reinforcement aligned?
  • Which workflows exist in documentation but not in daily behavior?

Red flag: RevOps ships process changes, but the field keeps running the old motion in Slack, spreadsheets, and manager exceptions.

A simple scoring rubric

Score each area from 1 to 4:

1 — Implicit: Rules live in people's heads. Execution depends on heroics.

2 — Documented: Some definitions exist, but they are inconsistently used.

3 — Operational: Rules are used in systems, cadence, and management decisions.

4 — Managed: The company regularly inspects and improves the operating model.

Apply the rubric by stage. Early-stage companies should not overbuild governance before the motion is known; they need clarity on the few rules that matter now. Scaling companies need enforcement because ambiguity starts multiplying across teams, regions, and products. Mature companies need governance and optimization because small rule changes can move large numbers or create large failure modes.

Do not average the score too quickly. A single weak area can break the system.

For example, strong pipeline definitions will not save a company with broken handoffs. Good dashboards will not save a company with incentives that reward bad-fit deals.

Build a 30/60/90-day remediation plan

Do not try to fix everything at once.

A practical sequence:

First 30 days: clarity and risk

  • Map the GTM operating model
  • Identify decision-critical data and system dependencies
  • Define top pipeline and forecast standards
  • Document major handoffs
  • Surface the biggest operating risks

Next 60 days: enforcement and cadence

  • Add stage exit criteria and hygiene reports
  • Implement handoff contracts
  • Clarify routing and ownership conflicts
  • Redesign forecast and pipeline review packets
  • Assign owners to critical fields and adoption checkpoints

Next 90 days: optimization

  • Review incentive edge cases
  • Improve lifecycle scorecards
  • Connect product signals to customer motions
  • Review systems architecture and remove manual reconciliation where it matters
  • Build experiment review cadence
  • Audit whether behavior changed

The goal is not a perfect system. The goal is a system the company can see, manage, and improve.

The tool: RevOps audit worksheet

Create a worksheet with columns:

  • Area
  • Current score
  • Evidence
  • Symptoms
  • Root cause hypothesis
  • Business risk
  • Owner
  • Recommended fix
  • Effort
  • Impact
  • Sequencing

This forces the audit to become an operating plan instead of a complaint list.

Bottom line

A Revenue Operations audit should diagnose whether the company has a working GTM operating model.

The CRM is part of the audit. It is not the whole audit.

Look for the places where strategy fails to become rules, rules fail to become behavior, behavior fails to become data, and data fails to become decisions.

That is where RevOps earns its mandate.