A sales onboarding program is a role-readiness system, not a calendar of presentations. It turns communicated competencies into practice, evidence, gates, supervised application, certification, and follow-through. A new hire advances because they demonstrate the approved workflow safely—not because day 30 or day 90 arrived.
Direct answer. Build one 30/60/90 checklist with a task, owner, due date, evidence, status, blocker, and readiness gate on every row. Days 1–30 establish prerequisites and safe practice; days 31–60 add supervised live application; days 61–90 transfer controlled ownership. Roleplay, shadowing, certification, remediation, manager coaching, and workplace evidence determine progression. Measure delivery, learning, transfer, and business outcomes separately.
This page is the canonical 30/60/90 operating program, not another onboarding-statistics or metrics article. Sales onboarding first week owns the detailed first five days; sales onboarding certification goes deeper on assessment; sales onboarding metrics covers measurement design.
Build the program around role readiness
Start from the work the role must perform. Map a representative workflow from account or lead context through outreach, qualification, discovery, demonstration, opportunity management, commercial steps, close/loss, handoff, and CRM evidence as applicable. Mark which steps the role owns, contributes to, observes, or must not perform.
Turn each owned job into a learning objective: actor, observable action, conditions, quality standard, evidence, and time horizon. CDC’s primary learning-objective guidance recommends learner-centered, action-oriented, specific, achievable, and measurable objectives aligned with competencies. “Understand discovery” is not assessable; “run the approved discovery opening, confirm purpose and agenda, and record a buyer-confirmed next step in a representative simulation” is.
| Competency domain | Evidence of readiness |
|---|---|
| Customer and market | Accurately distinguish ICP, persona, problem, trigger, alternative, and disqualifier in representative cases |
| Product and claims | Demonstrate approved use cases, limitations, proof, pricing/escalation boundaries, and safe “I don’t know” behavior |
| Conversation | Execute role-relevant opening, discovery, objection, demo, negotiation, or handoff under rubric |
| Workflow and systems | Use approved identity, data, outreach, calendar, call, CRM, and approval paths without prohibited shortcuts |
| Commercial governance | Recognize privacy, security, legal, financial, accessibility, recording, discount, and claim escalation triggers |
| Self-management | Prepare, prioritize, document, seek help, reflect, correct, and follow through |
Tailor objectives to SDR, AE, manager, solutions, partner, or customer role. Do not copy quota targets, call volumes, or a 90-day promise across segments. Use the first-SDR plan or AE onboarding for role-specific adaptations.
Assign owners before day one
| Owner | Accountability | Evidence |
|---|---|---|
| Executive sponsor | Role outcome, capacity, policy alignment, conflict resolution | Approved charter and resources |
| Frontline manager | Readiness, practice, live supervision, coaching, gate decision | Completed rubrics, checkpoints, sign-offs |
| Enablement/program owner | Objectives, curriculum, facilitation, assessments, versioning, evaluation | Program map, materials, change log |
| RevOps/admin | Accounts, permissions, sandbox, workflow, data, reporting, support | Access test and workflow certification |
| Subject owners | Approved product, pricing, security, legal, industry, and claim knowledge | Sourced content, approval, expiry |
| Buddy/mentor | Context, observation, questions, safe escalation—not rating authority unless assigned | Shadow debriefs and referrals |
| Learner | Practice, evidence, reflection, corrections, blockers, requests for support | Artifacts and status updates |
Name one accountable program owner and one owner per checklist row. “Sales,” “enablement,” or “manager” without a person and due date is not ownership. Audit manager commitments as carefully as learner tasks. Missing access, examples, feedback, territory, or safe practice cannot be recoded as learner failure.
Before day one, prepare role profile, objectives, rubric, 30/60/90 checklist, calendar, access, sandbox/synthetic records, buddy, shadow hosts, approved call library, manager capacity, accessibility or accommodation channel, privacy/recording rules, and support/escalation.
Define five readiness gates
- Gate 0—safe access: identity, device, permissions, confidentiality, data handling, communication, recording, AI, and escalation understood and demonstrated.
- Gate 1—knowledge in context: apply customer, product, process, claim, and policy knowledge to realistic cases, not recall trivia alone.
- Gate 2—simulated skill: pass representative roleplays and system workflows against published rubrics with evidence.
- Gate 3—supervised transfer: perform defined live tasks with manager approval, observation, debrief, and correction.
- Gate 4—controlled ownership: execute representative work independently within authority, with correct records and escalation.
Publish the gate criteria, evidence, assessor, pass/revise decision, remediation, retest, appeal/correction route, expiry, and recertification trigger. Do not invent an “80% pass” because it sounds rigorous. Critical safety or claim behaviors may be pass/fail; other skills may use behavior anchors. The gate is only as defensible as its relationship to the job.
Time does not waive a failed critical gate. A rep can move ahead on unrelated learning while remediation continues, but do not expose buyers or data to unverified work. Conversely, prior experience can justify evidence-based acceleration; do not force demonstrated competence through redundant seat time.
Days 1–30: foundation and safe practice
Month one establishes prerequisites and begins practice early. Mix short instruction with examples, retrieval, simulation, feedback, reflection, and increasingly realistic work. Avoid a content-only “academy.”
- Week 1: role/expectations; people and support; safe access; ICP/personas; product/use cases/limits; workflow map; initial observation; baseline demonstrations. Use the detailed first-week schedule.
- Week 2: CRM and workflow using synthetic cases; approved research; communication rules; opener/discovery or prospecting roleplays; structured shadowing.
- Week 3: qualification, objections, demo/handoff as relevant; failure and escalation cases; more complex roleplays; assisted internal tasks.
- Week 4: Gate 1 and Gate 2 evidence; remediation; manager readiness review; controlled live-work plan.
Day-30 exit is not “courses complete.” It is documented Gate 0–2 evidence for the role, unresolved gaps, remediation, manager approval, and a safe scope for month two.
Days 31–60: supervised application
Month two tests transfer with supervision. The learner prepares real work, explains their reasoning, performs within approved scope, and debriefs promptly. The manager observes a representative sample rather than only the best call.
- Build account/contact context from approved sources and document confidence and gaps.
- Draft permitted outreach and receive review before sending where required.
- Prepare for, observe, co-lead, then lead defined call segments.
- Write notes, next steps, qualification evidence, and CRM changes for manager review.
- Handle a no-answer, objection, wrong person, opt-out, missing data, and escalation case.
- Complete weekly roleplay, shadow debrief, artifact review, system-quality audit, and self-reflection.
Day-60 exit is Gate 3: representative supervised work completed to rubric, critical errors corrected, manager support delivered, and month-three authority explicitly documented. Do not demand an arbitrary count when opportunity volume differs; define an evidence sampling plan and extend observation if the natural sample is insufficient.
Days 61–90: controlled ownership
Month three transfers controlled ownership. The rep executes the normal workflow inside defined authority, while the manager samples evidence and intervenes on risk. Add variation: multiple personas, ambiguous qualification, pricing or security questions, stakeholder changes, stalled deals, and handoffs.
- Own a representative book of work with documented priorities and manager-approved boundaries.
- Run the role’s conversation and follow-through loop without prompts in sampled cases.
- Maintain accurate CRM source, owner, stage, next step, date, evidence, and escalation.
- Lead a deal/account/work review and distinguish fact, assumption, risk, and requested help.
- Demonstrate correction: identify one error, repair downstream state, and update the prevention checklist.
- Complete Gate 4 certification, response/correction, remediation if needed, and a post-onboarding coaching handoff.
Day 90 can produce ready, ready with bounded conditions, more evidence required, or remediation/retest. It must not produce automatic full quota or employment conclusions. Move the development plan into regular coaching and document who owns remaining gaps.
Run roleplay, shadowing, and feedback loops
Use a four-step practice loop: brief the scenario and rubric; run without interruption unless safety requires; learner self-reviews first; coach gives evidence-based feedback and one next practice. Repeat with variation. CDC’s Quality Training Standards link assessments such as exercises, observed practice, and problem solving to learning objectives.
Roleplays should include happy path, objection, ambiguity, missing information, prohibited claim, privacy/security question, competitor, pricing boundary, escalation, and system failure. Use synthetic buyer and company data. If recorded, define notice/consent, purpose, access, retention, correction, and deletion.
Shadowing has a pre-brief and debrief. The observer records buyer context, seller objective, questions, evidence, decision, next step, CRM state, what they would try, and open questions—not gossip or personality judgments. Gradually move from observe to assist to lead. Score live work with the same sales call scorecard used in simulation, adapted to the role.
Certify demonstrations and workplace transfer
Certification must sample knowledge, demonstration, and transfer. CDC’s primary training-effectiveness guidance distinguishes learning from transfer of learning and recommends assessing both when possible. A quiz can test knowledge; it cannot alone certify workplace performance.
| Evidence | Shows | Does not prove |
|---|---|---|
| Knowledge check | Recall/application under test conditions | Live execution |
| Roleplay | Behavior in a controlled scenario | Consistent workplace transfer |
| System simulation | Workflow and recovery in a safe environment | Production judgment at scale |
| Shadow/co-lead artifact | Observed transfer with support | Independent readiness across all variation |
| Representative live sample | Defined independent performance evidence | Guaranteed quota or future outcomes |
Use at least two assessors for high-stakes or subjective gates where feasible, calibrate with anchor examples, and preserve score, evidence, comments, disagreements, remediation, and retest. Certification should expire or trigger review after material product, process, market, policy, system, or role changes.
Run the manager and program cadence
| Cadence | Purpose | Artifact |
|---|---|---|
| Daily early check | Access, schedule, blocker, safety; fade as readiness grows | Blocker/owner/due date |
| Weekly manager 1:1 | Evidence review, feedback, support, next practice | One focus behavior and commitments |
| Weekly practice | Roleplay plus self-review and coaching | Recording/notes, rubric, next attempt |
| Weekly shadow/live review | Transfer and workflow evidence | Observation sheet and corrections |
| Biweekly program review | Cohort blockers, content, assessor calibration, access | Program change log |
| Day 30/60/90 gate | Progression, conditions, remediation, handoff | Signed decision and evidence references |
Manager capacity is a program input. Track feedback due and delivered, observation completed, blockers cleared, examples supplied, and escalations resolved. A learner cannot transfer a skill they were never allowed to practice or for which feedback arrived after the next gate.
Measure delivery, learning, transfer, and outcomes
Design evaluation before delivery. CDC’s primary evaluation-plan guidance recommends defining purpose, questions, stakeholders, methods, timing, and feasibility early.
- Delivery/process: access ready, tasks due/completed, attendance, feedback timeliness, manager capacity, blockers, remediation, learner experience.
- Learning: objective-level demonstrations, knowledge, rubric evidence, error types, retest, assessor agreement.
- Transfer: correct behavior and system state in representative live work, support required, durability at follow-up.
- Business outcomes: role-appropriate pipeline, meeting, deal, quality, customer, ramp, and retention outcomes with definitions and context.
CDC’s evaluation guide cautions that perceived learning is generally not a strong predictor of training effectiveness. Use surveys for experience and barriers, then direct evidence for skill and transfer. Compare cohorts only after role, segment, tenure, territory, opportunity, manager, program version, cutoff, and missing data are recorded. Do not infer causality from a before/after dashboard alone.
Printable 30/60/90 onboarding checklist
Copy or print this. Use one row per task and attach evidence by reference.
SALES ONBOARDING 30/60/90 CHECKLIST
Learner / role / segment / manager / buddy: ___ · start date: ___ · program/rubric version: ___
Row format: [Phase] TASK ___ · OBJECTIVE/GATE ___ · OWNER ___ · DUE ___ · EVIDENCE ___ · STATUS (not started/in progress/blocked/ready/revise/complete) ___ · BLOCKER/OWNER/DUE ___ · REVIEWER/DATE/DECISION ___
PRE-DAY 1: role/objectives approved ___ · checklist shared ___ · device/identity/access ___ · safe sandbox/synthetic data ___ · manager capacity ___ · buddy/shadows ___ · accessibility/accommodation channel ___ · privacy/recording/AI rules ___
DAYS 1–30: role/workflow map ___ · ICP/personas ___ · product/use cases/limits ___ · approved claims/escalations ___ · CRM/tools ___ · observation ___ · roleplays ___ · Gate 0 ___ · Gate 1 ___ · Gate 2 ___ · remediation ___
DAYS 31–60: supervised research/outreach ___ · shadow/debrief ___ · co-lead/live tasks ___ · notes/CRM audit ___ · objection/failure/escalation cases ___ · weekly artifacts ___ · Gate 3 ___ · conditions/remediation ___
DAYS 61–90: controlled book of work ___ · independent sampled conversations ___ · CRM/workflow quality ___ · review/forecast/handoff ___ · correction exercise ___ · Gate 4 ___ · coaching handoff ___
MANAGER COMMITMENTS: daily/weekly checks ___ · practice feedback SLA ___ · observations ___ · blockers/resources ___ · gate decisions ___
MEASUREMENT: process ___ · learning ___ · transfer ___ · outcomes/context ___ · learner feedback ___
FINAL: ready / ready with conditions / evidence required / remediate-retest ___ · learner comments ___ · manager/program sign-off ___ · next review/recertification trigger ___.
Status must reflect evidence, not optimism. “Complete” means the defined artifact exists and the assigned reviewer accepted it. “Blocked” names a blocker owner and due date. “Ready” is a gate decision, not a course completion badge.
Audit the program and adapt by role
After every cohort, audit task completion, bottlenecks, manager delivery, objective-level evidence, transfer failures, assessment fairness, accessibility, learner feedback, privacy incidents, support demand, business outcomes, and missing data. Version changes and preserve why each was made. The sales onboarding feedback loop owns this iteration process.
Adapt the program, not the control logic. Remote teams need explicit observation, time-zone-aware practice, accessible asynchronous evidence, and reliable support; see remote sales onboarding. Enterprise AEs may need longer supervised transfer and more security/procurement evidence. SDRs may reach representative volume earlier. Do not lower critical claim, data, or consent gates because a role is high velocity.
When role, product, ICP, methodology, system, policy, or buyer risk changes materially, re-map competencies and retest affected gates. Retire obsolete content and links. Maintain an approval and expiry owner for every factual product or policy asset.
Where Gangly fits—and does not
Gangly’s own product copy positions it around signals, call preparation, live guidance, reviewed notes, CRM hygiene, and follow-through. Those surfaces may support roleplay scenarios, live-work preparation, approved guidance, and transfer evidence. That is first-party positioning from this article’s publisher—not independent proof of faster ramp, quota attainment, or certification validity.
Do not let software automatically certify or make employment decisions. Validate source accuracy, access, recording/consent, AI output, correction, retention, deletion, and workflow fit. Managers remain accountable for observation and readiness; qualified owners control employment, privacy, security, and accessibility processes.
Scope boundary. This is an enablement template. It does not set employment, compensation, accommodation, discipline, or legal standards, and certification never authorizes unsupported customer claims.
The definitive onboarding program is the one a learner can run, a manager can evidence, and the business can audit—from first access through safe, representative ownership.