Measure ramp against a defined productivity result. Set the finish line, watch the signals that lead to it, and require the result to hold for a chosen window before calling the ramp complete. For sales development representatives, the quality of the sequences and messaging provided, rather than built from scratch, is a primary source of ramp variation, so review the setup around the hire as closely as the hire's output.1
Set the finish line
Choose the outcome that ends the measurement. Write the target before the hire starts and keep its definition stable while you compare progress.
Ramp time is how long it takes to bring a new salesperson to 100 percent productivity.2 For sales development and business development representatives, one reference point is a median of 3.2 months to reach 80 percent of booked-meeting quota.3 A reported range is 2 to 5 months, depending on outbound complexity and tooling familiarity.4
Use these figures as a sense check, not as a substitute for your own definition. Ramp time varies by role, deal complexity, and product type.5 Decide whether the endpoint is full quota, a booked-meeting threshold, or another observable output. Record the start date, target, and rule for sustained performance.
Build the measurement path
Your dashboard should show movement before the final outcome arrives. Order the measures by when a new hire encounters the work so you can find the earliest break.
Teams should instrument both leading and lagging indicators during ramp.6 Use activity volume in weeks 1 to 4, meeting quality scores from account executives in weeks 4 to 8, opportunity creation rate in months 2 to 4, and pipeline value in months 3 to 6 as leading indicators.7 Track the first qualified meeting, pipeline created, and conversion rates from outreach.8
At the representative and cohort levels, track call-score improvement, talk-track adherence, and objection handling, then connect those measures to ramp time and win rate.9 Have each rep record the path to quota every week and use one-on-ones to check whether the rep is on pace.10
In each review, ask:
- Which activity changed since the last check?
- Where did the handoff from activity to meeting quality weaken?
- What behavior should improve before the next checkpoint?
Move to the next checkpoint when the current one gives you enough signal to interpret it. If the activity record is incomplete, fix it before drawing a conclusion from pipeline or quota.
Model milestones
Give the path checkpoints that show progress before the endpoint. Each milestone should show what the person can produce now and what still needs work.
Representative ramping is typically modeled as a vector showing the percentage of steady-state productivity reached in each of the first four quarters.11 For an operating view, measure the share of the cohort reaching staged quota targets at 30, 60, and 90 days.12 Set those targets before the cohort starts so the review compares performance with a known expectation.
Tie each decision criterion to an onboarding milestone you track.13 A meeting-quality checkpoint should show whether the person can run the conversation at the expected standard. An opportunity checkpoint should show whether that quality turns into qualified pipeline. This distinction prevents the team from treating every missed result as the same problem.
Decide when ramp is complete
The endpoint needs a rule that can withstand a good week. Choose it before reviewing individual results, then apply it consistently across the cohort.
Choose a sustainment window, such as two consecutive months, and normalize the result for territory or product complexity.14 Record each rep's start date and the first month they reach 100 percent of quota, calculate the average across new hires, and track the trend over time.15 Track performance until the cohort consistently reaches the target.16
Keep individual elapsed time separate from the cohort average. A person can reach a milestone while still falling short of sustained productivity. In the review, ask whether the target held through the chosen window, whether the leading indicators support the result, and whether the same performance can be repeated without unusual help.
Diagnose a stall
When a measure stalls, find the earliest point where performance breaks. Use that point to choose the next coaching or onboarding action.
Compare calls, meetings, and pipeline generated per rep with the same measures from tenured performers.17 Track how long reps take to reach full productivity, where they stall, and which onboarding activities precede faster ramp.18 Use the earliest broken measure as the diagnosis point.
If activity is low, inspect the workflow and the training attached to it. If activity is healthy while meeting quality or pipeline trails, inspect talk-track use, objection handling, and conversion. If role-play performance is part of the program, keep the score history to see whether the pattern is improving or declining.
Ask the rep:
- Which step feels least repeatable?
- Where do prospects stop advancing?
- What part of the process still needs live support?
Use the answers to choose the next thing to test. Change one part of the onboarding path, then watch the same measure again.
What not to do
These errors make ramp time look like a rep problem when measurement or setup is causing the confusion.
- Giving a sales development representative no sequences, coaching, or defined target customer profile creates a significantly longer ramp.19
- Treating a role-play score as a verdict from one session hides whether performance is improving or declining. Review scores over time for a pattern.20
- Skipping cohort comparisons makes it hard to tell whether process changes improve ramp speed.21
- Ignoring ramp time by manager hides which managers produce the fastest-ramping reps.22