The Cycle Everyone Pretends Is Normal
Here’s the SaaS VP of Sales lifecycle. See if this sounds familiar.
Months 1-3: The honeymoon. New leader comes in with a playbook from their last company. The board is optimistic. The team is cautiously hopeful. There’s talk of “new energy” and “fresh perspective.” The VP does a listening tour. Makes some quick changes. Maybe fires a low performer to signal seriousness.
Months 4-8: The reality. The playbook from the last company doesn’t quite fit. The product is different. The market is different. The team is different. The VP starts building their own plan, which looks suspiciously like a slightly modified version of the last plan. Pipeline looks okay. Deals are moving. The forecast says the quarter will be close.
Months 9-14: The slide. The quarter misses. Then the next one. The VP blames ramp time, market headwinds, product gaps. Some of that is true. Most of it is the same set of excuses the last VP used. The board starts asking questions that aren’t really questions. “What’s your plan to accelerate pipeline?” means “we’re losing confidence in you.”
Months 15-18: The exit. Mutual decision. Parting ways. Grateful for their contributions. Already sourcing the replacement.
Then you do it again.
SaaS companies treat this cycle like weather – something that happens to you, not something you’re causing. But it’s not weather. It’s architecture. And until you fix what’s actually broken, the next VP will follow the same trajectory as the last three.
Why The Job Is Impossible
The SaaS VP of Sales inherits three problems that have nothing to do with their ability to lead a sales team.
Problem one: they inherit a pipeline they didn’t build and can’t trust. Day one, there’s a CRM full of deals at various stages. The new VP has no idea which of those deals are real. They can’t verify the stage assignments because the stage definitions were set by their predecessor and mean whatever each rep decided they meant. They’re being asked to forecast revenue against a pipeline they’ve never touched, using criteria they didn’t establish, populated by reps whose judgment they haven’t assessed. So they do what every new VP does – they trust the data in the system and hope for the best. By month six, they realize the pipeline was 40% fiction. But by then they’ve already committed those numbers to the board.
Problem two: they’re expected to bring a methodology but not allowed to change the system. Every SaaS VP of Sales hire is sold on the idea that they’ll “transform the revenue org.” In practice, transformation means implementing their preferred sales methodology while working within the existing CRM configuration, the existing comp plan structure, the existing territory model, and the existing reporting cadence. They’re being asked to renovate a house but told they can’t touch the foundation, the plumbing, or the electrical. So they change the paint – new talk tracks, new meeting cadences, new forecast templates – and wonder why the house still leaks.
Problem three: nobody defined what success actually requires. The board wants revenue growth. Obviously. But the conditions required to produce that growth – honest pipeline, qualification rigor, process discipline, forecasting accuracy – take six to nine months to build in a SaaS org of any complexity. The VP has eighteen months before the board gets restless. That’s barely enough time to diagnose the problems, let alone fix them. So the VP optimizes for short-term numbers instead of long-term systems, which produces a temporary lift that collapses the moment they stop personally driving deals. Which is exactly when the board decides it’s time for a change.
The Uncomfortable Truth About The Talent
Here’s what nobody says in the SaaS VP of Sales postmortem: most of these leaders aren’t bad. Some of them are exceptional. They’ve built revenue organizations at companies you’d recognize. They’ve hit numbers that would make your board weep with joy. And they still fail in your company. Repeatedly.
That should tell you something. When three consecutive experienced revenue leaders fail in the same role, the role is the problem. Not the people. The job description says “VP of Sales” but the actual requirement is “fix a broken revenue system, install a new operating methodology, retrain the team, rebuild the pipeline, reconfigure the CRM, redesign the comp plan, and deliver 40% growth – all in your first year, with no additional headcount and a board that reviews your pipeline weekly.” Nobody can do that. Nobody should be expected to.
But SaaS companies keep posting the same job, running the same search, hiring the same profile, and getting the same result. Then they blame the hire. It’s like blaming the pilot when the plane has no engine.
What Actually Needs To Change
Stop hiring a person and start installing a system.
The SaaS VP of Sales fails because they’re brought in to be the system. Their playbook is the methodology. Their judgment is the forecast. Their relationships are the pipeline strategy. When they leave, all of it leaves with them. The next VP starts from zero – not because the company lost a leader, but because the company never had anything that existed independently of the leader.
A revenue operating system is the infrastructure that persists regardless of who’s sitting in the VP chair. It defines what a qualified deal looks like – not in theory, but in specific, documented, verifiable criteria that every rep and every manager can apply consistently. It defines what stage progression means in terms of buyer commitments, not seller activities. It defines how forecast accuracy is measured, how pipeline health is monitored, and how coaching happens at every level.
With that system in place, the VP of Sales has a job they can actually succeed at. They’re leading a team that runs on a defined process, managing against metrics that mean something, and forecasting against data that reflects reality. They can focus on strategy, coaching, and execution instead of spending their first six months trying to figure out what’s broken and their last twelve months trying to fix it before the board runs out of patience.
Without that system, you’re not hiring a VP of Sales. You’re hiring an eighteen-month placeholder who’ll absorb the blame for a structural failure that existed before they arrived and will persist after they leave.
The Math Nobody Does
Let’s talk about what this revolving door actually costs a SaaS company.
VP of Sales compensation: $250-350K base plus bonus. Recruiting fee: 25-30% of first year OTE, so roughly $100K. Ramp time: two to three months of below-target performance from the entire team while the new leader assesses, plans, and implements. Productivity loss during the transition: conservatively 15-20% of the team’s quarterly output.
Run those numbers across three VP hires in five years – which is below the SaaS industry average – and you’re looking at $1.5-2M in direct costs. Add the opportunity cost of three separate ramp cycles, three separate methodology implementations, three separate “listening tours” where the team stops selling and starts auditioning for the new boss, and you’re closer to $3-4M. In a SaaS company doing $20M ARR, that’s 15-20% of annual revenue burned on a hiring strategy that keeps producing the same outcome.
For a fraction of that cost, you could install a revenue operating system that makes the VP role achievable. But that requires admitting something SaaS boards don’t want to hear: the problem isn’t the people you’re hiring. It’s the job you’re asking them to do.
The Question To Ask Before You Post The Job
Before you engage your next executive recruiter, before you write another job description promising “ownership of the entire revenue function,” before you tell your board you’ve found someone “transformational” – ask yourself one question.
If your next VP of Sales quit tomorrow, what system would continue operating without them?
If the answer is “nothing” – you don’t need a new VP. You need the thing that makes a VP successful.
I help B2B companies fix the revenue systems that legacy methodologies broke. If something in this post made you uncomfortable, it was probably the part that's true. Stop the bleeding.
