A sales onboarding checklist for technology sales is a manager inspection, not a course outline. Mark each item yes or no before a new seller works a live opportunity, because a completed module is not a pass. A pass is a written output a Head of Sales, a Head of Revenue Operations, or a Head of Enablement can read in the record.

Let's Meet!

What should a sales onboarding checklist for technology sales inspect?

Inspect the work the seller must do, not the topics they sat through. For a technology account executive, that work is a first meeting, a buying group, a qualified opportunity, and a next step the buyer accepts. For a sales development representative, it is different. The output is account selection, relevant outreach, a useful conversation, and a clean handoff.

"Understands the product" fails this test. A passing note names the buyer's current process, the business impact, the people involved, and the agreed next step. RevCentric builds sales enablement consulting around that difference. The work is playbooks, practice, and live coaching that show up in the deal, not only in a slide deck.

Keep this page as the pass-fail sheet. The guide to what sales onboarding should include covers how to design role-based practice. The sales onboarding blueprint covers how to structure the program. Do not rewrite either one here.

Association for Talent Development research on sales onboarding found that 77 percent of surveyed organizations named faster productivity as the top benefit of having a program. The same research named holding managers accountable for what was taught as the top barrier, cited by 56 percent. A checklist exists so that accountability has a mark, not a mood. ATD reported those findings from its Sales Onboarding: Launching Productivity study.

Who owns each check?

Split the sheet by the decision each leader already makes. If one person owns every box, the checklist becomes a training log and stops being an inspection.

Who signs each sales onboarding check.
Check.Head of Sales.Head of Revenue Operations.Head of Enablement.
Role output.Names the customer-facing action.Confirms the stage it belongs to.Builds the practice that produces it.
Buyer proof.Rejects a generic product story.Stores the proof the seller may use.Puts that proof in the call plan.
MEDDIC evidence.Says which fields must be true.Makes those fields required.Coaches the seller to fill them from the call.
First-meeting asset.Listens to one live or recorded call.Checks the next step is in the record.Supplies the guide the seller used.
Sign-off.Marks the seller ready for a live deal.Confirms the handoff fields exist.Notes what still needs practice.

A blank cell is a failed check. Do not let Enablement sign Sales work. Do not let Sales invent a CRM field that Revenue Operations has not defined.

Run the sheet on one named new hire, not on the program in the abstract. Pick a start date, write the role, and then mark only what you can see in a note, a recording, or the CRM. A verbal "they are doing fine" is not a mark.

Technology deals make vague marks expensive. A seller who can recite the platform still loses the room when they cannot say which workflow is broken. The checklist catches that gap before the first live opportunity, while a coach can still sit on the call with the seller.

Which role outputs must be written down first?

Write one observable output per role before you open the rest of the sheet. Two roles are enough to start, and specialists should wait until those two outputs are stable.

  • Account executive. After a first meeting, the note names the buyer's current process, the impact worth pursuing, the people in the deal, and the next step with a date.
  • Sales development representative. The outreach names a specific account problem, and the handoff includes what the buyer said, not only that a meeting was booked.
  • Manager. The review says what was missing and what the seller will do on the next call. "Nice job" is not a pass.

If the output cannot be pasted into the opportunity or account record, it is not ready for the checklist. A slide titled "discovery skills" does not count.

Write the output as a sentence the manager could defend in a forecast call. For an account executive, a usable sentence has four parts. The buyer still reconciles usage by hand each Monday. The delay hits the renewal forecast. The operations lead and the economic buyer both attend the review. The next working session is Thursday. That sentence can be checked. "They liked the vision" cannot.

For a sales development representative, the same test is stricter about the handoff. A meeting on the calendar is not the output. The output is the buyer's words, the reason the account was chosen, and the question the account executive should open with. If that context is missing, fail the row and redo the handoff. Do not hope the next seller will recover it.

Experienced hires often skip this row because they have sold elsewhere. Keep it anyway, because a prior logo does not tell you whether they can describe this buyer's process. Ask for the sentence on a practice account before you assign a live territory.

Two technology sales professionals discuss a call plan beside a blank monitor

How do you mark product and buyer proof?

Technology sellers drown in feature lists. The check is whether they can use one proof point a buyer would recognize. Ask for a short written answer, then mark it.

  1. The seller names the buyer's current workflow in the buyer's words, not the product category.
  2. The seller states one cost of staying with that workflow, and the cost is operational, not a slogan.
  3. The seller attaches one proof point, such as a result a similar buyer accepted, and says where it fits in the call.
  4. The seller can drop the proof if the buyer rejects the problem. A forced demo is a fail.

Fail the check when the answer could describe any software company. Pass it when a manager could brief a colleague from the note alone. RevCentric's work on what makes a good sales playbook is the place to design that proof. This sheet only asks whether the new seller can use it.

Use a real buyer situation, even if the names are changed. A cybersecurity seller might inspect a team that still exports alerts to a spreadsheet. A data-platform seller might inspect a team that cannot trace which pipeline failed. The category changes, but the test does not. The seller must say what the buyer does today, what it costs, and which proof belongs in the conversation.

Watch for the borrowed proof point. New hires often paste a customer story they did not learn. Ask them which fact the buyer would challenge, and what they will do if that fact is rejected. If they freeze, the asset is not theirs yet, so mark the row no and schedule another pass. Do not treat a polished paragraph as evidence of judgment.

How should MEDDIC evidence be checked?

MEDDIC is the qualification language RevCentric uses, as the authors of MEDDIC. Dick Dunkel authored it at PTC in 1996. On this checklist, do not teach the letters. Confirm the seller can point to evidence for the letters that change the next step.

Use a binary read of one practice opportunity:

  • Metrics. A number or operational impact the buyer stated, or a clear "not yet."
  • Economic buyer. A named person, or a plan to reach that person.
  • Decision criteria. What the buyer said they will compare, not the seller's feature list.
  • Decision process. The steps, the people, and the date of the next internal review.
  • Identify pain. The current process and why it is costly now.
  • Champion. A person who will sell internally, with a specific action they agreed to take.

A blank dressed up as "unknown" is acceptable, but a blank dressed up as a guess is not. MEDDPIC, MEDDPICC, and MEDDICC add paper process, competition, or both. Add those letters only if the team already inspects them in forecast reviews. Otherwise you are testing trivia.

Live deal coaching is where this evidence gets honest. Classroom recall is not the same as a seller stating the gap while a buyer is on the line. That is why RevCentric's sellers teach sellers in those live situations. That is the "Teaching in the Trenches" standard, not a podium quiz.

Score the practice opportunity in the same place the forecast will later be read. If the evidence lives in a side document, managers will not use it. A champion without a named action is a no, and a decision process without a date is a no. Pain that is only the seller's hypothesis is a no, and the note should say "not confirmed."

This row is also where paper process and competition stay optional. Add them when the team already asks those questions in deal review. If leaders never inspect them, a new hire should not be failed for leaving them blank. The checklist should match the operating review, or it will teach a second language.

Which assets must the seller use, not just find?

A library is not a pass. Pick the assets a technology seller touches in the first live cycle, and watch them use each one on a practice deal.

  • Call plan. The seller can show the question they will ask and the answer that would change the next step.
  • Discovery note. The note matches the sales discovery checklist standard: problem, impact, stakeholders, and commitment. Do not rebuild that question bank here.
  • Demo narrative. The story follows the buyer's problem, and it does not open with architecture.
  • Mutual next step. The follow-up names the owner, the date, and the evidence still missing.

If the seller cannot find the asset without a scavenger hunt, fail the asset check and fix the library. Do not coach around a messy folder. Heads of Enablement own that fix. Heads of Sales should not accept a "we covered it in week one" substitute.

What does a manager have to observe?

Read one call or one role-play before you sign. The ATD finding on manager accountability is the reason. A program that nobody inspects does not change the second week.

Mark these four items:

  • The manager heard or watched the call, or a qualified coach did, and wrote what the buyer actually said.
  • The debrief names one behavior to repeat and one to change. Both are specific to that call.
  • The seller restates the change in their own words and points to where it will appear in the next note.
  • The manager schedules the next observation. A single review with no second look is incomplete.

Shadowing a top rep for a week is not this check. Shadowing without a written standard teaches habits, including bad ones. The manager's note is the standard.

Keep the observation short enough to repeat. One call, one debrief, and one scheduled second look are enough, while a two-hour commentary teaches the manager's taste. A tight note teaches the behavior. If the seller cannot point to the line in the next note that will change, the observation did not land.

Dispersed teams fail this row when travel becomes the excuse. A recording plus a written debrief still counts. What does not count is a manager who never hears the buyer. The ATD research called out geographically dispersed teams as a barrier. The fix is a review that can happen without everyone in one room, not a waiver.

How do Revenue Operations and Enablement close the handoff?

The last rows stop a ready seller from entering a system that cannot hold their work. Revenue Operations confirms the fields, Enablement confirms the seller can fill them, and Sales confirms the person may take a live meeting.

Use this order:

  1. Stage names in the CRM match the actions the checklist tested.
  2. Required fields match the MEDDIC evidence above, and optional trivia is not required.
  3. The seller completes one record on a practice opportunity with no coach typing for them.
  4. The manager, Revenue Operations, and Enablement each initial the date. A missing initial keeps the seller in practice.

Do not use this sheet to pick a training vendor or a ramp target. Sales training programs covers what to buy first. Sales training measurement covers whether the skill transferred. Buyer-value evidence in the sales process covers how stages should read. Link those pages, and do not copy them.

When the three initials are in place, the new seller can work a live opportunity with a named manager still on the hook. That is the only graduation this checklist recognizes.

Date the sign-off, because a checklist with no date becomes folklore. Store it on the hire record that Revenue Operations already uses, not in a personal folder. The next manager should be able to see which rows passed, which were waived, and who waived them. A waiver needs a reason and a review date. "Trusted hire" is not a reason.

Reopen the sheet after the first live opportunity, even when every row passed in practice. Compare the practice note with the live note. If the live note drops the impact, the stakeholders, or the next step, the pass did not transfer. Put the seller back on a coached call. Do not wait for a missed number to discover the gap.

RevCentric's operators use this kind of inspection because customized programs still fail when nobody checks the work. Sellers teaching sellers only matters if the manager can see the same evidence the coach saw. The checklist is that shared view. It is not a promise of a ramp time, a win rate, or a quota outcome.

Claim Your Assessment

Frequently Asked Questions

How is this different from a sales onboarding program?

A program teaches the work over time. This checklist asks whether a manager can already see the work in a note, a call, and a CRM record. Use the program to build skill, and use the checklist to decide if the seller may take a live technology opportunity.

When should a manager run the checklist?

Run it before the first unsupervised live meeting, and again after the first observed call. A week-one completion certificate is too early, and waiting until the first missed quarter is too late.

Does every new seller need the same checks?

No. An account executive and a sales development representative need different outputs. Experienced hires still need the same evidence standard. They may move through it faster, but a resume is still not a pass.

What if the CRM fields are not ready?

Fail the handoff, not the seller. Revenue Operations should add or rename the fields before Enablement signs the record. Sending a new seller into a mismatched stage model trains them to invent data.

Can this checklist replace MEDDIC training?

No. It only checks whether the seller can show evidence for the letters the team already uses in live reviews. Training, live call coaching, and forecast inspection stay on their own pages and in the manager's weekly review.