How to Rebuild Your CRM When You Hire a New VP of Sales

When a new VP of Sales walks in, the most expensive thing they inherit is not the comp plan, it's a CRM nobody trusts. In RevBlack's experience working with revenue teams across HubSpot and Salesforce, the same three issues consistently appear after a new VP of Sales hire: stale lifecycle stages that no longer reflect the actual sales motion, broken sales activity tracking that makes pipeline reviews a guessing game, and forecast reports the board has quietly stopped relying on. Companies that rebuild in the first 60 days typically see meaningful gains in forecast accuracy by the next board review. Here is the 60-day playbook to follow.

Why Does a New VP of Sales Always Need a CRM Rebuild?

A new VP of Sales inherits a CRM built for a sales motion that may no longer exist, and every decision they make in the first 90 days will be based on data from that broken system.

The CRM was configured by the previous leadership team, or a RevOps hire who left six months ago, or an admin who did their best without a clear brief. The pipeline stages reflect how deals moved two years ago. The lifecycle stage definitions were never agreed across marketing and sales. Activity tracking was optional, so half the reps logged nothing. The forecast is built on whatever the last VP told people to put in.

This pattern shows up repeatedly in CRMs that follow a leadership change. The new VP pulls the pipeline report on day one and immediately questions whether the numbers are real. That question, "can I trust this data?" is the signal that a rebuild is needed. The longer it goes unanswered, the more expensive it gets. Boards lose confidence. Reps lose time. Deals fall through gaps nobody can see because the system does not show them.

The rebuild is not optional. The only question is whether it gets done in the first 60 days or after the first missed forecast.

What Should a New VP of Sales Audit in the First 30 Days?

The first 30 days are diagnostic. The goal is a documented baseline, not a list of things to fix, but a clear picture of what the system is actually doing versus what it is supposed to do.

The first 30 days should cover five audit areas:

Pipeline stage integrity. Are deal stages enforced with exit criteria, or do reps move deals forward on discretion? A pipeline where deals advance without required fields populated or stage-specific activities logged cannot produce a reliable forecast. For the full opportunity stage architecture, see RevBlack's Salesforce opportunity stage flow guide.

Lifecycle stage accuracy. Do the lifecycle stages in HubSpot and Salesforce reflect where contacts actually are in the buyer journey, or are they defaulted, manually overridden, or simply wrong? Filter for contacts with unknown or undefined lifecycle stages. It is common to find a significant portion of active contacts in stages that no longer match their actual status.

Sales activity tracking. Are calls, emails, and meetings being logged against the correct contact and deal records? Pull a sample of 20-30 open deals and check how many have zero activity logged in the last 14 days. If the number is above 30%, activity tracking is not a habit, it is an aspiration.

Forecast accuracy history. Pull the last three quarters of forecast versus actual close data. If the variance is consistently above 20%, the forecast methodology is broken, not because of the model, but because the underlying deal data is unreliable.

Integration health. If HubSpot and Salesforce are both in use, check the sync error log. Silent sync errors are one of the most common causes of data discrepancies the new VP will encounter in the first few weeks. For the full integration audit, see RevBlack's HubSpot Salesforce integration guide.

Document every finding with a severity score: breaking revenue now, will break revenue within 90 days, or degrades performance over time. That scoring framework determines the fix sequence.

What Does a New VP of Sales Actually Need From the CRM?

A new VP of Sales needs three things from the CRM: a pipeline they can trust, activity data that tells them what their reps are actually doing, and a forecast they can present to the board without caveats.

Everything else is secondary. The VP does not need a perfectly configured marketing attribution model on day one. They do not need a custom NPS dashboard or a complex lead scoring algorithm. They need to be able to open the CRM on Monday morning, look at the pipeline, and know which deals are real, which are stalled, and which are at risk.

The minimum viable CRM for a new VP of Sales:

Pipeline with enforced stage definitions. Every deal stage has a clear definition, required fields, and at least one mandatory activity that must be logged before the deal advances. Reps cannot move a deal to Proposal Sent without a logged discovery call. They cannot move to Negotiation without a logged demo or technical review. The stage name is a label, the exit criteria is what makes it meaningful.

Activity tracking that logs automatically where possible. Email sequences logged via HubSpot Sequences or Salesforce Engage. Meeting outcomes logged via calendar integration. Call dispositions logged via telephony integration. Manual logging is a last resort every step that requires a rep to remember to log something is a step where data will be missing.

A clean contact-to-account association. Every contact associated with a company record. Every deal associated with both a contact and a company. Orphaned records, contacts with no company, deals with no owner, are invisible in account-based reporting and create blind spots in territory management.

A single forecast view the board can read. One report, one number, one methodology. Not a Salesforce report, a HubSpot report, and an Excel model that someone reconciles every Friday afternoon.

Owner assignment on every active record. Every open deal, every active contact, every company in the ICP (Ideal Customer Profile), assigned to an active user. Records owned by deactivated reps or left unassigned are invisible in rep-level performance reporting and do not appear in assignment-based routing. For the full routing setup, see RevBlack's automatic lead routing guide.

How Do You Fix Broken Lifecycle Stages in HubSpot or Salesforce?

Broken lifecycle stages are the most common root cause of the forecast accuracy problems a new VP of Sales inherits, and fixing them requires agreeing on definitions before touching any configuration.

Don't start a lifecycle stage rebuild by opening the CRM settings. The first step is a cross-functional definition session with the VP of Sales, the marketing lead, and the RevOps owner. The goal is to agree on four things for each stage: what a contact in this stage has done to get here, what a contact needs to do to move to the next stage, who owns the contact at this stage, and what the SLA is for follow-up.

Without that agreement, rebuilding the lifecycle stages just replicates the previous disagreement in a new configuration. For the full lifecycle stage architecture and implementation sequence, see RevBlack's lifecycle stage and lead management guide.

The lifecycle stage rebuild sequence:

1. Freeze stage changes during the rebuild window. No manual overrides, no automation updates, until the new definitions are agreed and documented.
2. Audit the current stage distribution. How many contacts are in each stage? What percentage have been in that stage for more than 30 days without a logged activity? This data reveals where the bottlenecks and dead zones are.
3. Agree on the new stage definitions and map them to observable CRM events, not rep judgment.
4. Build the automation that enforces stage transitions. Entry criteria trigger the stage change. Exit criteria require a logged activity or a field update before the next stage is available.
5. Backfill the current active contacts to the correct stage based on their most recent activity date and deal status.
6. Run the new lifecycle stage report for two weeks before presenting it to the board. Verify the numbers against what the VP of Sales knows to be true from direct rep conversations.

The backfill is the step most teams skip. Without it, the new lifecycle stage architecture applies to future contacts only, and the pipeline report continues to include legacy contacts in the wrong stage for months.

What Does Proper Sales Activity Tracking Look Like for a New VP?

Sales activity tracking is the data layer that tells a VP of Sales whether their reps are doing the right things, and whether those things are producing results. Without it, pipeline reviews are based on rep self-reporting rather than system evidence.

Activity tracking should cover four mandatory log types: calls with a disposition (connected, left voicemail, no answer), emails sent via sequence with open and reply tracking, meetings logged with an outcome (demo completed, follow-up required, no-show), and notes with a next step and a follow-up date. Every open deal should have at least one of these four activity types logged in the last 14 days. Any deal without recent activity is a stalled deal, regardless of what stage it is in.

The three activity tracking fixes to install first:

Telephony integration. Connect the sales team's calling tool (Kixie, Aircall, Salesloft, Outreach) directly to HubSpot or Salesforce. Calls log automatically with disposition and duration. Reps do not need to remember to log, the integration does it on their behalf.

Calendar integration. Connect Google Calendar or Outlook to the CRM. Meetings with contacts log automatically as activities against the contact and deal record. Meeting outcomes get logged via a post-meeting prompt, a required field the rep completes before the meeting record closes.

Required activity on stage advance. Configure the pipeline stage settings so that moving a deal to the next stage requires a logged activity of the correct type. A deal cannot advance to Proposal without a logged discovery call. This single configuration change produces more complete activity data than any training or enforcement effort.

How Do You Fix Forecast Accuracy in the First 60 Days?

Forecast accuracy is a data quality problem disguised as a methodology problem. The new VP of Sales does not need a better forecasting model, they need deal data clean enough to run any model reliably.

Forecast accuracy can be fixed in 60 days by addressing three root causes in sequence: stage integrity first, activity data second, close date discipline third.

Stage integrity. A deal in the wrong stage produces a forecast contribution that does not reflect reality. Every deal in the pipeline needs to be in the stage that matches its actual status, not the stage the rep put it in three weeks ago because they did not want it to look stalled. After the lifecycle stage rebuild described above, pull every open deal and validate its current stage against the most recent logged activity. Any deal where the stage does not match the activity history gets corrected before the next forecast run.

Activity data. A forecast model that weights deals by stage and probability is only as accurate as the activity data behind it. Deals with no logged activity in 14 days get a probability penalty, automatically, via a workflow that reduces the forecast contribution of stale deals until a rep logs a qualifying activity.

Close date discipline. The most common forecast inflation is deals with close dates that have already passed and were never updated. Build a workflow that flags any open deal with a close date more than 7 days in the past and routes an automated task to the deal owner to update or close. This single automation eliminates the most common source of forecast inflation in most inherited CRMs.

With these three fixes in place, most teams move from forecast accuracy below 70% to above 85% within 60 days, not because the model changed, but because the underlying data is finally reliable.

When Should the New VP Rebuild vs Replace the CRM Entirely?

Rebuild in 90% of cases. Replace only when the platform itself is the constraint, not the configuration.

CRM replacement is proposed far more often than it is warranted. The logic is understandable: the new VP inherits a CRM that feels broken, assumes the platform is the problem, and proposes a migration to something new. But in most cases, the platform is fine. The configuration, the data, and the governance are the problems, and those travel with you to the new platform.

The conditions that justify replacement:

• The current platform cannot support the sales motion the new VP is building. A product-led growth motion that requires deep product telemetry integration may outgrow HubSpot's native capabilities. An enterprise sales team running multi-stakeholder deal management may need Salesforce's object model.
• The current platform has been so heavily customized that rebuilding on the existing configuration would take longer than a clean migration.
• The company is running more than two CRM instances from prior acquisitions and consolidation is the strategic priority.

In every other case, rebuild. A CRM migration takes 6-12 months, disrupts active deals, and resets the data history the new VP needs to understand the business. A rebuild takes 60-90 days and preserves the historical data while fixing the structural problems.

What Are the Three Things NOT to Change in the First 90 Days?

Moving fast is important. Moving fast on the wrong things destroys credibility with the board and disrupts active pipeline.

A new VP of Sales should hold three things stable in the first 90 days while the rebuild is in progress.

The compensation structure. Comp plan changes during an active rebuild destabilize rep behavior at exactly the moment when consistent activity data is most important. If the comp structure needs to change, plan it for the start of the next quarter, after the rebuild is complete and activity baselines are established.

The closed-won definitions. Changing what counts as a closed-won deal mid-quarter invalidates the historical data the forecast is built on. The new VP needs at least one full quarter of clean closed-won data under the new stage definitions before comparing against prior performance.

The reporting cadence. Weekly pipeline reviews, monthly forecast calls, quarterly board reporting, keep the cadence the board and the team are accustomed to. The rebuild will produce better data for those meetings. Changing the cadence at the same time as the data model creates confusion about what changed and why the numbers look different.

How Do You Measure Success? Which KPIs Prove the Rebuild Worked?

A CRM rebuild is an investment. It needs a measurement framework that shows the board what changed and what it produced.

Five KPIs measure the success of a CRM rebuild after a new VP of Sales hire:

Forecast accuracy: variance between forecast and actual close at the end of the quarter. Target: below 15% variance within 60 days of rebuild completion.

Pipeline stage velocity: average time in each deal stage before advancing or closing lost. A rebuild that enforces exit criteria typically reduces average time-in-stage within the first quarter as stalled deals either advance or get properly disqualified.

Activity coverage rate: percentage of open deals with at least one logged activity in the last 14 days. Target: above 85% within 30 days of the activity tracking fixes going live.

Lifecycle stage accuracy: percentage of active contacts in a defined lifecycle stage. Target: below 5% in unknown or undefined stages within 45 days of the lifecycle rebuild.

Data completeness on required fields: percentage of open deals with all required fields populated (close date, amount, owner, stage, account association). Target: above 95% within 60 days. For the full audit framework RevBlack uses to establish these baselines, see the RevOps audit roadmap.

Report these five metrics in the first board review after the rebuild. The board does not need to understand the technical work, they need to see that forecast accuracy is up, pipeline is moving, and the numbers can be trusted. These five metrics tell that story.