Most seed and Series A sales teams close four to ten deals a quarter. That is not enough volume for quota attainment or close rate to tell you anything reliable about a new VP of sales in their first two quarters. If you wait for the pipeline to prove the hire wrong, you will not know until month five or six, by which point a bad hire has already cost you a sales team and a year of momentum.
The fix isn't patience. It's tracking five proxy metrics every week starting in week one, metrics that move long before quota attainment does and that predict, with reasonable accuracy, the number the pipeline will eventually confirm.
Why pipeline numbers lie for the first two quarters
A new VP of sales' quota attainment in month one or two mostly reflects deals that were already moving before they started, not their own impact on the business. Full-cycle AE ramp for SMB and mid-market motions runs four to six months, with the first closed deal typically landing six to ten weeks in. A VP inherits that same math for their own reps, and their personal contribution to revenue lags even further behind, because their real job in month one is building the machine, not closing deals themselves.
Meanwhile, most B2B SaaS teams forecast at plus or minus fifteen to twenty five percent quarterly variance, with elite teams closer to five to ten percent. At four to ten deals a quarter, one lost or pulled-forward deal swings your quota number by double digits. That is not signal, it's noise dressed up as a KPI, and it's exactly why founders who wait for quota attainment to judge a new VP end up making the call two quarters too late, after the damage is already done.
The five proxy metrics that predict the outcome months early
These five numbers are visible by week two and update every week after. None of them require new software, just a shared doc and the same four questions asked inside the weekly one-on-one you're already having.
Forecast call accuracy. Ask your VP to call each open deal's close probability every week, then check it against what actually happens. Rep commit forecasting on its own runs at plus or minus twenty to forty percent, the least accurate method in B2B SaaS, not because reps lie but because commit calls are opinions with no proof requirement behind them. A VP whose team's calls drift further from actuals each week, instead of converging, is your earliest reliable signal, visible by week three.
Rep ramp velocity. That four-to-six month ramp and six-to-ten week first deal window is the benchmark for the reps your VP hires, not for the VP themselves. Track the actual date each new rep closes their first deal against that window. A VP who can't get two consecutive new hires inside it, even accounting for your specific sales cycle, has a structural coaching or hiring-bar problem that compounds as the team grows.
Deal review specificity. In the weekly deal review, do they name the next concrete buyer action and date, or do they say a deal 'feels good'? Specificity is a proxy for whether they're running an actual sales process or riding on optimism. A deal with no named next step and no economic buyer identified isn't fifty percent likely to close, it's unqualified pipeline wearing a probability label. Track how many open deals pass that test each week; the trend matters more than any single week's count.
Pipeline coverage trend. Coverage is open pipeline divided by the quarter's target, and the direction it moves week over week tells you more than its absolute value. A VP building real coverage should show that ratio climbing steadily through the first sixty days, not flat or falling while they lean entirely on inherited deals. A flat or declining trend by week eight means new pipeline generation isn't happening yet, whatever the deal reviews claim.
Recruiting signal. A VP of sales' own network is a leading proxy for their judgment and reputation in the market. If they haven't brought in, or gotten a firm yes from, at least one strong rep candidate within their first thirty days, that's a real warning sign, not a scheduling issue. The strongest operators arrive with people already lined up to follow them. If nobody good is willing to bet on this VP, that's worth knowing before you've bet a year on them.
How to track this without adding process
Don't build a dashboard. Add four questions to the one-on-one you're already having: what moved in the forecast this week and why, which new hire is closest to their first deal, what's the coverage ratio today versus last week, and who's the strongest candidate in their pipeline right now. Write the answers in a shared doc, dated, so you can see the trend in week eight instead of relying on memory. This isn't about second-guessing their strategy, it's about separating whether they're executing the model you agreed on from whether that model actually works, and tracking the first one starting immediately.
What a failing pattern looks like by week six
A VP who isn't going to work out rarely shows one dramatic red flag. It shows a pattern: forecast calls that get vaguer instead of sharper, no named candidate after a month, deal reviews still built on adjectives instead of dates, and a coverage ratio that hasn't moved since week two. Any one of these alone could be a slow month. All four together, still present at week six, is the same outcome the pipeline would eventually show you in month five, just visible three months earlier and a lot cheaper to act on.
The one move to make this week
Start the tracking doc this week, regardless of how good the hire looks so far. If they're strong, it costs twenty minutes a week and gives you a real record for their first review. If they're not, it's the difference between catching it at week six and explaining a missed quarter to your board that you never saw coming.
Frequently asked questions
How is this different from just reviewing a 30-60-90 day plan?
A 30-60-90 day plan review checks whether specific milestones got hit on schedule. These five proxy metrics track leading indicators every week regardless of what the plan says, which catches drift between review checkpoints, not just at them.
What if the VP inherited a broken pipeline or a messy CRM?
Then coverage trend and deal review specificity will start low, which is fine. What matters is the direction over the first sixty days, not the starting point. A VP who inherits a mess and gets specificity and coverage moving upward is doing the job. One who inherits the same mess and it's unchanged at week eight is not.
How many of these five need to fail before I act?
Two or more, sustained for four consecutive weeks, is a real pattern worth a direct conversation. One weak metric in isolation is usually noise. Waiting for all five to fail before acting is the same mistake as waiting for the quota number, just with extra steps.
Does this apply to a first sales hire who isn't technically titled VP?
Yes. Title has nothing to do with it. Anyone accountable for building your sales motion and hiring reps under them should be evaluated on these same five proxies, whether the offer letter says VP of sales, head of sales, or first sales hire.
What's the real cost of getting this wrong?
A bad VP of sales hire typically costs a full year once you count the salary, the reps hired under a flawed model, and the pipeline that didn't get built while you waited to find out. Catching the pattern at week six instead of month five is most of that cost avoided.
None of this requires becoming a sales expert overnight. It requires asking the same four questions every week and writing down the answers. Reach out if you want a second read on what your numbers are actually telling you.