30-60-90 day plan for sales reps

A 30-60-90 day plan for a sales rep should answer one question at each phase: is this person ready to carry more quota. That means the plan needs a ramp quota schedule, a pipeline coverage number, and a call cadence with the manager — not generic goals like "learn the product" that nobody can fail.

Below is a plan built around those three things, a filled example with invented numbers, and what the manager owes the rep at each phase so the ramp is fair. For the general version of this template across roles, see the new hire 30-60-90 day plan template.

Why a sales 30-60-90 plan needs a ramp quota, not just tasks

A task list ("shadow calls, learn the CRM, meet the team") tells you nothing about whether a rep is on track to hit quota once they are fully ramped. The plan below pairs every phase with a number the rep and manager can both check in the CRM: qualified conversations booked, pipeline generated, and percentage of full quota carried. Tasks still matter, but they exist to produce those numbers, not instead of them.

The 30-60-90 day plan

Copy this into your onboarding doc and fill in the brackets with your product, territory and quota numbers.

30-60-90 day plan — [Rep name], [territory or segment]
Manager: [name]        Start date: [date]        Full quota: [$/units per quarter]
Ramp schedule: 25% of quota by day 60, 75% by day 90, 100% by day 120

DAYS 1-30 — Learn the product, the market and the CRM
Owns:
- Complete product and objection-handling certification (target: day 20)
- Shadow 10 discovery calls and 5 demos with [names], with notes in [CRM]
- Log every account touch in [CRM] the same day it happens
- Build and QA a target account list of [N] accounts against the ICP
Produces by day 30:
- A one-page territory plan: top 20 accounts, why each fits, first outreach angle
- [N] qualified conversations booked for weeks 5-6 (not closed, just booked)
Manager owes:
- A named account list or warm territory, not "figure it out yourself"
- Two shadowed calls a week with feedback the same day
- Access to the last 4 quarters of win/loss notes and current battlecards

DAYS 31-60 — Run the motion solo, under review
Owns:
- Run discovery and demo calls solo; manager joins 1 in 5 to calibrate, not to take over
- Build pipeline to [N] x ramp quota in qualified opportunities
- Deliver first proposal or demo scorecard to a prospect
- Carry 25% of full quota
Produces by day 60:
- A forecast the rep can defend deal by deal, not a gut-feel number
- At least one deal in a late stage (proposal or negotiation)
Manager owes:
- A weekly 30-minute pipeline review, same day and time every week
- Real-time deal coaching on the calls the manager joins, not a delayed writeup
- Clear escalation path for pricing exceptions and legal redlines

DAYS 61-90 — Carry ramp quota and defend the forecast
Owns:
- Carry 75% of full quota with pipeline coverage of at least 3x that number
- Close or advance to signature at least [N] deals
- Present the 90-day forecast in the team pipeline meeting
Produces by day 90:
- A closed-won deal or a deal in final signature, whichever the sales cycle allows
- A written self-assessment against this plan for the 90-day review
Manager owes:
- The 90-day review meeting, calendar-blocked from day one
- A decision on ramp quota vs. full quota for day 91 onward, communicated in writing

Review cadence: weekly pipeline review (CRM stage report, not a subjective check-in),
formal sit-downs at day 30, 60 and 90.

A filled example: an invented mid-market account executive

What counts as "on track" between the milestones

A rep who is behind on closed revenue at day 60 is not automatically off track if their leading indicators are healthy: call volume at target, discovery-to-demo conversion in line with the team average, and pipeline coverage where it should be. Sales cycles are long enough that closed revenue lags the work that produces it. Watch the leading indicators weekly and treat a slip in closed revenue alone, with everything else healthy, as normal variance rather than a red flag.

The opposite is the real warning sign: a rep who is hitting a revenue number early because one large inbound deal landed in their lap, while call volume and self-sourced pipeline are both low. That rep looks ahead of plan and is actually behind it, because nothing underneath the number will repeat next quarter.

What the manager owes, and why each item is on the list

Running the 30, 60 and 90-day check-ins

Each check-in should take the numbers from the CRM into the room, not replace them with an impression. Pull the pipeline report before the meeting: qualified opportunities, stage distribution, and call activity for the period. Ask the rep to walk through their own forecast deal by deal before the manager gives an opinion; a rep who cannot explain why a deal is at 60 percent probability does not yet own that deal, whatever the CRM says.

Close every check-in with one specific commitment for the next phase: not "keep doing what you're doing" but a number and a date, written down in the same document as the plan so the 90-day review is checking commitments the rep already agreed to.

Adjusting the plan by sales motion

• Inside sales, short cycle (days to weeks): compress the ramp schedule; a rep should have closed-won revenue by day 60, and a day 90 without any closed deals is a real concern.
• Field or enterprise sales, long cycle (quarters): shift the ramp quota later and weight day 90 toward pipeline quality and stakeholder mapping over closed revenue, since the cycle itself may not have completed.
• Channel or partner sales: replace "target account list" with a named partner list and a partner-enablement milestone; the day 30 to 60 goal is partner-sourced pipeline, not direct outbound.
• Rep promoted internally into sales: shorten the product certification if they already know it, but keep the shadowing and pipeline-building phases in full; product knowledge is not the same skill as running a sales process.

Common mistakes that break the ramp

The most common failure is skipping the shadowing phase because the team is short-staffed and needs the rep selling immediately. The rep then builds habits by trial and error on real prospects, and the accounts burned in month one are gone for good. A close second is a ramp quota that was never written down, so the rep and manager disagree at day 90 about what "on track" was supposed to mean. Put the schedule in the plan on day one, in numbers, and treat any change to it as a conversation, not a surprise at the review.

A third mistake is measuring only the outcome (closed revenue) and never the behaviors that produce it. A rep can do everything right in the first 90 days — call volume, discovery quality, a clean pipeline — and still show zero closed revenue because the sales cycle has not completed yet. If the plan only tracks the final number, that rep looks like a problem when they are not one. Track both: the activity and pipeline numbers weekly, the revenue number as a lagging check.

A fourth is treating the day-90 review as a pass or fail gate with no middle option. Most new reps land somewhere between "clearly ramped" and "clearly not working out," and the plan should have room for a fourth phase — days 91 to 120 — with a narrower set of goals rather than forcing a final verdict before the sales cycle has had time to run its full length.

Where this plan intersects with the interview process

A ramp plan is only as good as the fit it is built on. If the pipeline coverage and call-volume numbers above look unreachable for a specific rep at day 60, it is worth going back to the interview scorecard and checking whether the interview actually tested for cold outreach and discovery skills, or only for polish on a rehearsed pitch. Hiring managers who keep the interview evidence — not just a final score — find it easier to tell a slow ramp from a bad fit, because they can compare what the rep is doing now against what was said and demonstrated in the loop. Interview Signal keeps that evidence as quotes tied to each scorecard score, which is useful months later when a ramp conversation needs more than a memory of how the interview felt.