30-Day Sales Operating System Review: Diagnose Before You Prescribe
When sales performance disappoints, the pressure to act is immediate. Leaders change targets, buy another tool, rewrite the pitch, increase activity requirements or tell managers to coach harder.
Some of those actions may eventually help. None should be the starting assumption.
Sales results emerge from a system: the market and offer, the sales motion, buyer access, opportunity quality, process design, manager behaviour, rep capability, data discipline and organisational constraints. If leaders prescribe a remedy before identifying which part of that system is failing, they can add effort without improving performance.
A 30-day sales operating system review creates a better starting point. It does not promise a revenue outcome. It establishes a shared diagnosis, tests the evidence behind current beliefs and selects one bounded improvement that management can inspect.
1. Define the sales motion
Begin with the commercial reality, not the CRM configuration.
Document:
- the products or services being sold;
- the customer segments and buying situations;
- typical deal value and sales-cycle shape;
- inbound, outbound, partner or account-led acquisition;
- the people involved in the buying decision;
- the seller roles involved from first contact to handover; and
- material differences between motions.
A transactional inbound team and an enterprise account team should not be assessed with the same assumptions. Neither should a new-business motion and an expansion motion. If several motions are mixed in one pipeline, segment them before comparing conversion, cycle time or activity.
Ask leaders and frontline sellers to describe how a real opportunity progresses. Differences between their answers are useful evidence. They often reveal that the documented process and the operating process are not the same.
2. Inspect stage definitions
Pipeline stages should represent meaningful changes in buyer commitment or seller knowledge. Too often they represent completed seller activity: a call happened, a demonstration was delivered, or a proposal was sent.
For each stage, define:
- the buyer condition that must be true;
- the evidence required to enter;
- the evidence required to leave;
- the decision or risk being resolved;
- the next agreed action;
- the owner; and
- the conditions for loss, recycle or disqualification.
Avoid definitions that depend only on seller confidence. “Good conversation” or “likely to proceed” cannot be inspected consistently. Useful evidence may include a confirmed problem, access to a decision participant, an agreed evaluation process, or a documented commercial constraint. The appropriate evidence depends on the motion.
Then sample recent opportunities. Do not begin by blaming people for inconsistency. First determine whether the stage definitions are clear, useful and practical enough to follow.
3. Test the quality of pipeline evidence
CRM completeness is not the same as pipeline quality.
Choose a small, representative sample of open, won and lost opportunities. Review the source material available to managers: notes, correspondence, meeting records, stage history, next actions and close-date changes. Ask:
- What customer problem is actually evidenced?
- Why is action needed now?
- Who is involved in the decision?
- What alternatives are being considered?
- What commercial or implementation constraints exist?
- What has the buyer agreed to do next?
- Which important statement is an assumption rather than evidence?
The aim is not to create maximum data entry. It is to identify the minimum information managers need to make useful decisions. Fields that nobody uses create administrative load. Missing evidence that managers repeatedly reconstruct creates forecast and coaching risk.
4. Review the manager operating cadence
Sales management is not a calendar of recurring meetings. It is a decision system.
Map the current cadence:
- one-to-one coaching;
- pipeline review;
- opportunity review;
- forecast review;
- team learning;
- call or meeting review;
- account planning; and
- handover or customer-risk review.
For each forum, record its purpose, inputs, decisions, owner and follow-up. Pipeline inspection, forecast judgment and coaching are related but different. Combining them into one hurried meeting usually weakens all three.
Observe whether managers spend the session reconstructing basic information, challenging unsupported optimism, solving deals for sellers, or identifying repeatable capability gaps. The pattern tells you whether the primary problem is data quality, process clarity, opportunity strategy, coaching skill or capacity.
5. Separate opportunity inspection from performance judgment
An opportunity review asks what is known, unknown and at risk in a specific buying process. A performance review asks whether a person is meeting role expectations over time. Mixing them can reduce learning and encourage defensive reporting.
Use opportunity inspection to improve the decision:
- What evidence supports the current stage?
- What would disconfirm the seller’s view?
- Which stakeholder or constraint is missing?
- What next action would produce useful information?
- Should the team advance, hold, recycle or disqualify?
Patterns across several opportunities may inform coaching. They should not become employment or performance conclusions from one incomplete record. Managers remain accountable for fair judgment, appropriate evidence and organisational policy.
6. Examine the forecast method
A forecast should make uncertainty visible. It should not turn a weak pipeline into a precise-looking number.
Document how the team currently forecasts:
- stage probability;
- seller category or commitment;
- manager judgment;
- historical conversion;
- time in stage;
- scheduled buyer events;
- or a combination.
Then inspect forecast movement over recent periods. Which opportunities entered late? Which close dates moved repeatedly? Which losses were known early but remained open? Where did expansion, slippage or deal size create surprise?
The purpose is not to demand perfect accuracy. It is to identify systematic sources of error and improve the decisions that depend on the forecast. A useful method states assumptions and ranges, distinguishes committed evidence from aspiration, and allows managers to explain changes.
7. Connect enablement to diagnosed gaps
Training is often prescribed because it is visible and available. It is valuable only when it addresses a real capability requirement and changes behaviour in the sales motion.
Review existing onboarding, playbooks, scripts, product material, call examples and manager coaching aids. For each resource, ask:
- Which observable behaviour should this support?
- At what point in the sales motion?
- What good judgment looks like in context?
- How will a manager recognise improvement?
- Is the material current and used?
A large content library can still leave sellers without practical guidance. Prefer a small set of reviewed examples, decision aids and practice loops connected to the gaps found in opportunity evidence.
AI can help organise material, prepare review summaries and surface patterns. It should not silently score people, invent customer evidence or make management decisions from incomplete context.
8. Select one bounded improvement
At the end of the diagnostic, avoid a broad transformation programme. Rank findings by consequence, evidence, controllability and learning value.
A useful first improvement might be:
- clearer entry and exit evidence for two disputed stages;
- a separate weekly opportunity-inspection forum;
- a minimum evidence standard for forecast categories;
- a manager coaching aid for one recurring capability gap; or
- a simpler next-action and close-date discipline.
Define the baseline, owner, affected team, review period and stop condition. Measure both adoption and usefulness. If compliance increases but manager decision quality does not, revise the intervention.
A practical 30-day sequence
Week 1: Understand the motion. Interview leaders and frontline roles, map the operating process, segment motions and identify competing definitions.
Week 2: Inspect evidence. Sample opportunities and stage histories, observe management forums and test what the current data can actually support.
Week 3: Diagnose patterns. Separate process, data, capability, management and market issues. Review findings with the people who do the work and record disagreement.
Week 4: Run one controlled change. Implement a narrow improvement, define evidence and review conditions, and schedule the next management decision.
The strongest output is not a long list of sales advice. It is a credible explanation of what is happening, what remains uncertain, and which change is most likely to create useful evidence.
Diagnose before you prescribe. In sales management, better action begins with a better account of reality.