How to Build a 90-Day Ramp Plan Around Skill Milestones, Not Calendar Weeks
'Finish CRM training by week two' isn't a ramp plan. It's a checklist wearing a ramp plan's clothes.
Every onboarding plan I've inherited from a predecessor has had the same shape: a spreadsheet with weeks running down the side and tasks across the top. Week one: CRM training, product certification, shadow five calls. Week two: first cold call block. Week four: first solo discovery call. Week eight: first proposal. The plan reads well in a board deck. It falls apart the moment you apply it to an actual human, because it was written before that human existed. It assumes every new hire arrives with the same starting competency and learns at the same rate, which is false for literally everyone who has ever been hired.
The result is predictable and I've watched it happen at three different companies: a rep who's genuinely ready for live discovery calls in week two sits on shadowing because the calendar says week four, and gets bored and starts questioning whether the job is what they thought. Meanwhile a rep who needs three more weeks on qualification technique gets pushed onto live calls at week four because the calendar said so, bombs two calls with real prospects, and now you're managing a confidence problem on top of a skill gap. The calendar didn't cause either outcome directly. It caused both by asking the wrong question. "Has enough time passed" is not the same question as "can this person do the thing."
The fix: gate advancement on competency, not on the calendar
A skill-milestone ramp plan replaces every calendar-gated step ("by week two, complete X") with a competency-gated step ("advance to live calls once X clears a defined bar, assessed against real evidence, whenever that happens"). The calendar becomes an expectation-setting tool, not a control mechanism — you still tell the rep "most people clear this in about three weeks" so they have a target, but the actual gate is a graded assessment, not a date on a spreadsheet.
Here's how to build one.
Step 1: Pick 3-4 gating competencies, not twelve
This is where most rewrites go wrong. Enablement teams, once given permission to build a "real" competency-based plan, try to gate on everything — discovery, objection handling, product knowledge, negotiation, forecasting hygiene, CRM discipline. Gate on everything and you've rebuilt the calendar checklist with better branding; nothing actually blocks advancement because nothing is prioritised.
Pick the 3-4 competencies that, if weak, would make an early live call actively harmful — to the prospect relationship, to the rep's confidence, or to your pipeline data. Everything else can develop in parallel, on the job, without a gate.
| Sales motion | Gating competencies (pick 3-4) | Why these and not others |
|---|---|---|
| Outbound SDR | Cold call opening, qualification questioning, objection handling (early-stage) | A weak opener burns the account before anything else matters; weak qualification pollutes the whole pipeline downstream |
| Mid-market AE (new logo) | Discovery questioning depth, active listening, deal qualification, next-step securing | Discovery quality is the single biggest predictor of everything that follows in the deal; a bad first discovery call is often unrecoverable |
| Enterprise AE | Multi-thread stakeholder mapping, discovery questioning depth, business-case articulation | Enterprise deals die from missed stakeholders and vague business cases more often than from weak closing |
| Customer Success / renewal | Active listening, risk-signal detection, expansion questioning | The job is retention and growth, not acquisition — the gating skills have to match |
Product knowledge and CRM hygiene are conspicuously absent from every row. That's deliberate. They matter, but they're trainable-and-testable in a day, not a skill that needs live-call reps to develop, and gating on them just adds calendar-shaped friction back into a plan built to remove it.
Step 2: Define the bar in observable terms, not "good enough"
Each gating competency needs a written bar that two different managers, watching the same recorded call, would score the same way. "Asks good discovery questions" is not a bar. "Asks at least four open-ended questions that surface a business consequence, not just a fact, before proposing next steps" is a bar. If you don't already have competency definitions at this level of specificity, that's the actual work of this project — the plan is downstream of the definitions, not the other way round. The Discovery Questioning Skill-Builder Cheat Sheet is a reasonable starting bar for that one competency if you're building from scratch.
Step 3: Build the evidence pipeline before day one
A gate is only as real as the evidence behind it. Decide, before the rep starts, exactly how each gating competency will be observed and scored — recorded role-plays reviewed by a manager, live-shadowed calls with a scoring sheet, or an assessment platform doing the first pass. What doesn't work is deciding this ad hoc in week three when someone asks "so is Priya ready or not" and you're improvising a judgment call under time pressure. Build the rubric and the collection method at the same time you pick the competencies.
Step 4: Publish two timelines to the rep, not one
Give the new hire both the calendar expectation ("most people clear discovery gating around day 18") and the actual gate ("you move to live discovery calls once you clear this bar, assessed on your third role-play"). This does two things. It sets a normal-range expectation so nobody panics if they're not there by day 10, and it makes clear that the real determinant of advancement is demonstrated skill, not patience. Reps respond well to this once they understand it — most people who are ready early resent sitting in a queue for a date, and most people who need more time would rather have an honest extra week than a real prospect finding out for you.
Step 5: Decouple the rest of the 90 days from the gate
Once the 3-4 gating competencies are cleared, the remaining ramp — deal cadence, forecasting discipline, negotiation, expansion selling — can run on a calendar-ish structure, because the cost of being wrong on timing there is much lower than the cost of putting an under-skilled rep in front of a real buyer. Don't over-engineer gates you don't need. The whole point is that gating is expensive to build and run properly, so spend it only where a miss is genuinely costly.
What this replaces, concretely
If you're working from a generic template right now, most of what needs to change is the "advance to next stage" logic, not the content list. The New Hire Sales Onboarding Checklist (Day 1 to Day 90) is a fine skeleton for the activity list; the gating logic above is what turns it from a checklist into a plan that actually protects your pipeline and your new hire's confidence at the same time.
The calendar was never measuring anything. It was just there so someone could point at a date and say "on schedule." A rep who's actually ready doesn't need the date, and a rep who isn't ready yet doesn't care about it — they care whether the next call they're pushed onto is one they can actually win.