The more useful question isn’t "did we pick a bad VP?" It’s "did we ever build something a VP could scale?" A VP of Sales is supposed to multiply an existing motion — not invent one from a standing start. When the underlying process was never validated, the hire doesn’t get a fair test. Neither does the founder’s conclusion about what went wrong.
The Signs Everyone Reads as "It’s the Person"
SaaStr’s Jason Lemkin has spent years cataloguing what a failing VP hire looks like in practice: revenue per lead and net new bookings don’t budge within one sales cycle, no strong reps join in the first sixty days, and deals simply slow down — longer cycles, more discounting, lower close rates. These are real signals, and founders are right to watch them closely.
But notice what all three signals have in common: they measure whether an existing motion accelerates under new leadership. They say almost nothing about whether a motion existed to accelerate in the first place. If a company never had a repeatable pattern — a way of finding, qualifying, and closing customers that worked more than once — then "revenue per lead didn’t improve" isn’t a verdict on the VP. It’s a symptom of asking someone to speed up a car that was never assembled.
This is the trap: the signals that indicate a mis-hire are almost identical to the signals you’d see if the company simply wasn’t ready to scale the role at all. Reading them correctly requires knowing which situation you’re actually in before you look at the numbers.
When Is There Actually Something to Scale?
The clearest readiness marker described in current hiring guidance is blunt: found the product-market fit motion yourself first. Founders should personally close a meaningful set of early customers, then bring on one or two reps who can repeat that success before adding a VP layer at all. The VP’s job, in this framing, is recruiting, coaching, and process design across a team — not personally discovering how the product gets sold.
That sequencing matters because a validation signal only means something if it’s repeatable. One enthusiastic customer, or one founder-led deal that closed because of relationship, luck, or heroic effort, doesn’t tell you whether a stranger following the same playbook can get the same result. A pattern that holds across several independent buyers is a genuinely different kind of evidence than a single win — and it’s the difference between "we have something to scale" and "we have an anecdote."
It’s worth being careful here about how far to push this. One widely cited estimate suggests that a large majority of first-time VP of Sales hires at startups don’t work out, with costs running into the millions once lost revenue and team disruption are counted. That number comes from a single source built around hiring services, and it shouldn’t be treated as an independently verified industry constant — but directionally, it lines up with a simpler and more defensible point: hiring a senior sales leader before there’s a repeatable motion to hand them is a structurally risky bet, regardless of the exact percentage.
Leading Indicators vs. the Verdict You Actually Want
Part of what makes this mistake so tempting is timing. Founders under pressure to "professionalize" sales quickly look for the fastest available signal, and the fastest signals are leading indicators — activity metrics that move before revenue does: meetings booked, pipeline created, early rep hires made. Lagging indicators — net new bookings, retained revenue, quota attainment across a full team — take longer to show up and are the ones that actually confirm whether a sales motion is working.
The danger is drawing a lagging-indicator conclusion ("this VP failed") from leading-indicator evidence gathered too early, layered on top of a process that was never proven in the first place. A confident 30-60-90 day plan in an interview is a leading indicator of communication skill, not of operating ability. A couple of early deals closing after a VP joins is a leading indicator of momentum, not proof the company is ready to scale that role. Both can be real and still tell you very little about the underlying question.
A Diagnostic: Person Problem or System Problem?
Before assigning blame to a hire, it helps to separate what a signal is actually about — the candidate, or the environment they were dropped into.
| Signal observed | What it can plausibly tell you | What it cannot tell you |
|---|---|---|
| No strong reps join within 60 days | Whether the VP has an activatable talent network | Whether a repeatable motion existed for those reps to run |
| Revenue per lead stays flat | Whether the VP improved existing conversion | Whether conversion had ever been proven possible pre-hire |
| Confident, detailed interview answers | Communication skill, possibly relevant experience | Actual performance under your product, market, and team |
| One or two founder-led deals closed pre-hire | That the product can be sold at all | That the same approach repeats across many buyers |
| Deals slow down after the hire | Whether the VP adapted to your specific sale | Whether deals were ever fast to begin with |
| Structured downward reference checks | Patterns in how a candidate actually managed people | Whether your company had the process infrastructure to support them |
The pattern across the right-hand column is consistent: individual signals, however vivid, rarely resolve the underlying question of process readiness. That question has to be answered separately, before the hire, not inferred backward from how the hire went.
How the Mistake Actually Unfolds
The failure sequence usually isn’t a single bad decision — it’s a chain, and each link looks reasonable in isolation.
flowchart TD A[No repeatable sales motion yet] --> B[Growth pressure pushes early VP hire] B --> C[VP expected to invent process, not scale one] C --> D[Early KPIs stay flat or slow] D --> E[Founder concludes: bad hire] E --> F[Real gap in process readiness goes uncorrected]
Each arrow feels like cause and effect at the time. Only in hindsight does it become clear that the weak link was several steps upstream of the hiring decision itself.
Better Validation, at the Hiring Stage Itself
None of this means gut feel should be discarded, or that founders are foolish for wanting senior help. It means the hiring process deserves the same skepticism founders apply to a new product feature. Decades of research on employment interviews consistently show that structured formats — the same questions for every candidate, evaluated against predefined criteria — predict job performance far better than free-flowing conversation, across industries and seniority levels. A confident, engaging interview is not, by itself, evidence of operating ability; it’s evidence of interviewing well. Pairing structured questions with reference checks aimed at former direct reports, rather than upward references alone, gives a founder something closer to a repeatable test than a single impressive conversation ever can.
The Real Question to Ask First
None of this proves that every failed VP hire is secretly a process problem, or that a bad candidate can’t genuinely be the issue — sometimes it really is the person. But before reaching for that explanation, it’s worth asking a harder question: did this company have a documented process, consistent metrics, and a clear handoff from founder-led selling before the VP ever started? If the honest answer is no, then the hire was never really being tested — the market was, retroactively, and the wrong subject got the blame.
The key takeaway is simple to state and easy to forget under pressure: don’t evaluate a high-stakes hire as if it were the first test of a system. First find out whether the system itself was ever ready to be tested at all.
