This is the most painful and expensive mistake in scaling a recurring-revenue business. It happens at almost exactly the same moment — somewhere between $5M and $15M ARR — with almost exactly the same pattern, and it has almost nothing to do with the quality of the hire.
The statistic is striking: between 50 and 70 percent of first VP Sales hires at scaling tech companies do not last 18 months. Most founders who have been through it describe the experience as one of the most costly and demoralising in their company’s history — not just in terms of salary, severance, and recruiter fees, but in terms of the deals that did not close, the reps who followed the departing leader out of the door, and the six to nine months it took to rebuild confidence in the commercial function.
Here is what I have learned from watching this play out across dozens of companies: the hire almost never fails because the person was wrong for the role. It fails because the system they walked into was never designed to support a hired commercial leader. The role was created to solve a problem that the organisation had not yet diagnosed correctly.
The 18-Month Failure Sequence
The pattern is consistent enough that you can map it month by month.
Months one through three: optimism. The new sales leader is experienced, credible, and energetic. They have done this before. They start meeting the team, reviewing the pipeline, getting into deals. The founder feels the relief of handing over a function they have been carrying personally.
Months four through eight: friction. The pipeline review is revealing things the new leader is not comfortable with. Deals that have been sitting in the same stage for months. ICP that is loosely defined. A CRM that does not reflect reality. Forecast calls that are exercises in collective uncertainty. The new leader starts to build process — but they are building on a foundation that was never designed, which means every structure they erect is slightly unstable.
Months nine through fourteen: board pressure. Revenue targets are not being met at the rate the board expected when the hire was made. The founder starts to question whether the hire was right. The board starts asking whether the commercial function has the leadership it needs. The new leader is working harder but the structural problems they inherited are now working against them at scale — because they brought on more reps who are now running the same inconsistent process.
Months fifteen through eighteen: departure. Either the board makes the decision or the leader recognises that the environment is not one they can succeed in. The founder is now searching for a replacement, the team is unsettled, and the revenue function is back to being founder-led by necessity.
The Architecture They Walk Into
What does the system look like when a commercial leader joins a company that has grown from zero to $10M on founder-led sales? It looks like this.
The ICP is understood intuitively by the founder but has never been formally documented. It exists as a feeling — ‘we know them when we see them’ — rather than as a set of specific, measurable criteria that a hired rep can apply independently. The new sales leader cannot teach their team to qualify against a definition that does not exist in writing.
The pipeline stages were set up three years ago, probably copied from a vendor default, and have not been reviewed since. There are no exit criteria. Deals advance when reps feel they should advance. The forecast is the sum of the rep’s optimism on any given day. The new leader inherits a number they cannot defend to the board because the data underlying it is structurally unreliable.
The handoff from marketing to sales is informal. Marketing sends leads when they feel they are ready. Sales accepts or rejects them based on individual rep preference. The qualification framework is whatever each rep learned at their previous company — which means the team of five is running five different sales processes simultaneously.
There is no formal expansion motion. Customer Success is a separate function that manages its own pipeline in its own system with no defined protocol for when and how expansion opportunities should be surfaced back to the commercial team. Renewal risk is spotted by the CSM when a customer stops logging in — which is typically six months after the risk first became visible in the usage data.
This is not an unusual company. This is a normal company at $8M to $15M ARR that has grown by being good at what it does, not by designing its revenue system. The founder could sell it because the founder understood it completely. The hired leader cannot sell it because it exists nowhere outside the founder’s mind.
What the Same Hire Looks Like in a Designed System
Now consider the same quality of hire walking into a company that has spent six to eight weeks properly designing its Lead-to-Order architecture before making the hire.
The ICP is documented with specific firmographic and behavioural criteria. The new leader can hand it to every rep on day one and they all start with the same definition of who qualifies and why. Pipeline stages have written exit criteria. The new leader can train against them, coach against them, and hold the team accountable to them.
The forecast is based on deals that have met specific exit criteria at each stage — which means the 90-day number has a structural basis rather than a collective feeling. The new leader can stand behind it in a board meeting because they know what conditions had to be true for each deal to be where it is.
The expansion motion is defined. Renewal triggers are documented. The CS-to-sales handoff protocol exists. The pricing governance is written. The new leader can scale the team by replicating a designed process rather than trying to impose structure retrospectively on an inherited chaos.
The ramp time in this environment is measurably shorter. The win rate improves quarter over quarter because the process is consistent enough to be coached and optimised. The forecast stabilises because the pipeline data is structured around buyer commitment rather than rep activity. The founder steps back from deal involvement because the system can run without their intuition as the primary input.
The Six Things Missing When the First Sales Leader Arrives
If you are preparing to make this hire — or if you have just made it and recognise the early stages of the pattern — these are the six architecture components that most commonly cause the failure:
First: a documented ICP with specific qualification criteria that any rep can apply independently. Second: pipeline stages with written exit criteria, not just entry events. Third: a formal qualification framework applied consistently at every stage. Fourth: a written marketing-to-sales handoff protocol with agreed lead definitions. Fifth: a pricing governance document that defines discount authority and approval rules. Sixth: a Customer Success handoff protocol and a defined expansion trigger that connects post-sale activity back to the revenue pipeline.
None of these are complex to design. All of them can be built in a structured process. The cost of not having them is a 50 to 70 percent chance that your first commercial leader hire fails within 18 months — and you absorb that cost in recruiter fees, salary, severance, team disruption, and lost deals.
The Question You Should Be Asking Before You Hire
Before you write the job description, before you engage the recruiter, before you make the first call to a candidate — ask yourself this question honestly: what system will this person be leading into?
If the answer is ‘our current process,’ and your current process lives primarily in the founder’s intuition, you are not hiring a sales leader. You are hiring someone to own a problem you have not yet diagnosed. The architecture needs to come first. Not because hiring is wrong, but because the hire will only succeed inside a system designed to support them.
Designing the revenue architecture before the hire is not a delay. It is the reason the hire works.
IS YOUR REVENUE ARCHITECTURE BUILT TO SCALE — OR BUILT BY ACCIDENT? Most recurring-revenue companies between $10M and $50M ARR have never formally designed their Lead-to-Order architecture. They have a CRM, a pipeline, a process of sorts — but not a system with deliberate structure, stage exit criteria, qualification frameworks, handoff protocols, and an expansion motion that runs without founder involvement. The Lead-to-Order Architecture Assessment shows you exactly where your system is designed, where it is accidental, and where it is missing — component by component, with a prioritised fix list. 15 minutes. No sales call. A clear picture of your revenue architecture and what to build next. >> TAKE THE LEAD-TO-ORDER ARCHITECTURE ASSESSMENT << https://techgrowthinsights.com/lead-to-order-assessment/
Is your revenue architecture built to scale — or built by accident?
Most recurring-revenue companies between $10M and $50M ARR have never formally designed their Lead-to-Order architecture. They have a CRM, a pipeline, a process of sorts — but not a system with deliberate structure, stage exit criteria, qualification frameworks, handoff protocols, and an expansion motion that runs without founder involvement.
The Lead-to-Order Architecture Assessment shows you exactly where your system is designed, where it is accidental, and where it is missing — component by component, with a prioritised fix list.
