# How do you audit a sales pipeline you inherited?

> Start with stage definitions, stale deals, close date history, fields nobody fills in and how reps use the CRM day to day. Talk to each rep about their own deals before you change anything, then fix stages and close dates first, because every forecast and report you'll give leadership depends on them.

By NeuroGTM, a fractional RevOps practice in Denver. Published November 15, 2026. Topic: CRM, data, and reporting.

Page: https://neurogtm.com/blog/audit-inherited-sales-pipeline

Start by finding out what the pipeline numbers mean before you trust them. Look at how stages are defined, which open deals have gone stale, how often close dates have moved, which fields are never filled in, and how reps use the CRM in a normal week. Then talk to each rep about their own deals, and fix stage definitions and close dates first, because every number you report to leadership is built on them.

## Why audit before you report anything?

When you start, leadership will ask what the pipeline looks like, and the easiest answer is the dashboard you inherited. That dashboard reflects whatever rules your predecessor set, or didn't set. If you report it and it turns out to be inflated, the miss becomes yours.

An audit gives you a baseline you can explain. It also tells you which problems are about the data and which are about how the team sells, and those need different fixes.

## What should you look at first?

The [CRM pipeline audit checklist](/templates/crm-pipeline-audit-checklist) covers each of these in more detail.

### Stage definitions

Find out whether the stages have written exit criteria. If they do, check a handful of deals at each stage against them. If they don't, ask two or three reps what has to be true for a deal to reach a given stage and compare their answers. Different answers mean the stage-weighted numbers can't be compared across reps.

### Stale deals

Filter for open deals with no logged activity for longer than your normal gap between buyer meetings. Look at how much value they carry and who owns them. These deals are still counted in pipeline totals and coverage, which is the value of open deals due in a period compared with the target for that period.

### Close date history

Pull open deals with a close date in the past, then look at how many times each deal's close date has moved. Some CRMs keep this history automatically; others need a field or a report on property changes. A deal pushed forward several times without a stage change is usually a deal nobody wants to close out.

### Fields that are never filled

List the fields on the deal record and check how often each one is filled in on open deals. You'll usually find a few that leadership relies on, such as lead source or loss reason, sitting mostly empty, and others that were added once and never used. The first group affects reporting now. The second is clutter you can remove later.

### How reps use the CRM day to day

Sit with a couple of reps and watch how they work for a while. Where do they keep their notes? Do they update deals after each call or in a batch before the pipeline meeting? Do they have a spreadsheet of their own? This tells you more about data quality than any report.

The first thing I check is where each rep keeps their latest notes on a deal. When the answer is a notebook or their inbox, I know the CRM is being updated for the meeting, and the fields will be thin on the details buyers gave on calls.

## How do you talk to reps about it?

Talk to each rep about their own deals, one at a time, before you announce any changes. Ask them to walk you through their open pipeline and tell you which deals they'd stake their number on. Reps usually know which of their deals are stale. They've kept them open because closing them lowers their pipeline, or because nobody asked.

Make it clear the goal is a pipeline you can both defend to leadership. Reps are more open when they can see that a smaller, accurate pipeline is safer for them than a large one that misses. Ask what slows them down in the CRM, too. Their answers usually point at the fields to remove and the entry work to automate.

When I've inherited a pipeline, the reps who pushed back hardest on the cleanup were the ones carrying the most stale deals. Going through their deals with them, one by one, worked better than sending a list of deals to close.

## What should you fix first?

1. **Stage definitions.** Write exit criteria for each stage, agree on them with the team, and re-stage open deals against them.
2. **Past close dates.** Every open deal with a past close date gets a new date with a reason, or gets closed lost.
3. **Stale deals.** Agree on a rule for how long a deal can go without buyer activity, and close or revive what breaks it.
4. **Required fields.** Pick the few fields your reports depend on and make them required at the stages where they matter. Remove fields nobody uses.
5. **Automation for the rest.** Alerts for past close dates and stale deals, and call recording that writes next steps and buyer details to the record, so reps aren't retyping what the call already captured. [CRM data quality with AI](/blog/crm-data-quality-ai-agents) covers how to set those up.

Save a snapshot of the pipeline before and after the cleanup, so you can show leadership what changed and why the total moved.

## What can wait?

A new CRM, a new sales methodology and a rebuilt set of dashboards can all wait until the basics hold. Most of what an inherited pipeline needs is agreement on what stages mean and current dates on every deal. Once that's in place, forecasting gets easier; [improving forecast accuracy](/blog/improve-sales-forecast-accuracy) covers the next step, and [the first months as a new head of sales](/blog/new-head-of-sales-first-90-days) puts the audit in the context of the rest of the job.

---

NeuroGTM works with founders and sales leaders on CRM, data, reporting, sales process and automation, on a monthly retainer or one-off projects. Contact: https://neurogtm.com/#contact
