--- name: planning-cro-first-90-days description: >- Structures a new revenue leader's first 90 days: a 30-day diagnostic and revenue baseline, 60-day funnel and forecast audits with narrow quick wins, and a 90-day installed operating cadence with dashboards and decision rules. Use when the user says "30-60-90 plan", "first 90 days", "new CRO", "new VP of sales", "just took over revenue", "onboarding plan for a revenue leader", "listening tour", "what should I fix first", "GTM diagnostic", "interviewing for a CRO role and need a plan", or asks what a new revenue leader should change and in what order. Use it whenever the task is sequencing a revenue leader's early diagnostic and change agenda, even if the user does not say "90 days". Do NOT use for running an established weekly forecast call (see running-forecast-calls), building the board revenue package (see building-board-revenue-reporting), or designing quotas and commission plans (see designing-sales-compensation). metadata: version: "1.0" --- # Planning CRO first 90 days Sequence one revenue leader's first 90 days: what to inspect, what to change, what to defer, and which operating cadence to install by day 90. Executing the resulting roadmap, and the detailed comp or board-reporting work it triggers, are out of scope. Note on sourcing: the 30-60-90 structure and the meeting cadence below come from vendor practitioner frameworks rather than primary research; the segment and attainment figures are labeled with their sources and several are self-published without external validation. ## Ordering rule that governs the whole plan Inspect before changing coverage, comp, or process, and listen longer than you talk in the first 30 days ([Weflow](https://www.weflow.ai/blog/cro-30-60-90-day-plan-framework)). A change made before the diagnostic lands cannot be attributed, and an unattributable change costs the credibility needed for the changes that matter in days 60–90. ## Workflow Copy this checklist into your reply and tick items as you complete them: ``` - [ ] 1. Days 1-14: stakeholder interviews, document review, call shadowing - [ ] 2. Days 15-30: quantitative baseline and forecast-accuracy audit - [ ] 3. Day 30: agree top 3 revenue priorities with the CEO - [ ] 4. Days 31-45: win/loss, ramp, enablement, comp alignment reviews - [ ] 5. Days 46-60: half-day GTM alignment workshop; draft 12-month roadmap - [ ] 6. Days 61-75: narrow quick wins with measured behavior change - [ ] 7. Days 76-90: install the cadence, dashboards, and decision rules - [ ] 8. Validate the plan against the gate; fix and re-run before presenting ``` **1. Days 1–14 — listen and read.** Run 1:1s with the CEO, VP Sales, VP Marketing, Head of CS, CFO, and Head of Product. Two questions are scripted; ask them verbatim because the wording forces a specific answer rather than a status update ([Weflow](https://www.weflow.ai/blog/cro-30-60-90-day-plan-framework)): - To the VP Sales: "Where does forecast confidence break down today?" - To the VP Marketing: "Which segments convert best after handoff, and where do leads stall?" Read the latest board deck, the annual operating plan, the investor memo, and the current forecast model. Shadow 3 AE discovery calls, 2 demos, and 2 CSM QBRs. Map the org chart, open roles, span of control, and where decisions stall. **2. Days 15–30 — build the baseline.** Pull ARR, NRR, GRR, churn, win rate, and coverage by segment, then run a funnel performance analysis, a lead-flow and qualification review, a coverage and pipeline-health review, and a CRM hygiene assessment ([Weflow](https://www.weflow.ai/blog/cro-30-60-90-day-plan-framework)). Run a forecast-accuracy audit comparing the last three quarters of forecast versus actual by rep, by manager, and by team; the by-manager cut is the one that identifies whether the problem is a modeling issue or an inspection issue. Benchmark the baseline rather than describing it. Private B2B SaaS median NRR is 101% and median GRR 91%, with 90% GRR stated as the floor for parity with peers, and retention benchmarks by ACV band rather than company age ([SaaS Capital](https://www.saas-capital.com/wp-content/uploads/2025/09/RB32WS1-2025-B2B-SaaS-Retention-Benchmarks.pdf)). CAC payback targets by segment focus: under 12 months SMB, under 18 mid-market, under 24 enterprise ([Bessemer](https://www.bvp.com/atlas/scaling-to-100-million)). Coverage requirement is 1 ÷ win rate, so a 20% win rate needs 5×, not 3× ([Clari](https://www.clari.com/blog/pipeline-coverage-best-practices/)). **3. Day 30 — deliverables and alignment.** Ship a current-state GTM summary, a stakeholder map, the revenue baseline (ARR, NRR, GRR, churn, win rate, forecast error rate, coverage), a listening-tour synthesis presenting the top 5 patterns, and the top 3 revenue priorities agreed with the CEO ([Weflow](https://www.weflow.ai/blog/cro-30-60-90-day-plan-framework)). Cap the priorities at three: the day-60 and day-90 work only lands if the change agenda is small enough for frontline managers to restate. **4. Days 31–45 — diagnose specifics.** Compare 5 closed-won against 5 closed-lost deals, evaluate ramp versus attainment for the last 5 AEs hired, assess enablement adoption, map the customer lifecycle, and review comp alignment ([Weflow](https://www.weflow.ai/blog/cro-30-60-90-day-plan-framework)). Focus is narrow by design in this window: conversion, inspection quality, and forecast quality. Interpret ramp against a realistic curve — roughly 15–25% of quota in months 1–2, 40–55% in months 3–4, 70–85% in months 5–6, and full productivity at month 7, integrating to about 50% average productivity across a 6-month ramp, with enterprise ramp running 9–12 months ([RevenueLab](https://www.revenuelab.fyi/blog/sales-capacity-planning), self-published figures with no external citation). **5. Days 46–60 — align, then draft.** Run a half-day GTM alignment workshop with Sales, Marketing, CS, RevOps, and Finance covering funnel data, handoffs, and segment performance, and leave with agreed segment priorities, messaging, and operating rules ([Weflow](https://www.weflow.ai/blog/cro-30-60-90-day-plan-framework)). Settle disagreements with evidence — conversion by segment, acceptance rates, source quality, cycle length — rather than by seniority. Update the ICP and messaging, validate SMB / mid-market / enterprise segmentation, and communicate the listening-tour findings as pattern recognition rather than verdicts on individuals. Day-60 deliverables: funnel diagnostics report covering stage conversion, bottlenecks, slip patterns, and segment differences; forecast model audit; tech and data stack assessment; performance gap analysis across people, process, and tools; and a 12-month revenue roadmap kept explicitly in draft, with input from Product, Finance, and the leaders who will run it ([Weflow](https://www.weflow.ai/blog/cro-30-60-90-day-plan-framework)). Keep it in draft: a roadmap published before the people who must execute it have edited it converts them from owners into audience. **6. Days 61–75 — quick wins that can be measured.** Identify 10 late-stage at-risk deals, assign executive sponsors, and run targeted outreach with named next-step owners. Pilot a pricing or packaging change. Improve demo and sales content. Run a 30-minute objection-handling micro-training for mid-performers, then inspect behavior change in live deals ([Weflow](https://www.weflow.ai/blog/cro-30-60-90-day-plan-framework)). The inspection is the point: training without live-deal verification produces no measurable change and burns the quick-win window. This step is high-freedom on which wins to pick and low-freedom on the selection criteria. Pick only wins that meet all four: visible inside 30 days, attributable to a specific action, reversible if wrong, and owned by someone other than you. **7. Days 76–90 — install the operating system.** Finalize the cadence, launch live CRO dashboards, document the operating model, present the 90-day impact, and define the next 3–6 month initiatives ([Weflow](https://www.weflow.ai/blog/cro-30-60-90-day-plan-framework)). Install this cadence, assembled from the same sources: | Cadence | Meeting | Owner | Content | |---|---|---|---| | Weekly | Rep-to-manager 1:1, 30–45 min | Frontline manager | 3–5 deals at 10–15 min each ([Rework](https://resources.rework.com/libraries/pipeline-management/pipeline-reviews)) | | Weekly | Forecast call, 60 min | CRO | Number / top-10 deals / patterns / decisions / actions ([Signals](https://www.signals.ceo/resources/cro-weekly-forecast-call)) | | Weekly | Early-warning dashboard review | RevOps + CRO | Reviewed weekly, not only before board meetings ([Weflow](https://www.weflow.ai/blog/revops-board-reporting-framework-best-practices)) | | Bi-weekly | Team pipeline review, 60–90 min | Manager | 2–3 deals from different reps, patterns, shared resources ([Rework](https://resources.rework.com/libraries/pipeline-management/pipeline-reviews)) | | Bi-weekly | GTM sync | CRO + heads of Sales/Marketing/CS/RevOps/Finance | Pipeline creation, conversion, handoff quality, forecast changes, churn risk, decisions needed before the next cycle — not a departmental status meeting ([Weflow](https://www.weflow.ai/blog/cro-30-60-90-day-plan-framework)) | | Monthly | Forecast review, 90–120 min | Managers + senior leadership | Commit versus progression, slippage, coverage, risk on major opportunities ([Rework](https://resources.rework.com/libraries/pipeline-management/pipeline-reviews)) | | Quarterly | Pipeline planning, half-day | Sales leadership + RevOps | Pipeline health, capacity planning, process improvement ([Rework](https://resources.rework.com/libraries/pipeline-management/pipeline-reviews)) | | Quarterly | Modeled versus actual ramp reconciliation | RevOps | Quantify the revenue effect of the gap ([Weflow](https://www.weflow.ai/blog/revops-board-reporting-framework-best-practices)) | | Board cycle | Board pack and narrative | CRO + RevOps | Context / Risks / Asks across 5–7 metrics on a five-quarter view ([Weflow](https://www.weflow.ai/blog/revops-board-reporting-framework-best-practices)) | Day-90 deliverables: the finalized GTM operating cadence with meeting structure, dashboard ownership, KPIs, and decision rules; live dashboards showing pipeline, NRR, churn, bookings, and forecast quality; a 90-day impact summary; updated GTM strategy communication; a 3–6 month roadmap aligned with the CEO; and a buy-in communication stating what is changing, why, how success is measured, and who owns each part ([Weflow](https://www.weflow.ai/blog/cro-30-60-90-day-plan-framework)). **8. Validate the plan, then loop.** Run this gate before presenting the plan to the CEO or the board, fix every failure, and re-run: ``` - Every day-30 baseline metric has a named source system and a named owner - Forecast-accuracy audit covers 3 quarters and is cut by rep, manager, and team - Exactly 3 top priorities, each with a measurable target and a named owner - No coverage, comp, or process change is scheduled before day 31 - Every quick win is visible in 30 days, attributable, reversible, and owned by someone else - The 12-month roadmap is marked draft until leaders who will run it have edited it - Every installed meeting has an owner, a duration, and a locked agenda - CRO/CFO assumption set for the forecast is written down and agreed ``` Only present when the gate passes, because a plan that survives its own audit is the first evidence the new operating model works. ## Boundary with the CFO The CRO owns the operating forecast and the actions behind it; the CFO owns financial rigor, scenario planning, and how numbers flow into board reporting, cash planning, and company targets. If the two run different assumptions, forecast meetings degrade into reconciliation exercises ([Weflow](https://www.weflow.ai/blog/cro-30-60-90-day-plan-framework)). Settle the shared assumption set in the first 30 days, while it is still a question rather than a dispute. ## Output format Emit this exact structure; keep the phase headings stable so progress can be tracked against it week by week. Content within phases is yours to adapt. ``` ## Revenue leadership plan — — days 1-90 **Mandate** Top 3 priorities agreed with CEO: 1) 2) ... 3) ... **Days 1-30 — diagnose** Interviews: | Calls shadowed: | Documents reviewed: Baseline: ARR $X | NRR N% | GRR N% | churn N% | win rate N% | coverage N.Nx | forecast error N% Top 5 patterns: **Days 31-60 — analyze and align** Win/loss findings | ramp vs attainment (last 5 hires) | forecast model audit | stack assessment GTM workshop outcomes: segment priorities, messaging, operating rules 12-month roadmap: DRAFT — reviewers: **Days 61-90 — install** Quick wins: Cadence installed: Dashboards live: Decision rules: **Deferred with reason** - — deferred to — because ``` ## Gotchas - Do not diagnose a capacity problem as a headcount problem. If attainment is below 50% while pipeline coverage is above 4×, the constraint is conversion — onboarding gaps, ICP drift, discovery quality, product-market-fit slippage — and hiring more reps will not help ([RevenueLab](https://www.revenuelab.fyi/blog/sales-capacity-planning)). This is the single most common day-45 misread, because the hiring fix is easier to approve than the conversion fix. - The hiring calendar back-solves further than most plans assume: requisition open month equals the month capacity is needed minus ramp length minus 6–10 weeks of recruiting. A hire needed to contribute in Q3 with a 6-month ramp must start in Q1, meaning the requisition opens in Q4 of the prior year, and hiring 12 reps in the second half yields perhaps 30% of their annual quota in that year ([RevenueLab](https://www.revenuelab.fyi/blog/sales-capacity-planning)). Any first-90-days plan that promises H1 relief from hires not yet requisitioned is already wrong. - Model required headcount as target ÷ (quota × expected attainment), not target ÷ quota. On a $10M target with $1M quotas and 70% expected attainment, the first formula requires 14.3 productive-rep-equivalents against 8 today and yields about 15 hires including attrition backfill; the naive formula says 2 ([RevenueLab](https://www.revenuelab.fyi/blog/sales-capacity-planning)). Use the trailing four-quarter median attainment as the input, and note SaaS sales attrition runs 25–35% per year and 40–60% at startups. - Roughly 20% of pipeline dated to close in a quarter, measured on day one, actually closes in-quarter ([ORM-Tech](https://orm-tech.com/blog/sales-forecast-categories-explained/)). A new leader who accepts the inherited day-one pipeline as a landing range will commit to a number in week two that the data never supported. - Coverage arithmetic on inherited data is usually overstated before purging. A team reporting 4× with 30% stale pipeline actually holds 2.8× qualified coverage, and reviewing coverage in week 10 of a 13-week quarter leaves no runway to correct ([Clari](https://www.clari.com/blog/pipeline-coverage-best-practices/)). Do the purge in the first 30 days so the first quarter you own has a real starting number. - Fix the forecast's evidence base before its math. Move from rep opinion to a team roll-up supported by stage conversion, pipeline aging, and deal-inspection criteria, and inspect category usage, slip rates, close-date hygiene, manager cadence, pipeline definitions, activity completeness, roll-up logic, and CRM data quality weekly ([Weflow](https://www.weflow.ai/blog/cro-30-60-90-day-plan-framework)). Buying a forecasting tool before this holds moves the same rep opinion into a nicer interface. - Segment operating shapes constrain what you can change quickly: enterprise typically runs $100K+ ACV with 6+ month cycles, and mid-market $25K–$100K with 2–4 month cycles, with standardized offers recommended below $100K ACV and under four-month cycles ([Weflow](https://www.weflow.ai/blog/cro-30-60-90-day-plan-framework), stated without an external source). In a 6+ month enterprise cycle, no change made in days 61–90 will show in closed revenue inside the first 90 days — commit to leading indicators instead.