Built for sales managers and enablement leads running the ramp

The 90-day sales onboarding checklist that actually tracks to a shorter ramp curve, not a shelf of binders.

Most sales onboarding checklists collapse into a day-one PDF, an LMS course that nobody finishes, and a Slack channel the new hire goes quiet in after week three. This checklist is different. Each item has a named owner, a deliverable, and a timing anchor. The structure covers pre-start, day-one, week-one, 30-60-90, and the exit criteria for ramp. Pulled from the onboarding patterns of RevOps teams who have measured ramp time against this specific template.

Start free trial See pricing
What this audience is actually dealing with

The pains that bring buyers here.

A sales onboarding checklist that lives in a shared Google Doc gets opened on day one and never again. The hire fills in the easy items in the first week, the medium items by week three, and the hard items get stalled against the manager's calendar for the rest of the quarter. By day 60 nobody knows what is actually done and what is pretend-done. The six pains below are what sales managers describe when their ramp curve stretches past the 90-day target and they go hunting for a better template. The common thread is that checklists without ownership, timing, and exit criteria behave like decoration rather than operating structure.

Owner-less items

The checklist lists tasks but nobody owns the completion.

A checklist with 60 items and no named owner for each item collapses into "the new hire owns everything." Reality: half the items require a sales engineer, a product marketer, a legal partner, or a finance partner to deliver. If those owners are not named, the hire chases people for weeks. The fix: every item has a named owner (role or person) and a backup owner if the primary is out.

No timing anchor

The ramp drifts because nothing is time-bound.

A checklist that says "complete product training" without "complete product training by end of day five" lets completion slide. Hires with ambition finish early, hires who need structure drift to week four, and the manager cannot tell either apart on week two. The fix: every item has a day or week anchor so the manager spots drift in the one-on-one before it compounds.

Fake completion

Checked off is not the same as competent.

A hire can check "watched the product demo recording" without being able to deliver the product demo. The checklist that stops at the task-done level produces graduated hires who cannot run the plays. The fix: every learning item has an exit criterion where the hire demonstrates the skill (recorded demo, mock discovery call, written objection response) before the item marks complete.

No milestone gates

The 30-60-90 slips because the gates are soft.

Without explicit go/no-go milestone gates at day 30, 60, and 90, the ramp becomes a continuous slope with no decision points. A manager who sees drift at day 50 waits until day 90 to intervene, costing another month of production. The fix: each gate has specific pass criteria (certifications earned, deliverables produced, calls shadowed) and a documented decision at each gate.

Hire reports instead of the manager

The hire self-reports progress and the manager flies blind.

Checklists where the hire updates their own status in a doc give the manager a Monday morning problem: scanning 60 checked boxes to find the two that stalled. The manager cannot see the pattern across the hire's workload because the data lives in a doc rather than a surface. The fix: the checklist lives on the record where the manager, the enablement partner, and the hire all see the same real-time state.

Checklist dies at day 30

The template covers day-one but not days 31 through 90.

The most common template failure is a checklist that is detailed for days 1 through 7, lighter for days 8 through 30, and silent for days 31 through 90. The ramp curve matters most between days 30 and 90 (first deals closed, first pipeline generated, first forecast submitted) and the template abandons the hire in that window. The fix: the checklist stays specific through day 90 with weekly deliverables and exit criteria for ramp.

Pre-start (offer-accept to day zero)

The handoff that makes day one productive.

The pre-start window runs from offer-accept to day zero (typically 2 to 6 weeks). Pre-start items are the handoff work that must land before the hire shows up so day one is productive rather than an access-ticket scramble. The checklist below assigns each pre-start item to the owner.

Access provisioning

Email, CRM, Slack, calendar, documents by day minus three.

IT and RevOps provision access to email, CRM (Strkr or equivalent), Slack, calendar, documents, dialer, and the sales toolkit by day minus three. Day zero includes a provisioning verification pass where the hire logs into each tool and confirms access. The owner on this item is the IT lead; the backup owner is the RevOps lead.

Day-one calendar

The first week of meetings on the calendar by day minus two.

The hiring manager and the enablement partner co-author the first-week calendar: welcome breakfast, manager one-on-one, enablement partner introduction, team round-robin, product deep-dive, and the first 30-minute "nothing scheduled" blocks. The calendar lands on the hire's calendar two business days before start date.

Welcome package

Hardware, swag, and the printed handbook.

The hire receives the welcome package (laptop, monitor if remote, swag, printed handbook or digital equivalent) by day minus one for in-office hires and day minus five for remote hires. The package includes a one-page "what day one looks like" written by the hiring manager with the day's meeting-by-meeting plan.

First-30-day plan draft

The manager drafts the plan before the hire arrives.

The hiring manager drafts the first-30-day plan with specific deliverables (certifications, call shadowing counts, mock discovery calls, product proficiency) before day one. The draft is a working document that gets refined with the hire in the first-week one-on-one, not a finished artifact imposed on day two.

Team announcement

The team hears about the hire by day minus five.

The hiring manager sends a team-wide introduction note by day minus five with the hire's background, start date, territory or segment assignment, and a request for team members to send one Slack welcome message in the first week. The announcement also goes to adjacent teams (SE, marketing, CS, legal, finance) that the hire will partner with.

Buddy assignment

A peer buddy named and scheduled.

A peer buddy (a tenured rep in the same role or adjacent segment) is named by day minus seven with a 30-minute buddy-introduction scheduled for day two. The buddy is the hire's "stupid question" partner for the first 30 days; the hiring manager explicitly scopes the buddy role so it does not become uncompensated enablement work.

Day one and week one

The first-five-days structure.

The first five days are high-density by design. The hire absorbs company context, product context, team context, and territory context in a order that builds progressively. The checklist below covers day-by-day deliverables.

Day one: orientation

Welcome, access verification, mission context.

Day one covers welcome breakfast (or virtual equivalent), access verification across all systems, mission and strategy context from a VP-level leader, hiring manager one-on-one, team round-robin introductions, and the first "nothing scheduled" block for the hire to catch their breath. The day ends with a 30-minute reflection with the hiring manager.

Day two: product deep-dive

The product foundation that supports every other skill.

Day two is a product deep-dive led by product marketing with the hire shadowing a product demo and attempting their own at the end of the day. The deliverable is a 20-minute product walkthrough recording that the hire submits to the enablement partner for feedback. The buddy introduction happens on day two as well.

Day three: ICP and messaging

Who we sell to and the messaging that lands.

Day three covers ideal customer profile (ICP) depth, buyer personas, the three to five message frames the sales team uses, and the top five objections with written responses. The hire delivers a 10-minute "pitch to a mock buyer" exercise at the end of day three with the hiring manager scoring on specific anchors.

Day four: process and tools

The CRM workflow, the forecast rhythm, and the toolkit.

Day four is the CRM and process deep-dive: the opportunity stages, the exit criteria for each stage, the forecast categories, the data hygiene standards, the Monday forecast rhythm, and the toolkit (dialer, sequence tool, call recording, document generator). The hire creates a mock opportunity in the CRM and advances it through two stages.

Day five: territory and plan

The hire's specific book, pipeline, and 30-day plan.

Day five covers the hire's specific territory assignment (if a new book), inherited pipeline (if a backfill), named account priorities, and the first-30-day plan review with the hiring manager. The plan gets locked by end of day five with specific deliverables, metrics, and check-in cadence.

Week-one wrap

A 45-minute reflection with the manager.

The week closes with a 45-minute reflection one-on-one covering what landed, what still feels foggy, what questions came up, and the week-two preview. The hire also sends a one-paragraph recap to the hiring manager summarizing the week in their own words; the manager uses the recap to spot misunderstandings early.

Shadowing count

Four live calls shadowed by end of week one.

The hire shadows at least four live calls in week one: two discovery calls, one demo, and one closing or expansion call. Each shadowed call includes a 15-minute debrief with the host rep. The buddy or hiring manager coordinates the shadow calendar before day one so the hire does not spend week one hunting for calls to join.

Certifications started

Product and process certs scheduled in the LMS.

The hire enrolls in the three to five foundational certifications on day two with specific completion target dates (typically day 10 to day 20 depending on cert depth). The certifications are not day-one busywork; they are a structured path to specific proficiency outcomes measured against defined anchors.

The 30-60-90 structure

Milestone gates with specific pass criteria.

The 30-60-90 structure converts the ramp curve into three explicit decision gates. At each gate the hiring manager, the enablement partner, and the hire review specific pass criteria and document a go/no-go decision. The structure prevents the common failure where ramp drift goes unnoticed until day 90.

Day 30 gate: foundation

Product, process, and ICP fluency demonstrated.

Day 30 pass criteria: three foundational certifications complete; one recorded product demo scored at a 4 of 5 or better; one recorded mock discovery call scored at a 4 of 5 or better; CRM workflow proficiency demonstrated through five live opportunity updates; 20 shadowed calls logged with debriefs. Fail the gate: a 15-day remediation plan with specific daily deliverables and a renewed decision at day 45.

Day 60 gate: first motions

First outbound, first discovery, first demo.

Day 60 pass criteria: 50 outbound touches logged (if a hunter role); five live discovery calls run (manager shadowed on two); two live product demos run (manager shadowed on one); first opportunity created and advanced to a middle stage; first manager-reviewed forecast submission for the hire's book. Fail the gate: a 15-day remediation plan with specific coaching cadence and renewed decision at day 75.

Day 90 gate: ramp exit

First deal closed or first qualified pipeline generated.

Day 90 pass criteria vary by role. New-business AE: at least one closed-won deal or 150 percent of monthly target in qualified pipeline. SDR: 80 percent of monthly meeting target delivered. CSM: ownership of the full account book with the first renewal conversation complete. Enterprise AE with longer cycles: 200 percent of monthly target in qualified pipeline. Fail the gate: a structured conversation about role fit, extended ramp, or offboarding.

The decision document

A one-page gate decision at each milestone.

Each gate produces a one-page decision document: the pass criteria met and missed, the manager's commentary, the hire's self-assessment, and the next-step commitments. The document lives on the hire's record and the enablement partner reviews it. Pattern recognition across hires reveals systemic ramp friction (specific certifications that always miss, specific shadow calls that are not happening) that the enablement team then fixes.

Weekly manager one-on-one

A agenda template through day 90.

The weekly manager one-on-one through day 90 follows a agenda: week recap from the hire, checklist items at risk, coaching topic chosen by the manager, questions from the hire, next-week commitments. The template is not negotiable; drift to free-form one-on-ones is the leading indicator of ramp slippage.

Weekly enablement check-in

A 30-minute conversation with the enablement partner.

The enablement partner holds a 30-minute weekly check-in with the hire through day 60 (biweekly through day 90) covering certifications in flight, specific skill gaps, and emerging questions that the manager one-on-one does not catch. The enablement partner shares pattern data with the manager so the two coach from the same signal.

Buddy rhythm

A weekly 20-minute buddy conversation through day 30.

The buddy rhythm is a weekly 20-minute conversation through day 30 covering the week's stupid questions, cultural nuances, and the hire's informal read on how the first 30 days are going. The buddy is not a formal evaluator; the buddy is the hire's psychological safety partner for the first month and the role gets explicit scope so it does not drift into enablement work.

Pipeline review inclusion

The hire joins pipeline reviews from week three.

The hire joins the team pipeline review from week three as an observer, from week six as an active participant on their own deals, and from week 12 as a full participant on the team's cross-coaching. The inclusion ladder prevents the common failure where the hire gets dropped into pipeline review on day 60 without context and freezes.

The exit criteria

What ramp-complete actually means.

Ramp-complete is not a day on the calendar; it is a set of specific exit criteria that mark the hire as fully productive. The exit criteria below are the ones used by sales organizations that have measured ramp time against this template and found the criteria predict sustained production in quarters two through four.

Productive capacity achieved

Monthly quota attainment at 80 percent of a tenured rep.

The hire delivers 80 percent of a tenured rep's monthly quota attainment over trailing three months. The 80 percent threshold is the common ramp-complete marker; 100 percent attainment typically arrives in months six to nine depending on segment and cycle length. The metric uses trailing three months to smooth variance; a single-month hit does not mark ramp complete.

Forecast reliability

Three consecutive monthly forecasts within tolerance.

The hire's forecast submission lands within the organizational tolerance band (typically plus or minus 15 percent of actuals) for three consecutive months. Forecast reliability is a stronger ramp-complete signal than raw quota attainment because it indicates the hire has internalized the pipeline math, the exit criteria for stages, and the judgment calls that produce accurate forecasts.

CRM hygiene standard

Hygiene score at 90 percent or better for 60 days.

The hire's CRM hygiene score (next-step current, close-date current, amount current, decision-maker identified, mutual action plan attached) sits at 90 percent or better for 60 consecutive days. Hygiene discipline is the operational muscle that supports forecast reliability; the two metrics correlate strongly and should ramp-complete together.

Pipeline generation independence

Self-sourced pipeline at 30 percent or better.

For hunter roles, 30 percent or more of the hire's pipeline is self-sourced through outbound, personal network, event follow-up, or partner referral. The threshold varies by role (SDR-fed AEs run lower, pure hunters run higher), but the percentage is defined in the role scorecard and the hire crosses it before ramp exits.

Cross-functional partnership

Independent partnership with SE, legal, and CS.

The hire runs independent partnerships with sales engineering, legal, and customer success without the hiring manager mediating. Independent partnership means the hire owns the handoff, the briefing, and the follow-up. Managers who still broker these handoffs at day 120 are the signal that cross-functional ramp is incomplete.

Coaching posture shift

Weekly coaching moves from fundamentals to deal-specific.

The weekly one-on-one coaching topic shifts from fundamentals (how to do discovery, how to run a demo, how to update the CRM) to deal-specific coaching (how to handle this specific objection on this specific deal, how to run the next step on this specific opportunity). The shift signals that the hire has internalized the fundamentals and is ready for deal-level coaching.

Team contribution started

The hire gives in a team meeting at least monthly.

By ramp exit, the hire contributes to the team's collective learning at least monthly: sharing a objection response that worked, presenting a tactic from a successful discovery call, or walking through a lost-deal post-mortem. The contribution signal marks the shift from net-consumer to net-contributor on the team.

Ramp certification

A documented, signed ramp-complete decision.

The ramp-complete decision is documented and signed by the hiring manager, the enablement partner, and the hire. The decision moves the hire from "ramping" status to "tenured" status in the CRM and the compensation plan. The documentation also closes the loop with HR on probation period and the comp plan transitioning from ramp-adjusted to full plan.

Head-to-head

Checklist with ownership vs typical onboarding template.

Most downloaded sales onboarding checklists are a flat list of tasks. The structured checklist below treats onboarding as an operational workflow with owners, timing, and exit criteria. The comparison shows what changes.

Feature Strkr Typical flat checklist
Named owner per item Every item has a role or person as owner Items are implicitly owned by the new hire
Timing anchor Specific day or week for every item General phase (week one, month one)
Exit criteria Demonstrated skill or deliverable produced Self-reported task completion
Milestone gates Day 30, 60, 90 explicit go/no-go decisions Soft gates with implicit expectations
Manager visibility Real-time surface in the CRM Shared doc the manager scans weekly
Days 31 through 90 coverage Specific weekly deliverables and gates Light or absent coverage after day 30
Shadowing coordination Shadow calendar pre-scheduled by day minus one Hire sources shadows themselves
Buddy scope Explicit buddy role with weekly rhythm Informal "ask any question" posture
Pass criteria at each gate Specific anchors with scored evaluations Manager intuition
Ramp-complete decision Documented and signed with HR trigger Implicit, often never formally made
How teams use Strkr

How sales managers used the checklist.

The patterns below are from sales managers and enablement leads who adopted the checklist as the operating structure for their ramp program. The common thread is measurable ramp time reduction and sustained production in quarters two through four.

Series B SaaS, 15 to 45 reps in 18 months

Ramp time cut from 128 days to 83 days.

A Series B SaaS scaling from 15 to 45 reps adopted the checklist as the operating template for every hire. The pre-start owner assignment and the day-30-60-90 explicit gates were the two interventions that moved the needle. Average ramp time across 30 hires in the sample window dropped from 128 days to 83 days, measured as days from start to 80 percent of tenured monthly quota attainment on trailing three months.

Enterprise B2B, long-cycle AEs

Forecast reliability landed by day 90 instead of day 180.

An enterprise B2B with 12 to 18 month sales cycles adopted the checklist with heavy customization for the long-cycle context. Forecast reliability (plus or minus 15 percent of actuals for three consecutive months) landed at day 90 across the next cohort of six hires, versus day 180 historically. The hiring manager cited the weekly forecast submission starting in month two as the intervention that produced the earlier forecast muscle.

Growth-stage, remote-primary

Buddy rhythm cut 30-day attrition in half.

A growth-stage remote-primary company with a historical 20 percent 30-day attrition rate on sales hires adopted the explicit buddy rhythm (weekly 20-minute conversation through day 30) as the headline intervention. The next two hiring cohorts (14 hires total) ran at 7 percent 30-day attrition. The hiring manager cited the scoped buddy role as the fix for remote isolation that previously drove early churn.

Field sales organization, 60 reps

Shadowing coordination freed 40 manager hours per hire.

A field sales organization with 60 reps and a historical pattern of hires spending week one hunting for shadow calls adopted the pre-start shadow calendar. The shadowing coordination (buddy or hiring manager pre-scheduling 20 shadow calls in weeks one through three) freed an average of 40 manager hours per hire that previously went to shadow brokerage. Manager coaching time increased by the same magnitude.

Mid-market, 30 to 90 day cycles

Day 90 close rate matched tenured reps by month six.

A mid-market B2B with 30 to 90 day sales cycles adopted the checklist with specific emphasis on the day 60 "first motions" gate. The gate's pass criteria (first opportunity in middle stage, first demo run, first forecast submission) caught two hires who were otherwise on-pace to miss day 90. Both remediated with the structured 15-day plan and landed day 90 on-criteria. Day 90 close rate across the subsequent six-hire cohort matched tenured reps by month six, a 60-day improvement.

Run every ramp from a checklist that lives on the record.

Strkr ships the 90-day sales onboarding checklist as a template on the hire's record with named owners, timing anchors, exit criteria, and the day 30, 60, 90 gates built in. Start a 14-day trial and run your next hire against the template that cuts ramp time by 30 to 45 days.

Start free trial See pricing
Common questions

What buyers in this bucket ask most.

How long should a sales onboarding checklist actually be?

A full checklist runs 60 to 120 items across the 90-day window. Fewer than 50 items usually means important work is implicit; more than 150 means the checklist is probably a dumping ground. The count varies by role: a transactional SDR role might run 55 to 75 items, a full-cycle AE role 90 to 115, an enterprise AE with a complex product and legal process 120 to 150. The item count is not the point; the point is every item has an owner, a timing anchor, and an exit criterion. A 60-item checklist that meets those three bars outperforms a 200-item checklist that does not.

Who should own the checklist overall?

The hiring manager owns the checklist for a hire; the sales enablement partner owns the checklist as a template across all hires. The two-owner structure matters: the hiring manager customizes the template for the role and the hire, and the enablement partner refines the template based on pattern data across hires. Without the enablement owner, every manager invents their own checklist and the organization loses the compounding learning. Without the hiring manager owner, the template never gets the role-specific customization and the hire ramp drifts.

Can one checklist cover different sales roles?

No. The template structure (pre-start, day-one, week-one, 30-60-90, exit criteria) is the same across roles, but the items and pass criteria differ by role. An SDR's day 60 gate includes outbound volume and meeting generation; an enterprise AE's day 60 gate includes mutual action plans and multi-threading. Treat the template as a shell that gets filled with role-specific items. A single generic checklist for all sales roles is worse than no checklist at all because it signals that the organization has not thought about the role.

How do we handle hires who ramp faster than the checklist?

Fast rampers compress the timing anchors on the checklist, not skip items. The exit criteria at each gate are what mark ramp progress, not the days. A hire who hits day 30 pass criteria at day 20 should move to day 60 pass criteria early with the manager; a hire who hits day 60 criteria at day 45 should start on quota-earning deliverables rather than continue running through onboarding items. The structure accommodates fast rampers by letting them demonstrate exit criteria early rather than imposing arbitrary wait time.

What happens at the day 30 or day 60 gate if the hire fails?

The hire enters a structured 15-day remediation plan with specific daily deliverables, a renewed decision at day 45 (for the day 30 miss) or day 75 (for the day 60 miss). The remediation plan is not a performance improvement plan in the HR sense; it is an operational response to specific missed exit criteria. If the day 45 or day 75 renewed decision also fails, the organization has a role-fit conversation. The structured gate approach prevents the common failure where ramp drift goes unaddressed until day 90 and then the hire gets off-boarded with 90 days of mutual dissatisfaction.

Where should the checklist actually live?

The checklist should live on the hire's record in the CRM alongside their pipeline and their one-on-one notes. Living on the record (rather than in a shared doc) means the manager, the enablement partner, and the hire all see the same real-time state, with the same ownership, timing, and status. The CRM record also surfaces the checklist in the manager's weekly review alongside the hire's pipeline, which is where ramp coaching naturally happens. Strkr's onboarding surface is built for exactly this pattern; teams on legacy CRMs cobble together an equivalent through tasks, lists, and custom objects.

Also built for

Related audiences.

Sales Onboarding Platform Sales Operations Sales Operations Manager Sales Ops Sales Enablement Account Executives

Try it free. Bring your team next week.

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.

Start free trial See pricing