Privacy Settings
Thinking

SDR Ramp Time: Benchmarks and How to Cut It

5 min read

SDR ramp time typically runs a few months, and most of that time goes on learning answers the organisation already has: product facts, objection responses, and the tribal knowledge locked in senior reps' heads. Cutting ramp means moving that knowledge into new reps' calls faster.

How long does SDR ramp take?

Ramp time is the period from a rep's start date to full productivity, usually defined as the first month they carry full quota. For SDRs, a cleaner version is the first month they book the expected number of qualified meetings.

Benchmark surveys have put the average at around three months for years. The Bridge Group's sales development research measured average ramp at 3.3 months in 2016, down from 3.8 months two years earlier (summary at For Entrepreneurs). Teams selling technical products to technical buyers often report five or six months before a rep holds a full number.

The reason the number matters is tenure. The same research put average SDR tenure at 1.4 years. If a rep spends three of those seventeen months below full output, roughly a fifth of their time in the seat is ramp. Cut ramp by a month and you buy back productive weeks from every single hire, forever.

Treat the benchmarks as context rather than targets. The useful question is what your reps actually do during those months.

What actually consumes ramp time?

New reps learn the dialler, the sequencer, and the CRM in the first week or two. Tools are rarely the bottleneck. What takes months is knowledge:

  • Product answers. What the product does, what it does not do, how it differs from the two competitors every prospect mentions, what the pricing logic is. A prospect's third question is usually one the rep has never heard.
  • Objection patterns. "We already use X." "Send me an email." "We have no budget until Q3." Every team has perhaps twenty objections that cover most calls, and good responses to each already exist somewhere.
  • Tribal knowledge. Which personas actually buy. Which case study lands with finance versus engineering. Which phrase your best SDR uses to reframe a pricing question. None of it is written down; all of it lives in the heads of people who ramped years ago.

Notice what these have in common: the organisation already knows the answers. Ramp is slow because transfer is slow. The default transfer mechanism is a new rep slowly absorbing knowledge through months of calls, most of which go worse than they needed to.

How do you cut SDR ramp time?

Six levers, roughly in order of effort:

  1. Build the answer key from real calls. Pull your last hundred recorded calls, list the questions and objections that actually occur, and write the responses your best reps actually give. This beats a messaging doc written by marketing, because it reflects what prospects say rather than what you wish they said.
  2. Certify on scenarios. Replace "finish the onboarding modules" with "handle these fifteen scenarios convincingly". A rep who can respond to the top objections cold is ramped for practical purposes, whatever week they are in.
  3. Roleplay the highest-stakes moments. Simulation tools such as Hyperbound let reps rehearse openers and objection handling against an AI buyer before burning real leads. Practice reps used to cost a manager's afternoon; now they cost nothing.
  4. Put the answers on screen during real calls. A real-time sales assistant like Caretta listens to the live conversation and surfaces the relevant answer, proof point, or objection response as the prospect raises it. This changes the ramp equation directly: the rep no longer needs to have memorised everything before they dial, because the organisation's knowledge is present on the call with them.
  5. Get reps into real conversations early. Aim for week two. Real calls generate the questions that make training stick, and with answers available live, early calls stop being lead-burning exercises.
  6. Review the rep's own calls weekly. Ten minutes on two of their real calls teaches more than an hour of generic training, because the feedback attaches to something they said.

What does not cut ramp time?

Some popular fixes consume weeks and move nothing:

  • More shadowing alone. Passive listening without a framework teaches imitation of surface behaviour. Two or three annotated calls with a manager explaining why each move worked are worth more than two weeks on mute.
  • Longer onboarding decks. A 90-slide product deck does not survive contact with a live prospect. Reps forget most of it before their first connect, then relearn the useful tenth of it from real calls anyway.
  • Extending the classroom period. Delaying real calls delays the feedback that drives learning. Ramp measured from start date gets longer, not shorter.
  • Generic sales training. Frameworks help, but they do not contain your product answers or your objections, which is where the months actually go.

Should new SDRs memorise everything before they dial?

This is the assumption behind most onboarding programmes, and it is worth questioning. The traditional model front-loads knowledge: learn the product, learn the objections, pass the certification, then dial. Roleplay tools improve the practice step, and they are genuinely useful for building composure and delivery.

But rehearsal still assumes the rep must carry every answer in their head before the call starts. A real-time assistant drops that assumption. When the answers appear on screen during the live call, drawn from your docs, CRM, and your top reps' actual calls, a second-week SDR can handle questions that used to require a second-year memory. The rep still learns, and faster, because they see the right response at the exact moment it is needed, on their own real calls.

The two approaches stack. Rehearse the ten moments where delivery matters most, and let live assistance cover the long tail of questions nobody can fully prepare for. Our overview of what a real-time sales assistant actually does explains the mechanics, and if you are comparing tools, see our guide to real-time AI sales assistants by use case.

Ramp time is mostly knowledge-transfer time. Shorten the transfer and the months come off.

See what your new reps could answer in week one: book a demo.

Frequently asked questions

How long does it take for an SDR to ramp?
Benchmark surveys have put average SDR ramp at roughly three months from start date to full quota. Teams with complex or technical products often take longer, sometimes five or six months. The spread between companies is wide, so your own trend matters more than the industry average.
What does SDR ramp time mean?
SDR ramp time is the period from a rep's start date to full productivity, usually defined as the first month they hit full quota. Some teams instead track the first month a rep books the expected number of meetings, which is a cleaner measure for SDRs.
How do you reduce SDR ramp time?
Move the knowledge that already exists in your organisation to new reps faster. Build an answer library from real calls, certify reps on a short list of scenarios, use roleplay for the highest-stakes moments, and give reps live access to answers during real calls so they can dial before they have memorised everything.
Does more call shadowing reduce SDR ramp time?
Shadowing on its own rarely moves ramp much. Watching calls without a framework teaches reps to imitate surface behaviour, and the learning is slow and unstructured. A small amount of shadowing paired with annotated call clips and scenario practice works far better than weeks of passive listening.