Why first VP of Sales hires fail in SaaS
There is a pattern that repeats itself often enough in early-stage SaaS that it has become almost predictable. A founder-led business reaches a point where the sales function is clearly outgrowing what one person can manage. The founder raises a round, decides the answer is senior sales leadership, and makes the hire. Not long afterwards, the VP is gone, the pipeline is still unpredictable, and the postmortem focuses on whether they picked the wrong person.
The person question is rarely wrong. It is just rarely the whole answer.
The first VP of Sales is usually hired for the wrong job
The difference between a sales leader and a sales system builder
A VP of Sales, at their best, brings operating discipline. They can read a pipeline and spot deal patterns. They know how to run a forecast call, coach discovery, and manage a team through a difficult quarter. What they are not, by training or by reasonable expectation, is the person who builds the commercial system from scratch while simultaneously delivering the numbers that justify their own salary.
Those are two different jobs. The first is leadership. The second is architecture. Hiring a senior sales leader into a company with no defined sales architecture and expecting both outcomes is the source of most first VP failures.
Why founder expectations are often too broad
When a technical founder decides to hire a VP of Sales, the mental model is often something like: “I will hand this person the revenue problem and they will solve it.” That framing is understandable; it is also how you set someone up to fail.
The mandate becomes: build the pipeline, manage the reps, clean the CRM, formalise qualification, define the ICP, build a forecast model, improve conversion, hire more people, and report progress weekly. That is not a sales leadership role. It is an undefined rescue mission, and senior hires rarely survive one intact.
According to Harvard Business Review, the average CRO tenure is just 25 months. Short tenure at the top of the sales function is not a coincidence – it reflects, in part, the conditions those leaders are hired into.
The hidden failure point: no sales operating model
What the VP inherits when the system is undefined
In most founder-led SaaS companies, the sales process lives in the founder’s head. ICP decisions are made case by case, qualification is informal, pricing exceptions are negotiated deal by deal. CRM stages describe what the rep hopes will happen, not what the buyer has actually done. There are no documented handoff rules between marketing and sales, no shared definition of a qualified opportunity, and no management cadence the team has internalised.
When a VP steps into this environment, they do not inherit a sales function. They inherit a set of individual behaviours and founder instincts that have never been written down, tested against a broader team, or made repeatable.
The VP then faces a choice: start building the system, which takes time and produces little immediate pipeline, or try to drive performance through the existing motion, which reinforces the same undisciplined patterns. Neither produces a quick win, and both get judged faster than is reasonable.
It is worth noting what this costs. According to Pavilion’s 2024 compensation data, median annual OTE for sales function executives is $375,000. A failed hire at that level, including severance, recruitment fees, and the time spent recalibrating, represents a significant drag on a company still burning through its Series A or B.
Why activity can increase while performance stays unclear
One of the more confusing outcomes of a VP hire is that activity visibly increases but results remain opaque. The VP introduces weekly pipeline reviews. The team starts logging calls. There are more opportunities in the CRM. But forecast accuracy does not improve, quota attainment stays inconsistent, and the founder still cannot answer the question: is this working?
The reason, almost always, is that the activity increase is real but the signal quality is not. Pipeline stages are still based on rep optimism rather than buyer evidence. Deals move forward because someone decided they should, not because a clear qualification criterion was met. The CRM records volume, not decision quality.
You cannot manage a sales team accurately from a CRM that logs activity rather than commercial progress. A VP cannot improve what has not been defined.
Five reasons first VP of Sales hires fail
These are not independent failures. They usually stack.
The mandate is vague. “Own revenue” is not a mandate. It is a proxy for not having thought through what the role actually requires in the early period. A VP hired without a clear scope tends to prioritise what feels urgent over what is architecturally important, and gets measured inconsistently as a result.
Founder judgement is still trapped in founder-led sales. A VP implements a qualification standard. The founder continues joining late-stage calls and changing deal strategy case by case. The team watches this, draws the obvious conclusion that the process does not actually apply, and continues operating the way they always have. The VP cannot build consistency in a system where exceptions are still made by someone with more authority than the process. If this dynamic feels familiar, the article on when founder-led sales stops scaling covers the underlying transition in more detail.
The CRM records activity, not decision quality. This is worth restating because it is consistently underestimated. A VP who inherits a CRM full of optimistically staged deals has no reliable starting point. They cannot identify where conversion is actually breaking, which reps need what kind of coaching, or which deals are real. The first months are often spent trying to understand what is actually in the pipeline, not managing it.
The team has no shared qualification standard. Two reps performing differently under the same VP is not automatically a coaching problem. Before drawing that conclusion, it is worth asking whether both reps are working the same ICP, using the same qualification logic, and advancing deals by the same criteria. Often they are not, because no such standard existed before the VP arrived and has not yet been formalised since. The performance difference may have nothing to do with capability. This is the same diagnostic question explored in the piece on whether the problem is the salesperson or the sales system.
The VP is judged before the system can produce signal. The Bridge Group’s SaaS benchmarks show that average AE ramp time is 5.7 months. A VP hired to improve a team’s performance, redefine process, and build pipeline is being judged on a system with at least one full ramp cycle of lag built into it. Judgements made early are often measuring the environment they inherited, not the change they introduced.
How to tell if the issue is the VP or the architecture
This is the right diagnostic question, and it is not always easy to answer from inside the company.
Look for repeatable patterns rather than isolated misses. If forecast accuracy is low, ask whether the problem is consistent across all reps or concentrated in specific deal types or segments. If pipeline is thin, ask whether the sourcing strategy was defined before the VP arrived or left to them to figure out. If conversion from discovery to proposal is weak, ask whether the discovery framework was documented before the hire was made.
A leadership gap and an operating model gap produce similar-looking symptoms: inconsistent performance, unpredictable pipeline, rep behaviour that varies too widely. The difference is that a leadership gap shows up in the VP’s specific decisions, in how they run a call or coach a rep; an operating model gap shows up everywhere, uniformly, because there is no shared infrastructure for the team to operate against.
Separating the two matters before making a people decision. Replacing the VP without fixing the architecture usually produces the same failure cycle with a different person at the centre.
What to build before or alongside the hire
The question is not whether to hire a VP of Sales – for most scaling SaaS companies, senior sales leadership is necessary. The question is whether the company has created a role that a capable person can actually succeed in.
That requires a clear sales architecture: defined pipeline stages that reflect buyer progress rather than rep hope, qualification criteria the whole team uses, an ICP the founder has written down and is willing to hold to, a CRM that captures decision quality rather than just activity, and a management cadence that works without the founder in the room.
It requires a realistic VP mandate. If the hire is expected to build the system and drive revenue simultaneously, that needs to be explicit, the timeline needs to reflect it, and the success metrics need to be sequenced accordingly. Architect-builder is a legitimate role. It is just a different role from sales leader, and the two should not be conflated.
Finally, it requires a genuine transition from founder-led to leader-led sales, which means the founder stepping back from deal-by-deal involvement in a structured way rather than all at once or not at all. The companion article on when to hire a VP of Sales covers the sequencing and readiness signals in more detail.
Senior sales leadership amplifies what is already there. If what is already there is unclear, a strong VP makes the ambiguity more expensive, not less.
Sales Sherpas’ approach is built around exactly this problem: establishing the commercial foundation and operating model before or alongside a leadership hire, so that when a VP does come in, they inherit a working system rather than an open brief. The goal is not to replace senior sales leadership; it is to make sure the hire has something real to lead.
