A sales rep who cannot use your CRM is a rep who cannot forecast, cannot handoff cleanly, and cannot be coached from evidence. The first two weeks decide whether the CRM becomes a reflex or a chore. This guide gives you a day-by-day plan: provisioning, baseline training, hands-on practice, mentor pairing, certification, and the first live deals. Follow it and you shorten ramp time, cut data debt, and give managers the signal they need to coach well.
Time: 2 weeks (full onboarding cycle)
The worst onboarding day begins with a rep sitting at a laptop watching the admin create their account. Have everything ready the Friday before they start. Provision the CRM user, assign the correct role, attach the right permission set, map them to their territory, assign a quota, and plug them into the forecast hierarchy. Decide what records they can see on day one and what unlocks after week two. New reps rarely need visibility into every account in the system; a scoped view protects data hygiene while they learn. Create their email signature, their calendar availability, their meeting-booking link, and their phone extension in parallel. If your CRM integrates with messaging, add them to the right channels. The goal is that when they log in Monday morning, nothing is missing, nothing is broken, and the system looks like it was built for them.
Resist the urge to open onboarding with a two-hour slide deck. Open with a walkthrough of the live CRM, logged in as the new rep. Show them the home screen, their pipeline view, their task list, their inbox, and the search bar. Explain the three jobs the CRM does for them: it remembers context, it enforces process, and it feeds the forecast. Everything else is detail. Then take them through a single real account owned by their mentor, from first touch through closed-won, so they see the full lifecycle before they memorize any field. End the day by having them log a single call themselves with the mentor watching. One real action beats three hours of theory. The point of day one is not mastery; it is removing the fear of touching the system.
With the CRM mechanics introduced, spend days two and three teaching the sales process the CRM is built to enforce. Walk through each pipeline stage and the exit criteria that gate it. Show them which fields are required at creation, which fire at stage advancement, and which must be set before closed-lost. Explain the next-step discipline you expect, the activity logging cadence, and the way your team uses tasks versus follow-ups. Then do the same for leads, contacts, and accounts, with emphasis on where each object lives, how they relate, and when to create a new one versus attach to an existing record. Avoid dumping every edge case at once. Teach the ninety-percent path first and promise them a reference guide for the rest. Reps retain the main road; they look up detours when they hit one.
Theory ends on day three. Hand the new rep a sandbox environment seeded with twenty-five realistic opportunities, fifty leads, and a hundred contacts. Give them a scripted set of exercises: create a lead, convert it to a contact and account, open an opportunity, advance it through each stage with the correct fields, log activities, book a meeting, send a sequence, and close the deal. Then do the same for a loss, with a loss reason captured correctly. The exercises should mimic the exact motions they will perform in live records next week. The mentor sits beside them for the first few, then lets them work alone and reviews the output at the end of each block. Mistakes in the sandbox are free; mistakes in live data cost weeks of cleanup. Push them to make the mistakes here.
By Friday of week one, the new rep should have the mechanical motions down. Spend the morning shadowing their mentor on three live calls: a discovery call, a mid-stage working session, and a closed-won handoff. The rep sits in, listens, and takes notes directly in the CRM against the mentor-owned opportunities. This serves two purposes: it exposes them to real conversation patterns, and it reinforces that notes belong in the CRM, not in a side document. In the afternoon, promote them from sandbox to live access on a small, scoped book: three to five accounts that are low-stakes or inactive, where they can own the record without endangering a real deal. Give them a specific task on each account before the weekend. They should log into the system Monday morning with real work waiting for them, not another training session.
The second week is where ramp either accelerates or stalls. Set the daily rhythm on Monday. The rep works their scoped book, logs every activity before end of day, and reviews their pipeline with the mentor for fifteen minutes before leaving. Introduce the morning standup if your team has one, and the end-of-day pipeline hygiene check. The pattern you install this week is the pattern they will keep for a year. Make it tight. Do not let a Monday pass without them logging at least five activities and advancing at least one record. If they resist the activity logging standard here, they will resist it forever. Managers who intervene on activity discipline during week two cut long-run data debt by more than half.
By midweek, the new rep should have logged thirty to fifty activities and moved at least two records through a stage. Expand their book by another ten to fifteen accounts, this time including a few with active opportunities. Introduce them to the weekly forecast cadence: how your team calls the number, what evidence managers expect, and how the forecast rolls up through the hierarchy. Walk them through their own forecast submission, even if the pipeline is small, so they practice the mechanics on real stakes. This is also the moment to introduce reporting: show them their rep dashboard, the metrics they will be measured on, and the leaderboard if your team runs one. Transparency about measurement reduces anxiety and raises engagement. Reps who understand what good looks like close the gap faster than reps who guess.
Before you hand a new rep their full book, require them to pass a short certification. Not a slide-deck quiz; a live demonstration. The certification covers four things: they can create and advance an opportunity with correct fields, they can run a clean discovery call with notes logged live, they can submit a forecast with evidence against each committed deal, and they can describe the exit criteria for each stage in their own words. Fifteen minutes with the mentor and the sales manager, pass or fail, no middle ground. A rep who cannot clear the certification does not get their full book on Monday; they get two more days of coaching and retest Wednesday of week three. This is not punitive. It is the single highest predictor of long-term CRM compliance. Reps who are allowed to limp into a full book never catch up.
On Friday of week two, the new rep submits their first forecast on their full book. The mentor sits beside them for the submission, challenges each committed deal with the same questions a manager would ask in a real forecast call, and either agrees with the call or asks the rep to revise. Then the mentor formally hands off. From Monday of week three onward, the manager owns the one-on-ones and the mentor steps back to an on-call role. Do not skip the formal handoff moment. Reps who feel the mentorship ended without ceremony tend to drift. A short written handoff document, co-signed by the rep, mentor, and manager, that lists what the rep now owns, where they are strong, and where they still need reps logs the state for the next quarter of coaching. Store it in the CRM against the rep user record so it is retrievable later.
Ramp does not end at day ten. The first ninety days decide whether what you installed in week two becomes habit or decays. Keep the mentor on standby for one scheduled check-in per week through day forty-five. Have the manager audit the new rep CRM hygiene once a week for the first month: are activities logged daily, is the next-step field never older than seven days, are required fields clean, are stage advancements supported by evidence. Catch drift early. A rep who skips activity logging in week four almost always skipped it in week two and nobody flagged it. Measure new-rep ramp in two signals: time to first logged activity on a live opportunity (should be inside day six) and time to first forecasted deal that actually closes (should be inside day sixty). Teams that track these two numbers find the levers that compress ramp from quarters to weeks.
Core CRM onboarding should run two full weeks: week one for mechanics and sandbox practice, week two for live scoped access and certification. Full ramp to quota is a separate measurement that typically runs sixty to ninety days depending on segment and cycle length. Compressing the two-week CRM onboarding to save calendar time almost always costs more in data debt and coaching load across the following quarter.
No. Scope their visibility to three to five accounts for the first week and expand to fifteen or twenty by midweek two. Full-book access unlocks after certification. Reps with unbounded access on day one tend to touch records they do not understand, create duplicate contacts, and generate cleanup work for the admin team that outlives the onboarding itself.
The mentor teaches mechanics and sits beside the rep for the first two weeks. The manager owns performance, forecast review, and coaching from week three onward. Overlap the two roles only in the handoff meeting at the end of week two. Blurring them earlier leaves the rep unsure whose standard to follow and whose feedback to prioritize.
They get two to three extra days of targeted coaching on the specific skills they missed and a retest at the end of that window. Failure is not grounds for separation; it is grounds for a different ramp path. A rep who fails on the first attempt and passes on the second typically ramps as fast as a first-attempt passer, provided the gap is addressed with reps rather than ignored.
For teams of ten or more reps, yes. Sandboxes let new hires practice destructive actions (deleting a lead, closed-lost reasons, stage reversions) without endangering live data. Smaller teams can simulate a sandbox with a dedicated set of fake accounts flagged clearly in production, but true environment separation is cheaper than cleaning up contaminated real records.
Track two leading signals and one lagging signal. The leading signals are days-to-first-live-activity on a real opportunity (target: inside day six) and daily activity count by day fourteen (target: at least five logged touches per day). The lagging signal is days-to-first-closed-deal (target varies by segment, typically inside day sixty for mid-market). If leading signals miss, intervene on process. If only the lagging signal misses, intervene on sales motion.
Strkr gives you the role-based access, sandbox environments, certification checkpoints, and ramp dashboards you need to run this plan without stitching tools together. Install the rhythm once, repeat it with every hire.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
