Every CRO has a hiring plan for this year. Fewer have priced what that hiring plan actually costs before it pays off.
That’s not a knock. It’s just where the math tends to fall through the cracks. Headcount plans get built around quota targets, not ramp curves. A board deck says “we’re hiring 12 reps this year to hit the number,” and the number assumes those 12 reps are productive on a timeline that’s more optimistic than what actually happens on the floor. The gap between those two things, planned productivity and actual productivity, is real money, sitting unaccounted for in a plan that otherwise looks precise.
Key Takeaways
- Sales ramp time is a revenue risk, not just an onboarding metric.
- A single average ramp-time number can mislead forecasts, especially across SMB and enterprise segments.
- CROs can quantify quota at risk using hiring volume, deal size, and segment-specific ramp time.
- Understanding ramp exposure helps leaders build more realistic hiring plans and revenue forecasts.
The line item that doesn’t exist on any slide
Ramp time shows up in plenty of internal conversations. It’s in the onboarding retro, the enablement roadmap, the “why did Q2 come in soft” post-mortem. What it almost never shows up as is a dollar figure on a forecast: a specific, quantified cost sitting next to CAC, next to churn, next to the other numbers that get real scrutiny.
That’s worth correcting, because ramp time isn’t a soft, HR-adjacent metric. It’s a revenue timing problem, and revenue timing problems are exactly the kind of thing a CRO is supposed to own. Every quarter a new rep spends short of full productivity is a quarter of quota that either doesn’t get hit, or gets quietly absorbed by the reps who are already ramped, which shows up somewhere else, as burnout, as missed expansion revenue, as a forecast that only works because your best people are covering for a hiring plan that isn’t paying off yet.
Why the “average ramp time” number lies to you
If you ask most sales leaders how long ramp takes, you’ll get a single number: “about six months” is the common answer. That number is more dangerous than not having a number at all, because it implies uniformity that doesn’t exist.
A rep selling a $10K SMB product ramps on a completely different curve than a rep selling a $150K enterprise contract: different sales cycle, different deal complexity, different muscle memory required before they’re closing at full pace. Blending those into one “six months, roughly” figure doesn’t just lose precision. It actively misleads the forecast, because it applies the wrong ramp assumption to whichever mix of reps you’re actually hiring this year. If your hiring plan skews toward enterprise reps this year and your forecasting model is still using a blended SMB-weighted average from two years ago, you’re walking into a quarter with a number that was never built for the reps you’re actually adding.
This is the part that’s genuinely worth a CRO’s direct attention, not just Enablement’s: the exposure compounds with the plan. The more aggressive your hiring plan, the more reps sitting in that ramp gap at any given time, and the bigger the swing between “the plan as modeled” and “the plan as it actually performs” if ramp time assumptions are wrong.
Three numbers, one exposure
The actual exposure comes down to three inputs, and all three are things you already know or can find quickly:
How many reps you’re planning to hire.
This is already in your headcount plan. It’s the one number that’s never in question.
What they’re selling, and at what price point.
Deal size isn’t just a pricing detail. It’s the single biggest driver of how long ramp actually takes and how fast a fully-ramped rep can close once they get there.
How long ramp actually takes for reps at that deal size.
Not a company-wide average pulled from a board deck two years ago, but the real number for the segment you’re hiring into this year.
Multiply those together correctly, and you get a specific, defensible figure: the quota sitting at risk this year purely from the gap between when reps start and when they’re actually productive. That’s a number worth knowing before the hiring plan is locked, not after a soft quarter forces the question.
Put a number on your own exposure
Most CROs have a rough intuition that ramp time costs something. Very few have turned that intuition into a specific figure they’d be comfortable putting in front of the board, which means it’s also not a number that’s shaping how the hiring plan itself gets built.
That’s a fixable gap, and it doesn’t require a full forecasting exercise to get a useful first estimate. On this page, there’s a quick calculator that takes exactly the two inputs above (how many reps you’re planning to hire, and what they sell at) and turns them into your own quota-at-risk figure for this year. It won’t replace a full model, but it’s a fast way to see whether ramp time is a rounding error in your plan or something that belongs on the board slide next to the rest of your revenue assumptions.
Once you have that number, the natural next question is where it’s actually coming from: which parts of ramp are genuinely slow because of deal complexity, and which are slow because of gaps in how knowledge, coaching, and feedback move through the team. That’s a more tactical breakdown than a CRO typically needs to walk through personally, but it’s worth knowing it exists: our five-point onramping maturity framework is built for exactly that conversation with whoever owns Enablement or RevOps on your team.