Sales leadership guide

Make the sales pipeline reliable without turning CRM into administrative control

Define qualification, stage, evidence, next action and forecast with useful data entry.

For: Sales leaders, sales managers, key accounts, marketing and finance
01 · Short answer

What to clarify before discussing a solution

The signal

Forecasts vary by person and opportunities remain open without a dated next action.

The answer

What evidence genuinely allows an opportunity to move to the next stage?

The answer does not lie in an isolated feature: it is built by connecting rules, actors, data and evidence.
The expected outcome

A pipeline governed by observable criteria and decision-focused reviews.

02 · Structural decisions

Four decisions to make before configuration

These decisions make the scope testable and prevent structural choices from being discovered during the project.

01

Define minimum qualification

The decision must specify the rule, its owner, the required data and the evidence used to accept it.

02

Associate evidence with each stage change

The decision must specify the rule, its owner, the required data and the evidence used to accept it.

03

Require next-action owner and date

The decision must specify the rule, its owner, the required data and the evidence used to accept it.

04

Separate forecast, potential and commitment

The decision must specify the rule, its owner, the required data and the evidence used to accept it.

03 · Scope

A readable end-to-end flow

Scope is not a list of modules. It is a chain of events, ownership and decisions.

1Qualification
2Stages and evidence
3Next action
4Forecast
5Review and coaching

In the first scoping

  • One representative flow and its useful variants
  • Authoritative events and minimum data
  • Roles, decisions and escalation times
  • Acceptance criteria and baseline measurement

To sequence in waves

  • Additional sites, activities or populations
  • Rare variants that do not condition the pilot
  • Automations whose rule is not yet stable
  • Advanced dashboards after source reliability

To decide explicitly

  • Define minimum qualification
  • Associate evidence with each stage change
  • Require next-action owner and date
  • Separate forecast, potential and commitment
04 · Roadmap

From direction to measured improvement

  1. 1Navigator
  2. 2Personalised review
  3. 3Scoping workshop
  4. 4Wave-based deployment
  5. 5KPI measurement

Each stage produces a decision or evidence reusable in the next. Deployment remains business-led and verifiable.

05 · Metrics

Measure to decide, not to fill a dashboard

Every KPI needs a definition, a source, a cadence and an associated decision.

KPIFormulaSourceDecision
CRM coverageDocumented opportunities ÷ active opportunitiesAccounts, activities and opportunitiesImprove pipeline reliability and next actions
Sales cycle lengthDecision date − qualification dateStages, activities and decisionsRemove qualification and decision bottlenecks
Forecast accuracy1 − |forecast − actual| ÷ actualForecasts, orders and actualsRecalibrate assumptions, data and horizon
Conversion rateTransactions or orders ÷ visits or opportunitiesChannels, opportunities, baskets and ordersTarget breaks in the buying journey
06 · Business scenario

A review that decides rather than collects

Situation
The sales meeting is used to update information instead of deciding actions.
Approach
The pipeline is simplified, each stage receives evidence and the review focuses on blockage, action and date.
Target outcome
The forecast becomes explainable and meetings focus on real progress.
This scenario illustrates a scoping method. Outcomes must be established with data from the selected scope.
07 · Frequently asked questions

Useful answers before the first discussion

01Where should we start in practical terms?

Choose a representative scope spanning “Qualification” and “Stages and evidence”, then document one normal case and one frequent exception. The first flow should be important enough to matter but contained enough to observe end to end.

02Do all existing systems need replacing?

No. Scoping starts with decisions, authoritative events and ownership. It then determines what should be retained, integrated, replaced or simply better governed, wave by wave.

03What data should be prepared before a workshop?

Prepare a few real cases, the volumes shaping the operation, the main variance reasons and the sources used to measure CRM coverage. The quality of examples matters more than the quantity of documents.

04How should the right pilot scope be chosen?

Choose a scope with an available owner, accessible data, a meaningful exception and a measurable outcome. Avoid both an overly simple case that proves nothing and an overly broad scope that dilutes learning.

05How can scope changes during the project be limited?

Make assumptions, interfaces, variants, exceptions and acceptance criteria explicit. Every new request can then be classified: essential to the wave, suitable for a later wave, or outside the objective. Discussion focuses on impact rather than intuition.

Next step

Turn this guide into a personalised review

Complete Navigator to position your context, then use the review as the starting point for a scoping workshop.

  1. 1Navigator
  2. 2Personalised review
  3. 3Scoping workshop
  4. 4Wave-based deployment
  5. 5KPI measurement
NavigatorPlan a discussion with an expert