A 30-60-90 Sales Onboarding Ramp Built Around Practice Reps
The gate ladder is the artifact
Day-30 gate. Scenarios: a first discovery call with a distracted owner; the price question in minute two. Threshold: both passed at the rubric row's exit criteria, scored from the transcript. Grants: solo discovery calls on inbound leads. Decision: advance, repeat, or escalate.
Day-60 gate. Scenarios: a qualification review with a skeptical economic buyer; a stall on the decision process. Grants: mid-tier lead routing. Day-90 gate. Scenarios: a full demo with two interruptions; a late discount push. Grants: demo certification and unsupervised late-stage calls.
The gate ladder is that one page; without it, a sales onboarding ramp is a calendar with meetings on it. A gate ladder names the scenarios, the pass threshold, the privilege a pass earns, and the decision the manager must say out loud. Write it before the hire starts and hand it over on day one; the rep then practices for something specific instead of performing enthusiasm.
TL;DR
A gate ladder turns a 30-60-90 sales onboarding ramp from a countdown into privileges earned through scored roleplays. Each phase ends with named scenarios passed at a set threshold on the transcript, and each checkpoint forces a spoken decision: advance, repeat, or escalate. Dates say when to check; gates say what must be true first.
- Write the gate ladder before day one: scenarios, thresholds, privileges, decisions.
- End every phase with named scenarios passed at threshold, not topics covered.
- Gate privileges you control: solo discovery calls, lead-tier routing, demo certification.
- Force a decision at every checkpoint: advance, repeat, or escalate.
- Treat escalation as a hiring-quality conversation, never as more training.
Why is a 30-60-90 with dates but no gates just a countdown?
Time passes whether or not the rep is ready. A 30-60-90 with dates but no gates is a countdown, not a ramp. The calendar version measures survival to day 90, then rewards it with a full lead load as if survival were skill.
Time-in-role feels like a fair proxy: every hire gets the same clock. The trouble is what a clock cannot hear. Thirty days of shadowing look identical for the rep who can run discovery and the rep who can only talk about it, and confidence reads as competence everywhere except a scored roleplay, so a date-based sales onboarding plan advances the confident ahead of the capable.
The syllabus version gives itself away. Week 1, learn the product. Week 4, shadow calls. Week 8, first demo. HR wrote it, checkpoints exist, and nothing is at stake at any of them; the review meeting carries no decision, so it produces encouragement and another meeting.
Gates do put manager judgment back into a comp-adjacent decision; the clock's defenders are right to press there. The decision is still not an opinion. Scenario, rubric row, and threshold exist before the hire starts, and the evidence is a transcript anyone can read. Keep managers consistent by giving every hire the same named scenarios and blind-scoring one another's gate transcripts, we recommend one a month; appeals go to the transcript, not memory.
What should passing each gate turn on?
A privilege the manager actually controls: solo discovery calls at day 30, lead-tier routing at day 60, demo certification at day 90. Before the day-30 gate, every discovery call is paired or shadowed; after it, the rep takes inbound discovery alone. Passing day 60 moves the rep off the bottom lead tier into the mid-tier rotation the same afternoon. Demo certification means no unsupervised demo to a qualified account until the demo scenario passes at threshold. Budget the hidden cost: paired discovery and chaperoned demos are manager and senior-rep hours for the full 90 days.
Notice what is not on the list: pipeline access. Gating pipeline sounds rigorous and dies in the first comp review; in most plans the quota clock is already running and commission pays on closed revenue. The first gated rep who misses draw because leads were held back will be right, and the gate will be waived. The quota clock and the comp plan always win a fight over pipeline access, so gate privileges the manager controls outright.
Lead-tier routing survives that fight only inside the ramp window, where ramp quota and a protected draw keep lead tier from setting pay. A rep parked on the bottom tier at day 75 is annoyed, not underpaid, while the draw holds. A tier gate that outlives draw protection dies the same death, so end the ladder before the guarantee does.
The checkpoint agenda: advance, repeat, or escalate
The agenda fits on an index card. One: transcripts open, gate attempts read against the rubric rows, flags first. Two: the rep places themselves against each exit criterion before the manager speaks. Three: the decision, spoken and written down. Four: if repeat, which scenario re-runs, which rubric row, what date. We recommend 20 minutes; the decision is the agenda.
Advance means the privilege turns on the same day. Repeat means a named scenario against a named rubric row with a scheduled re-run; a repeat is a normal outcome of an honest threshold. Checkpoint dates hold; only gates slide. A rep who repeats day 30 and passes at day 45 still sits the day-60 checkpoint on day 60 with less runway, and a checkpoint whose gate is unattempted records repeat or escalate, never advance. The ladder is built to end before draw protection does, so no date moves.
Escalate is the word everyone writes into a sales onboarding plan and no one defines. Escalate means a hiring-quality conversation between the manager and their own leader, not another lap through the same training. After a repeated gate is missed again, the question is whether the transcripts still support the hire; a third training pass only defers it. Bring HR in at the first escalation, because if the answer is exit, the record already exists: transcripts, scores, and written checkpoint decisions.
Filling the phases: named scenarios, not topic lists
Named scenarios make a gate checkable; a phase that ends in a topic list ends in an opinion. Cover objections is a topic. A price push in minute two from a buyer who will not name a budget is a scenario, and a manager can read a transcript and say whether the rep held the standard.
The phase between gates is practice; the gate is measurement. Run each phase on the weekly practice format: short scored roleplays against the exact scenarios the gate names, one rubric row at a time. Days 1 through 30 belong to discovery, days 31 through 60 to qualification, where MEDDIC fits as a qualification checklist drilled letter by letter with buyer-verified evidence demanded for each letter, and days 61 through 90 to the demo and holding value under pressure.
Set thresholds as readiness scores that gate something real, pinned to exit criteria observable in the transcript. A threshold nobody can locate in a transcript is a mood.
The drill card: rehearsing the day-30 gate
We recommend rehearsing each gate scenario as a scored drill in week 3, so the gate attempt is never the rep's first exposure. The card below covers the day-30 discovery gate.
Roles: the manager plays the buyer, a distracted owner who answers questions but volunteers nothing; the new rep runs the first call. Time-box: we recommend 12 minutes. Reps: we recommend 2 back-to-back runs, the second against a shorter-tempered version of the same buyer.
Behavior scored: one only: the buyer states the concrete cost of the problem before hearing about any capability. Pass bar: the transcript records the buyer naming what the problem costs them before the rep first mentions a product. A failing attempt sounds like: the rep collects a surface complaint and pivots into a capability tour by minute three; the cost never enters the transcript.
Debrief script: the rep goes first and names where they left discovery. The manager names one behavior, not three: you proposed before the buyer priced the pain. The re-run is scheduled before anyone stands up. Re-run rule: a failed drill re-runs the same scenario, not a fresh one; passing a different scenario proves nothing about the miss.
Frequently asked questions
What happens if a rep misses the 30-day gate?
The decision is repeat: the same scenario re-runs on a scheduled date, targeting the failed rubric row, and the privilege stays off until the pass. Downstream checkpoint dates hold. A second miss turns the next checkpoint into an escalation.
Do experienced hires skip the gates?
No. Tenured hires compress the calendar, not the ladder: clear the day-30 gate in week 1 and solo discovery calls start Friday. Gates measure readiness, which has no tenure requirement.
How many scenarios should each gate include?
We recommend 2 or 3: one core scenario and one harder variant. One invites memorizing a script; more than 3 turns the gate into an exam week.