# First 90 Days Sales Onboarding Framework

> The stage-by-stage architecture: pre-boarding through full solo launch: that enablement leaders use to design any new onboarding program from scratch, with objectives, exit gates, and ownership defined at every stage.

Free framework for sales leaders. Topic: [Onboarding & Ramp](https://www.peerlab.ai/library/topic/onboarding-ramp/). Published by PeerLab in the [Sales Enablement Resource Library](https://www.peerlab.ai/library/). Source: https://www.peerlab.ai/library/first-90-days-sales-onboarding-framework/

## How to use it

Use this as the blueprint when designing or auditing an onboarding program: every stage needs a defined objective, exit criteria, and named owner before you build a single training deck.

## What's inside

- Stage 0: Pre-boarding
- Stage 1: Foundation / Knowledge
- Stage 2: Observation / Shadowing
- Stage 3: Guided Practice / Supervised Selling
- Stage 4: Certification Gate
- Stage 5: Solo Launch with Scaffolding
- Stage 6: Full Productivity Transition
- 5 design principles for building your own program

The architecture underneath every good sales-onboarding program, regardless of industry or deal complexity. Design top-down: define the stages and gates first, then build content to fill them, not the other way around.

---

## Stage 0: Pre-boarding

**Objective:** every system, account, and calendar block is ready before the new hire's first day, so day 1 is spent learning, not waiting on IT.
**Duration:** the week before start date.
**Core activities:** hardware and account provisioning, buddy/mentor assignment, first-week calendar built.
**Exit criteria:** new hire can log into every required system on day 1 without a support ticket.
**Owner:** hiring manager + IT/enablement.
**Common failure mode:** access requests submitted on start date instead of the week before, costs the new hire their most attentive week.

## Stage 1: Foundation / Knowledge

**Objective:** the new hire understands the product, the customer, and the process well enough to recognize what a good call sounds like before they're asked to run one.
**Duration:** days 1–15 (overlaps with Stage 2).
**Core activities:** product training, ICP/persona training, CRM training, methodology introduction, quiz-bank modules 1–3.
**Exit criteria:** passes knowledge-check quizzes at 80%+; can explain the ICP and top use cases unprompted.
**Owner:** enablement.
**Common failure mode:** knowledge transfer treated as a one-time event (a single deck) instead of tested and reinforced.

## Stage 2: Observation / Shadowing

**Objective:** the new hire has seen the skill executed live enough times to build a mental model of "good," before being asked to produce it themselves.
**Duration:** days 10–30 (overlaps Stage 1 and 3).
**Core activities:** structured shadow sessions with tenured reps across deal types and stages, debriefed immediately after each, not batched at the end of the week.
**Exit criteria:** minimum shadow-session count met (recommend 8–10 minimum) AND new hire can articulate, unprompted, what the tenured rep did at each methodology stage.
**Owner:** manager, delivered via peer reps.
**Common failure mode:** shadowing without a structured debrief: reps watch, but no one asks them what they noticed, so nothing transfers.

## Stage 3: Guided Practice / Supervised Selling

**Objective:** the new hire executes the skill themselves, with a safety net, before doing it alone with real money on the table.
**Duration:** days 30–60.
**Core activities:** role-play practice, reverse-shadowing (new hire leads, tenured rep silently observes), first supervised live calls.
**Exit criteria:** scores "meets bar" (3+ on the 4-point scale) on 3 consecutive supervised interactions.
**Owner:** manager.
**Common failure mode:** graduating a rep out of supervision based on calendar time elapsed rather than demonstrated skill.

## Stage 4: Certification Gate

**Objective:** a single, objective checkpoint confirms the new hire is deal-safe before being handed a live territory unsupervised.
**Duration:** a single sitting, typically around day 45–60.
**Core activities:** formal certification exam/assessment against the *New Rep Certification Scorecard*.
**Exit criteria:** Pass or Conditional Pass per the scorecard's decision rules.
**Owner:** enablement + manager (assessor).
**Common failure mode:** certification treated as a formality that's never actually allowed to fail anyone, this destroys the gate's credibility and the data it's supposed to produce.

## Stage 5: Solo Launch with Scaffolding

**Objective:** the new hire runs their own pipeline, but with fast feedback loops still in place, so early mistakes get caught and coached rather than compounding.
**Duration:** days 60–90.
**Core activities:** full pipeline/territory ownership, weekly deal reviews, CRM hygiene spot-checks.
**Exit criteria:** activity volume and pipeline-generation targets from the 30-60-90 plan are being met without manager reminders.
**Owner:** manager.
**Common failure mode:** scaffolding removed all at once instead of tapered: go from daily oversight to zero oversight in one step, and problems surface too late to fix cheaply.

## Stage 6: Full Productivity Transition

**Objective:** the new hire is now a standard member of the roster, tracked on the same cadence and KPIs as tenured reps.
**Duration:** day 90 onward.
**Core activities:** day-90 review comparing actuals to the 30-60-90 plan; transition off the onboarding tracker onto the standard team dashboard.
**Exit criteria:** ramp curve (see the *Sales Ramp-Time Calculator*) reaches 100% expected quota attainment.
**Owner:** manager, sign-off from skip-level.
**Common failure mode:** no formal close-out: the new hire quietly stops being "the new hire" with no retro on what worked, so the next cohort doesn't benefit from this one's lessons.

---

## 5 design principles for building your own onboarding program

1. **Gate on demonstrated skill, not on calendar days.** A rep who's ready at day 40 shouldn't wait until day 60 because "that's when solo launch happens", and a rep who isn't ready at day 60 shouldn't launch anyway because the calendar says so.
2. **Every stage needs a named owner, not "the team."** If no single person is accountable for a stage, it's the first one that silently slips.
3. **Debrief every observation.** Shadowing or role-play without an immediate "what did you notice" conversation is entertainment, not training.
4. **Taper scaffolding, don't cut it.** The jump from fully-supervised to fully-solo should happen in visible steps, each with its own exit criteria.
5. **Build the retro into the design, not as an afterthought.** Every cohort that completes the program should generate at least one improvement for the next cohort's version.