The 90-Day Plan a New CRO Should Actually Run

A new CRO has roughly one quarter before their honeymoon ends and the board starts asking what's changing. Most 90-day plans get that window wrong. They optimize for visible action — re-orgs, new comp plans, fresh process — when the only thing that compounds in the first 90 days is diagnostic clarity. The CROs we see succeed at the 12-month mark spent their first quarter learning the business cold, naming the two or three real problems, and deferring almost every structural change to days 90-180. Here's what that sequence actually looks like.

Days 1-30: Read the business, don't change it

The first 30 days are about evidence. Not opinions, not relationships, not "quick wins." A new CRO who ships a quick win in week three usually pays for it in month nine, because the win was based on the previous leader's framing of the problem. The right work in month one is unsexy: read the data, sit in the calls, talk to the customers.

• Pull four quarters of full-funnel data. Lead source to closed-won, segmented by ICP fit, deal size band and rep tenure. You're looking for the two or three segments where the unit economics actually work, and the long tail where they don't.
• Sit in 25 sales calls. A mix of discovery, demo, negotiation and closed-lost debriefs. No coaching, no intervention. You're listening for the gap between the messaging deck and what reps actually say in front of buyers.
• Interview 15 customers. Five recent wins, five long-time accounts, five recent losses or churns. Same three questions: what was the trigger, what was the alternative, what almost killed the deal.

At day 30 you should be able to write a one-page memo titled "What I think is actually true about this business." If you can't, you don't have enough evidence yet — extend the diagnostic phase another two weeks rather than guessing.

Days 30-60: Name the two or three real problems

Most underperforming GTM motions have at most three structural problems. The trap is that there are usually fifteen visible symptoms, and a new CRO can spend a year fixing symptoms without ever touching the structural problem underneath. Common patterns we see in the GTM Diagnostic data:

• ICP drift masquerading as a sales execution problem (see the real cost of an undefined ICP).
• Pipeline coverage that looks healthy but doesn't predict attainment because qualification is subjective (see the coverage ratio that predicts next quarter).
• A segment mix that's quietly shifted toward deals the product isn't built for, killing NRR 12-18 months later.
• Comp plans that reward bookings but punish the behaviour the motion actually needs (multi-year deals, expansion-ready structures, ICP-fit qualification).

Day 60 deliverable: a written diagnosis the CEO and CFO sign off on. Three problems, named specifically, with the evidence attached. This document is the contract for everything that follows.

Days 60-90: Sequence the work, don't ship it all

Days 60-90 are where most CROs over-rotate. The temptation is to launch the re-org, rewrite the comp plan, replace the weakest reps and announce a new methodology in the same week. That sequencing almost always backfires. The team interprets the volume of change as "the new CRO doesn't know what matters," and the signal-to-noise ratio collapses.

The discipline is to pick the one change with the highest leverage and the lowest organisational cost, ship it cleanly, and let the team feel the result before the next change lands. In most motions that's tightening qualification criteria, not re-orging the team. Sharper qualification compounds inside one quarter — pipeline quality improves, forecast accuracy improves, conversion rates climb — and gives you the political capital to make harder structural changes in days 90-180.

What to publicly commit to in the first board meeting

The first board meeting after day 90 sets expectations for the next four quarters. The strongest CROs commit to two things and only two: a sharpened diagnosis (the one-page memo from day 60) and a single measurable improvement target for the next 90 days, tied to one of the named problems. Everything else gets framed as "in evaluation, decision by day 120." That framing protects optionality, which is the most valuable thing a new CRO has and the easiest thing to give away.

The 90-day anti-patterns to avoid

• Replacing the VP of Sales in week six. You don't yet know whether the VP is the problem or a downstream symptom. Wait until day 90 minimum.
• Rewriting the comp plan inside the first quarter. Comp changes ripple for two quarters. Do not ship comp changes until you've finished diagnosis.
• Launching a new methodology. MEDDIC, Force Management, Command of the Message — they all work, but rolling them out before you understand the existing qualification gaps just adds vocabulary, not discipline.
• Promising a number you don't yet own. The board will push for a Q+1 commit by day 60. Resist. The right answer is "I'll commit in the day-90 review, with the diagnosis behind it."

How the right diagnosis changes the comp conversation

The single change a new CRO most often wants to ship — a new comp plan — is also the one with the highest blast radius. Comp shapes behaviour for at least two quarters after a change, which means the wrong comp plan persists long after the new CRO realises it was the wrong call. The discipline is to treat comp as the last lever, not the first. By the time you ship comp changes (usually day 120-150), you should be able to defend three things to the team: which behaviours are being incentivised, which behaviours are being de-emphasised, and what the math looks like for a representative top, median and bottom rep. If any of those three are unclear, the comp change isn't ready and the team will read the ambiguity as leadership uncertainty.

A useful test: write the one-paragraph announcement of the comp change as if you were sending it to the team tomorrow. If the paragraph contains hedges ("we're hoping this will encourage…", "we'll see how this lands…"), the change isn't finished. The strongest comp announcements name a specific behaviour change, the metric that will move, and the date by which leadership will review the result.

What the board should expect to hear at day 90

The board doesn't need a 40-page deck at day 90. They need three things: the diagnosis, the prioritised problem the new CRO is solving first, and the leading indicators that will signal whether the fix is working. Boards that get more than that at day 90 usually push back, because the volume of proposed change implies the diagnosis is still in flux. Boards that get less than that lose confidence in the new leader. The discipline is calibration: enough specificity to show the diagnosis is real, enough restraint to show the leader knows what's premature.

Where to start this week

If you're inside the first 90 days as a CRO, audit your own calendar against the sequence above. If more than 30% of your time is going to internal meetings and re-org planning before day 60, you're already off track. The first quarter is for listening, reading and writing a diagnosis the leadership team will defend. Everything structural should sit in the day-90 plan, not the day-30 plan.

The GTM Diagnostic is built to compress that day-60 diagnosis into an afternoon — eight pillars scored against the data your team already has, with a prioritized view of which two or three problems actually matter. The full methodology is open. Most new CROs who run it find their day-60 memo writes itself.