How to write a sales training plan that ramps reps and holds the gains

The first mistake teams make is writing one giant deck labeled sales training and dropping it on every rep regardless of tenure. A real plan has two distinct tracks that share a methodology but not a calendar. Onboarding is the 90-day path every new hire runs through: company, product, ICP, methodology, systems, certifications, and first live deals. Ongoing education is the always-on program every tenured rep participates in: monthly product updates, quarterly deep dives on new segments or competitors, call-review rituals, and advanced skill tracks. Write the two tracks on separate pages, assign separate owners, and give each its own measurement surface before you touch content. Blending them is why most training plans become a graveyard of unwatched videos within six months.

• Draft a one-page charter for onboarding (audience: new hires in first 90 days, goal: productive on first real deal).
• Draft a one-page charter for ongoing education (audience: all reps post-ramp, goal: compounding skill and current knowledge).
• Assign a distinct accountable owner for each track, even if the same Enablement lead oversees both.
• Agree on the shared assets (methodology, ICP, battlecards, call library) and keep them in one place both tracks pull from.

Month-level onboarding plans read well in a slide and fail in practice because reps have no idea what good looks like on any given Tuesday. Write the 90 days at week granularity instead. Week 1 is company, product fundamentals, systems access, and shadowing. Weeks 2-3 cover ICP, methodology, qualification framework, and first mock discovery calls. Weeks 4-6 are segment and persona depth plus competitor positioning, ending in a certification. Weeks 7-9 move to live deal participation under a ride-along with a tenured rep or manager. Weeks 10-13 are owned pipeline, with a final certification against a scored mock full-cycle call. Each week has a learning goal, named owners, time budget, and an artifact the rep produces that someone else reviews.

• Write one row per week with: learning goal, modules, SMEs, time budget, output artifact, and reviewer.
• Front-load mechanics (systems, ICP, methodology) in weeks 1-3 so reps can be useful shadows by week 4.
• Place the first certification at week 6 and the final full-cycle certification at week 13 as hard gates.
• Keep the weekly time budget under 15 hours of structured training so the other 25 hours are deal reps.

Certifications are what turn a training plan from a library into a system. For every major competency (product pitch, discovery, qualification, objection handling, demo, full-cycle call), define a certification with a written rubric, a live performance component, and two human raters. A rep is not certified when they finish the course; they are certified when two raters independently score their recorded performance above the rubric threshold. Make certifications visible: show them on a team dashboard, celebrate when reps pass, and treat failed attempts as expected (they are, and they are the point). Reps who know they must perform the behavior live, under review, learn differently than reps who only have to click through slides.

• Define 4-6 core certifications with written rubrics scored on a 1-5 scale across 4-6 dimensions each.
• Require two independent raters per attempt and reconcile disagreement greater than one point before passing or failing.
• Build in a scheduled retake path within 7-14 days so a failed attempt is a learning event, not a career threat.
• Publish certification status on the team dashboard so managers and peers can see where every rep stands.

Call review is the engine of ongoing education. Run two different rituals and do not confuse them. The first is per-rep call review, which lives inside the manager coaching plan and focuses on one rep's development priorities. The second is team call review, owned by Enablement, where the whole team watches 10-15 timestamped minutes from a shared call library and discusses the methodology moment: the discovery question that unlocked the champion, the pricing objection handled well, the next-step clarity that saved a deal. Rotate hosting across tenured reps so the team teaches itself. Build a durable call library tagged by methodology stage, segment, and competitor so new hires in month two can rewatch what great looks like in the moments they are about to live themselves.

• Schedule a recurring 45 minute weekly team call review owned by Enablement, not by a sales manager.
• Pick 10-15 minutes of call clips in advance tagged to a methodology stage, not a full call end to end.
• Rotate the host role across tenured reps so skill transfer compounds beyond the Enablement team.
• Tag every clip into a durable call library organized by stage, segment, competitor, and persona.

Ride-alongs are the fastest skill transfer mechanism in a sales training plan and the first thing teams let slip. Build them into the schedule explicitly. In weeks 4-6 the new hire shadows a tenured rep on 8-12 live calls across discovery, demo, and close stages. In weeks 7-9 the relationship flips: the tenured rep co-pilots while the new hire runs the call, with debrief notes shared the same day. In weeks 10-13 the new hire runs calls solo with the tenured rep listening async and leaving timestamped feedback within 24 hours. Pair ride-alongs with a written debrief template so the learning survives the ride itself. The template captures what the new hire would do differently, what pattern the tenured rep saw, and the one behavior they will try on the next call.

• Assign a named ride-along partner per new hire for the full 90 days, not a rotating pool.
• Target 8-12 shadowed calls in weeks 4-6, 6-10 co-piloted calls in weeks 7-9, and 10-15 solo calls with async feedback in weeks 10-13.
• Standardize a one-page debrief template so pattern recognition survives the specific call.
• Comp or recognize the tenured partners explicitly: ride-along time is work, and unpaid work decays fast.

A training plan without a measurement surface is a cost center. Instrument four layers of signal and review them together, not in isolation. Leading signal is quiz and certification data: first-attempt pass rate, average rubric score, dimensions where cohorts struggle most. Behavior signal is time to first qualified opportunity, time to first closed-won, and call-review rubric trends over the first 90 days. Pipeline signal is win rate at 60, 90, and 180 days segmented by cohort versus the prior-year baseline. Business signal is ramp length to full productivity and quota attainment at month 6 and month 12. Review quiz data weekly, behavior data monthly, pipeline data quarterly, and the full stack at a semi-annual Enablement operating review.

• Instrument quiz and certification data in the LMS with cohort tagging so trends are comparable across hires.
• Measure time to first qualified opportunity and first closed-won deal from day one of each cohort.
• Compare cohort win rate at 60, 90, and 180 days against the prior-year baseline for the same segment.
• Report quota attainment at month 6 and month 12 as the ultimate ramp measure, not month-3 activity volume.

Writing the plan is easier than running it. Launch with a named cohort of 3-6 new hires, publish the full week-by-week schedule to the cohort, their managers, and leadership, and run the first 90 days as a visible beta. Hold a weekly 30 minute Enablement standup with the cohort to surface friction while it is still cheap to fix. Keep a running changelog of what moved, got cut, or got added so later cohorts inherit the fixes, not the original mistakes. The first cohort is not where you prove the plan works; it is where you harden it. Expect 20-30 percent of the week-by-week schedule to change before cohort two.

• Pick a cohort of 3-6 hires who can tolerate ambiguity and give structured feedback.
• Hold a weekly 30 minute cohort standup owned by Enablement, separate from any manager 1:1.
• Keep a visible changelog of module changes and the reason, with cohort tags for every revision.
• Debrief with managers at week 6 and week 13 so the cohort experience and manager experience both inform v2.

The hardest part of a training plan is what happens after onboarding ends. Most teams stop here and ramp decays within 18 months. Build an ongoing-education calendar that runs quarterly for every tenured rep: monthly product-update sessions tied to real releases, quarterly deep dives on new segments or competitors as the business moves, half-yearly advanced skill tracks (negotiation, multi-threading, executive conversation, forecasting), and an annual sales kickoff that resets the methodology. Pair the calendar with recertification: every tenured rep recertifies on the pitch and discovery frameworks annually, so the floor of the team does not drift as the product and ICP evolve. Reps who see Enablement invest in them past day 90 engage differently than reps who feel abandoned at ramp.

• Publish a rolling 12 month ongoing-education calendar with named owners for every session.
• Require annual recertification on pitch and discovery for every rep, with the same rubric as new hires.
• Tie each quarterly deep dive to a real business change (new segment, new competitor, new product line).
• Keep the sales kickoff a methodology-and-skill event, not a comp-plan event, so the training signal survives.

Reps rate a training plan highly when it is comfortable. Reps win more deals when it is demanding. Those two things diverge. Iterate the plan every two cohorts (roughly every 90-180 days depending on hiring pace) against the paired evidence: win rate at 60, 90, and 180 days versus baseline, time to first closed-won, certification first-attempt pass rate, and rubric trend by dimension. Use rep satisfaction as a secondary signal, not a primary one. For every revision, name the metric it is intended to move, freeze the change for a full cohort, and only then evaluate. Keep a changelog so the plan has an auditable history and leadership can see the arc of ramp getting shorter and win rate getting steadier.

• Hold an Enablement operating review every two cohorts with the full paired-metric stack on screen.
• Rank proposed revisions by the pipeline metric each is meant to move, not by rep sentiment alone.
• Freeze each change for a full cohort before evaluating so you do not read noise as signal.
• Publish the changelog and the metric arc up to sales leadership so the training plan has budget air cover.