OnboardingReviewed by Adroit Staffing editorial reviewPractice guidance, no data claims5 min read
The short answer
Measure understanding at 30 days, activity quality at 60 days, and pipeline outcomes at 90 days. Judging a new seller on closed revenue in month one tells you nothing about whether the hire is working; judging their questions and call quality tells you a great deal.
Key facts
- Day 30 measure
- Understanding — of product, customer and process
- Day 60 measure
- Quality of activity, not volume
- Day 90 measure
- Self-created pipeline and forecast accuracy
- Written plan
- Shared with the hire before day one
The plan
| Checkpoint | The hire focuses on | You measure | Early warning sign |
|---|---|---|---|
| Day 30 | Product, ICP, competitors, listening to calls | Can they explain the customer's problem unprompted | Can only describe features |
| Day 60 | Running their own conversations with coaching | Question quality, follow-up, CRM accuracy | Activity is high, conversations are shallow |
| Day 90 | Owning pipeline and forecasting it | Self-created pipeline, stage accuracy | Pipeline exists only because it was inherited |
What the manager owes the hire
- A written definition of what good looks like at each checkpoint, given before day one.
- Weekly call reviews for the first eight weeks, in the diary before the start date.
- Access to real customer conversations in week one, not week five.
- One named person to ask stupid questions without it becoming a performance conversation.
Acting on what you see
If two checkpoints are missed, have the direct conversation immediately. In our own searches the problem is rarely that the signs were absent by day 60 — it is that the conversation waited until a formal review, which is expensive for the business and unfair on the person.
Missing one checkpoint is information, not a verdict. Ask which of the three things you owed the hire was missing before you conclude the hire was wrong: a written definition of good, real customer exposure, or coaching time that survived a busy quarter.
Building the checkpoints around your own sales cycle
The 30/60/90 shape is a convention, not a rule. What has to be true is that each checkpoint sits far enough apart to produce evidence the previous one could not. Take your own median cycle length, add the time it realistically takes to build a first pipeline, and place the outcome checkpoint after that point rather than at day 90 because the template said so.
- Cycle under one month: the day 90 checkpoint can reasonably include closed business.
- Cycle of one to three months: day 90 measures qualified pipeline created and stage accuracy.
- Cycle of six months or more: day 90 measures stakeholder coverage and written business cases; revenue is not yet evidence of anything.
- Write the chosen checkpoint dates into the offer conversation, so the hire and the manager are measuring the same thing.
What not to measure in the first 90 days
| Tempting measure | Why it misleads | Use instead |
|---|---|---|
| Closed revenue in month one | Reflects inherited pipeline and cycle length, not the hire | Whether they can explain the customer's problem unprompted |
| Call and email volume | Rewards activity that nobody listens back to | Quality of the last five conversations, reviewed together |
| Pipeline value | Inflated by optimistic stages and old opportunities | Self-created pipeline, with stage definitions applied strictly |
| Peer comparison against a tenured seller | Compares different territories, accounts and support | Progress against the written definition of good for each checkpoint |
Role-specific versions of this plan
This page is the framework. Where the seat is known, the role-specific plans below carry full phase-by-phase objectives, manager actions, checklists and KPI sequencing rather than a summary table.
Common questions
- Should ramp be different for enterprise roles?
- Yes. Where the cycle is six months or more, the 90-day measure is pipeline created and stakeholder coverage, not closed revenue. Set the checkpoints against your own cycle length.
- Does a 30/60/90 plan belong in the interview process?
- For leadership hires, yes — ask for their own version. For individual contributors, provide yours instead; asking candidates to write one for a business they do not know tests imagination more than ability.
- Do you publish average ramp times for sales hires?
- No. Ramp depends on cycle length, deal complexity and how much enablement exists, and an average across those would not describe your business. This page shows how to set checkpoints from your own cycle instead.
- Who writes the plan — the manager or the new hire?
- The manager writes the first version before the start date, and the hire annotates it in week one. A plan the hire has never seen is a review document, not an onboarding plan.
Sources and review
- Written by
- Adroit Staffing
- Reviewed by
- Adroit Staffing editorial review
- First published
- Last reviewed
This page is practice guidance from our own Sales and GTM recruitment work. It makes no claims about current market data, so it cites no external figures.