A comprehensive worksheet to audit your entire sales operating system, from lead handling through close and post-sale handoff.
The problem
Revenue operations problems rarely live in just one place. This audit walks you through every layer of your sales operating system so you can see the full picture before making changes.
What is inside
Lead routing and qualification criteria
Sales process definition and adherence
CRM architecture and automation logic
Compensation and incentive alignment
Quote-to-cash workflow integrity
Reporting and decision-support infrastructure
A sales operating system is not your CRM. It is not your process document. It is the full machine: process, tools, pipeline, enablement, reporting, and feedback loops, all working together to produce predictable revenue.
When revenue stalls or becomes unpredictable, the problem is rarely one broken thing. It is usually 2 to 3 pillars that have degraded quietly while the team compensated with extra effort. This audit helps you find them before the compensation breaks down.
How to use this audit
Walk through each pillar. For every question, answer honestly:
Yes: This is in place and working consistently
Partial: This exists on paper or happens inconsistently
No: This is not happening
Mark any red flags that apply. These are the patterns that signal deeper structural problems, not just missing checklist items. At the end, use the prioritization framework to decide what to fix first.
Pillar 1: Sales Process
Your process is the sequence of actions that moves a buyer from first contact to closed revenue. If the process is not defined, adopted, and enforced, everything downstream (pipeline accuracy, forecasting, enablement) breaks.
Diagnostic Questions
Is the sales process documented in a format a new hire can follow in their first week, without needing to shadow a senior rep to fill in the gaps?
Does each stage map to a specific buyer action or commitment (budget confirmed, decision maker engaged, proposal requested), not a seller activity (email sent, demo scheduled)?
Are there documented exit criteria for advancing a deal, and does the CRM enforce them (required fields, validation rules) or merely suggest them?
Is the process actually followed by 80%+ of the team, 80%+ of the time? (If you are not sure, the answer is probably no.)
Has the process been updated in the last 6 months based on analysis of wins and losses, not just management intuition?
Does the process account for meaningfully different deal types (enterprise versus mid-market, new business versus expansion), or is it one-size-fits-all?
Red Flags
The process document exists but nobody has opened it in 6 months
Different reps describe the process differently when asked
New hires learn by shadowing because the documentation is incomplete or outdated
Stage definitions are based on seller actions ("sent proposal") rather than buyer actions ("requested proposal and confirmed budget")
Nobody can articulate why the process has the number of stages it has, or what buyer behavior each stage represents
Pillar 2: CRM Configuration and Discipline
The CRM should be the single source of truth for revenue. When it is not, every report, every forecast, and every pipeline review is built on unreliable data.
Diagnostic Questions
Does the CRM schema match the actual sales process: same stages, same fields, same lifecycle definitions?
Are required fields enforced at the system level (validation rules, mandatory fields on stage transitions), or does compliance depend entirely on rep discipline?
Is there a single designated owner for CRM configuration, or do multiple people make changes without coordination?
Is there a regular cadence (monthly or quarterly) for cleaning dead records, deduplicating contacts, and archiving stale opportunities?
Can a manager pull a pipeline report and trust the numbers without calling reps to verify deal status?
Are integrations (marketing automation, invoicing, support) flowing data cleanly, or are there manual steps where data gets dropped or duplicated?
Red Flags
Multiple reps own overlapping accounts with no clear assignment rules or conflict resolution process
Close dates are routinely in the past on open deals, indicating nobody is maintaining deal timelines
Required fields are filled with placeholder data ("TBD", "$1", "test") to satisfy validation rules
Pipeline reports require manual adjustment before leadership review because the raw data is unreliable
Nobody on the team can explain who administers the CRM, how change requests are handled, or where configuration decisions are documented
Pillar 3: Pipeline Management
Pipeline management is the practice of inspecting, progressing, and pruning deals with enough discipline to forecast reliably and allocate resources where they will have the most impact.
Diagnostic Questions
Are pipeline reviews held on a fixed weekly cadence with a consistent format, or do they happen ad hoc when leadership requests them?
Are reviews structured around deal-level inspection (stage, next step, blockers, timeline) or do reps give verbal updates with no data on screen?
Is pipeline coverage tracked as a ratio to target, calculated on clean data (excluding stale and aged deals)?
Are stale deals (no activity for a defined period) identified automatically and addressed within a set timeframe?
Do you track stage-to-stage conversion rates and use them to identify where deals stall or leak?
Can you answer "what needs to close this month for us to hit the quarter" with data from the CRM, not a whiteboard exercise?
Red Flags
Pipeline reviews are status updates where reps narrate deal history instead of strategy sessions where the team solves blockers
Coverage ratio is calculated on gross pipeline including deals with no activity for 30+ days
There is no defined process for removing or re-engaging stale opportunities, so dead deals accumulate indefinitely
Forecast accuracy is consistently off by more than 20%, a threshold where the forecast stops being useful for resource planning
The team cannot state their average deal cycle by segment without running an ad hoc report
Pillar 4: Sales Enablement
Enablement is everything that equips the team to execute the process: onboarding, content, tools, training, and coaching. When enablement is weak, even a well-designed process will not stick because reps lack the skills or materials to follow it.
Diagnostic Questions
Does onboarding have a defined curriculum with milestones and assessments, or is it "shadow a senior rep for two weeks and figure it out"?
Are sales collateral (decks, one-pagers, case studies, battlecards) current, organized by use case or stage, and accessible from a single location?
Is there a coaching cadence where managers review recorded calls, inspect deal strategy, or conduct pipeline coaching with individual reps at least biweekly?
Do reps have documented frameworks or talk tracks for the 5 most common objections, or does everyone improvise?
Is training ongoing (monthly or quarterly skill-building sessions), or was the last formal training session the onboarding they attended when they joined?
Can you measure whether enablement investments (new training, updated collateral, tool rollouts) correlate with performance changes, or is the impact assumed?
Red Flags
New hires take 6+ months to hit quota with no structured ramp plan or defined ramp quota
Sales collateral is scattered across Google Drive folders, Slack messages, and email attachments with no single source of truth
Coaching happens only when a deal is in trouble, not as a proactive development practice
The most recent formal training session was more than 6 months ago
Reps create their own decks and materials because the official versions are outdated, generic, or do not match how buyers actually evaluate
Pillar 5: Reporting and Analytics
Reporting should answer three questions: What happened? Why did it happen? What should we do about it? If your reports only answer the first question, they are dashboards, not decision tools.
Diagnostic Questions
Can the sales leader access pipeline, activity, and revenue reports on demand without requesting a custom build from another team?
Do reports show trends over time (this quarter versus last quarter, this cohort versus prior cohort), or just current-state snapshots?
Are leading indicators (activity volume, stage velocity, meetings booked, proposals sent) tracked alongside lagging indicators (revenue, win rate, Average Contract Value)?
Is there a standing report package that leadership reviews on a fixed cadence (weekly pipeline report, monthly business review, quarterly board package)?
Do reports drive specific actions (changes to process, reallocation of resources, coaching interventions), or are they reviewed and filed?
Can you attribute closed revenue back to source (marketing channel, campaign, rep outbound) reliably and without manual reconciliation?
Red Flags
Reports are built ad hoc for each leadership meeting, creating inconsistency in definitions and metrics across reports
Nobody trusts the CRM numbers without cross-referencing a spreadsheet or another system
Revenue is tracked, but the activities and conversions that produce revenue are not, making it impossible to diagnose a miss
Revenue attribution requires manual reconciliation across multiple systems and still produces disputed results
Reports exist and are reviewed regularly, but nobody can point to a decision or behavior change that resulted from them
Pillar 6: Feedback Loops
Feedback loops are the mechanisms that take information from the field (wins, losses, customer objections, delivery friction, competitive intelligence) and route it back into process improvement, enablement updates, and strategy decisions.
Diagnostic Questions
Are closed-lost reasons captured in a structured picklist (not free text) and reviewed at least monthly for patterns?
Does customer feedback from delivery, support, or customer success reach the sales team in a format that changes how they qualify, position, or set expectations?
When a pattern emerges (a new competitor appearing in deals, a shifting objection, pricing pushback in a specific segment), is there a defined path to update the process or enablement materials?
Are formal win/loss analyses conducted on deals above a defined value threshold, with findings documented and distributed?
Is there a regular retrospective or operational review meeting focused on process improvement, separate from pipeline review?
Red Flags
Closed-lost reasons are "other" or blank on more than 30% of lost deals
Delivery problems surface as churn 6 months later, not as feedback to the sales process at the point of handoff
The most recent sales process change driven by field feedback was more than 6 months ago
Wins are celebrated in Slack but never analyzed to understand what made them close
Reps have stopped providing feedback because nothing changes when they do
Prioritization Framework
Count your results for each pillar:
Pillar
Yes
Partial
No
Red Flags
Sales Process
CRM
Pipeline
Enablement
Reporting
Feedback Loops
Where to start
Start with the pillar that has the most "No" answers and the most red flags. That is where the system is breaking.
If two pillars are tied, prioritize in this order:
Sales Process: everything downstream depends on this being defined and adopted
CRM Configuration: if the data layer is broken, reporting, forecasting, and pipeline management all inherit the problem
Pipeline Management: this is where revenue visibility lives and where forecast accuracy is built
Reporting: you cannot manage what you cannot see, and you cannot improve what you do not measure
Enablement: this drives adoption and consistency across the team
Feedback Loops: this drives long-term improvement and prevents the same problems from recurring
If three or more pillars have majority "No" answers, do not attempt to fix them all at once. That approach spreads effort thin and produces shallow improvements that do not stick. A diagnostic will sequence the work so each layer builds on a solid foundation, with the highest-impact pillar addressed first.
What to do next
This audit gives you the map. The diagnostic gives you the plan.
If you found multiple pillars with serious gaps, a Sales Operating System Diagnostic will walk through each finding, identify root causes, map dependencies between the pillars (for example, CRM problems that are actually process problems in disguise), and produce a prioritized remediation plan with specific actions, owners, and timelines.