Inheriting a Sales Pipeline: The New AE Audit Checklist

You start your new AE role on a Tuesday. By Thursday, you have CRM access.

You open the pipeline view, sort by close date, and count 14 open deals assigned to you. The previous rep left three weeks ago. You scan the list.

Nine of the 14 have close dates in the past. Two more are marked at 90 percent probability but show no logged activity since February. The three remaining ones look current, but when you open the records, the notes field says "great call" or "following up soon."

This is not an unusual situation. B2B sales teams see roughly 30 percent annual AE turnover. On a 10-person team, that means three pipeline handoffs per year. Each transition is a version of this same problem: a new person staring at deals they did not build, trying to figure out which ones are real.

The audit below is the systematic approach. Work through it before you make a single outreach call.

Why Inherited Pipeline Data Is Almost Never Accurate

Understanding the problem makes the audit make sense.

CRM data reflects what a rep found worth logging, not what actually happened in a deal. Most reps log meetings when they remember to, copy in email threads selectively, and update close dates to match what the prospect said on the last call, even when that date was clearly aspirational.

CRM data also decays. Contact details, job titles, and budget authority all shift over time. At a typical decay rate of 22 to 30 percent per year, a record that was accurate when created is a materially different picture 12 months later.

When a rep leaves, the tribal knowledge they carried goes with them: which stakeholder actually drives budget decisions, why a deal has been dormant for six weeks, whether a prospect said privately they were evaluating another vendor. That context was never in the CRM. Now it is nowhere.

The incoming rep inherits a list that looks active but tells them almost nothing useful about the real state of each opportunity.

The Day-One CRM Audit

Do this before you send any emails or make any calls. Making outreach decisions on unaudited data is how you burn a prospect relationship on a deal that was already progressed before you arrived.

Pull the full deal list

In HubSpot, go to Sales, then Deals, filter by Owner set to you (or your predecessor's name if records have not been reassigned yet), and export to a spreadsheet. In Salesforce, build an Opportunity list view filtered by Owner and set it to include Closed Won and Closed Lost so you can see the full history, not just Open.

Do the same in Pipedrive under Pipeline, then All Deals.

You want every deal, not just the open ones. Seeing what closed recently and how it closed tells you what this territory actually produces.

Tag each deal into four categories

Go through the list record by record and assign each deal to one of four buckets.

Active. The deal has logged activity in the past 30 days AND at least one response from the prospect side: a reply, a meeting attended, a document opened, a question sent back. These are the deals you pick up immediately.

Dormant. The deal had real motion at some point, but the last logged activity is 31 to 90 days old, or the last activity is outbound only with no prospect response. These are worth one re-engagement attempt with a soft touchpoint.

Zombie. The deal has a close date that has already passed, no logged prospect engagement in 90 or more days, or a stage that clearly does not match the activity history. These get closed lost in the CRM after one honest re-engagement attempt. A bloated pipeline with dead deals is worse than an accurate smaller one.

Territory base. Accounts with no active deal but some prior engagement history in the CRM. These are prospecting candidates for the next phase.

Most inherited pipelines break down roughly as 20 to 30 percent Active, 30 to 40 percent Dormant, and 30 to 40 percent Zombie, with the rest as Territory base. The distribution depends on how disciplined your predecessor's logging was, but it is rarely more favorable than this.

Check the activity log on every Active and Dormant deal

For each deal you tagged as Active or Dormant, click into the activity log and answer three specific questions:

1. What was the last thing the prospect did? Not what the rep did, but what the prospect did: replied to an email, showed up to a meeting, asked a follow-up question.
2. What is the documented next step?
3. Who is the named decision-maker or economic buyer?

If you cannot answer all three from the CRM record, the deal is Dormant at best and possibly Zombie. An Active deal has a named buyer, a documented next step, and evidence of recent prospect engagement. Anything short of that is a deal you are going to have to rebuild from scratch.

How to Re-Engage Inherited Prospects Without Burning the Relationship

The most common mistake new AEs make is reaching out as if they already know the prospect. They write something like "just wanted to check in on where things stand with the project" with no indication they are a new person. The prospect, if they respond at all, wonders who this is.

Do not do that.

Make the handoff visible from the start. Your opening outreach for any inherited deal should do three things.

Introduce yourself clearly. "I am [name], and I am taking over [predecessor's name]'s accounts as they have moved to a different role" is honest and immediately sets context.

Reference something specific. "I saw in our notes that you were evaluating [problem area] back in [month]" shows you have reviewed the record and are not starting from zero.

Make it easy to say no. "If the timing has shifted since you last spoke with [predecessor], I completely understand. Would a quick 15-minute catch-up be useful, or should I check back in [timeframe]?" Giving prospects an honest exit reduces the sense that they are being chased by a sales machine that does not know their situation.

This framing works for Dormant deals. For Zombie deals, lower your expectations. You are prospecting, not resuming. Treat the contact as cold outreach with the light advantage of a prior conversation on record.

The Internal Handoff Step You Control

Even with poor CRM records, there is one resource you should use before the departing rep loses access: a 15-minute knowledge-transfer call per Active deal.

Ask your manager to schedule these conversations while the rep still has access (the sales rep offboarding checklist covers the manager-side process for extracting this context). Come to each call with the deal record open and ask:

• Who is the actual decision-maker, not just the main contact listed in the record?
• What is the real reason the deal is stalled or slow?
• What has been promised or implied that is not in the notes?
• What does the prospect think happens next?

Take notes during the call and paste them immediately into the CRM record. If your predecessor is already gone, work backward from their email history. Your IT team can provide read access to a departed rep's Google Workspace or Microsoft 365 account for a limited period for business continuity. Pull the threads on each Active or Dormant deal and extract the same answers where the history reveals them.

What Good Inherited Pipeline Data Looks Like

Here is what makes this entire audit much faster: when a rep's email and calendar activity has been captured continuously throughout their tenure, a new AE can review the full deal history without doing archaeology.

You should be able to open a deal record and find a complete log of every email thread, every meeting that happened, and a summary of what was discussed. You should be able to ask a plain question about any account and get an accurate answer from the deal history, without searching through the rep's sent folder or trying to reconstruct what was said months ago.

That kind of pipeline visibility requires that activity capture happened throughout the rep's time on the account, not just at the moment of handoff. When it does, the 30 to 60 minutes you just spent doing a manual CRM audit compresses into a quick read of a deal timeline. When it does not, you spend your first two weeks on data archaeology instead of advancing opportunities.

Building Your First 30-Day Plan from the Audit Output

Once the audit is complete, your first-30-days pipeline plan writes itself.

Active deals get a re-introduction email this week. Dormant deals get a sequenced touchpoint starting next week, using the honest re-engagement framing above. Zombie deals get one outreach attempt and then get closed lost if there is no response within two weeks. Territory base accounts go into a prospecting list for weeks three and four.

The average AE ramp time in 2026 is 5.7 months, up 32 percent since 2020. A meaningful portion of that extended ramp is time spent figuring out which inherited deals are worth investing in. If you do the audit in week one, you compress that learning curve and know within your first month what your real pipeline actually is.

That is a much better outcome than discovering in month three that the 14 deals you were counting in your forecast were actually four real ones, six dormant ones, and four zombies.

After the Audit: Closing the Loop on Data Quality

The habits that make this audit hard, sparse notes, missing next steps, unlogged activity, are the same habits that will make the next new AE's life difficult when you eventually move on or take on a different territory.

The practical fix is not asking reps to log more manually. The fix is capturing activity automatically so the record grows without anyone having to remember. Reviewing how to automatically log sales activity to your CRM and how to sync email to your CRM automatically gives you the setup options that work with HubSpot, Salesforce, and Pipedrive.

When activity capture runs in the background, your CRM becomes a real record of what happened in every account from the first touch forward. That is what an inherited pipeline should look like. It is also what keeps CRM data hygiene from being a recurring manual exercise: automatic capture makes the records self-maintaining rather than dependent on rep discipline.

The irony of a bad inheritance is that it is almost entirely preventable. Build the capture infrastructure now and the next person who inherits your pipeline will find something that tells the full story.

Frequently Asked Questions

What should a new AE do with an inherited pipeline on day one?

Pull a CRM report of all open deals assigned to you or your predecessor, sorted by close date. Flag every deal with no activity in the past 45 days and every close date that has already passed. Those two filters surface most of the dead weight before you invest any relationship capital.

How do you tell which inherited deals are worth pursuing?

A deal is worth pursuing if it has a named decision-maker, a documented next step, and at least one piece of evidence that the prospect engaged recently: a reply, a meeting attended, or a logged call. Deals with only outbound activity from the previous rep and no prospect response are dormant until proven otherwise.

How do you re-engage a prospect you inherited from another rep?

Be transparent: introduce yourself by name and role, acknowledge the handover, and reference something specific from the previous conversation to show continuity. Prospects who sense a rep swap without explanation often assume the deal has gone cold, and many will quietly deprioritize it.

Why is inherited CRM pipeline data unreliable?

CRM data reflects what a rep found worth logging, not what actually happened. Most reps log selectively, leave next step fields blank, and update close dates optimistically. When a rep departs, whatever context they carried about each account leaves with them, and the CRM record is often a snapshot from the last time they felt like updating it.

How long does it take a new AE to get up to speed on inherited deals?

The average AE ramp time in 2026 is 5.7 months across the industry. Inheriting a pipeline with accurate CRM data shortens that window because the new rep can focus on deals rather than data archaeology. Inheriting a pipeline with sparse, stale records extends it significantly.