Sales Onboarding First Week: The 5-Day Plan

The first week of sales onboarding is a five-day readiness sequence. It should give a new rep safe access, an accurate mental model of the buyer and product, representative observation, deliberate practice, bounded supervised activity, and a documented handoff. It should not promise that five days makes anyone fully ramped.

This page owns the exact five-day artifact. The canonical sales onboarding program owns the full 30/60/90 system; sales onboarding certification owns assessment depth; remote sales onboarding owns delivery adaptations.

Before day one: make access safely ready

Do not spend the new hire’s first morning discovering that the CRM seat, device, accessibility requirement, or manager calendar is missing. The manager and operations owner should complete a preflight before start: role profile and learning objectives, five-day calendar, buddy and shadow hosts, rubric, approved examples, synthetic practice data, manager feedback capacity, support channel, and 30/60/90 handoff owner.

Provision accounts from an approved role baseline, then verify each privilege. NIST SP 800-171 Rev. 3 describes least privilege as only authorized access necessary for assigned tasks and calls for review and removal/reassignment when needed. CISA guidance recommends phishing-resistant MFA and least privilege. These are general security principles; qualified security owners define the actual control set.

If critical access is blocked, do not quietly mark the learner behind. Mark the task blocked, name the operational owner and due time, move to safe offline work, and adjust downstream evidence fairly.

Day 1: role, people, access, and workflow

Objective: the learner can explain their role, identify support and escalation owners, authenticate safely, distinguish permitted from prohibited actions, and narrate the end-to-end sales workflow without production changes.

1. Welcome and role contract: purpose, customer, responsibilities, authority, expectations, first-week gates, schedule, response route, and working agreements.
2. People map: manager, buddy, enablement, RevOps, IT/security, product, solutions, customer success, support, finance/legal escalation as relevant.
3. Access lab: authenticate, MFA, support/recovery, recognize suspicious requests, verify each system and role permission; never paste credentials into evidence.
4. Workflow walkthrough: observe one synthetic or approved account flow from source and identity through outreach, scheduling, call preparation, meeting, notes, CRM, and handoff.
5. Debrief: learner redraws the workflow, labels system and human authority, lists three stop/escalation points, and submits blockers.

Day-1 gate: access/security critical items pass or are blocked with operational owners; the learner explains safe-use boundaries and workflow sequence; the manager accepts the workflow map. No unsupervised production writing is granted merely because login succeeded.

Day 2: ICP, product, evidence, and observation

Objective: apply approved ICP and product evidence to representative cases, distinguish sourced fact from inference, and observe how a seller turns buyer context into a conversation and recorded next step.

CDC’s primary learning-objective guidance recommends learner-centered, action-oriented, specific, achievable, and measurable objectives aligned to competencies. Replace “learn the ICP” with “classify five representative accounts under the approved rubric and explain evidence, uncertainty, and disqualifiers.”

• ICP, segments, personas, jobs, triggers, problems, alternatives, disqualifiers, and buying-group hypotheses.
• Product use cases, demonstrated behavior, limitations, integrations, implementation, approved proof, pricing/discount boundaries, roadmap and claim escalation.
• Evidence lab: trace five claims to current approved sources; label fact, buyer statement, hypothesis, inference, and unknown.
• Call observation: pre-brief context and objective; observe an approved recording or live call; debrief questions, evidence, buyer response, decision, next step, and CRM state.

Day-2 gate: learner classifies representative cases, states product limits without improvising, cites approved evidence, escalates an unknown, and completes an observation sheet. The manager records corrections and one focus for day three.

Day 3: systems practice and roleplay

Objective: execute the approved workflow and a role-relevant conversation in simulation, recover from common errors, and produce correct evidence.

Use synthetic accounts, buyers, inbox/calendar, call scenarios, and CRM records. Practice identity match, research, draft/review, opt-out or wrong-person handling, call prep, scheduling, note capture, owner/stage/next-step updates, handoff, and correction. Seed a duplicate, missing field, expired credential, unsupported claim request, sensitive-data phrase, and CRM conflict.

Run two or more roleplays only if useful for the role and time available: baseline, feedback, replay with variation. The CDC Quality Training Standards connect exercises, observed practice, questions, and problem solving directly to learning objectives and recommend realistic, relevant assessments.

Use one rubric: objective and context; opening/permission; questions and listening; evidence and claims; response to uncertainty/objection; next step; system artifact; safety/escalation. The learner self-scores first, the coach cites observable evidence, and both select one behavior for the replay. Use the sales call scorecard as a starting point.

Day-3 gate: critical privacy, claim, consent, identity, and data behaviors pass; workflow artifacts reconcile; the learner demonstrates the focus behavior or receives explicit remediation. Still no automatic live-work permission.

Day 4: structured shadowing and rehearsal

Objective: identify how the approved workflow appears in representative work, explain the seller’s decisions and alternatives, then rehearse the next-day bounded task.

Shadowing is not passive calendar attendance. Before the call, the host shares approved context, objective, roles, recording/participation rules, and what the learner may do. During observation, the learner records buyer evidence, seller hypothesis, questions, proof, objections, decisions, next step, and system updates—without copying unnecessary personal or confidential data.

Afterward, learner debriefs first: what changed, why, evidence, missed cue, alternative, next action, and open question. The host corrects and links examples. Review the final CRM state through the CRM hygiene lens. If live shadowing is unavailable or unsuitable, use an approved recording or simulation rather than forcing a buyer interaction.

Rehearse tomorrow’s exact bounded activity: selected account/case, approved message or call segment, manager role, stop conditions, escalation, evidence, correction, and rollback. Test one difficult variation.

Day-4 gate: observation artifact accepted; privacy/recording rules followed; rehearsal passes critical anchors; manager signs the precise activity allowed on day five and what remains prohibited.

Day 5: bounded supervised activity

Objective: apply approved knowledge and skill to one or more representative tasks under supervision, produce correct system state, reflect, and accept remediation. Volume is deliberately unspecified.

The manager selects a bounded task based on role and gates: research and draft for review; open a call then hand off; lead a discovery segment; prepare and document a meeting; update an approved CRM record; or present a synthetic deal review. Use approved data, channels, accounts, claims, and permissions. Stop when identity, consent, buyer safety, data, commercial authority, or system state is uncertain.

Observe without taking over unless a stop condition occurs. Afterward, compare expected and actual workflow, buyer response where applicable, system evidence, errors, recovery, and learner reflection. CDC distinguishes learning from workplace transfer and recommends assessing both when possible. One supervised task is early transfer evidence, not proof of stable performance.

Day-5 activity gate: critical behaviors pass, records reconcile, corrections complete, and the manager states independent/supervised/prohibited scope for week two. Any miss becomes a named remediation, not a hidden “close enough.”

Run the Friday readiness review

Reviewers cite evidence and rubric version. Give the learner corrections and response space. A Friday review is not an employment verdict or quota certification; it defines safe next-week scope and the evidence still needed.

Remediate without hiding blockers

For every missed row, record the expected behavior, observed evidence, risk, learner response, remediation activity, owner, due date, required support, retest evidence, reviewer, and decision. Separate learner gap from operational blocker. A missing CRM seat belongs to the access owner; unavailable feedback belongs to the manager/program.

Remediation can be a corrected source review, targeted system simulation, contrast example, roleplay replay, different shadow case, accessible format, or additional supervised sample. Do not repeat the entire week by default. Critical data, claim, privacy, consent, identity, or security failures must pass before related authority is granted.

Debrief the manager and learner

Hold a 30-minute close. Learner answers: what can I do, what needs supervision, what is prohibited, where is evidence, what am I unsure about, what support is missing, and what will I practice next? Manager answers: which gates passed, what evidence supports them, what corrections remain, what access is changing, what coaching I owe, and which tasks are authorized.

Program owner captures schedule/content defects, inaccessible or stale materials, broken links, inconsistent assessors, access delays, poor scenarios, and manager capacity. Do not wait for a cohort survey to fix a critical issue.

Hand off into the 30/60/90 program

Create a handoff packet: learner/role/segment/start date; objective and rubric versions; completed evidence references; access and authority; critical gates; independent/supervised/prohibited tasks; remediations; learner questions; manager commitments; buddy/shadow plan; day-30 evidence; and next review.

The receiving owner signs acceptance into the 30/60/90 sales onboarding program. Role-specific plans can then adapt the task mix through first-SDR onboarding or AE onboarding. Do not reset week-one evidence or silently broaden access.

Printable five-day onboarding checklist

“Complete” means evidence accepted. “Blocked” means an owner and due time exist. Never store passwords, private HR information, unnecessary customer data, or sensitive recording content in this checklist.

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 workflow demonstrations, synthetic practice, supervised work, and artifact review. That is first-party positioning—not independent proof of faster ramp or authority to certify an employee.

Validate access, data scope, AI grounding, recording/consent, corrections, retention, deletion, and CRM behavior before use. Do not expose live customer data merely to make training realistic; use synthetic or specifically approved cases. Human managers own readiness decisions and qualified owners control security, privacy, accessibility, and employment processes.

A strong first week ends with evidence and bounded authority: the learner knows what they can do, the manager knows what still needs coaching, and the 30/60/90 owner receives a usable handoff.