Onboarding starts the moment the offer is accepted, not on the first day. The hiring manager makes a personal welcome call, followed by a written welcome. Enablement sends a day-by-day Week 1 preview. IT and RevOps provision and test the CRM, content platform, and Meridian platform logins. The onboarding buddy sends an intro message. A short pre-start check-in answers questions, even if nothing has changed. A rep who spends Day 1 waiting on logins has already lost a day of ramp, so tool readiness is measured, not assumed.

The most fragile point in onboarding is the move from company orientation to role-specific training, so it gets a named owner. People Ops owns orientation in days 1 to 3 (policies, benefits, culture, company strategy). Enablement owns role onboarding from day 4 (product, buyer, methodology, certifications). The handoff includes confirmed tool access, completed compliance items, and an intro to the buddy and manager. Ownership is mapped in the RACI on the Collaboration page.

In week 1, a placement check sets each person’s path, using the same scorecards the gates use. A New Hire follows the full plan. Lateral Hires, who have sold elsewhere but are new to Meridian, can test out of general sales-skills content, such as prospecting basics and objection handling, by showing the skill on the track’s scorecard. They move straight to product, market, and Meridian’s own methods. Testing out changes the path, not the standard. Everyone takes every gate, and the Discovery Questioning Framework and Meridian’s product and positioning are not skippable. Time freed by testing out goes to extra practice on those.

“Advance on proof, not a calendar” needs a plan for the person who isn’t there yet. The manager and enablement review the attempt against the scorecard within two days and name the specific gap. The person gets targeted coaching on it, with a practice session before the retake. The retake comes within a set window (for example, two weeks), on a new scenario so it isn’t memorized. After a second miss, the person, the manager, and enablement decide whether the problem is the skill, the plan, or the fit, and if it’s the plan, it goes back to enablement to fix. After repeated misses (for example, three), the manager and People Ops hold a performance conversation, and the gate record shows what support was given. Patterns get reported, because where people miss tells enablement which parts of the program need work. A gate with no consequence is a formality, and a gate that only punishes teaches people to hide gaps. The point is to find the gap early and close it.

Before launch, Meridian records a baseline from recent hires for each metric. Each new cohort is compared to it, and specific targets are set once the baselines exist. A person isn’t “onboarded” because 90 days have passed. They’re onboarded because they cleared every gate, and the numbers back it up. Each measure is defined on the Metrics page. This page says which apply to which role:

• AEs: time to first meeting, time to first self-sourced qualified opportunity (grade B or higher on the Opportunity Grading Agent, not just “an opp exists”), time to first, second, and third deal (reported separately, so an inherited late-stage deal isn’t mistaken for early success), and ramp-quota attainment.

• SDRs: time to first self-sourced meeting, time to first self-sourced qualified opportunity, and meeting-to-opportunity conversion, reported with counts.

• CSMs and account managers: time to first independent kickoff (CSM) or first agreed expansion opening (account manager), the share of the portfolio health-scored by day 90, and renewal checkpoints met on schedule (CSM).

• Everyone: certification pass rate (first attempt vs. total), day-one readiness, time to certified readiness, and the on-time rate for each gate, since repeated delays at one gate show where support or practice is missing.

New Hire Pulse scores are reported alongside these numbers, so leadership sees both the results and the experience behind them. Each cohort should beat the baseline, with first-attempt pass rates rising over time.

Certification gates show whether someone can do the work. The Pulse shows whether the program is working for them. It is the same survey at Day 30, Day 90, and Day 365, covering tools and technology (“I have the systems and access I need”), productivity and skills (“I feel equipped to contribute to team goals”), and culture and connection (“I feel my background and experience are valued here”). It takes under 15 minutes, with protected time in the plan. The multiple-choice questions are required and the open-ended ones are optional.

Responses are confidential, and no individual’s answers go to their manager or into their performance reviews. Individual responses are seen only by enablement. Results are segmented by role and experience only where the group is large enough, and reported only above a minimum size, so no one can be identified. Open-ended comments are grouped into themes. Response rate is tracked as its own number, and a low rate is treated as a signal about the program. Findings go to the teams that own each part of the experience (People Ops, IT, RevOps, and sales and CS leadership). Every program change is logged alongside the feedback that prompted it, and new hires are told what changed as a result. Onboarding happens over months, so measuring once tells you how Week 1 felt, not whether the program worked.

Certification ends at Day 90. Onboarding doesn’t. From day 90 to 365, people move into ongoing training and coaching (every two weeks once certified), with reinforcement built on the Adoption Loop’s Lock It In phase (see Coaching, and the Adoption Loop on Real Work). The Day 365 Pulse measures whether early gains held through year one. Year-one retention reporting uses early signals (onboarding completion, Pulse scores, early attrition), and full retention proof arrives in year two.

The three outcome numbers, the role measures, and the Pulse are reported back to leadership and decide whether the program itself needs to change, following the weekly, monthly, and quarterly cadence on Collaboration. A cohort that is struggling gets re-engaged through the Adoption Loop on Real Work, rather than just flagged.