Skip across the chapter
Quota Playbook

New-seller onboarding time: track it with 3 milestone parts

Quota Playbook Editorial Team · Published · 10 min read

A Mindtickle customer story reports that onboarding was expected to take 22 days and now takes five, according to Mindtickle. Treat that account as a case, not a benchmark, and set your own milestones so that each one can be marked done or not done.

Key takeaways

  • Record each hire's onboarding days using the same start and finish dates.
  • Count the hours your team spends searching for sales content before you change any tools.
  • Write milestones that can be marked done or not done, each with a due date and a named checker.
  • Keep one place where reps can find what they need to learn.

Why onboarding time is a figure you can track

Onboarding time is a count you can record for every new seller, and that makes it easier to discuss than a general feeling that ramp is slow. The count needs two dates for each hire: the start date and the date your team agrees onboarding is finished. Agree on both definitions before the next hire begins, because a count that changes its starting point cannot be compared with the one before it.

Write the count down at the end of each onboarding so it sits beside the next hire's count. Over several hires, that record shows whether your ramp time is drifting or holding steady. Keep the method the same each time, so that any change you see comes from the hire and not from how you counted.

A single figure tells you little on its own. Short notes beside each count, describing what the hire was asked to learn and which materials were used, help you separate a change in your process from a change in the role. Store the count and those notes in the same place as your other team records, so the series is easy to find when the next hire starts. If you want a checklist to start your note fields from, see Timestamped call notes: 5 fields before you post.

What the 22-day and five-day figures measure

It says the customer originally expected to onboard new hires in 22 days, and that onboarding now takes just five days, according to Mindtickle. The same page carries both figures.

Check whether the five-day result still applies before you present it as current practice for your team.

The quoted sentence names Shukre as the person who originally expected the 22 days, according to Mindtickle. That attribution shows whose expectation the figure records. Read the 22 days as one person's starting expectation, not as a schedule the company set for every hire.

The same story includes a customer quote that says administrative time has been reduced drastically, according to Mindtickle. That quote describes administrative time, not onboarding days, so keep the two apart when you write about the story. Mixing them would turn an administrative result into an onboarding claim.

Ask whoever shares a figure how the days were counted and when the clock started. Without that answer, a neighbouring number on a different count can look like a match when it is not. If the source cannot tell you its start and finish points, mark the figure as unverified in your notes.

Write the two figures in your notes exactly as the source words them, with the source named beside them. Keep the five-day result tied to the account it came from, so a later reader cannot mistake it for your own number.

Where the time went: content search and scattered files

The story ties lost time to how sales content was stored and answered. It puts the loss at an average of 2-5 hours a week, because sales content was saved on Asana or Google Drive, and marketing was spending time responding to sales questions about content in Slack, according to Mindtickle.

Training was also spread across formats. The story says the change was not easy, given that some parts of the organization relied on WhatsApp groups and presentations of 60+ slides to train their sales teams, according to Mindtickle.

Make a short list of every place a new seller looks for training material today, such as chat groups, shared drives, and slide decks. Next to each place, note roughly how many hours a week people spend searching there, so the list shows where the search time goes. For one way to file the material, see Example sales calls: File them in 2 library areas.

The story describes two separate habits behind the lost time: content kept in shared storage, and questions about that content answered in chat. Each habit needs its own fix, so write them as separate lines in your list rather than one general complaint about tools.

The Mindtickle blog states a vision of having all learning happen in one portal, according to Mindtickle. It also describes the aim that sales reps can easily go in, find what they need to learn, and go out and do their work, according to Mindtickle. Those lines describe a goal and a vision. If you adopt one portal as your target, pick the single place your reps open first, move the material they use most into it, and then count the search hours again after the move.

Milestones that can be marked done or not done

A milestone is useful when the person checking it can answer yes or no. Vague goals such as "ramp faster" cannot be answered that way, so rewrite each goal until it has a visible end state.

The Mindtickle blog gives examples of targets specific enough to mark done or not done, such as cutting onboarding time by 30%, consolidating three tools into one, or hitting a compliance deadline by Q3, according to Mindtickle. The 30% cut is presented there as an example of a target, not as a typical result.

Write each milestone with three parts: the end state, the date it is due, and the person who checks it. The end state should be something a manager can see, such as a set of materials a seller can open or a call a seller can finish without help. Dates matter because a milestone without one cannot be checked on a schedule. Keep the list short enough that every item actually gets checked. For a practice-goal checklist, see Sales rep practice goals: 5 checks to write today.

One milestone that meets this test reads: the seller can open the one place that holds current call materials, and the manager confirms it by the due date. It has one end state, one date, and one checker, so the answer is yes or no. A vaguer goal, such as onboarding goes well, gives nobody anything to check.

Two or three items on one date are easier to review in one sitting than a long plan that nobody reads. Where a milestone depends on a tool, name that tool in the milestone so the check is clear.

At the due date, mark each milestone done or not done, and keep that result with the onboarding count for the same hire.

Illustrative example: one hypothetical hire

Suppose a new seller starts on day 0 and the team agrees onboarding is finished on day 20. The milestones are: the seller can open the one place that holds current call materials (due day 5); the seller finishes a practice call without help (due day 10); and the manager signs off on the first live call (due day 20). On day 20, the first and third are marked done and the second is marked not done. The count records 20 days, and the missed item goes on the list for the next hire.

How to compare your own onboarding number

Compare your number only with hires you counted the same way. If the start date or the finish date moved between hires, the comparison measures your counting rather than the ramp.

Place your figure beside the 22-day expectation and the five-day result from the customer story. Read the gap as a question about your process rather than as a score. Ask which milestone took longest, where the search time went, and whether the materials a seller needed were in one place.

If your team has changed where content lives, compare hires on either side of the change. Record the content search hours for the last hire before the change and for the first hire after it, using the same method both times.

Keep the milestone wording the same across hires as well. A milestone that changes its wording between hires cannot be marked against the same standard, so the comparison breaks down even when the dates are correct.

Repeat the comparison after each hire, using the same two dates and the same milestone checks, so the series stays readable over time.

If your own counts sit well above five days, treat the gap as the starting point for a question about the next milestone, not as a verdict on the team. Look at the trend across several hires before you change how onboarding works, because a single hire can be unusual in ways one note will not show.

The limits of one customer's figures

The 22-day and five-day figures come from one customer account, so they are not a benchmark for any other firm. The same caution applies to the rollout described in the Mindtickle blog, where one quoted account says the team used the platform to roll out training to 18,000 of its sellers in six weeks, according to Mindtickle. That rollout belongs to one customer, and it is not a standard for a small team.

A Salesforce article carries a headline promising how to scale sales in one quarter or less, according to Salesforce. A headline describes what a page promises. It is not a measured result.

The Xactly Plan product page describes streamlining the administration and management of compensation programs, according to Xactlycorp. That wording concerns compensation administration, not onboarding time.

If you share these figures with your team, name the source and say they come from one customer account. That keeps the figures in their proper place as a case.

Only your own records can show what your team should achieve.

The table below lists one quoted statement from each publisher.

Publisher Source Quoted statement
Mindtickle Integrace Health customer story Originally Shukre expected to onboard new hires in 22 days, but now onboarding takes just five days.
Salesforce Scale a Sales Team in One Quarter article Here's how to scale sales in one quarter or less.
Xactlycorp Xactly Plan product page Streamline the administration and management of your compensation programs to help GTM teams maximize their performance.

Next step: write down the onboarding days for your last new hire, then set two milestones that can be marked done or not done before your next hire starts.

FAQ

How long did the onboarding example take?

Onboarding was expected to take 22 days and now takes five, according to Mindtickle. Those are the two figures to compare, and they describe one customer account.

How much rep time was lost searching for content?

The story reports an average loss of 2-5 hours a week, according to Mindtickle, because sales content was saved on Asana or Google Drive, and marketing was spending time responding to sales questions about content in Slack.

What should onboarding milestones look like?

They should be targets that can be marked done or not done, and the Mindtickle blog gives examples of that kind, according to Mindtickle. Use the same test for your own milestones.

Can one large rollout tell me what mine should be?

No. One quoted account says the team used the platform to roll out training to 18,000 of its sellers in six weeks, according to Mindtickle, and that rollout belongs to one customer. Set your milestones from your own last hire instead.

Sources

  1. Backup admin checklist: 8 checks for sales tool logins
  2. Check the 28-day backup line before a practice reset
  3. Saved-reply limits: 5 checks before the first follow-up
  4. Seller daily time: 3 tasks that pull reps off selling
  5. Lost seller phone recovery

More plays