GrowthStack Advisory / Resources / Pipeline Audit
How to audit a sales pipeline in 72 hours
The short answer
A pipeline audit answers one question: at which stage are deals leaving, and why. Three days is enough, because the answer is almost always visible in conversion rate by stage rather than in any individual deal. Spend the first day on data quality and stage definitions, because a pipeline nobody updates consistently cannot be diagnosed. Spend the second on the six diagnostic questions below. Spend the third deciding which single fix to make first. The most common finding is not that deals are being lost. It is that deals which were never qualified were counted as pipeline, so the forecast was wrong months before anyone noticed.
- Conversion by stage, not deal count, is where the answer lives
- Fix stage definitions first, or you are auditing opinions
- Expect stage inflation, the most common and least discussed leak
- One fix at a time, so you can tell what moved the number
Founder, GrowthStack Advisory. Ran sales development at Locus, GoComet and Landmark’s Logistiq division, and has since delivered for Easyship, ConvertCart and NuVista AI. LinkedIn.
· 7 min read
Day one: decide whether the data can be trusted
Before anything is diagnosed, two things have to be true: every open deal sits in a stage that means the same thing to every rep, and the stage was last changed recently enough to be believed. Want this done for you? The sales pipeline audit is a fixed-price version, delivered in 5 to 7 business days.
Pull three numbers. The share of open deals whose stage has not changed in 30 days. The share with no next step recorded. And the number of distinct people who have moved a deal to the stage before closed-won in the last quarter. The first two tell you how much of the pipeline is abandoned rather than active. The third tells you whether the stage definition is shared or personal.
Then read the stage definitions as written. Most CRMs ship with stage names and no criteria, so each rep invents their own. If two reps would place the same deal differently, the conversion rates you are about to calculate are averages across several incompatible systems, and no fix derived from them will hold.
This is the same discipline that applies one stage earlier, at the handoff into sales, described in improving MQL to SQL conversion. A written definition that two people apply identically is the prerequisite for measuring anything.
Day two: the six diagnostic questions
Each one isolates a different failure. Answer them in order, because an early yes changes what a later answer means.
- Where does conversion drop hardest between two consecutive stages? That gap, not the overall close rate, is the thing to fix. An overall rate averages a healthy stage and a broken one into a number that describes neither.
- Is the drop present for every rep, or concentrated? Present everywhere means the process or the targeting. Concentrated in one or two people means coaching, and that is a different investigation covered in the five lever SDR diagnostic.
- How long do deals sit in the stage before the drop? A fast drop is usually disqualification, which is healthy and should happen earlier. A slow drop is usually a deal nobody wanted to close out, which is stage inflation.
- Does the drop differ by lead source? If one source converts at a fraction of the others past the same stage, the problem is upstream of sales and no amount of rep coaching will move it.
- Are the deals that closed different in kind from the ones that stalled? Compare the last twenty closed-won against twenty stalled on whatever attributes you have. When a pattern shows up here it is usually an ICP problem, and the ICP framework is the fix.
- What proportion of current pipeline was created more than two cycles ago? Anything older than twice the median cycle is not pipeline. It is history that has not been archived, and it is inflating every forecast that includes it.
Stage inflation, and why it hides for so long
The most common finding in this audit is not lost deals. It is deals promoted into a stage they did not earn.
It happens for understandable reasons. A rep has a good call, the prospect is engaged, nobody has asked about budget or authority yet, and the deal moves forward because it feels like progress. Multiply that across a team and pipeline coverage looks strong while the close rate quietly falls, because the denominator grew and the numerator did not.
The tell is a stage with high entry and low exit that deals sit in for far longer than the median. The fix is exit criteria written as evidence rather than as feeling. Not prospect is interested, but prospect has named the problem in their own words and confirmed who signs. Choosing between the standard frameworks for this is covered in BANT vs MEDDIC vs your own.
Running global sales development at Locus, Shobhit Gupta moved MQL to SQL conversion from 10% to 25% without adding a single lead, and most of that movement came from tightening what was allowed to count, not from working harder on the deals already in the system.
The four places pipeline actually leaks
Across audits the same four recur, and they fail in a fixed order. Fixing one out of sequence wastes the work.
- Targeting. The accounts were never going to buy. Shows up as a drop early, consistent across reps, and differing sharply by source.
- Qualification. The accounts could buy but were not tested. Shows up as stage inflation and a long, slow middle.
- Follow up. The deals were real and went quiet. Shows up as a high proportion of stale open deals with no next step, and it is usually the cheapest to fix. Speed matters more than most teams assume, which is the subject of speed to lead.
- Handoff. The deal survived qualification and lost momentum changing hands. Shows up as a drop concentrated at exactly one stage boundary and at no other.
Targeting first, then qualification, then follow up, then handoff. A team that fixes follow up while the targeting is wrong will chase the wrong accounts more diligently.
Day three: choose one fix, not four
An audit that produces a list of eleven improvements produces nothing, because when four changes land in the same month no one can say which of them moved the number, and the next decision is made on a guess.
Rank the findings by how much of the gap each explains and how quickly it can be tested. Take the top one. Define what you expect to move and by roughly how much, write that down before you start, and give it a full sales cycle before judging it. Where the change is a messaging or sequence test rather than a process change, the volume required to tell a real difference from noise is larger than intuition suggests, and the cold email A/B test calculator gives you the number.
What to keep watching
An audit is a one-off. What prevents the next one is a short weekly review of conversion rate between the two stages that were broken, split by rep and by source, alongside the count of deals older than two cycles.
That is four numbers. Teams that track forty do not notice when one of them moves. Which numbers earn a permanent place, and which ones only look useful, is the subject of the sales metrics that actually predict revenue.
Related reading
This guide sits alongside the metrics that predict revenue and the five lever SDR diagnostic. Between them they cover the pipeline, the numbers that describe it, and the individual rep.
For the reporting layer that makes any of this visible in the first place, see GTM analytics and sales reporting.
Frequently asked questions
How long should a pipeline audit take?+
Three days is enough for a first pass, because the answer almost always lives in conversion rate by stage rather than in individual deals. Day one establishes whether the data can be trusted and whether stage definitions mean the same thing to every rep. Day two runs the diagnostic questions. Day three picks a single fix. An audit that runs for three weeks usually produces a list nobody acts on.
What is stage inflation?+
Deals promoted into a stage they did not earn, usually because a good conversation felt like progress before budget or authority were tested. It inflates pipeline coverage while the close rate falls, because the denominator grows and the numerator does not. The tell is a stage with high entry, low exit, and deals sitting in it far longer than the median. The fix is exit criteria written as evidence rather than as sentiment.
Where does B2B pipeline usually leak?+
In four places, and they fail in a fixed order: targeting, qualification, follow up, then handoff. Targeting problems show as an early drop consistent across reps and varying by lead source. Qualification problems show as stage inflation. Follow up problems show as stale open deals with no next step. Handoff problems show as a drop concentrated at exactly one stage boundary.
Should you fix several pipeline problems at once?+
No. When four changes land in the same month, nobody can say which one moved the number, so the next decision is made on a guess. Rank findings by how much of the gap each explains and how fast it can be tested, take the top one, write down what you expect to move before starting, and give it a full sales cycle.
How much old pipeline is too much?+
Anything older than twice the median sales cycle should be treated as history rather than pipeline. It is not necessarily dead, but including it inflates every forecast built on the total, and it is the single easiest correction available in most CRMs.
Pipeline not behaving as the dashboard says
Thirty minutes on where it is actually leaking.
Book 30 minutesWritten with AI assistance from Shobhit Gupta’s notes and client work, then reviewed and edited by Shobhit Gupta on .