How to Build a Ramp Plan Around Skill Tiers Instead of Calendar Days
The 30/60/90 template assumes every rep learns at the same speed. Gating the plan on skill tiers instead of dates fixes the two failure modes calendar plans can't.
Every 30/60/90 plan makes the same silent assumption: that skill acquisition runs on a clock. It doesn't. I've managed reps who could run a clean discovery call by week three and reps who needed nine weeks to stop reading off the battlecard. The calendar plan treats both the same, and that's the whole problem. It doesn't fail occasionally — it fails in two specific, predictable, avoidable ways, every single cohort, and most managers never name either one because the plan itself looks tidy on a slide.
The two failure modes calendar plans can't avoid
Failure mode one: you cap your fastest learner. A rep who's genuinely ready to run solo discovery calls by day 22 sits in shadowing until day 30 because that's what the plan says. You're paying full salary for a week-plus of a capable person doing supervised busywork, and you're teaching them that competence doesn't shift the number here — only the calendar does. Multiply that across a cohort of eight and you've burned real ramp cost on nothing. The Ramp-Time & Cost-of-Ramp Calculator will put a number on it, and it's usually bigger than people expect.
Failure mode two — the expensive one: you release your slowest learner anyway. Day 90 arrives, the plan says they graduate, and they get thrown at full quota whether or not they can run a qualification call unsupervised. This isn't neutral. They build bad habits under live deal pressure because nobody stopped the clock to fix the fundamentals first, those habits get reinforced by repetition before anyone catches them, and by month five you're doing a much harder remediation on a rep who's now also demoralised and defensive about being "behind." You paid for a ramp and didn't get a ramped rep.
Both failure modes have the same root cause: the plan is gated on tenure, not on demonstrated skill. Fix the gate, fix both problems at once.
The fix: exit criteria, not exit dates
A tier-gated ramp plan replaces "by day 30 you should be comfortable with X" with "you move to Stage 2 when you demonstrate X at a defined level, evidenced by Y." The date disappears from the gate entirely. It doesn't disappear from the org's planning — you still need to know roughly what ramp costs and how long it typically takes for cost modelling and hiring cadence — it just stops being the thing an individual rep is measured against.
Here's the conversion, in five steps.
- Name the four to six competencies your ramp plan is actually testing. Most 30/60/90 templates bury these inside vague milestones ("comfortable with product", "running calls independently"). Pull them out and name them properly — discovery questioning, objection handling, qualification rigour, whatever your process actually depends on early.
- Write three tier definitions per competency: Foundation, Proficient, Advanced. Each one has to describe an observable behaviour on a real call, not a feeling. "Understands the product" is not a tier definition. "Can answer a buyer's technical objection without pulling in a solutions engineer" is.
- Attach an evidence method to each tier. Shadowed calls scored against a rubric, a manager sign-off after reviewing a recording, a set number of independently-run calls hitting a bar. Without evidence, "tier" is just a nicer word for "vibe," and you're back to a manager's gut deciding who's ready.
- Set the minimum tier required to unlock the next stage of the plan. A rep doesn't move from shadowing to solo discovery calls because three weeks passed — they move because they hit Proficient on discovery questioning, evidenced by a scored review. If they hit it in twelve days, they move in twelve days.
- Decouple the calendar from the individual, keep it for the cohort. Track median days-to-tier across your last several ramp cohorts. That number tells you what to tell finance and what to expect operationally. It should never appear on an individual rep's plan as a deadline.
Worked example: tiering a single competency
Take discovery questioning — usually the first competency a calendar plan gets wrong, because "ran discovery calls in week 4" tells you nothing about whether the rep can actually run one.
| Tier | What it looks like on a real call | Evidence required to advance |
|---|---|---|
| Foundation | Asks the core discovery questions in sequence, captures answers accurately, doesn't yet follow up when a buyer's answer implies something unasked. Sticks close to the script. | 3 shadowed calls independently scored at pass or above on question sequencing and note accuracy. |
| Proficient | Departs from the script when a buyer gives an unprompted signal — a budget comment, a timeline hint, a mention of a stakeholder not yet named. Asks at least one genuine follow-up "why" per call. Can restate the buyer's actual pain in their own words afterward, not just repeat what was said. | 3 solo discovery calls reviewed against a scorecard, with adaptive questioning (not script adherence) present in at least 2 of 3. |
| Advanced | Connects threads across multiple calls or stakeholders in the same deal — notices that what the economic buyer said in call one contradicts what the end user said in call two, and probes the gap. Surfaces a priority the buyer hadn't stated out loud. | Manager or peer review flags at least one call per month where the rep surfaced something the buyer never said directly, sustained over two consecutive review cycles. |
Notice what's missing from that table: a day number. A rep who's spent five years in a related industry might walk in at Proficient and skip Foundation's evidence requirement entirely if a manager verifies it on day one. A rep with zero prior sales experience might need six weeks at Foundation before the evidence holds up. Both are fine. Neither is a problem to be managed around — that's the plan working as designed.
The New Rep Certification Scorecard is a reasonable starting point for building evidence templates like the one above across your other core competencies, rather than inventing a rubric from scratch for each one.
The objection every manager raises
"We need dates for planning — ramp cost, quota assignment, hiring cadence all run off a calendar." Correct, and tier-gating doesn't remove that. It just moves the calendar up a level. You stop tracking individual rep against date and start tracking cohort median days-to-tier against date. That number is more useful for planning than a fixed 90-day assumption anyway, because it's derived from what actually happens rather than what the template says should happen. If your median Proficient-on-discovery time is 34 days this quarter versus 41 last quarter, that's a real signal about hiring quality or onboarding content — a fixed calendar plan can't produce that signal because it never measures against anything real. The Time-to-First-Deal Tracker Template is the natural companion metric here: track time-to-tier per competency alongside time-to-first-deal and you get a genuine diagnostic on where ramp actually slows down, rather than a guess.
What changes for you as a manager
- No more graduating a rep on Friday because the plan says so, knowing full well they can't run discovery solo.
- No more parking your best natural talent in observation for two extra weeks because the template has a Week 4 box to tick.
- A real, evidenced answer to "is this rep ready," instead of a tenure-based guess dressed up as a plan.
- A cohort-level metric — median days-to-tier — that's actually useful for forecasting, unlike a fixed day count nobody hits exactly anyway.
Building it this week
Pull your last ten completed ramps, successful and unsuccessful. For each, ask what specific thing the good ones could do that the struggling ones couldn't, at the point it became obvious. That list is your competency set. Write Foundation/Proficient/Advanced for the two or three that show up most often, attach an evidence method to each, and run your next cohort against tiers instead of dates. You'll know within one cohort whether the calendar was ever telling you the truth.
The 30/60/90 was never wrong because it had numbers in the name. It was wrong because it measured the one thing that doesn't actually predict whether someone can do the job.