Commercial Growth

Sales pipeline audit: what to check when you can't trust the pipeline

8 mins read

A smoked glass pipe on brushed silver brackets, examined by a silver loupe that shows a red sphere lodged inside, on a deep purple background.

KEY TAKEAWAYS

  • Commission a pipeline audit when the pipeline and the results stop agreeing and nobody can say why. Do it before you change people, process or tools.

  • An audit looks at the whole pipeline for patterns. A deal review judges one opportunity, and a data cleanse only makes the pipeline smaller.

  • Agree the definitions first. Stages, forecast categories, revenue and qualification have to mean the same thing everywhere, or every later number is suspect.

  • Read the findings as symptoms. Deals that slow at proposal may trace back to discovery, and some causes may sit outside sales.

  • Decide who owns each finding before the audit starts, then repeat a lighter check each quarter against the same definitions.

If you can't trust the pipeline and the forecast keeps moving late in the period, commission a sales pipeline audit before you change people, process or tools. A good audit looks at the whole pipeline at once, not deal by deal. It checks that everyone uses the same definitions, that opportunities carry the evidence their stage claims, how deals convert and age by stage and segment, where value leaks, and how forecast calls are made. It should end by naming the causes and who owns each one. A tidier CRM is a by-product.

This guide is for a CRO, sales director or revenue operations leader deciding whether to commission an audit and what to ask it to check. Single stalled deals and forecasting software have their own guides, linked below.

When a sales pipeline audit is worth commissioning

Commission one when the pipeline and the results stop agreeing and nobody can say why. Typical triggers:

  • pipeline coverage looks healthy, but quarters still close short;

  • the forecast swings in the last weeks of the period;

  • managers argue about the number on forecast calls instead of about the deals;

  • a new revenue leader needs to know what they've inherited;

  • you're about to buy a forecasting tool, change the CRM or redesign the sales process, and want a baseline first.

For a new leader, our guide to a sales director's first 90 days treats "the pipeline is strong" as a claim to test, not a fact.

The reason to act early is that revenue moves last. Merlin5's view, set out on its page on why velocity matters, is that by the time revenue changes, the drivers behind it have been shifting for months.

What a pipeline audit is, and what it isn't

A pipeline audit is a periodic check of the whole system that produces your pipeline: the definitions, the evidence, the flow of deals through stages, and the way the forecast is built from them. It asks whether the pipeline can be believed and, if not, why not.

Keep it separate from three other things:

  • A deal review. A deal review asks whether one opportunity will close. Our guide to stalled deals covers the signs that a single deal has stopped. An audit looks for patterns across all of them.

  • A forecast call. A forecast call agrees this period's number. An audit asks whether the method behind the number holds up.

  • A data cleanse. Removing duplicates and dead deals makes the pipeline more honest, but on its own it adds no revenue and doesn't explain why the pipeline drifted. Cleaning is one step in an audit.

What a sales pipeline audit should check

Seven checks, in roughly this order. The first two decide whether you can trust the other five.

1. Are the definitions agreed?

Stage names, forecast categories, revenue definitions and qualification criteria have to mean the same thing in every team before any number built on them is worth reading. Merlin5's Sales Velocity Analysis™ makes this the first job: every dataset gets a named owner, and stage criteria, forecast categories and revenue definitions are formally agreed before analysis begins.

2. Does each deal carry the evidence its stage claims?

Take a sample of open opportunities at each stage and check them against that stage's exit criteria. Look for what the buyer has done, not what the seller has done. Merlin5's sales process page describes what happens when deals move through the CRM without clear evidence: qualification standards vary and forecasts become subjective. If your stages don't have exit criteria yet, our guide to sales process stages shows how to write them.

3. Is enough qualified pipeline coming in?

Check opportunity creation by source and by segment over several quarters, and how much of it survives qualification. A pipeline can look full because old deals never leave, while too few new qualified opportunities enter. Opportunities are the first of the four drivers in our sales velocity formula guide.

4. Where do deals slow down or drop out?

Measure conversion and time in each stage, by segment and deal type, and compare them over time. A single total can hide where the engine changed. One pattern Merlin5 lists among what the analysis surfaces is opportunities spending significantly longer in proposal and commercial stages than expected.

5. Where is value leaking?

Merlin5's view is that revenue is lost long before a deal is marked closed lost. Compare deal value when an opportunity is created with its value at close, and check win rate by segment and deal size. Merlin5's own list of where revenue leaks includes poor qualification, weak opportunity progression, inconsistent value articulation, poor forecasting disciplines and weak stakeholder engagement.

6. How clean is the data?

Look for duplicates, deals with no owner or amount, close dates already in the past, and deals with no activity for months. Count them, then remove or reset them as a separate step. Cleaning makes the pipeline smaller and more honest, so report it as clean-up rather than as lost pipeline.

7. How is the forecast built?

Put each period's forecast beside what actually closed, over several quarters, and trace where each gap came from: deals pulled in late, deals that slipped, or deals that were never real. Then check how commit is decided and who can change it. If you're considering a tool to help, our guide to sales forecasting software covers the inputs to fix before you buy one.

Read causes, not symptoms

The checks tell you where the pipeline is weak, but not yet why. A slow proposal stage is a symptom. In our view, the cause may sit earlier in the deal.

For that proposal-stage pattern, Merlin5's page lists the common factors: business drivers not fully understood, desired outcomes not quantified, compelling events not established, stakeholder alignment happening too late, and decision processes not fully understood. Our reading is that each of those is established, or missed, in discovery, well before the proposal is written.

Some causes may sit outside the sales team. Merlin5's Growth Assessor™ page notes that a sales problem frequently originates outside sales. In our reading, that can mean marketing shaping what enters as a lead, finance deciding how revenue is counted, and systems deciding what data exists. An audit that only interviews sellers may miss part of the answer, and Merlin5's own Growth Assessor™ workshop involves sales, marketing, operations, finance and leadership. The table below gives our rules of thumb: possible causes to test, not findings.

What the audit finds

Possible cause to test

What to look at next

Stage conversion varies widely between teams

Different stage definitions or exit criteria

Deals from each team, checked against the same criteria

Deals stall at proposal

Discovery that didn't establish outcomes, events or the decision process

Discovery notes on recent won and lost deals

Large pipeline, low win rate

Weak qualification when deals enter

How many deals are lost or closed out from early stages

Forecast still misses after clean-up

How commit is decided, not the data

How commit was set on last quarter's misses

Deal values fall between creation and close

Value not quantified with the buyer

Value at creation against value at close, by segment

Run it yourself, or bring someone in?

Run it internally when your definitions are already agreed, someone has the time and data access, and the people doing the analysis aren't the people the numbers judge. Bring in someone independent when teams disagree about definitions, when the people who run the pipeline are also judged by it, or when nobody has the time. Merlin5's own page puts the time problem plainly: most CROs know the questions, but few have time to answer them properly.

Either way, decide before the audit starts who will act on each finding. If the report ends with nobody owning the findings, expect little to change.

What you should have at the end

  • written definitions for stages, forecast categories, revenue and qualification;

  • one dataset the leadership team will keep using;

  • the four drivers measured by segment, with the stages where deals slow or drop out;

  • where value is being lost, and what it is costing;

  • the likely causes, with the evidence for each;

  • a short list of actions, each with an owner and a date to check it.

In our view, a full audit is worth repeating when the business changes: a new leader, a new market, a new CRM or a new owner. In between, our rule of thumb is a lighter quarterly check against the same definitions. Keep the definitions stable so the results compare. Our guide on how to increase sales velocity covers reading the drivers over time.

Where Merlin5 fits

Several of these checks are part of Merlin5's Sales Velocity Analysis™. It agrees definitions and builds one dataset first. Then it measures the four drivers, shows where value is being lost, and benchmarks performance against world-class commercial standards. The findings are presented to the leadership team with a prioritised action plan. Merlin5 says most organisations move from data collection to actionable insight within weeks, depending on data availability and stakeholder participation.

It's the first step, not the whole answer. The analysis shows what the problems are, and the Growth Assessor™ then looks at why they are happening across the wider commercial system. On forecasting, Merlin5's process and CRM FAQ says forecasts become unreliable because of how opportunities are managed before they enter the forecast. That is why the audit traces each forecast gap back to how the deals were managed.

Where to start

  1. Ask three managers to define each stage, and "commit", in writing. Compare the answers.

  2. Export the open pipeline and check ten deals per stage against the evidence the stage requires.

  3. Put the last four quarters' forecasts beside what closed, and mark where each gap came from.

Frequently asked questions

What is a sales pipeline audit?

A structured check of the whole pipeline: the definitions it rests on, the evidence behind each stage, how deals flow and convert, where value leaks and how the forecast is built. It asks whether the pipeline can be trusted and, if not, why.

How long does a pipeline audit take?

The state of the data and how quickly teams agree definitions decide most of it. In Merlin5's process work, agreeing definitions across teams that have used their own is what usually sets the pace. For its velocity analysis, Merlin5 says most organisations reach actionable insight within weeks rather than months.

Is a pipeline audit the same as a forecast review?

No. A forecast review agrees the number for this period. A pipeline audit checks whether the method behind the number holds up, across every deal.

Who should own the findings?

The sales leader is accountable for the result. Each finding needs a named owner before the audit ends, for example a first-line manager for stage evidence, revenue operations for data and definitions, and marketing or finance where the cause sits with them.

Sources

This guide uses no external research or statistics. Merlin5 facts come from its Sales Velocity Analysis™ and Sales Process and CRM Transformation pages.

NEXT STEP

Start from one dataset everyone trusts

Sales Velocity Analysis™ agrees your definitions, builds one clean dataset, and shows which drivers are constraining performance and where value is leaking.

Explore Sales Velocity Analysis™

Headshot of Chris Thomas

WRITTEN BY

Chris Thomas

© 2026 Merlin5

© 2026 Merlin5