New Sales Manager's First 90 Days Framework
What to observe, fix, and build in the first 90 days of a sales leadership role, in that order — with day-by-day actions, deliverables, and the common mistake at each phase.
What's inside
- Phase 1 (Days 1-30) Observe: full checklist including 1:1s, call reviews, pipeline data pull, process mapping
- Phase 2 (Days 31-60) Fix: highest-leverage, time-sensitive fixes and first pipeline review cadence
- Phase 3 (Days 61-90) Build: skill-development plans, coaching cadence, forecasting standard
- A 'Do' and 'Don't' list for each phase
- Deliverable checkpoint at the end of every phase
- One-page summary table
- Common mistake called out per phase
Most first-time sales managers try to fix things in week one. That's backwards — you don't have the information yet, and premature changes cost you credibility with a team still deciding whether to trust you. This framework sequences the work in the order that actually works: Observe, then Fix, then Build.
Phase 1 — Days 1–30: OBSERVE
Goal: understand the team, the numbers, and the gaps before you touch anything.
Do:
- 1:1 with every rep in week one — ask, don't tell: "What's working? What's getting in your way? What would you change if you were me?"
- Sit in on (or listen to recordings of) at least 3 calls per rep — discovery, demo, and negotiation/close if possible
- Pull 12 months of individual and team pipeline/win-rate/ramp-time data — look at raw numbers, not the dashboard summary
- Shadow one full deal cycle with one rep, start to finish, to map the process as it's actually run
- Meet every cross-functional partner your team depends on: marketing, product, CS, finance/RevOps
- Review 4 quarters of forecast-vs-actual to gauge forecasting discipline and sandbagging/overcommitting patterns
- Read every enablement asset the team is supposed to use, and ask 3 reps if they actually use it
- Identify informal leaders — the people the team already listens to
Don't:
- Don't change comp plans, territories, or process yet — you don't have enough data, and rushed changes here are the #1 credibility killer for new managers.
- Don't publicly critique the previous manager's decisions, even if invited to.
Deliverable at day 30: a written diagnosis — 1 page per rep (strengths, specific skill gaps, retention risk) and 1 page on team/process (what's broken, what's working, what's unclear).
Common mistake: mistaking "talks a lot in meetings" for "strongest performer." Score against data, not visibility.
Phase 2 — Days 31–60: FIX
Goal: resolve the highest-leverage, time-sensitive problems from Phase 1 — the things actively costing revenue or people right now.
Do:
- Address any retention-risk conversations you identified — don't let a flight-risk top performer wonder for 60 days whether you've noticed them
- Fix the top 1–2 process breakages costing deals today (e.g., broken lead routing, stale pricing on a battlecard, a forecasting habit hiding risk)
- Run your first real pipeline review in your own format — establish the standard of evidence (next steps, timeline, why-now, economic buyer engaged)
- Start weekly 1:1s on a fixed structure: pipeline + 1 skill focus + 1 blocker, every time
- Give every rep specific, individual feedback from your Phase 1 call reviews
- Resolve any cross-functional friction you found (lead quality, handoff SLAs)
- Kill or fix any enablement content reps told you they don't trust or use
Don't:
- Don't try to fix everything at once — pick 2–3 highest-leverage fixes and execute them visibly and well.
- Don't skip hard 1:1 conversations in favor of only doing the easy process fixes.
Deliverable at day 60: 2–3 fixes are live and visible; a documented weekly cadence (pipeline review, 1:1s) is running without you chasing it.
Common mistake: fixing process before fixing trust — fast process changes rolled out to a team that doesn't trust you yet get quiet non-compliance.
Phase 3 — Days 61–90: BUILD
Goal: put a durable system in place — the thing that keeps working after your "new manager" grace period ends.
Do:
- Build a skill-development plan per rep, tied to the specific gaps from Phase 1 — not a generic training calendar
- Establish your call-review/coaching cadence (e.g., 2 recorded calls per rep/month, feedback tied to a named skill)
- Set your forecasting standard and enforce it consistently — same evidence bar for every deal, every rep, every week
- Publish or refresh the playbooks/battlecards Phase 1/2 revealed were missing or stale
- Define what "ramped and independent" looks like for a new hire, and check it against actual onboarding content (see the New-Hire Ramp Content Checklist)
- Set your own next-90-day goals with your manager
- Run a team retro: what's changed, what the team wants next
Don't:
- Don't build a system so rigid it can't flex per rep — the cadence is fixed, the content of each session isn't.
- Don't stop the call-listening and data-digging habit that got you good information in Phase 1.
Deliverable at day 90: a written, repeatable operating cadence the team can describe back to you accurately, plus a documented skill-development plan per rep.
Common mistake: treating day 90 as "done" rather than as the point where Observe restarts at a deeper level.
One-Page Summary
| Phase | Days | Core Question | You Should NOT |
|---|---|---|---|
| Observe | 1–30 | "What's actually happening here?" | Change comp, territory, or process |
| Fix | 31–60 | "What's costing us the most, right now?" | Try to fix everything at once |
| Build | 61–90 | "What keeps working after day 90?" | Stop listening to calls and digging into data |
How to use it
Work through the phases in order on your actual calendar — block the Day 1-30 checklist items in your first two weeks before scheduling any changes, and use the day-30/60/90 deliverables as your own check-in agenda with your manager.