What onboarding ramp timeline should you bake into hiring decisions for different career stages in 2027?

The requisition that quietly cost four million dollars

Picture a Series C company with a February fiscal year start and an $18M bookings number. The CRO looks at the org chart in January and counts twelve enterprise AE seats. Eight are filled with tenured reps carrying $1.5M quotas each. Four are open. Recruiting is told to fill them "as fast as possible," and by late June all four seats have butts in them. On paper, the team is fully staffed against plan. Everybody exhales.

December arrives and bookings land at $13.9M. Nobody can explain the gap, because the headcount roster says twelve of twelve. What actually happened is arithmetic that nobody wrote down. The eight tenured reps produced at roughly 90% attainment, which is $10.8M. Two of the "ramped" reps were themselves only nine months into a nine-month curve at the start of the year and produced at about 80% of a tenured baseline, which is $2.16M instead of $3M. The four new hires started in months three through five of the fiscal year, on a nine-month enterprise ramp, meaning their first quota-relevant closed deal landed somewhere between month eleven and month fourteen — outside the fiscal year entirely. Their combined contribution was under $1M of early, small, marketing-sourced deals.

The gap was never a performance problem. It was a modeling problem. Every one of those reps was tracking dead-center on a normal enterprise ramp curve. The forecast simply assumed a filled seat equals a producing seat, and a filled seat does not equal a producing seat for six to nine months in enterprise, or four to six in mid-market, or thirty days in an acquisition-retention scenario. The single most valuable thing RevOps does in a hiring cycle is convert "we hired four AEs" into "we bought $4M of bookings that will arrive in Q2 of next fiscal year."

The scenario generalizes well past sales. A newly hired implementation consultant at a services firm bills at maybe 40% utilization in month one and does not reach the 75–80% target until month four or five, which means the professional-services revenue forecast has the exact same hole in it. A support engineer hired into a Tier-2 queue takes 60–90 days before their ticket-resolution rate stops dragging the team average down. A demand-gen manager hired in September will not have a campaign of their own design produce attributable pipeline until January, because campaign build plus buying cycle is a two-quarter loop. Anywhere a person's output feeds a number a finance team commits to, ramp is a forecast assumption wearing an HR costume.

There is a second, less visible cost. A territory assigned to a slow-ramping rep is not merely under-produced; it gets partially burned. Accounts that received a low-conviction outreach pattern-match the brand as amateur. Buyers who took a discovery call and never got a competent follow-up remember it. Competitive deals lost on a weak discovery do not come back around for twelve to eighteen months. The visible loss is one year of under-attainment. The invisible loss is the next rep inheriting a territory that has to be rebuilt before it can be sold into, which is why replacement hires in a burned territory routinely ramp slower than the role default even when the rep is excellent.

How the ramp clock actually converts into money

The mechanism is simpler than most enablement decks make it look. Three curves run simultaneously from a rep's start date, and hiring decisions go wrong when a company tracks one and ignores the other two.

Curve one is cost, and it starts at 100% on day one. A mid-market AE at $200K OTE on a 60/40 split costs roughly $120K base, plus a ramp guarantee on the variable, plus benefits and payroll burden at 20–30%, plus tooling and seat licenses at $3K–$8K a year, plus manager and enablement time. Fully loaded, that is $240K–$290K in year one before a dollar of net-new revenue exists. The company pays that at full rate from the first Monday.

Curve two is productivity, which starts at zero and climbs. It is not linear — it is closer to an S-curve with a long flat toe. A rep in month one produces essentially nothing that a forecast can use. The steep part of the curve arrives after the first closed deal, because pattern recognition compounds. And it plateaus at whatever the tenured baseline is, which is usually 85–95% attainment rather than 100%.

Curve three is evidence, which is the one nobody models and the one that determines whether the hire survives. Evidence lags productivity, because closed revenue is a trailing indicator with a lag equal to the deal cycle. In a nine-month enterprise cycle, a rep who becomes genuinely competent in month three does not produce evidence of that competence until month nine or ten. Which is precisely why enterprise ramp has to be measured on pipeline coverage and multi-threading depth rather than bookings — the bookings signal simply does not exist yet at the moment the retain-or-terminate decision has to be made.

The practical consequence of these three curves is the two-checkpoint rule: 50% of full productivity by the midpoint of the window, 80% by the end of it. A rep below the midpoint checkpoint is a hiring miss, not a coaching opportunity, and the sooner an organization is willing to say that out loud the cheaper its hiring gets. The reason is mechanical rather than moral — with the toe of the S-curve behind them, a rep who has not started climbing by the midpoint has no runway left to reach the plateau inside the window, and extending the window means the guarantee dollars keep flowing against a curve that has not inflected.

The same three-curve mechanism explains why the ramp conversation belongs to whoever owns the capacity model. Enablement owns curve two. Finance owns curve one. Nobody owns curve three by default, and curve three is where the decisions live. RevOps taking explicit ownership of the evidence curve — defining which leading indicators substitute for bookings during the window, and at what thresholds — is the whole discipline in one sentence.

The numbers to underwrite, by role and by career stage

Start with the role default. These are the windows that hold up across well-run B2B software organizations, and they cluster tightly enough that treating them as physics is more useful than treating them as negotiable.

SDR/BDR — 90 days. Day 30: product and persona certification complete, templated sequences going out, twenty live handoff calls shadowed, positioning articulated in sixty seconds without notes. Day 60: self-personalized sequences on real territory, activity at 60–70% of full quota, three opportunities handed to AEs that reached stage two. Day 90: full quota, full activity, top-of-territory accounts handled solo. The day-60 checkpoint carries more diagnostic signal than any other single data point in early-career revenue hiring — a rep booking zero meetings at day 60 is a miss, and every week of hope past that point costs guarantee dollars against a curve that is not going to inflect.

Mid-market AE ($25K–$100K ACV, 30–90 day cycles) — 4 to 6 months. First closed-won deal by month three. First self-sourced opportunity opened by month four. Pipeline coverage at 0.5x by month two, 1.5x by month three, 2x by month four, 3x by month six. Bookings at 75% of full monthly quota by month five, 100% by month six, with self-sourced pipeline at 30% or more of total opportunity volume. Forecast accuracy tightening from ±15% at month five to ±10% at month six.

Enterprise AE ($100K–$500K ACV, 4–9 month cycles) — 6 to 9 months. Months one and two are account planning and territory analysis, not selling; the honest expectation is three to five champion-building meetings inside existing customers in the territory. First opportunity opened month three at 1x coverage. First procurement-stage deal and four-plus engaged contacts on the top three accounts by month four. First closed deal months five to six. Full quota, 3x coverage, and 35%+ self-sourced pipeline at month nine. Compressing this seat onto a 90-day ramp because "we need pipeline now" is the most expensive routine mistake the segment makes, and the failure is structural rather than motivational — you cannot close a six-month deal cycle inside a six-month window when the rep started with an empty territory.

Strategic/named AE ($500K+ ACV, 9–18 month cycles) — 9 to 12 months, full quota at 15. These hires are typically poached at $400K–$600K OTE. The underwrite has to be written down and signed before the requisition opens: zero net-new closed revenue expected in the first six months, 1.5x pipeline coverage by month nine, first closed deal by month twelve. If leadership will not sign that, the role does not match the time horizon — either carve a faster-cycle subset of the territory and reclassify it as enterprise, or do not open the seat. Comp structure that survives this window is 50/50 base/variable with a year-one guarantee around 75% of variable, plus an MBO tied to pipeline coverage and account-plan execution rather than bookings. Without the MBO the rep starves and quits at month seven, right before the investment would have paid.

Sales engineer — 4 to 6 months. Month one: admin, developer, and integration-layer certification, eight customer technical calls shadowed. Month two: eight more shadowed, two internal mock demos run. Month three: solo discovery on three live opportunities under partner observation. Month four: POV scoping owned solo, architecture objections handled without backup, first competitive technical bake-off. Months five and six: deep objection handling on complex deals and mentoring the next SE. An SE still escalating routine technical objections at month six is a hiring miss, and under-ramping the seat shows up as AEs losing deals on technical credibility rather than as an SE performance metric — which is why the cost lands somewhere nobody is looking for it.

CSM — 60 to 90 days SMB, 4 to 5 months enterprise. The curve differs because the job-to-be-done is retention and expansion of an existing book rather than net-new acquisition. An SMB CSM on a book of 80–150 accounts is productive fast. An enterprise CSM on 8–20 strategic accounts needs four to five months because executive trust is the prerequisite for expansion conversations and executive trust is not compressible. Watch for the two mirrored failure modes: the CSM treating the seat as support technician, and the organization treating the seat as support technician. Either one produces flat NRR and near-zero expansion contribution, and only one of them is the hire's fault.

First-line sales manager — 90 to 120 days. Day 30: a 1:1 with every inherited rep, every deal above 50% probability reviewed, a documented coaching plan per rep. Day 60: runs the deal forecast call solo and owns the number publicly. Day 90: runs the team QBR and owns hiring decisions for open seats. Day 120: produces measurable net-new pipeline lift against the predecessor's monthly baseline, with attribution they can defend. The day-60 forecast milestone is the load-bearing one. A manager who cannot defend a forecast number to a VP at day 60 is either being over-managed or mis-hired, and both diagnoses are cheaper at day 60 than at month nine.

Director/VP — 6 months to full quota ownership, 9–12 to compounding lift. Month three: every manager met three times, every top-decile ARR customer met once, the three largest forecast risks named. Month six: owns the org's forecast number, has restructured at least one team configuration with a documented business case. Month nine: 10–15% pipeline lift against the predecessor baseline. Month twelve: owns the annual planning document end to end, including the capacity model and the ramp matrix itself.

Now apply the career-stage modifiers, which account for a large share of the variance you actually observe in practice:

• First time in role (BDR→AE, AE→manager, manager→director): +30 to +60 days. This is calibration cost, not coaching cost. They are learning the role's vocabulary, forecast cadence, escalation patterns, and political map simultaneously. Under-budgeting this modifier is how organizations fire promising internal promotions at month five who would have landed at month seven.
• Industry lateral (martech→fintech, enterprise IT→vertical SaaS): +30 to +45 days. Selling mechanics transfer; buyer empathy does not. They can run discovery on day one but it will be flat discovery — playbook questions without situational nuance. Vocabulary takes 30–45 days of customer exposure; nuance takes 60–90.
• Direct competitor hire, identical buyer persona: −30 to −60 days. The cheapest ramp money available if non-competes permit. The offsetting risk is playbook contamination — they will instinctively run the competitor's qualification flow, which may not suit your product's strengths. Budget a 30-day unlearn module.
• Re-entry after a 12+ month gap (parental leave, career break, founder exit): role default, unshortened. Tenure on the résumé is not muscle memory in the seat, and their old accounts have churned. The acute risk is psychological rather than technical — they remember being top performers and momentarily are not, and the attrition spike lands around month four.
• Internal transfer (CSM→AE, SE→AE, marketing→SDR): highest variance in the matrix. Some ramp in half the default because product and customer knowledge is already banked. Others fail outright because the new seat's core skill is genuinely different. Underwrite at the role default, set quota and comp at the role default, and let the rep beat the structure if they can.
• New product or category creation: +60 to +90 days on top of everything else. When the category does not exist yet, the rep has to teach the buyer the vocabulary before discovery can even begin.
• Regulated or specialized vertical (healthcare payer, federal public sector, process manufacturing): +60 days for vocabulary, +30 for relationships. Federal specifically runs long because the procurement vehicles are themselves a months-long learning curve.

Trade-offs: what you are actually choosing between

Ramp policy is a set of trades, and each one has a real cost on both sides. Pretending otherwise is how organizations end up with a ramp doctrine that satisfies no one.

Guarantee generosity vs. urgency. A flat 100% variable guarantee for six months protects the rep completely and removes every incentive to ramp faster, because the payout is identical at month two and month six. Zero guarantee creates maximum urgency and maximum first-year attrition, because a competent rep on a legitimate curve cannot pay rent. The resolution is a stepped guarantee — 100% of variable in months one and two, 75% in months three and four, 50% in months five and six, zero after — with the rep free to earn above the floor whenever commissions exceed it. That structure does three things at once: it carries the rep through the genuinely unproductive phase, it pays for speed, and it returns the plan to commission-only at exactly the moment production should exist.

Quota tiering vs. plan simplicity. Assigning a new AE the full annual quota on day one is simple to administer and guarantees that every new hire arrives at their first QBR at 20% attainment and gets put on a performance plan while sitting perfectly on the expected curve. Tiering the quota at 25/50/75/100 across the first four quarters of tenure adds administrative work and keeps the attainment math honest. Take the administrative work.

Speed of hire vs. fit of hire. Filling a seat in three weeks with an adequate candidate versus twelve weeks with a strong one looks like a clear win for speed until you price the ramp. In enterprise, an adequate candidate who washes at month nine costs the guarantee, the loaded comp, the destroyed territory pipeline, and a full second ramp cycle — call it $300K a seat plus a year of lost territory compounding. Nine extra weeks of vacancy costs one quarter of that territory's production. Speed wins in SDR seats where ramp is 90 days and the candidate pool is deep; fit wins in every seat where ramp exceeds six months.

Buying ramp vs. building it. Poaching from a direct competitor buys you 30–60 days of ramp at a compensation premium. Hiring an athlete and training them costs less in cash and more in time, and produces someone whose playbook is native rather than imported. Most organizations should run a mix, weighted toward bought ramp when the fiscal calendar is tight and toward built ramp when the product is differentiated enough that competitor instincts actively mislead.

Fixed decision deadlines vs. case-by-case judgment. Pre-committed no-fault deadlines — 120 days for SDRs, 180 for mid-market AEs, 270 for enterprise, 365 for strategic, 180 for first-line managers — feel rigid and occasionally cut short someone who would have made it. Case-by-case judgment feels humane and reliably drags failed hires from month six to month fourteen at roughly $120K a seat in mid-market and $300K in enterprise. The fixed deadline is kinder in aggregate even though it is harsher in individual cases, and writing it into the offer letter as a performance milestone rather than a termination trigger makes the conversation survivable for everyone.

There is also a timing trade that most organizations discover a year late. If the fiscal year starts in February and enterprise ramp is nine months, every requisition opened after May 1 produces zero quota-relevant bookings in the current fiscal year. That is not a reason to stop hiring — pipeline built this year closes next year — but it is a reason to stop counting those hires in this year's capacity model. The honest framing for the CFO is: hires made November through March buy current-year revenue; hires made April through October buy next-year revenue. Both are worth making. Only one belongs in this year's forecast.

Where this goes wrong, and the fixes that hold

Treating ramp as enablement's problem. The tell is the sentence "we'll figure out ramp once they start." Ramp is a finance assumption wearing an enablement costume. The fix is procedural: the documented ramp window, the candidate-specific modifier, the milestone checkpoints, the fully loaded guarantee cost, and the named leader who will own the no-fault decision all get written into the requisition before it opens. If any of the five answers is "we'll figure it out later," the offer is not ready to go out. The 48 hours of delay that introduces is the cheapest insurance in the entire revenue cost structure.

Restarting nothing when the ground moves. Four events legitimately reset or extend the ramp clock and almost nobody documents them: a territory re-cut that removes half the accounts the rep was underwritten against, a comp plan change mid-ramp (you cannot ramp on mechanics that are moving), a manager transition mid-ramp (add 30 days — the new manager needs evaluation time and the rep needs to rebuild trust), and a product or packaging overhaul that invalidates the pitch the rep just learned. Each of these deserves a written reset with the comp plan and the decision deadline moved accordingly. Organizations that skip this fire reps for a territory decision the reps did not make.

Measuring ramp on the wrong indicator. Bookings lag by one full deal cycle, so grading a nine-month enterprise ramp on bookings means the first honest data point arrives at month nine — one month before the decision deadline. Grade on leading indicators instead: pipeline coverage against the tiered expectation (1x by month two, 2x by month four, 3x by month six), multi-threaded contacts per target account, self-sourced share of opportunity volume, and forecast accuracy on the rep's own deals. Those are visible early enough to act on.

Holding the rep accountable for the manager's failure. When a rep is on the productivity curve but pipeline coverage misses, the diagnosis is almost always upstream — insufficient coaching cadence, thin enablement content, weak marketing support in the territory, or a manager who has not run the account-planning session. Ramp adherence belongs on the manager's scorecard, reviewed monthly with their VP. Managers evaluated on ramp adherence coach hard in the first 90 days; managers without checkpoints drift, and drifting managers produce drifting reps.

Failing the top of the distribution. The mirror-image error of tolerating slow ramps is treating a fast one as ordinary. An SDR beating milestones by 30%+ at day 60 should be on a documented promotion path by day 90. Top-decile SDRs move into closing seats in 12–15 months and re-ramp into AE roles with roughly half the time cost of an external hire — you have already paid for the product knowledge, the customer exposure, and the cultural fit. Let that person stall and a competitor buys the ramp you funded.

No shared standard across managers. The fastest diagnostic for an inherited org is to ask five first-line managers the same question: what is the documented ramp expectation for a new AE on your team? Five different answers means there is no standard, only folklore. Round it out with four more checks. Plot every rep's tenure against attainment — a tight curve climbing through 25/50/75/100 across the first four quarters means discipline; a scattered cloud means every hire is on a custom path. Bucket the last 18 months of terminations by tenure — healthy organizations resolve most non-ramp failures inside the no-fault window; broken ones resolve the majority after month nine, which means they carried known misses for two quarters. Read the last year of offer letters and count how many contain a ramp window, milestone checkpoints, and a no-fault structure. And sit in on three forecast calls listening for whether new reps' deals get flagged as partial-confidence ramp deals or get committed like tenured pipeline — if managers are not drawing that line, ramp variance is silently polluting the forecast.

The downstream payoff of fixing all this is not just better hiring decisions. It is a capacity model that produces an honest number. When the ramp matrix is real, the plan says $13.96M against an $18M target in January rather than in December, and the leadership team gets eleven months to decide whether to add headcount, cut the target, or shift the mix. That is the entire value proposition of the discipline: not that it makes reps ramp faster, but that it makes the shortfall visible while there is still time to do something about it.

Related questions

How does ramp differ for a rep hired into a brand-new territory versus an inherited book?

A rep inheriting an active book can produce from existing late-stage deals in month two, which compresses the visible ramp by 30–60 days. A greenfield territory has no inherited pipeline, so the full deal cycle stacks on top of the learning curve. Underwrite greenfield at the role default plus 30 days.

Should ramp expectations appear in the offer letter or only in the onboarding plan?

The offer letter. Putting the window, the milestone checkpoints, and the stepped guarantee in writing before acceptance converts ramp from an opaque internal target into a shared expectation. It dramatically reduces the political drama at the retain-or-terminate conversation, because both parties agreed to the standard before day one.

Does ramp apply to non-revenue roles like implementation or support?

Yes, with different currency. Implementation consultants ramp on billable utilization — roughly 40% in month one to 75–80% by month four or five. Support engineers ramp on resolution rate and escalation frequency over 60–90 days. Any role feeding a committed number needs a documented curve.

What happens to the ramp clock if the comp plan changes mid-window?

Restart it from the change date. A rep cannot ramp against mechanics that are moving underneath them, and annual comp redesign landing mid-ramp is one of the most common and least acknowledged causes of ramp failure in mid-stage organizations. Document the restart and move the decision deadline with it.

How do you model ramp for a whole team hired at once, like a new segment launch?

Worse than the sum of individuals. Simultaneous cohorts overload the manager's coaching capacity and there is no tenured peer to shadow. Add 30 days to the role default for any cohort exceeding three reps per manager, and stagger start dates two to four weeks apart where recruiting allows.

FAQ

What happens if a new hire is not hitting the 50% productivity midpoint?

Treat it as a hiring miss rather than a coaching gap. If a rep is not at half of full productivity by the midpoint of their window — month two of a four-month mid-market ramp, month four or five of a nine-month enterprise ramp — the S-curve does not leave enough runway to reach the plateau inside the window. The honest move is to escalate to the documented checkpoint conversation immediately rather than hope through another quarter of guarantee dollars.

Should ramp timelines differ for internal promotions versus external hires?

The baseline matrix still applies, but internal moves often run 30–40% shorter because product knowledge, customer context, and internal navigation are already banked. The mistake is assuming internal promotions need no formal ramp at all. They need the same stepped quota, the same guarantee structure, and the same checkpoints — just compressed. And a first-time-in-role modifier of +30 to +60 days often cancels out the internal-knowledge advantage entirely.

Does a candidate with 10+ years of experience deserve a shorter window than a new grad?

Experience changes the starting point on the productivity curve, not the length of the window. A senior hire may hit the 50% checkpoint faster, but they still need the full window to build pipeline, learn internal systems, and establish credibility with a new buyer set. The matrix is role-based with career-stage modifiers layered on top — not experience-based. The one genuine exception is a direct competitor hire selling the identical persona.

Can you shorten ramp for an obvious top performer?

Rarely, and it is a common trap. Even exceptional hires need the full window to build pipeline depth and process fluency, because deal cycle length is a property of the buyer, not the seller. What you can do for a fast ramper is accelerate scope — more territory, larger accounts, a promotion path — rather than compress the clock. Shortening the window mostly produces premature performance reviews against pipeline that has not had time to exist.

What is the difference between ramp and probation?

Ramp is a productivity timeline with financial guarantees attached. Probation is a legal and HR construct governing termination terms. They frequently overlap in duration but serve different purposes, and mixing them muddies performance conversations. Ramp should be tied explicitly to quota relief, stepped guarantees, and milestone checkpoints. Probation should live in a separate contractual clause with its own language.

How do you handle ramp when the team is already behind quota?

Do not compress it — that reliably makes the gap worse by producing burnout and higher first-year attrition. Hold the timeline fixed and adjust the pipeline coverage model to reflect the new hire's delayed contribution, so the forecast tells the truth. Then front-load support: shadowing, deal assistance, and manager-led account planning. The gap gets closed by tenured capacity or by resetting the target, not by pretending the curve is shorter than it is.

Sources

• https://www.shrm.org/ — SHRM research on onboarding practices, time-to-productivity, and first-year retention.
• https://hbr.org/ — Harvard Business Review on onboarding effectiveness, internal promotion, and executive transitions.
• https://www.gartner.com/en/sales — Gartner sales research on enablement, quota setting, and seller productivity.
• https://business.linkedin.com/talent-solutions — LinkedIn Talent Solutions data on hiring benchmarks and tenure by role.
• https://www.bls.gov/ — U.S. Bureau of Labor Statistics on employee tenure, turnover, and occupational job openings.
• https://www.salesforce.com/resources/research-reports/state-of-sales/ — Salesforce State of Sales on seller time allocation and productivity.
• https://www.gainsight.com/resources/ — Gainsight customer success research on CSM book sizing and expansion motion.
• https://www.mckinsey.com/capabilities/growth-marketing-and-sales — McKinsey growth and sales practice on go-to-market capacity planning.
• https://www.atd.org/ — Association for Talent Development on onboarding program design and time-to-competence.

Related on PULSE

• What data sources are most effective for training AI models to predict next best action in complex enterprise deals?
• How does the expanding size of B2B buying committees increase the risk of vendor consolidation paralysis?
• Which vendor consolidation strategies are failing most often when integrating AI sales tools into existing stacks?
• Why are longer sales cycles now correlating with a shift from pipeline velocity to deal value predictability?
• What specific metrics are B2B RevOps teams using to measure AI's impact on lead quality in the top-of-funnel?