Blog
Onboarding a new B2B salesperson
When does a new salesperson on your team get to talk to their first customer alone? If the honest answer is “whenever someone has time to walk them through it,” onboarding isn’t running on the system at all. It’s running on one person’s free time, and if that person is busy, the new hire is stuck reading old emails.
Why new salespeople take longer than they should to ramp
The problem usually isn’t product knowledge. That takes a few days to teach. The real problem is that the new hire doesn’t know where deal information lives: why a customer went quiet two weeks ago, what’s already been said, what should happen next. If that lives in a former rep’s head, a private chat thread, or a manager’s memory, the new hire waits for someone free enough to explain it, and only gets as much as that person happens to remember.
Teams that onboard fast aren’t more skilled than teams that onboard slowly. The difference is that the fast ones give a new hire somewhere to look up every deal’s status, history, and next step without interrupting anyone. The slow ones depend on a live explainer, which ties ramp speed to one person’s calendar. The bigger the team gets, the worse this gets, because the number of people who need training grows faster than the number of people who have time to give it.
What a new hire can’t find in week one
Watch what a new salesperson asks about most in their first week. It usually comes down to four things: what’s already been discussed on this deal (buried in someone’s private chat), why a deal has been sitting at this stage for weeks (no reason was ever logged when it moved), who owns which account (so they know who to ask if a customer calls and the owner is out), and what has to be true before a deal can move to the next stage (a rule that was never written down anywhere they can check themselves).
None of these should wait until a new hire has been working long enough to pick them up by osmosis. They belong in the system from the day someone logs in for the first time. When the answers live in people’s heads instead, the team pays the same ramp-up cost every time someone joins, or leaves.
What the system needs to show before a first solo call
Before a new hire talks to a customer on their own, the system should answer four things without anyone explaining them out loud.
First, the full pipeline in one page they can read in ten minutes, not a twenty-page document nobody actually reads. Second, the exit criteria for each stage, spelled out, so moving a deal forward isn’t a judgment call. Third, the last few interactions on any deal they’re picking up, with dates and a short note on what was discussed. Fourth, who owns which deal, and who to ask when that owner isn’t around.
With those four visible, a new hire walks into a call already carrying context, instead of starting from zero on a deal that’s actually halfway closed.
The first 30 days, week by week
Letting a new hire run calls solo on day one is too risky. Making them read documentation for a month is too slow. A working system sets a clear rhythm for what happens each week instead.
| Week | What the new hire does | What the system needs to show |
|---|---|---|
| 1 | Reviews real deals in the system, no customer calls yet | The full pipeline, stage-exit criteria, the team’s deal history |
| 2 | Joins customer calls with a mentor, and logs the outcome themselves | The deals being worked jointly, with a place to log results |
| 3 | Owns a couple of small deals solo, reviewed weekly from the system, not from a verbal recap | Their own deals, visible to the mentor for review |
| 4 | Runs a full pipeline and joins the regular sales meeting | Their own pipeline, clearly separated from everyone else’s |
This rhythm has the new hire learning the system and learning to sell at the same time, instead of treating them as two separate phases. It also means a mentor reviews from what’s actually in the system, not from whatever the new hire chooses to recap out loud, which tends to leave out the parts they’d rather skip.
This four-week rhythm assumes at least one mentor with time to review weekly. If your team is really just one owner who’s also carrying their own pipeline, it doesn’t work as written. Stretch it to six or eight weeks instead, so there’s still real time for a weekly review rather than a rushed one.
Signs a new hire isn’t ready to go solo
Three signs say someone shouldn’t be handling deals alone yet. First, they open a deal in the system and can’t say what the next step is without asking. Second, they finish a call and don’t log the outcome right away, so details get lost by the time they do. Third, when asked why a deal can’t move forward, they answer from a feeling instead of the stage’s written criteria.
None of this means blame the new hire. It means checking whether they actually used the system over the past few weeks, or were left to figure it out on their own. These signs usually point to a gap in the training process, not a mismatch between the person and the job. If the same signs show up across several new hires in a row, look at the four-week rhythm first, not the people going through it.
Start with whoever joined most recently
You don’t need the whole onboarding process finished before you start. Pick whoever just joined the team, or whoever joins next. Open the full pipeline to them from day one, write the stage-exit criteria down on a single page, and run the four-week rhythm above for that one person before rolling it out further.
This connects directly to who should own your sales system: whoever trains new hires on the system should be the same person who keeps checking that it still works week to week. And if your team has dealt with customers going quiet when a salesperson leaves, a working onboarding process is the other half of that same problem: it keeps whoever replaces them from starting at zero.
If you want to talk through what onboarding rhythm fits your team’s size and sales cycle, book a 45-minute call and start designing it around the deals actually changing hands right now.