-
1
Write the 30-day goals around learning, shadowing, and the first real discovery call
The first 30 days are about building a working model of the product, the buyer, and the sales motion, not about hitting pipeline numbers. Write the 30-day goals in three buckets: product knowledge (pass the product certification with a live demo scored by the manager), shadowing (observe at least 10 live calls across discovery, demo, and negotiation stages), and the first real discovery call by day 25 to 30 with the manager on the line. The point is to get the rep in front of a buyer before the month closes so the gap between classroom and reality shows up early, while the manager still has time to course-correct inside the ramp window.
- Day 1 to 7: product sandbox, playbook read-through, and a written test on ICP, pricing tiers, and the top three competitors.
- Day 8 to 20: shadow at least 10 live calls (4 discovery, 4 demo, 2 negotiation) and write a short pattern note after each one.
- Day 21 to 25: pass product certification by delivering a live demo scored by the manager on a shared rubric.
- Day 26 to 30: run the first real discovery call on a warm pre-qualified lead with the manager on mute as backup.
Tip: Do not let the rep touch outbound prospecting in the first 30 days. Early outbound without a working product and buyer model burns leads the team cannot afford to burn, and the rep learns the wrong lesson from early rejections.
-
2
Write the 60-day goals around first qualified opp, first solo demo, and a pipeline-gen target
Days 31 to 60 shift the rep from learning to generating. Write the 60-day goals around three measurable outcomes: at least one qualified opportunity sourced and advanced to the demo stage, at least one solo demo delivered without the manager co-piloting, and a pipeline-generated target set at roughly 50 percent of a tenured rep's monthly bar. This is also when the rep starts owning their own book of sample accounts, running outbound sequences built from the playbook, and logging activity in Strkr the way the full team does. The goals are written as numeric targets, not as effort proxies, so the rep knows exactly what good looks like before the month starts.
- At least 1 qualified opportunity sourced by the rep and advanced to demo stage, using the team's written qualification criteria.
- At least 1 solo demo delivered without the manager leading, scored on the demo rubric by both the manager and the mentor.
- Pipeline-generated target set at ~50 percent of a tenured rep's monthly bar, measured on created pipeline, not just activity counts.
- Full CRM hygiene: every activity logged, every next step dated, every deal with a documented reason for its current stage.
Tip: If the rep is behind on the 60-day pipeline target by week 7, do not extend the ramp quietly. Pull them into a focused coaching block on the specific stage where the drop-off is happening (usually discovery-to-demo), rather than adding more activity volume on top of a broken motion.
-
3
Write the 90-day goals around first closed deal and a 25 percent quota ramp
Days 61 to 90 are the proof window. Write the 90-day goals around a first closed-won deal (new logo or expansion, depending on segment), a quota ramp set at roughly 25 percent of a tenured rep's monthly quota, and a demonstrated ability to run a full-cycle deal from sourced lead through signed order form without the manager stepping in on structural decisions. By day 90 the rep should be running a weekly pipeline review the same way the rest of the team does, forecasting their own number inside a 10 to 15 percent accuracy band, and asking for feedback on specific moments rather than needing it pushed. If any of those three signals are missing at day 90, extend ramp by 30 days with a written plan rather than silently rolling the rep into full quota and setting up a performance conversation two months later.
- At least 1 closed-won deal (any size that meets the segment's minimum ACV floor) sourced or progressed by the rep.
- Quota ramp at ~25 percent of a tenured rep's monthly quota, measured on booked revenue the rep can defend in forecast.
- A full-cycle deal run end-to-end: sourced lead, discovery, demo, pricing, procurement handoff, and signed order form.
- The rep runs their own weekly pipeline review segment and forecasts their number inside a 10 to 15 percent accuracy band.
Tip: Celebrate the first closed deal publicly in the team channel with the specific moment that made it work (the question that opened the budget, the proof point that closed the loop). The team learns the pattern, and the ramping rep learns that the plan is a path to recognition, not a scorecard waiting to catch them out.
-
4
Build a weekly 1:1 cadence that holds through all 90 days
A 30/60/90 plan without a weekly 1:1 is a document in a shared drive. Book a protected 45-minute 1:1 with the ramping rep every week, same day and time, with an agenda template that walks through the current month's goals, the trailing week's calls and deals, and one development priority tied to the next step on the plan. Keep the 1:1 separate from forecast and from team pipeline review so skill coaching never gets crowded out by number-chasing. The mentor runs a second 30-minute weekly check-in focused on tactical plays and in-the-moment questions, so the rep has two different surfaces to raise issues on before they become a ramp risk.
- Book a 45-minute weekly 1:1 for the full 90 days as a recurring hold labeled onboarding, not just 1:1.
- Run every 1:1 off the same agenda: current-month goals, last week's calls and deals, one development priority, one written commitment.
- Add a 30-minute weekly mentor check-in on a separate day for tactical questions the rep is not ready to raise with the manager.
- Open each 1:1 by replaying one specific call or deal moment, not by reading status; replace status with a shared ramp dashboard.
Tip: If the weekly 1:1 slips three weeks in a row, that is the single strongest predictor the ramp will miss. Fix the cadence before you blame the rep or the content, and never reschedule the onboarding 1:1 for a forecast call.
-
5
Define a three-gate certification path: shadow, role play, live
Reps who skip straight from classroom to live buyers blow trust with the pipeline and learn the wrong lessons from early misses. Build a three-gate certification path and require the rep to pass each gate before advancing. Gate one is shadow: 10 observed calls across stages with a written pattern note per call. Gate two is role play: a scored mock discovery and mock demo with the manager and one tenured peer, graded on the same rubric used for live calls. Gate three is live: supervised real calls with the manager on mute as backup, graduating to solo once the rep clears two consecutive calls at or above the team average rubric score. Write the gates into the plan with a target day and a scoring threshold so there is no ambiguity about when the rep moves forward.
- Gate 1 Shadow: 10 observed calls (4 discovery, 4 demo, 2 negotiation) with written pattern notes submitted to the manager.
- Gate 2 Role Play: scored mock discovery and mock demo with the manager and one tenured peer, graded on the live-call rubric.
- Gate 3 Live: supervised real calls with the manager on mute, graduating to solo after two consecutive at-or-above-average scores.
- Freeze the thresholds for the full quarter so passing the gate feels fair, and publish them to every rep on day 1 of onboarding.
Tip: Score the first role-play round with the manager and one other tenured rep sitting in. If the two scorers disagree by more than one point on any rubric dimension, the rubric wording is too loose and the whole certification path will drift inside a month.
-
6
Measure ramp velocity against the plan, not just at day 90
Ramp velocity is the leading indicator the plan is working, closed-won is the proof. Build a simple weekly dashboard that tracks each milestone (certification pass, first opp, first demo, first closed deal, pipeline-gen target, quota ramp) against the planned day it should land, and plot the trend across the full 90 days. Pair the milestone trend with the rubric scores from the weekly 1:1 so you can see when skill lift is tracking but the pipeline math has not caught up yet, which is normal inside the ramp window. Review the dashboard with the rep at every 1:1 so there are no surprises at day 90, and the rep sees progress accumulating week over week instead of waiting for a quarterly verdict.
- Chart each milestone's planned day vs actual day on a shared ramp dashboard the manager and rep both see weekly.
- Pair milestone progress with weekly rubric scores so skill lift and pipeline math get read together, not in isolation.
- Flag any milestone that slips by more than 7 days as a yellow signal and trigger a focused coaching block, not a status comment.
- Compare the ramp curve against the trailing three new hires on the team so each rep's trend has a cohort baseline to read against.
Tip: If the ramp dashboard shows every rep slipping on the same milestone (usually first qualified opp), the plan is wrong, not the reps. Rewrite that milestone or the training step before it, and do not keep running cohorts into the same wall.
-
7
Protect the plan when the business gets noisy
The single most common reason onboarding plans fail is the manager reassigning the ramping rep to a fire drill in month two. Someone leaves, a territory opens, a big deal needs an all-hands, and the ramping rep gets pulled off plan with a vague promise to catch up later. The catch-up almost never happens cleanly. Write protection into the plan: the ramping rep does not pick up quota accounts outside the ramp territory, does not get pulled into deal reviews that are not theirs, and does not inherit a departed rep's book inside the 90-day window. If a business reality forces an exception, write it down, extend the ramp by a documented amount, and tell the rep in the 1:1 the same week it happens. Silent extensions and silent compressions are both ways the plan loses credibility inside a quarter.
- Write guardrails into the plan: no quota accounts outside the ramp territory, no inherited books, no fire-drill reassignments inside 90 days.
- If a business reality forces an exception, extend the ramp window by a documented number of days and update the dashboard the same week.
- Keep the mentor and the manager on the same page about guardrails so the rep does not get conflicting pulls from different directions.
- Review guardrail adherence at the end of each 30-day block so creeping exceptions get caught before they compound into a missed ramp.
Tip: Treat the ramp window the same way you treat the forecast window with your CFO: hard commitments on both sides, written exceptions, and no surprises at the end of the quarter.
-
8
Iterate the plan every quarter against ramp evidence
Freeze the 30/60/90 plan for a full cohort, then open it up for revision at the end of each quarter. Pull the ramp dashboard for every rep who graduated or missed, run a 30-minute ramp retro per rep on what moved and what did not, and ask the team which parts of the plan felt most useful versus which felt like busywork. Rewrite the goals, the certification thresholds, or the mentor commitments based on what the data and the reps both say. Treat the onboarding plan the way you treat the sales playbook: a living document that evolves with the segment, the product, and the team, not a template that gets copied forward for four quarters without a second look.
- Run a 30-minute ramp retro with every rep who hit or missed the 90-day mark, inside two weeks of their day-90 review.
- Pull the paired ramp dashboard and rubric trend per cohort before the retro so the conversation starts on evidence, not opinion.
- Rewrite the plan in the same 30/60/90 structure every quarter so cohorts are comparable across time rather than freshly invented.
- Keep a changelog of plan versions and the business reason for each change so the plan has an auditable history for leadership.
Tip: If every cohort shows the same milestone slipping on the same day, that is the signal to rewrite the plan, not to coach the next cohort harder on a step that is systematically underbuilt.
