What to Build in Your First 90 Days as CRO

You got the job. The board is watching. Your first pipeline review is in two weeks and you do not know what the numbers mean yet.

Most "first 90 days" advice tells you to listen, learn, and build relationships. That is necessary but not sufficient. You also need a system. Not a deck. Not a list of initiatives. A documented operating plan that connects your revenue strategy to the metrics your board cares about.

Here is how to build one.

Week 1-2: Assess What You Inherited

Before you change anything, you need to know what is actually happening. Not what the last QBR deck said. What the data says.

Run these diagnostics first:

Pull pipeline by stage and look at conversion rates between each stage. If nobody can tell you the historical CR1 through CR8 (visitor to MQL, MQL to SQL, SQL to SQO, etc.), that is your first finding.
Check quota attainment distribution. What percentage of reps hit quota last quarter? If it is below 60%, you have a capacity problem, a quota-setting problem, or both.
Look at your win rate by deal size and segment. Most companies have a sweet spot they do not know about.
Review ramp time for recent hires against their quota schedule. If reps carry full quota at month 4 but historical data shows they do not hit stride until month 9, your ramp model is broken.

Watkins' "The First 90 Days" calls this the STARS assessment: is each function in Startup, Turnaround, Accelerated Growth, Realignment, or Sustaining Success mode? You probably have a mix. The sales org might be in turnaround while CS is in sustaining mode. Each requires a different approach.

Week 3-4: Design Your Revenue System

Once you know what you inherited, design what needs to change. This is not a strategy deck. This is an interconnected set of decisions that cascade downstream.

The 17 components you need to design:

Category	Components
Strategic Foundation	Revenue strategy, ICP segmentation, positioning and messaging
Go-to-Market	Sales motion, pipeline generation, channel and partners
Deal Economics	Pricing and packaging, forecasting, territory and coverage
Post-Sale	Customer onboarding, customer success
Execution	Org design, compensation, tech stack, enablement
Operating System	Operating rhythm, board reporting

The order matters. Your revenue strategy determines your ICP. Your ICP determines your sales motion. Your sales motion determines your pipeline targets, comp plan, and territory model. If you design comp before you design territory, you will redesign comp.

Revenue Architecture by Jacco van der Kooij maps these dependencies explicitly. The key insight: every revenue decision is connected. Change one component and the downstream components need to update.

Week 5-8: Generate Your Playbook

Your design decisions need to become documentation your team can execute against. For each major function, you need:

Process definition: What are the stages, exit criteria, and handoff points?
Metrics and targets: What numbers define success? Who owns each metric?
Cadence: What meetings happen when, with what agenda and what output?
Escalation rules: What triggers an alert, and who responds?

Roberge's Sales Acceleration Formula is clear on this: you cannot manage what you have not defined, and you cannot scale what you cannot repeat. The playbook is the repeatable part.

A common mistake at this stage is writing a playbook that describes the ideal state without acknowledging the current state. Your team did not start from zero. They have habits, tools, and tribal knowledge. Your playbook needs to bridge from where they are to where you need them to be.

Week 9-12: Operate and Measure

Your operating plan is live. Now you need to know if it is working. Three systems matter:

1. Weekly operating rhythm

One 60-minute meeting per week where every function reports against their core metrics. No status updates. Numbers and decisions. Jordan and Vazzana's "Cracking the Sales Management Code" framework is useful here: separate leading indicators (activities, pipeline created) from lagging indicators (revenue, attainment) and manage the leading ones.

2. 90-day health checks

At the end of month 1, month 2, and month 3, assess your revenue operating plan against its milestones. What is on track? What is behind? What needs a course correction? This is not a performance review. It is a diagnostic.

3. Board reporting

Your board cares about a small number of things: ARR growth rate, net revenue retention, pipeline coverage, burn multiple, and whether you are tracking to plan. Build a board deck structure that shows these numbers in context, with a narrative that explains variance and your response.

The Most Common Mistake

The biggest failure mode for new CROs is not moving too slowly. It is designing the revenue system in their head instead of on paper.

Tribal knowledge does not scale. When your operating plan lives in your head, it dies when you are out sick, and it definitely dies when you need to onboard your next three hires. The plan needs to be documented, connected, and trackable.

Your board did not hire you to run pipeline reviews. They hired you to build a revenue operating system that works with or without you in any given meeting.

Getting Started

The gap between "I know what needs to happen" and "my team is executing a documented plan" is smaller than you think if you have the right system.

Start with the assessment. Design the 17 components. Generate the playbook sections. Then operate against it and measure what happens.

The alternative is the same thing that did not work for the last CRO: good instincts, no system, and a board that starts asking hard questions at month 3.