AE ramp measures time to closed-won. SDR ramp measures time to qualified meetings. The jobs are different, the curves are different, and the capacity plan reads both numbers independently.
SDR ramp is the time between a new sales development rep's start date and the week they first produce qualified meetings at the full non-ramped quota. For B2B SaaS it typically takes 60 to 120 days, far shorter than AE ramp of 6 to 9 months. Standard milestones are week 1 to 2 for product and tool mastery, week 3 to 6 for scripted outbound, week 7 to 10 for pipeline contribution, and week 11 and after at full quota. SDR ramp is a core input to sales capacity math.
The six things to understand about SDR ramp before you plot a hiring schedule or set a quota for the next cohort of sales development reps, including why SDR ramp lives on a weeks timeline instead of a months timeline.
SDR ramp is the number of weeks between a new sales development rep's start date and the first week they book qualified meetings at or above their full non-ramped meeting quota. It is measured in weeks, not months, because the SDR activity cadence is daily and the output signal appears in days instead of quarters. Most teams track ramp in 2 week checkpoints across a 60 to 120 day window.
SDR ramp usually completes in 60 to 120 days depending on target market and tech stack. Transactional SMB outbound ramps in about 60 days. Mid-market ramps in about 90 days. Enterprise and account-based outbound ramps in about 120 days because the research load and multi-threading complexity are higher. The right window is driven by target-account complexity, not by what a founder wishes it could be.
AE ramp runs 6 to 9 months and measures time to closed-won against revenue quota. SDR ramp runs 60 to 120 days and measures time to qualified meetings against a meeting quota. The jobs are different, the training content is different, and the ramp curves are not comparable. Measure them separately or the capacity plan conflates two unrelated numbers.
The canonical SDR ramp has four checkpoints. Week 1 to 2 covers product and tool mastery with scripted practice calls. Week 3 to 6 covers scripted live outbound with a reduced quota. Week 7 to 10 covers measurable pipeline contribution against a stepped quota. Week 11 and after covers at-quota autonomy on the full non-ramped meeting number. Each checkpoint has written exit criteria the manager grades against.
SDR ramp is a core input to the sales capacity model. If AEs need 1,200 meetings next year and SDRs ramp in 90 days, hiring 10 SDRs in October will not produce the meetings the AE team needs in Q1. Ramp time, hiring lead time, and attrition compound in the staffing math. Companies that measure SDR ramp hire on a schedule finance can forecast. Companies that guess miss the AE pipeline target.
SDR ramp is observed, not written. A manager cannot assign a ramp time. The company sets a target ramp curve, hires against it, and measures each cohort's actual ramp against the target. Variance is the signal. Too slow means weak enablement, bad lists, or wrong profile. Too fast means the ramped meeting quota was set too low, not that the rep is a star.
SDR ramp runs on a weeks timeline, which is faster than AE ramp but still structured. The curve has four phases, and each phase has a specific exit gate. A manager who skips a gate is not accelerating ramp, they are turning the back half of the curve into a diagnostic problem no dashboard can resolve. The four phases below are the version most B2B SaaS teams converge on.
The new SDR learns the product in enough depth to answer a prospect's first two questions, learns the ICP and disqualifiers, and masters the stack (CRM, sequencer, dialer, LinkedIn Sales Nav). Exit gate is a product pitch delivered on a recorded practice call, graded against a rubric, plus a tool proficiency check. No live outbound in this phase.
The SDR starts live outbound with a scripted sequence, a prescribed call opener, and a reduced daily activity target. Call recordings are reviewed in the weekly 1:1. Meeting quota in this phase steps from 25 to 50 percent of the full non-ramped number. Exit gate is three accepted meetings in a single week plus a passing call-review score.
The SDR moves off scripts, personalizes outreach, and books meetings that pass AE acceptance criteria. Meeting quota steps from 50 to 100 percent of the full non-ramped number. Discovery call quality starts to appear in the data. Exit gate is three consecutive weeks at or above 75 percent of full meeting quota with an AE accept rate above the team floor.
The SDR carries the full non-ramped meeting quota, runs their own list and sequence selection, and participates in the standard team cadence. Managers stop grading against the ramp curve and start grading against the normal performance cadence. A rep who misses the week 11 gate is placed on an extended ramp with a specific gap to close, not quietly carried on the roster.
Every phase gate is written down and graded. Verbal pass or fail is how a 90 day ramp quietly becomes a 150 day ramp and the AE pipeline target slips. Mature SDR programs publish the rubric to the rep on day one, so the rep knows what counts as passing week 6 before week 6 arrives. The written rubric is the single highest leverage artifact in the program.
The weekly 1:1 reviews one recorded call, one sequence step performance, and one pipeline-impact number. The biweekly cohort session covers one new objection, one new persona, or one new tool trick. Managers who try to coach ramp in group settings alone slip the cohort by weeks. SDR ramp is a weekly 1:1 discipline, not a quarterly review.
SDR ramp is faster than AE ramp but the measurement traps are the same. Three methods are common and they do not all give the same answer. The right one for a given team depends on list quality, cycle length on the AE side, and whether the SDR quota is set on booked meetings or on held meetings. Picking a method and holding it steady matters more than picking the theoretically best one, because comparing cohorts quarter over quarter is only possible when the measurement does not drift.
Count the weeks from start date until the first week the SDR books meetings at or above the full non-ramped weekly meeting quota. Simple, clear, and matches the weekly cadence of the role. Weakness: a lucky week with one easy list can trigger a false signal. Pair it with a two-consecutive-weeks rule or an at-or-above-quota-in-three-of-four-weeks rule to filter the noise.
Measure when the SDR's trailing four-week meeting output annualizes to at least 100 percent of full quota. More stable because it averages out weekly spikes and droughts. Weakness: it needs four weeks of data before it produces a number, which delays early-cohort coaching signals and makes it harder to intervene in week 5 or 6.
Measure each week whether the SDR hit the stepped ramped quota for that week. An SDR who hits ramped quota every week is declared ramped at week 11 regardless of single-week full-quota attainment. Great for compensation alignment and for coaching. Weakness: if ramped quotas are set too low, every rep ramps on paper while the AE pipeline target still misses.
Some teams count booked meetings as the ramp quota, some count held meetings, some count AE-accepted held meetings. All three are defensible. What is not defensible is drifting between them inside a single ramp cohort, because the ramp number stops being auditable. Pick one definition, publish it in the comp plan, and hold it for the full fiscal year.
Two SDRs with identical skill ramp at different speeds if their account lists carry different intent density. A ramp number that does not account for list quality blames people for a market problem. Mature programs tag lists by tier (A, B, C) and compare each SDR against the median for their tier, not the global median.
Ramp attainment must come from the same closed-meeting data the AE forecast uses, not from the sequencer dashboard. The two drift inside a quarter if they are not the same source, and when they drift the sales ops team loses credibility. Pull meeting counts from the CRM, by SDR, by held date, with a stable owner-change history, or the number is not auditable.
An SDR ramp program lives or dies on week-by-week visibility. If the manager cannot see at the end of week 5 whether a new SDR is tracking to curve, the first signal of a stall arrives in week 9, which is too late to fix without extending the ramp. If the SDR cannot see their own ramped quota, sequence performance, and meeting output, they lose the thread by week 4. A CRM that keeps the ramp curve, ramped quota, sequence performance, and meeting output on the same screen is what turns the written target into a tracked outcome. The loop usually looks like this.
Each new SDR has a ramp card that shows week-since-start, ramped quota for the current week, meetings booked against ramped quota, AE accept rate, and the trailing four-week annualized attainment. The manager scans the cohort in under two minutes and knows which SDRs are on-curve, which are drifting, and which need an intervention this week instead of next month.
Strkr steps an SDR's meeting quota through the ramp schedule automatically (0, 25, 50, 75, 100 percent across the 11-week curve, or whatever the plan is). Compensation and attainment math all read the stepped number for the current week. Managers do not re-enter quotas every two weeks, and SDRs see the right target in their home screen at all times.
The SDR home screen shows the daily activity baseline (dials, email sends, LinkedIn touches) alongside booked meetings against the current week's ramped quota. Drift in activity shows up on day two instead of week two, so coaching conversations are specific. The connection between inputs and outputs stays visible, which is the single most useful habit a new SDR can build.
Strkr AI reads call recordings, sequence performance, and reply tone to flag coachable ramp-stage patterns: opener skipping the discovery hook, reply rate below the cohort median, call duration under the floor, follow-up SLAs breached. The weekly 1:1 agenda becomes specific instead of generic, which is how ramp coaching stays useful through week 7.
A booked meeting that gets rejected by an AE is not real pipeline. Strkr tracks AE accept rate on every SDR's ramp card so quality shows up alongside quantity. SDRs who book a lot of rejected meetings get coached to the ICP in week 6 instead of week 10, and the ramp number stops being a vanity metric.
Sales ops opens a cohort view that plots the median ramp curve for each hire month against the target curve. A cohort trailing target for three months in a row is a program problem that gets fixed by enablement, not a hiring freeze. The capacity plan and the enablement plan work from the same data, which is the only way they ever stay aligned.
Strkr steps ramped meeting quotas automatically, plots the ramp curve against target, surfaces coachable patterns from call recordings and sequence data, and shows cohort attainment on a single dashboard. The ramp becomes a tracked outcome instead of a spreadsheet reviewed too late, which is the only reason AEs ever get the pipeline the capacity plan said they would.
SDR ramp typically takes 60 to 120 days depending on target market and tech stack. Transactional SMB outbound ramps in about 60 days. Mid-market ramps in about 90 days. Enterprise and account-based outbound ramps in about 120 days because the research and multi-threading load is higher. The right window is driven by target-account complexity and sales cycle length on the AE side, not by what the hiring plan wishes it could be.
AE ramp measures the time to closed-won against a revenue quota, usually 6 to 9 months in B2B SaaS. SDR ramp measures the time to qualified meetings against a meeting quota, usually 60 to 120 days. The jobs are different, the training content is different, and the ramp curves are not comparable. The capacity plan reads both numbers independently because a slow SDR ramp starves AEs of pipeline, and a slow AE ramp wastes the pipeline SDRs produced.
The standard milestones are week 1 to 2 for product and tool mastery with no live outbound, week 3 to 6 for scripted outbound at reduced quota, week 7 to 10 for pipeline contribution at a stepped quota, and week 11 and after at the full non-ramped meeting quota. Each milestone has written exit criteria the manager grades against. Verbal pass or fail is how a 90 day ramp quietly becomes a 150 day ramp.
The three common methods are weeks to first full-quota week (simple, prone to lucky-week noise), weeks to trailing-four-week attainment at full annualized quota (more stable), and ramped-quota attainment path (hit the stepped quota every week). All three should pull from CRM meeting data instead of the sequencer, segment by list tier to avoid blaming people for a market problem, and use a consistent booked-versus-held definition for the full fiscal year.
A ramped SDR quota is a reduced weekly meeting target that steps up across the ramp period until it matches the full non-ramped quota. A standard 11-week ramp might use 0, 0, 25, 25, 50, 50, 75, 75, 100, 100, 100 percent of full across the weeks. The ramped quota drives compensation and coaching during the curve. Full quota is used to measure when ramp is actually complete and the SDR moves to the normal performance cadence.
SDR ramp directly controls when new hires contribute meetings. If AEs need 1,200 meetings next year and SDRs ramp in 90 days, hiring 10 SDRs in October will not produce the meetings AEs need in Q1. Ramp time, hiring lead time, and attrition compound in the staffing model. Companies that measure SDR ramp hire on a schedule finance can forecast. Companies that guess miss AE pipeline targets, usually in the back half of the year.
The common causes are weak enablement content, no measurable weekly exit criteria, poor list quality, wrong SDR profile for the role, missing playbook or sequence library, no call-review cadence, and a manager who skips the weekly 1:1. The curve diagnoses which one. A flat week 5 points at enablement or list. A curve that never reaches target points at profile. A curve that spikes then drops back points at coaching.
Yes, and usually one of two things is happening. Either the SDR is a senior hire whose prior experience compresses the learning curve, or the ramped meeting quota is set too low and SDRs are hitting a target that does not reflect real productivity. Fast ramp is worth investigating, not just celebrating. Cohorts that consistently ramp faster than target are a signal the ramped quota needs a yearly recalibration against the AE pipeline target.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
