First 90 Days as CRO: A Playbook Based on What Boards Actually Expect

The first 90 days as CRO are a paradox. The board wants you to move fast. The organization wants you to listen first. The CEO wants visible wins. Your direct reports want to know if they should update their resumes. Every stakeholder has a different expectation, and you don't have time to satisfy all of them.

I've watched this play out dozens of times, from both sides. As a VP Sales reporting to a new CRO. As a revenue leader taking over an organization. And now, tracking 1,500+ executive sales postings weekly through The CRO Report, I see what companies explicitly expect from their new CROs in the job descriptions themselves.

This playbook combines what the postings say, what Spencer Stuart and other executive search firms report, and what I've observed directly. It's organized by time block: Days 1-30, Days 31-60, Days 61-90.

Days 1-30: Diagnose Before You Prescribe

The single biggest mistake new CROs make is restructuring before they understand the current system. I've seen CROs walk in on week two and announce a new comp plan. The sales team panics. The best reps start interviewing. Pipeline stalls. Three months later, the CRO is explaining to the board why bookings dropped while they were "transforming the organization."

Month one is a listening tour. It's not glamorous. It won't produce a board deck. But it's the foundation for everything that comes after.

The Revenue Audit

Before you meet anyone, spend two days with the data. Pull these numbers yourself. Don't trust the existing dashboards until you've verified the underlying math.

• Pipeline health: Total pipeline by stage, conversion rates between stages, average deal size, average cycle length. Compare current quarter to the previous four. Look for the trend, not the snapshot.
• Win/loss rates: By rep, by segment, by deal size. The aggregate win rate means nothing. The variance between your best and worst rep tells you everything.
• Churn and retention: Gross revenue retention, net revenue retention, churn by cohort, churn by customer segment. If the company hired you partly to fix retention, this is the data that tells you how bad it is.
• Unit economics: CAC, LTV, CAC payback period, magic number. If these metrics aren't tracked, that's a finding in itself.
• Forecast accuracy: Pull the last four quarters of forecasts vs. actuals. A company that consistently misses by 15-20% has a process problem. A company that misses by 40%+ has a data integrity problem.

This audit takes 3-5 days. Some CROs skip it because the data is messy or because they want to meet people first. Don't skip it. The data gives you the questions to ask in every meeting that follows.

The Stakeholder Tour

After the data audit, spend the remaining three weeks meeting people. Not group meetings. One-on-ones. Here's the priority order:

1. Your direct reports. VP Sales, VP CS, Head of RevOps, Head of Partnerships (if you own them). Ask each one: "What's working, what's broken, and what would you change if you had my job?" Write down their answers verbatim. You'll compare notes later.
2. The CEO. You had the interview conversation. Now have the real one. What does success look like in 12 months? What's the board's patience threshold? What happened to your predecessor? The answer to that last question tells you more than anything in the job description.
3. The CFO. Understand the financial model. Where does the revenue plan live? What assumptions drive it? Is the plan bottom-up (built from quota capacity) or top-down (board target divided by reps)? Top-down plans are aspirational. Bottom-up plans are operational.
4. The CMO. If marketing reports to you, this is a direct report conversation. If marketing reports to the CEO, this is a peer alignment meeting. Either way, the question is: how does pipeline get created, and who owns which parts?
5. 5-10 customers. Not the happy ones your CS team picks. A random sample. Ask them: "What's working? What isn't? Would you buy from us again?" Customer conversations in month one prevent you from building strategy on internal assumptions.

What You Deliver at Day 30

A written diagnostic. Not a strategy. Not a reorg plan. A diagnostic. Here's what's working, here's what's broken, here's what I need to investigate further. Share it with the CEO. The board doesn't need it yet. They need it at Day 90.

Days 31-60: Triage and Quick Wins

Month two is where you start making moves. Not structural moves. Tactical ones. The goal is to build credibility by fixing visible problems that the organization already knows about but hasn't prioritized.

The Triage Framework

From your Day 30 diagnostic, categorize every issue into one of three buckets:

Bucket	Definition	Action
Fix Now	Costs revenue daily, can fix in under 2 weeks	Execute immediately
Plan for Q+1	Structural issues, needs headcount or budget	Build the business case
Monitor	Might be a problem, need more data	Set a 60-day check-in

Examples of "Fix Now" items I've seen repeatedly:

• Pipeline stages that don't match the actual sales process (forecast garbage in, garbage out)
• No SLA between SDR and AE on lead follow-up time
• CS team doesn't have access to the sales CRM (so they can't see what was promised in the deal)
• Comp plan incentivizes new logos but ignores expansion (in a company where NRR is the board metric)

These are fixable in days, not months. Fixing them builds credibility with the team because they've been complaining about these issues for quarters.

Talent Assessment

By Day 45, you should have a clear view of your direct reports. The assessment isn't "who do I like." It's "who can execute the plan I'm building."

A framework that works: evaluate each leader on two axes. Skill (can they do the job at the level I need) and Will (are they motivated, aligned, and coachable). High skill / high will: keep and invest. High skill / low will: have the conversation about alignment. Low skill / high will: coach or reposition. Low skill / low will: plan the transition.

Don't fire anyone in month two unless they're actively destructive. Making a people change too early signals to the organization that you came in with a hit list. That kills trust. Making a change at Day 75-90, after you've clearly defined expectations and given people a chance to meet them, signals fairness.

Cross-Functional Alignment

If you own CS, RevOps, and partnerships in addition to sales, month two is when you start connecting these functions. The most common misalignment I see:

• Sales closes deals that CS can't implement (scope mismatch)
• Marketing generates leads that sales doesn't want (ICP mismatch)
• RevOps builds reports that nobody uses (metric mismatch)
• Partnerships brings in leads with no handoff process (process mismatch)

You won't fix all of these in month two. Pick the one that's costing the most revenue and fix it. The others go into the Q+1 plan.

Days 61-90: The Strategic Plan

Month three is about converting your diagnostic into a 12-month plan. This is the deliverable the board actually cares about.

What the Board Wants at Day 90

Based on Pavilion's CRO community data and executive search firm interviews, boards evaluate new CROs at 90 days on three dimensions:

1. Diagnostic accuracy. Does the CRO correctly identify what's working and what isn't? If the CRO's assessment matches what the board already suspects but the previous CRO wouldn't say out loud, confidence goes up.
2. Team assessment. Has the CRO evaluated talent without causing unnecessary turnover? The board doesn't want to hear "I'm firing three people." They want to hear "Here's my assessment of the team, here's my plan for the gaps, and here's the timeline."
3. A credible 12-month plan. Specific milestones. Resource requirements. Budget implications. The plan should include what you'll do, what you'll stop doing, and what you need from the board to execute.

Building the 12-Month Plan

The plan structure that works:

• Q1 (you're already here): Quick wins executed, diagnostic complete, team assessed
• Q2: Structural changes. Reorg if needed, new comp plan if needed, process changes, tool evaluation
• Q3: Execution at scale. The new processes should be producing measurable results. If you restructured the team, the new org should be ramped.
• Q4: Optimization. Doubling down on what's working, cutting what isn't, planning for next year

Each quarter should have 2-3 measurable milestones. Not "improve pipeline quality" but "increase Stage 2 to Close conversion rate from 18% to 25%." Not "align with marketing" but "implement joint pipeline review with marketing by end of Q2, targeting 40% of pipeline from marketing-sourced leads by Q4."

The Budget Conversation

Most CROs underestimate how important the Day 90 budget conversation is. The board approved a comp package in the range of $231K-$302K base to hire you. They're now asking what else you need.

Be direct about resource requirements. If you need three more AEs and a RevOps manager to hit the plan, say so at Day 90, not Day 180. Late budget requests signal poor planning. Early requests signal confidence and clarity.

The Traps to Avoid

Trap 1: The "New Sheriff" Problem

Some CROs arrive wanting to put their stamp on everything. New CRM, new methodology, new comp plan, new vendors, new process. The organization spends six months in transition instead of selling. Revenue stalls. The CRO blames the team. The team blames the CRO. Everyone loses.

Change what needs changing. Keep what works. The best CROs I've worked with changed 30% of what they inherited and kept 70%. The worst changed 80% and kept 20%.

Trap 2: Ignoring the Predecessor

Your predecessor left for a reason. Maybe they were fired. Maybe they quit. Maybe the role was newly created. Regardless, understanding what happened before you arrived prevents you from repeating the same mistakes.

If the previous CRO was fired for missing the number, find out why the number was missed. Was the plan unrealistic? Was the team wrong? Was the product broken? If it was the plan, make sure your plan is grounded in reality. If it was the team, your talent assessment is urgent. If it was the product, that's a conversation with the CEO before Day 30.

The CRO failure rate data shows that most CROs who fail within 18 months cite misalignment with the CEO on expectations as the primary cause. That misalignment usually starts in the first 30 days and compounds.

Trap 3: Choosing Loyalty Over Competence

Do not bring your former team with you in the first 90 days. I've seen CROs hire their former VP Sales, their former head of CS, and their former RevOps lead within the first two months. It sends a clear signal to the existing team: you're not being evaluated on merit, you're being replaced by the new boss's network.

If you genuinely need to bring in outside talent, do it after Day 90 and only for roles where you've given the incumbent a fair chance to perform at the level you need.

Trap 4: Board Deck Over Operations

Some CROs spend the first 90 days building a beautiful board presentation while the pipeline deteriorates. The board deck matters. But if bookings drop 20% in your first quarter because you were too busy strategizing to notice that three AEs have gone dark, the board deck won't save you.

Block two hours every day for operations: deal reviews, pipeline checks, customer escalations. The strategic work happens in the remaining time. Not the other way around.

The 90-Day Checklist

Here's a concrete checklist. Every item should be complete or in progress by Day 90.

Day	Milestone	Deliverable
1-5	Revenue data audit	Internal assessment document
6-20	Stakeholder 1:1s complete	Meeting notes, pattern analysis
21-25	Customer conversations (5-10)	Customer insights summary
30	Written diagnostic to CEO	What's working, what's broken, unknowns
31-45	Triage and quick wins	2-3 visible fixes executed
45-60	Talent assessment complete	Skill/Will matrix, gap analysis
60-75	12-month plan drafted	Quarterly milestones, resource needs
75-85	CEO review and alignment	Revised plan with CEO input
90	Board presentation	Diagnostic + plan + budget ask