Introduction
Most 30/60/90 plans are written to be handed over rather than used. They list activities — complete the product training, shadow five calls, read the competitive deck — and every one of them can be completed by a rep who will not survive the year. Attendance is not a proxy for capability.
A plan worth writing does two things the template version does not: it states outcomes you can verify rather than activities you can tick, and it says what the manager owes the rep at each stage. This article gives that plan, plus the harder part nobody puts in the document — the signals visible at day 30 that predict a rep who will not make it, and what to do about them while it is still cheap.
Why Most 30/60/90 Plans Fail
Two failures, and they compound.
The first is that activities are easy to write and easy to complete, so that is what plans contain. “Shadow five discovery calls” is unambiguous and unfalsifiable as a measure of readiness. A rep can shadow five calls and learn nothing; another can shadow two and be ready. The plan measures the wrong thing because the wrong thing is easier to measure.
The second is that the plan is one-directional. It lists what the rep must do, and says nothing about what the organisation must provide. Then at day 45 the rep is behind, and half the reason is that nobody gave them territory, or accounts, or answers to their questions within a useful timeframe. A one-directional plan makes the rep solely responsible for an outcome they only partly control.
Fix both and the document changes character: it becomes a contract between two people rather than a checklist handed to one of them.
Days 1 to 30: Can They Explain It and Ask About It
The goal for the first month is not selling. It is comprehension deep enough to hold a real conversation.
Outcomes to verify by day 30:
- Can explain the product to a peer, unprompted, in five minutes, including what it does not do. The “does not do” part is the tell — a rep who can only recite the good parts has memorised a deck rather than understood a product.
- Can run a discovery call to a script with a real prospect or a realistic role-play, without freezing on the second follow-up question.
- Can articulate the customer’s problem in the customer’s words, not in product language. If the rep describes the problem as “they don’t have our workflow feature,” they are not there yet.
- Knows how the CRM works for the parts they will use daily, and has logged their own first activities correctly.
What the manager owes by day 30: a clear definition of the target customer, access to everything on day one rather than week three, three recorded calls that are actually good rather than three that were convenient to find, and a scheduled weekly one-on-one that does not get moved. That last one carries more weight than it looks: a new rep reads a rescheduled one-on-one as a statement about their importance.
Days 31 to 60: Working Deals With Support
The second month is where capability becomes visible, because the rep is now doing the job rather than preparing for it.
Outcomes to verify by day 60:
- Owns a small pipeline — a handful of real opportunities, sourced or assigned, that they are responsible for.
- Runs discovery unaided and comes out with the information needed to qualify, not just a friendly conversation.
- Has taken a first deal to proposal, with the manager present but not leading.
- Qualifies out at least one deal for a defensible reason. A rep who has qualified nothing out in a month is either lucky or unwilling to say no, and the second is much more common.
- Keeps their own pipeline current without being chased — next steps on open deals, stages that match reality.
What the manager owes by day 60: joining calls as a second pair of ears rather than as the person who takes over, feedback within a day rather than at the next one-on-one, and honesty about what is going badly. The temptation in month two is to be encouraging and defer the hard feedback. That is a kindness that costs the rep a month.
Days 61 to 90: Owning the Number
The third month is about independence and forecasting, not just activity.
Outcomes to verify by day 90:
- Forecasts their own deals with reasons, and the forecast is roughly right. Accuracy matters less than whether they can explain the basis.
- Carries a defined share of quota — usually a partial ramp rather than the full number, agreed in advance and in writing.
- Handles a stalled deal without escalating immediately, having tried a diagnosis first.
- Has closed something, or has a clear, evidence-backed reason why not that does not depend on luck.
What the manager owes by day 90: a written statement of what the ramp looks like for months four to six, so the rep knows what they are being measured against, and an honest assessment of trajectory. If it is going badly, day 90 is the last cheap moment to say so.
The Day-30 Signals Worth Acting On
This is the section most onboarding plans leave out, and it is the one that saves the most time and money.
By day 30 several things are visible, and they predict outcomes better than anything on the activity checklist:
- Question quality. A rep who asks specific, sharp questions — about why a deal was lost, about how a customer decided — is processing. A rep who asks only logistical questions, or none at all, usually is not. This is the single most reliable early signal.
- Response to correction. Give one piece of direct, uncomfortable feedback in week three and watch what happens. Adjustment within a week is a good sign. Defensiveness, or agreement followed by no change, is the pattern that repeats for the next six months.
- Curiosity about the customer versus the product. Reps who ask about how customers work tend to run better discovery than reps who ask about feature roadmaps.
- Whether they have found their own first opportunity. Not required, but the reps who do this in month one are usually the ones who ramp fastest.
What to do about a bad signal: name it in the one-on-one, specifically and without drama, and agree one concrete change with a date. Then check it. The mistake managers make is waiting — hoping month two resolves it, then month three, until the conversation has to happen at month five when it is expensive for everyone and the rep can rightly say nobody told them.
Saying it at day 30 is the kinder version, even though it feels harsher.
Worked Example: One New Hire Through Ninety Days
An illustrative example. A rep joins a team selling to mid-market operations leaders.
Day 12. First check: asked to explain the product to a colleague from another team. Gets the value proposition across but cannot answer “when is this a bad fit?” — the manager gives three concrete cases and asks them to explain those back next week. They do, unprompted, on day 16.
Day 24. Feedback in the one-on-one: their discovery calls are collecting facts but not finding the problem behind them. The specific correction is to ask “what happens if this stays as it is?” on every call. Two weeks later, that question is in every recording — the response-to-correction signal is good.
Day 38. Owns four opportunities. Qualifies one out because the buyer has no timeline and no budget owner — a defensible decision, and a good sign in month two.
Day 55. First proposal, with the manager on the call as backup. The rep leads, mishandles a pricing objection, and recovers when the manager stays quiet. Debriefed the same afternoon rather than at the next one-on-one.
Day 82. Forecasts three deals: one commit, two best case. Two land as forecast; the commit slips a fortnight for a reason the rep had already flagged. That is a working forecast — the number was slightly wrong, the reasoning was right.
Day 90. Ramp agreed for months four to six in writing. The whole trajectory was set by two conversations, on day 12 and day 24, neither of which appears on any standard onboarding checklist.
FAQ
What should a new sales rep achieve in the first 30 days?
Explain the product to a peer including its limitations, run a discovery call to a script, describe the customer’s problem in the customer’s own words, and use the CRM correctly for their daily work. Comprehension, not sales.
When should a new rep carry quota?
Typically a partial share from month three, with a written ramp for months four to six. What matters most is that the expectation is agreed and documented in advance rather than assumed.
How do I know at 30 days whether a hire will work out?
Watch the quality of their questions and their response to a piece of direct correction. Both are visible by week four and predict the following six months better than any activity metric.
Should the 30/60/90 plan be written by the manager or the rep?
The manager writes the first version; the rep rewrites it in their own words in week one. The rewrite is a comprehension check and it makes the plan theirs.
What if the rep is behind at day 60?
Diagnose which of the three causes it is — not enough activity, activity that is not converting, or a territory problem — before deciding on a response. Each needs a different intervention, and the generic answer of “do more” only works for the first.
Conclusion
A 30/60/90 plan earns its place when it states outcomes somebody can verify and commitments the manager has to keep. Month one is comprehension: can they explain it, including what it is not for. Month two is supported execution: a real pipeline, unaided discovery, a first proposal, and at least one honest qualify-out. Month three is independence: their own forecast, a defined share of quota, and a diagnosis before an escalation.
The part that decides the outcome is not in the document. It is whether you act on what you see at day 30 — specifically, question quality and response to correction — and say something while it is still a small conversation. Rewrite your current plan this week so that every line is an outcome someone could confirm or deny, and delete every line that is only an activity.
