The First 90 Days of a VP Sales (What Actually Matters)

I've run the first 90 days of a VP Sales job twice. Once it went well. Once I nearly torched the pipeline in week three by ripping out a sequence that offended my sense of how outbound should look. It was quietly booking meetings. I killed it anyway. Both runs taught me the same lesson: the first 90 days of a VP Sales aren't about strategy. They're about proving the revenue motion can survive without one person carrying it on their back.

So here's the short version. The first 90 days of a VP Sales should do three things: diagnose why pipeline is or isn't converting, fix the single bottleneck costing the most money, and build a motion the team can run without heroics. Skip the 30-page strategy deck. Ship one repeatable win by day 90.

Now the uncomfortable backdrop. The average VP of Sales lasts somewhere around 17 to 19 months in the seat, according to Gong's tenure data — turnover that runs several times faster than most other executive roles. Founders read that number and assume the fix is hiring better. Usually it isn't. The job gets scoped as "own revenue" with no working system underneath it, so every quarter rides on a single person's stamina. Hire a stronger person and you've just bought a stronger version of the same dependency.

What most founders get wrong about the first 90 days

Most 30/60/90 plans are theater. Learn the product in month one. Shadow calls in month two. Own quota in month three. Tidy. Also close to meaningless, because it measures activity instead of the one thing that matters: where does a qualified lead actually die?

Here's what most people get wrong. They treat the first 90 days as a learning period. It isn't. It's a diagnosis period with a hard deadline. If a new sales leader can't point to one fixed leak and one repeatable source of pipeline by day 90, they haven't been onboarding. They've been decorating.

Days 1 to 30: diagnose, don't rebuild

The strongest urge in month one is to rebuild everything. Resist it. You don't have the context yet, and the thing you're itching to rip out might be the thing that's working. Ask me how I know. In my second run I killed a warmed-up sequence in week three because it looked ugly to me. It had been booking calls. Don't be that person.

Month one is for reading the funnel end to end. How many contacts get worked, how many reply, how many book, how many close, and where the biggest drop-off sits. Small numbers move everything downstream. Across our campaigns a 6% reply rate on cold HVAC outreach was the whole difference between a full calendar and a dead one. You can't fix what you haven't measured, and most teams have never actually measured their own drop-off honestly.

Days 31 to 60: fix the one bottleneck

You'll find five things broken. Fix one. The single biggest leak, the one where money is visibly leaving the building. Trying to fix all five at once is how new leaders spread themselves thin and hit day 90 with nothing shippable. One bottleneck, before-and-after numbers, done. For a lot of teams the leak is ramp itself — SaaS ramp time has stretched to roughly 5.7 months in some 2025 benchmarks, per Lative's ramp data, largely because reps get handed a patch of territory and told to invent the motion themselves. Your month-two job is to remove that invention tax so a new rep can follow a path instead of cutting one.

Days 61 to 90: make it repeatable without you

By day 90 the test is embarrassingly simple. Can the motion run for a week while you're on a plane with no signal? If the answer is no, you built a dependency, not a system.

This is where founders get burned twice. They hire a VP. The VP builds something that only works when they're in the room. The VP leaves at month 18, right on the tenure average, and the pipeline walks out with them. Now you're re-hiring and rebuilding the exact same fragile thing.

It's why I stopped selling "a person" and started building outbound that lives in your stack, with full system access and no lock-in. When the system produces the meetings, the motion doesn't leave when someone does. A VP running that kind of setup spends their first 90 days tuning an engine, not becoming a single point of failure. If you want an outside read on which one you're actually missing, book a free GTM audit and I'll tell you straight.

The 90-day scorecard I'd actually use

Forget the activity checklist. By day 90 I'd want to see four things, and nothing else:

• One documented, repeatable source of pipeline that isn't "the VP's personal network."
• A named bottleneck fixed, with real before-and-after numbers next to it.
• Rep ramp measured in weeks, not vibes.
• A forecast the team believes, not one the VP has to defend alone in the room.

Hit those four and the tenure statistics stop being your problem. Miss them and no amount of month-four strategy will save the hire.

Frequently asked questions

What should a VP of Sales do in the first 90 days?

Diagnose the funnel in month one, fix the single most expensive bottleneck in month two, and make the winning motion repeatable without them by month three. One shippable, documented win beats a polished strategy deck every time.

What are realistic 90-day goals for a new VP of Sales?

One repeatable pipeline source, one fixed leak with numbers attached, a measurable rep ramp, and a forecast the team actually trusts. Notice none of those is "hit the annual number." That comes later, and only if the first four are real.

Should a new VP of Sales change the sales process right away?

No. Month one is for diagnosis, not demolition. Rip out too early and you risk killing something that quietly works. Measure first, then change the one thing the data tells you is bleeding the most.

How do you measure a VP of Sales in the first 90 days?

On whether the motion runs without them. If pipeline dries up the week they're offline, the score is low regardless of how busy the quarter looked. Repeatability is the real metric.

Why do so many VP of Sales hires fail?

Because they're hired to "own revenue" with no working system underneath, so success depends on personal effort that can't scale or survive their exit. Fix the system design and the failure rate drops on its own.

Do I need a VP of Sales or an outbound system first?

If your motion isn't diagnosed yet, a system usually beats a six-figure hire. A VP is worth it once there's an engine to tune. Dropping a leader onto a blank page is how you burn 18 months and a salary finding out what you could have tested in a quarter.

How long before a VP of Sales generates real pipeline?

Expect the first repeatable pipeline signal inside 60 to 90 days if the motion is being fixed rather than invented from scratch. If they're building the entire motion from zero, budget closer to five or six months, and plan for it honestly instead of pretending it'll be quicker.

Where to start

If you're about to spend six figures on a VP Sales to fix a motion you haven't diagnosed, run the diagnosis first. Before you sign anything, read what a £45k SDR actually costs and the honest comparison of outsourced SDRs versus AI. If you'd rather just see numbers, pricing is here. Either way, decide whether you're buying a person or building a system before the offer letter goes out.