Sales consultancy vs hiring a VP of Sales: which comes first?
At some point in the growth of almost every founder-led SaaS company, the same question surfaces: do we hire a VP of Sales, or do we bring in external support first?
The honest answer is that most founders are asking the wrong question. The choice between a sales consultancy and a VP of Sales is not really a choice between internal and external. It is a choice between two things the business needs at different times: commercial architecture and commercial leadership. Getting the sequence wrong is expensive in ways that take months to surface.
The real decision is not consultancy or VP. It is architecture or leadership first.
A VP of Sales is primarily a leadership, management and scaling hire. They should be managing a team, building a culture of performance, owning forecasting, running pipeline reviews, developing reps and making consequential hiring decisions. That is the role at its best.
A sales consultancy is better suited to a different set of problems: diagnosing a fragmented sales process, defining what "good" looks like across qualification and discovery, aligning CRM stages to the real buyer journey, building the operating rhythms that give a sales team consistency, and leaving behind the frameworks and playbooks the company can run without ongoing external support.
These are not the same job; treating them as interchangeable is where companies get into difficulty.
What a VP of Sales is best placed to solve
A VP of Sales delivers the most value when the commercial foundation is already in reasonable shape. When there is a repeatable sales motion; a clear ideal customer profile; documented stages; enough CRM discipline to produce credible forecasts; and a team that needs coaching, performance management and direction, a VP is exactly the right hire.
SaaStr's guidance on VP of Sales hiring makes the threshold clear: do not hire a VP of Sales before at least two reps are performing well and the sales motion is showing repeatable results. The reasoning is straightforward. The VP's job is to scale something that works, not to figure out whether anything works at all.
When a business has that foundation in place, the VP hire is lower risk and faster to impact. The mandate is clear. The CRM is usable. The process exists. The VP can spend their first months building on it rather than questioning everything from scratch.
The expensive mistake is hiring a VP to answer a question the business has not yet defined. "We need to scale sales" sounds like a mandate, but it can mean hiring more reps, redesigning the process, improving win rates, building an outbound function, entering a new segment, reducing founder involvement, or fixing forecasting. Those are not the same job description.
What a sales consultancy is best placed to solve
Most early-stage SaaS companies that think they need a VP of Sales actually have an architecture problem first. The symptoms tend to cluster: pipeline is inconsistent but no one is sure why, reps are doing deals differently from each other, discovery is shallow, qualification criteria are either absent or ignored, the CRM has stages that no longer reflect how buyers actually make decisions, and the founder is still involved in most deals because nothing works well without them. If any of that sounds familiar, the problem may be the sales system rather than the salesperson.
In this state, hiring a VP is often slower than it looks. The Bridge Group's 2024 AE benchmarks put the median annual ACV quota for a SaaS AE at $800K. When there is no defined process, no shared qualification standard and a CRM that does not reflect reality, the cost of underperformance against that quota becomes significant very quickly. And according to SaaStr, the majority of first VP of Sales hires at SaaS start-ups do not make it twelve months. Some of that attrition is about the hire itself; a meaningful part of it is about what the hire was asked to walk into.
A well-scoped consultancy engagement addresses the operating model before the leadership question. That means: what are we selling, to whom, at what stage of maturity, through what kind of conversation? It means building practical qualification criteria, defining what a qualified discovery looks like, aligning CRM fields to real pipeline logic, and creating the shared view of "good" that a sales team needs to function consistently.
Critically, a consultancy that is doing its job correctly reduces dependency rather than creating it. The output should be operating rhythms, process documentation, decision criteria and reporting logic that the company can run independently. If a consultancy leaves a company needing more consultancy to stay functional, something has gone wrong.
This is how Sales Sherpas thinks about the work. The approach is designed to install a commercial engine the company owns, not to manage it on their behalf.
A decision framework: which should come first?
Choose a VP first when:
The sales motion is already producing consistent results across more than one rep. Qualification criteria exist and are being used. The CRM reflects reality rather than optimism. Pipeline conversion is reasonably predictable. The main constraint is that the team needs leadership, coaching and hiring support that the founder cannot provide while also running the business.
Choose consultancy first when:
Pipeline is inconsistent and the root cause is unclear. Reps are qualifying differently from each other. Deals are regularly stalling without explanation. The CRM is not trusted. The founder is still required in most commercial conversations. There is no shared view of what a good discovery looks like, what the real sales stages are, or where deals are typically won or lost. In this situation, a VP inherits a system that will slow them down. This is also one of the most common reasons first VP hires fail in SaaS: the architecture was not there for them to build on.
Consider both when:
Some companies are far enough along in one dimension but not another. A founder may have a clear ICP and strong product-market fit but no documented process and a CRM that no one believes. In that case, a short consultancy engagement running in parallel with the VP search, rather than instead of it, can mean the VP starts into a cleaner mandate. The sequencing matters more than the categories.
The strongest sequence is often consultancy first, VP later
The argument for sequencing is not that VPs are bad or that external consultants are better. It is that these are two different roles with different purposes, and conflating them creates problems for both.
Phase 1: diagnose and design the operating model
A well-run first phase is time-boxed and starts with a proper diagnostic: looking at where deals are actually won and lost, how reps qualify, whether discovery is consistent, what the CRM is and is not telling you, and where the founder's involvement is carrying something the process should be doing instead. The output is a clear picture of the operating model as it currently exists and what it needs to look like to be repeatable without founder dependency. The article on when founder-led sales stops scaling covers this transition point in more detail, and most of the diagnostic signals it describes apply directly here.
Phase 2: implement and transfer knowledge
The second phase installs the changes. CRM stage definitions that match the buyer journey. Qualification criteria the team actually uses. A practical playbook that captures what the best reps do naturally. Reporting that surfaces real pipeline risk rather than giving false confidence. This phase is where most of the work happens, and it is also where knowledge transfer matters – the team should understand why the model is built the way it is, not just what to do.
Phase 3: hire or onboard sales leadership into a working system
With the operating model in place, the VP search becomes a cleaner exercise. The job description is more specific; the mandate is less ambiguous. The new hire can focus on leadership and scaling rather than archaeology. And when they make changes to the system, those changes are visible against a baseline rather than being lost in noise.
The cost of mis-sequencing is real. In 2012, Research from the Center for American Progress put the total cost of replacing an executive-level hire at up to 213% of annual salary, covering recruitment, onboarding, lost productivity and transition costs. In the context of a VP of Sales role at a Series A or B company, a hire that does not work out because the mandate was unclear or the operating model was undefined is an expensive problem to absorb.
None of this is an argument against hiring a VP of Sales. The role matters, and done well it is one of the most important hires a scaling SaaS company makes. The argument is about timing and about what the VP is walking into.
A sales consultancy is not a permanent substitute for commercial leadership. It is a way of building the system that leadership will run. The programmes Sales Sherpas offers are designed with that transition in mind: staged, implementation-focused, and structured to leave a company with a working commercial engine rather than an ongoing dependency.
If you are unsure whether your company needs architecture or leadership right now, that uncertainty is itself diagnostic. In most cases, it means the architecture work comes first.
