When to Hire a VP of Sales (Not Before)

Hire a VP of Sales when you have a repeatable motion, not when you hit a revenue number. That means 1 to 2 reps, often a founding AE, who have closed deals using a consistent pitch, ICP, and objection pattern, and you, the founder, have become the bottleneck: coaching, pipeline review, and hiring are slipping while you're still closing every deal yourself. Most companies land in this window between $1M and $3M ARR, but that figure is a lagging indicator, not the trigger. Hire before repeatability exists and you're paying $200K-plus for someone to build what a founding AE should have built first.

Key takeaways

• 8 of 10 first-time VP of Sales hires fail, with an average tenure of just 11 months once they do.
• The trigger is repeatability, not revenue: 1 to 2 reps closing consistently beats any ARR milestone as a signal.
• Most companies land the hire between $1M and $3M ARR, but hiring before you can whiteboard your last 10 deals is premature at any revenue.
• A mistimed VP of Sales hire costs $200K to $2M once you count ramp time, backfill, and the pipeline months you lose relearning the motion.
• Across 555+ GTM leadership placements, the pattern holds: the hire that fails is almost always the hire that came before the motion did.

What's the actual trigger, revenue or something else?

Revenue is the easiest thing to point to, so boards and founders default to it. "We'll hire a VP of Sales at $1M ARR" sounds like a plan. It isn't one, because ARR tells you nothing about whether there's a motion to scale.

The real test: can you draw your sales process on a whiteboard, from first touch to signed contract, and have it match how your last 10 deals actually closed? If every deal closed differently, on a different pitch, against a different objection, with a different discount, there's nothing repeatable yet. A VP of Sales's job is to scale a motion that already works. Hand them a motion that doesn't exist and they'll spend their first six months inventing one, which is founder work, at VP compensation.

The second half of the trigger is you. If you're still personally closing every deal and nothing else is slipping, you're not ready. If hiring, forecasting, and coaching are visibly falling through the cracks because you're stretched across founder duties and sales management, that's the bottleneck signal. Get both: a proven motion and a founder who's become the constraint. Get only one, and you're probably early.

Founders who anchor on revenue instead of repeatability tend to make the same mistake twice. They hire against a number ("we said $1M ARR"), the hire fails because there was nothing to scale, and eighteen months later they hire again, still anchored on a revenue milestone rather than the underlying test. The revenue figure is useful only as a sanity check, most companies that pass the repeatability test happen to be somewhere near $1-3M ARR, not as the trigger itself. Treat it as a coincidence worth noting, not a rule worth following.

How many reps do you need before this hire makes sense?

One to two, doing the job well enough that their results aren't a fluke. Not five, not a founding team of one. The point isn't headcount, it's proof: has anyone besides you closed deals using the same pitch, the same ICP, the same handling of the three objections that kill every deal in your category?

If the answer is yes, you have a motion. If the answer is "the founder closed everything and one AE has a maybe," you don't have a motion, you have a hopeful anecdote. A VP of Sales hired against a hopeful anecdote spends their first quarter finding out the hard way, usually by missing a number nobody could have hit, because the number was never real.

There's also a quality bar hiding inside the headcount question. Two reps who both hit quota using two completely different approaches aren't proof of a motion, they're proof that your product sells itself well enough to survive inconsistent process. That's a good problem to have, but it's not the same signal. Look for reps converging on the same pitch, the same disqualification criteria, and the same handling of your hardest objection, independently of each other. Convergence is the tell. Coincidence isn't.

What happens if you hire too early?

You get a builder doing an operator's job, or an operator doing a builder's job, and either way it goes wrong on a predictable clock. Months 1 to 3 look fine: the new VP audits the pipeline, meets the team, talks strategy. Months 4 to 6 is when the absence of a real motion shows up as inconsistent forecasting and reps who don't know what "good" looks like because nobody has ever defined it. By month 9 the board is asking why the number keeps missing, and by month 11, the average tenure for a failed first VP of Sales hire, they're gone.

None of this is usually a talent problem. It's a sequencing problem: you hired someone to scale a motion that didn't exist, so they built one under pressure, on the clock, with a board watching. That's a much harder job than scaling a motion that already works, and it fails more often. We've broken down the full cost of getting this wrong, ramp time, backfill, lost pipeline months, in our guide to what a bad sales hire actually costs, and at the VP level it routinely runs into seven figures.

What happens if you wait too long?

The opposite failure is quieter but just as expensive. You keep closing deals yourself past the point where it's a good use of your time, and every rep you've hired develops their own version of "how we sell here" because nobody's defining it consistently. Deals start closing on inconsistent discounting. Your best rep starts freelancing a pitch that works for them but doesn't transfer. Forecast accuracy degrades because three people are reporting three different realities to you.

Founders who wait too long also pay a talent tax: the reps who joined expecting a real sales organization start leaving, because "report directly to the founder forever" isn't the job they signed up for. By the time you finally hire the VP of Sales, you're not scaling a motion, you're also rebuilding a team.

There's a personal cost too, and it's worth naming plainly. Founders who stay in the closing seat past the point of usefulness burn out on a job that was never meant to be permanent, and the burnout shows up in the decisions that matter most: fundraising conversations get rushed, product roadmap gets neglected, and the next hire, whoever it is, inherits a founder who's running on fumes rather than judgment.

VP of Sales, founding AE, or fractional leader: which do you need right now?

Match the hire to the stage, not the title you think you're supposed to have:

That last row matters more than founders expect. If you're past the VP of Sales window and running multiple motions or segments, the coordination problem is bigger than one function. Our guide on when to hire a CRO covers where that threshold actually sits, and it's higher than most boards assume.

What does the first 90 days look like when the timing is right?

When the hire lands at the right moment, three things show up fast. Forecast accuracy improves within one or two cycles, because the VP is refining a real process instead of inventing one under pressure. Your calendar visibly opens up for product work, fundraising, or whatever you were neglecting while closing every deal yourself. And the team starts operating from documented process rather than founder instinct, which is the actual point of the hire: it makes the sales motion survive without you in the room.

If none of that shows up by month four, don't wait for month eleven to admit it. Revisit whether the motion was as repeatable as you thought, or whether the hire was scoped against the job you wished you had rather than the one you actually do.

One more thing worth planning for before the search even starts: write down what "good" looks like at day 30, 60, and 90 before you have candidates in front of you. Boards and founders who skip this step end up grading the new VP against a moving target, which is unfair to the hire and makes it harder to catch a real mismatch early, when it's still cheap to fix.

FAQ