Ramp time isn't a write-down. It's a metric you can move.

Most founders treat ramp time the way accountants treat a write-down: a cost you already knew was coming, so you absorb it, note it, and move on. Three months of salary before an SDR closes their first real pipeline isn’t a surprise — it’s priced in. The mistake is stopping there. Ramp time isn’t a fixed cost you endure once per hire. It’s a metric, and it moves — and moving it compounds in a way that a one-time write-down never does.

The benchmark, and why it’s a range, not a fact

Our own ramp-benchmarks post puts SDR/BDR ramp at 1–3 months, and multiple 2026 sources converge close to the top of that range — Bridge Group’s SDR research (the same organization behind the 4.2x AE quota multiplier the calculator uses) puts the industry figure around 3 months. The single best predictor of that number, per the same post: sales cycle length. Minimum ramp is roughly one cycle, full ramp roughly two. That’s the part worth sitting with — ramp time isn’t a random variable, it’s downstream of specific, nameable things about how your motion works.

The compounding math

Here’s the calculation, built on two numbers this blog has already sourced separately: average sales rep tenure is 18 months (HubSpot, via Xactly), and SDR ramp runs close to 90 days. Hold tenure fixed at 18 months and just move the ramp number:

• 90-day ramp:15.0 productive months out of 18 — 83% of the rep’s tenure spent producing.
• 60-day ramp:16.0 productive months out of 18 — 89%.
• 45-day ramp:16.5 productive months out of 18 — 92%.

Cutting ramp from 90 to 60 days doesn’t just save a month of salary once. On an 18-month average tenure, it’s a real increase in the fraction of that tenure spent producing — and that fraction is exactly what a write-down mindset never asks about, because a write-down is a number you absorb once, not a ratio you can improve. To be clear about what this math is and isn’t: it’s illustrative arithmetic on two independently-cited figures, holding tenure constant — not a claim that a faster ramp mechanically extends how long someone stays. Tenure and ramp speed are plausibly correlated in reality (a rep who ramps fast is probably also more engaged), which would make the real effect larger, not smaller — but that’s a direction, not a number we’re claiming to have measured.

Why this compounds instead of just adding up once

A write-down happens once per hire and is forgotten. A ramp-time improvement is a process change, and process changes pay out differently:

• It repeats on every hire. Fix the onboarding flow or the pipeline handoff once, and every SDR you hire afterward starts from the improved number, not the old one.
• It scales with headcount growth. A fixed process fix is worth more the more you’re hiring — five SDRs this year, ten next year, the same fix pays out on all fifteen.
• It raises effective bench capacity for free. Shrink the ramp window and, at any given moment, a larger share of your current headcount is fully productive rather than still climbing — more realized output from the same number of seats, no new hiring required.

What actually moves the number

Search around for “how much does structured onboarding cut ramp time” and you’ll find percentages all over the map — 30%, 40%, 50%, 70%, depending which site you land on, almost none of them tracing back to a named study. We’re not going to repeat one of those numbers here just because it sounds precise. What’s consistent across the sourcing, even without a trustworthy magnitude attached, is the direction and the levers:

• Cycle-length levers are structural, not motivational. Since ramp scales with cycle length, anything that shortens the rep’s path to a first real deal cycle — better-qualified pipeline at handoff, a tighter ICP, fewer stakeholders to route through — moves the ramp number directly, not just morale.
• Internal promotion starts further along the curve. A promoted BDR already knows the product, the objections, and the team — the part of ramp that’s about learning the motion, not learning to sell, is mostly already done. That’s the same mechanic behind promoting from inside instead of a cold AE hire.
• A published ramp schedule doesn’t shrink ramp, but it protects the number you have. Scoring a ramping rep against full quota in month one doesn’t make them ramp faster — it just makes founders conclude someone’s failing when they’re on schedule, which is its own, separate way to lose the hire before the real number ever gets a chance to show up.

What to do next

If you don’t know your own ramp number, start with the benchmark reference to see where your role and stage should land, then track your actual hires against it instead of a single flat quota. If you’re deciding whether to invest in shrinking that number at all, the math above is the case — it’s not a one-time fix, it’s a ratio that pays out on every hire you make from here on.