Common Sales Pipeline Mistakes and How to Avoid Them

Ten pipeline mistakes that quietly wreck forecasts, from stale close dates and zombie deals to partner deals nobody can see, with what each looks like and how to fix it.

May 28, 2024 · By Joseph Lamoureux

Common Sales Pipeline Mistakes and How to Avoid Them

Most pipeline problems aren’t dramatic. Nobody deletes the CRM or loses the biggest customer overnight. Instead, small habits pile up until the pipeline says one thing and reality says another, and nobody notices until the quarter ends short.

Here are ten of the most common, what each one looks like, and how to fix it.

1. Deals with no next step

What it looks like: open deals where nobody can say what happens next, who’s doing it or when.

Why it hurts: a deal with no next step isn’t being worked. It’s waiting to go cold.

The fix: make “every open deal has a next step with an owner and a due date” a rule, and check it in every review. In Recordbook, action items turn yellow within seven days of their due date and red within three, so missing and overdue next steps are hard to miss. See sales action items.

2. Close dates in the past

What it looks like: deals that were “closing in March” in May.

Why it hurts: every past close date is either a win nobody recorded or a slip nobody admitted. Either way, the forecast is wrong.

The fix: sort the pipeline by close date once a week and fix every date in the past before the review starts.

3. Happy ears

What it looks like: confidence set at 80% after one good meeting. Deals marked “commit” without a confirmed budget.

Why it hurts: an optimistic forecast feels good until it misses, and then nobody trusts the pipeline.

The fix: tie stages to customer actions, write down what each confidence level means, and compare forecast with actual results each quarter. If the forecast consistently runs high, recalibrate.

4. Never closing lost deals

What it looks like: a pipeline that only grows. Deals from last year still “in discovery.”

Why it hurts: zombie deals inflate the pipeline, flatter the win rate and hide how much new pipeline you actually need.

The fix: if a deal has had no customer response in three weeks and no next step, close it as lost. You can always reopen it if they come back.

5. Stages defined by your activity

What it looks like: deals move to “Proposal” when the proposal is written, whether or not the customer has seen it.

Why it hurts: your activity doesn’t predict revenue; the customer’s commitment does. Activity-based stages make the pipeline look further along than it is.

The fix: define exit criteria in terms of what the customer has done. The guide to pipeline stages has examples for each stage.

6. One big deal hiding a thin pipeline

What it looks like: a healthy total that’s mostly one or two large deals.

Why it hurts: if the big deal slips, the quarter goes with it.

The fix: look at the number of qualified deals as well as their value, and plan coverage without counting the single largest deal. If the plan only works with it, you need more pipeline.

7. The pipeline lives in several places

What it looks like: the CRM says one thing, the spreadsheet another, and the real status is in someone’s inbox.

Why it hurts: time goes to reconciling versions instead of selling, and every report starts with an argument about which number is right.

The fix: one place where deals live, and a rule that if it isn’t there, it doesn’t count. For deals you work with a partner, that means a record both companies share. Recordbook connects your CRM and your partner’s to one shared workspace for exactly that reason.

8. No record of who sourced the deal

What it looks like: end-of-quarter debates about whether a partner brought the deal in or just joined the call.

Why it hurts: credit disputes sour partnerships, and you can’t tell which partners or channels are actually producing revenue.

The fix: record the source and the originating person on every deal when it’s created, and keep dated notes. For AWS co-sell, dated evidence is also what protects a deal’s “sourced” status in ACE; see the AWS ACE guide.

9. Reviewing the pipeline monthly

What it looks like: a big pipeline meeting at the end of each month, and nothing in between.

Why it hurts: by the time a monthly review spots a stalled deal, it’s often too late to save it.

The fix: a short weekly review with a fixed agenda. How to improve sales pipeline management has a 30-minute version.

10. Measuring everything, acting on nothing

What it looks like: dashboards full of charts that nobody uses to make a decision.

Why it hurts: time spent building reports is time not spent on deals, and important signals get lost in the noise.

The fix: pick a few metrics (coverage, win rate, cycle length, deal size) and review them the same way every month. Sales pipeline metrics explains which ones matter and how to read them together.

A five-minute pipeline health check

How many open deals have no next step?
How many have a close date in the past?
How many haven’t changed in longer than your average sales cycle?
What share of the pipeline is your single largest deal?
How many deals are missing a source?

Each answer above zero (or above a third, for question 4) is a mistake from this list, waiting to show up in the forecast.

Common questions

How do I clean up a messy pipeline?

Do it in one sitting: close every deal that’s dead, fix every close date in the past, add a next step to every open deal, and fill in missing sources. Then keep it clean with a weekly review.

Is it bad to close a lot of deals as lost?

No. Closing dead deals makes your numbers honest and frees time for deals that can close. A pipeline where nothing is ever lost is the warning sign.

Try it on your own pipeline

Recordbook is free to start. Every feature is on every plan, and adding your team or your partners costs nothing extra. Create your free workspace.