New CRO OKRs: Setting Goals in the First 90 Days

A newly appointed CRO's OKRs are the system of objectives and key results that translates the revenue diagnostic into measurable 90-day commitments, both for the CRO personally and for the entire revenue organization they lead. It is the tool that turns strategic vision into quarterly execution discipline, and that aligns the CEO, the leadership team, and the sales, BDR, CSM, and RevOps teams around a single, quantified roadmap.

For a newly appointed CRO, the paradox is temporal: OKR methodology requires a solid diagnostic before objectives can be formalized, yet the company is already running on a quarterly cadence that will not pause to give them time to listen. Caught between the current quarter (which they inherit without having defined it) and the next quarter (which they must build from a still partial diagnostic), most CROs fall into one of two classic traps: they rewrite the OKRs too fast, imposing their own reflexes without context, or they wait too long to cascade and leave the organization without a compass for 60 to 90 days.

This guide details the sequenced method for setting CRO OKRs when taking on a new role, the writing rules that distinguish a real Key Result from an activity metric, the archetypal OKRs observed among CROs who succeed in their first months by company stage (growth, scale-up, pre-IPO), the cascade to the VP Sales, Head of BDR, Head of CSM, and Head of RevOps, the monthly and quarterly review rituals to put in place, the mistakes that invalidate an OKR system in under 90 days, and ready-to-use templates for each stage of maturity.

Key Takeaways

• Inherit the current quarter: during days 1 to 30, do not touch the existing OKRs. Observe how the organization executes them, and identify the gaps between the reported numbers and what is actually happening on the ground.
• Draft your personal OKRs by day 60: the CRO's OKRs must be built on the phase 1 diagnostic, aligned with the CEO, and validated before any cascade.
• Cascade by day 90: the next quarter starts with a complete OKR cascade, from the CRO to the revenue leaders, then from the leaders to their teams.
• 3 to 5 Objectives maximum per level, 3 Key Results per Objective, all measurable within 90 days. Beyond that, the system becomes unreadable and unmanageable.
• Key Results are outcomes, not activities: "generate €2M in qualified pipeline" is a KR, "make 5,000 calls" is not. Confusing the two is the most frequent and the most costly mistake.
• OKRs do not replace quotas: the two coexist. Quotas measure the contractual execution of sales reps, OKRs measure the ambitious bets that move the organization forward.
• Weekly review at team level, monthly at CRO level, quarterly at leadership team level: without these three rituals, an OKR system dies within 6 months.

"OKRs are not a magic formula. They don't spare you from thinking, they demand it. They force leaders to ask the hard questions: what really matters in the next 90 days, and how will we know we succeeded? Companies that treat OKRs as a reporting exercise produce mediocre OKRs. Those that treat them as a strategic discipline produce extraordinary results."

John Doerr, Measure What Matters (Portfolio Penguin)

Why a New CRO's OKRs Are Not Set on Day 1

The temptation for a newly appointed CRO is to set their OKRs within the first week to make their mark and reassure the CEO. This is a structural mistake. A system of objectives built without a diagnostic produces targets that are disconnected from reality, either overestimating what the organization can deliver (generating demotivation by mid-quarter) or underestimating its potential (installing an artificial glass ceiling).

The New CRO's Temporal Paradox

The CRO joins an organization that is already running on a quarterly cadence. The current quarter has its OKRs, its commitments, its reviews. The organization did not wait for the new CRO to define its priorities: they are already there, often carried by an interim VP Sales or directly by the CEO. A CRO who arrives mid-quarter mechanically inherits objectives they did not write.

Faced with this situation, two flawed reflexes are commonly observed. The first is to rewrite everything immediately, in the name of the need to "make one's mark." This destabilizes the organization mid-effort, invalidates work already underway, and sends a signal of arrogance to the leadership team. The second is to do nothing and wait for the start of the next quarter to produce anything at all. This leaves the team without a signal for 90 days, and deprives the CRO of a chance to observe how the organization executes under real conditions.

The third path, which we consistently observe among CROs who last, is to inherit without modifying during the first 30 days, draft their own personal OKRs by day 60 aligned with the diagnostic, and cascade them to the revenue organization at the start of the next quarter, around day 90.

What Our Diagnostics Reveal About Revenue OKRs

Across our Revenue Health Score diagnostics conducted with B2B scale-ups between €10M and €100M ARR, three patterns show up consistently in organizations suffering from poor OKR governance. First: a large share of the revenue OKRs we examined contain at least one KR that measures an activity ("number of demos delivered," "number of outbound calls") rather than an outcome ("revenue generated," "demo to opportunity conversion rate"). Second: many organizations have more than 5 Objectives at the CRO level, which dilutes focus and makes the system unmanageable. Third: very often, sales, BDR, and CSM OKRs are not consistent with one another, each following its own local logic without an explicit cascade.

These three dysfunctions are invisible on a quick read. They become obvious the moment you run a simple exercise: ask the CRO to recite their 3 to 5 Objectives for the quarter without looking at the document. In healthy organizations, they do it in 30 seconds. In unhealthy ones, they stumble, hesitate, or recite vague phrases without the associated KRs.

OKRs vs. KPIs: A Distinction Most CROs Forget

Confusing OKRs and KPIs is probably the most widespread mistake in revenue management systems. Both are useful, but they do not serve the same purpose, and mixing them dilutes both.

Operational Definitions

KPIs are the health indicators of the revenue machine that you maintain permanently: pipeline coverage, stage conversion rate, win rate, churn rate, NRR, CAC, cycle time, ACV. They are measured every month, do not change from one quarter to the next, and are used to detect drift. See our article on essential revenue KPIs for a B2B CEO for the full list.

OKRs are the ambitious bets the organization makes over a given quarter to move the machine forward. They are temporary by nature: they change every quarter. They do not replace KPIs, they push them forward.

When a KPI Becomes an OKR

A KPI can temporarily become a Key Result if the organization decides to make it a quarterly priority. Example: NRR is a permanent KPI that is tracked every month. If the CRO decides in Q3 that NRR is the priority initiative, "bring NRR from 108% to 115% by the end of Q3" becomes a Key Result. The following quarter, if the target is hit and another priority emerges, NRR goes back to being a background KPI that is maintained without being turned into an OKR.

This distinction matters because it avoids a classic pitfall: turning every KPI into an OKR. A system with 25 OKRs is no longer an OKR system, it is a dashboard in disguise. The whole point of OKRs is to pick the 3 to 5 battles that matter, not to list everything you track.

The Writing Rules for a Key Result That Holds Up

The quality of a Key Result is measured by its ability to survive three tests: is it measurable without ambiguity, is it achievable in 90 days with the team and resources available, and does hitting it prove that the Objective has progressed?

The 5 Criteria of a Good Key Result

A solid Key Result meets five characteristics. First, it expresses an outcome (a business result), not an activity (an action carried out by the team). Second, it is quantified by a number, not an adjective. Third, it has an explicit starting point and a clear target. Fourth, it is achievable in 90 days with the resources allocated to the team that owns it. Fifth, it is measurable from a documented source of truth (a CRM view, a dashboard, a financial report), not from a verbal claim.

Good KR vs. Bad KR: Concrete Examples

The Activities That Are NEVER Key Results

Certain metrics show up systematically in broken OKRs and must be banned as Key Results. "Number of calls made" measures effort, not result. "Number of demos delivered" measures activity volume without saying anything about quality. "Number of emails sent" encourages spam. "Number of meetings booked" ignores their qualification. These numbers belong in a BDR activity dashboard or in individual coaching, never in quarterly OKRs at the CRO level. See our article BDR performance: the KPIs that matter for a deeper look at this distinction.

The Timeline for Setting OKRs When Taking on a New Role

A newly appointed CRO does not write their OKRs on day 1. They set them in three stages, each with its own deliverables and its own alignment rituals.

Phase 1 (Days 1 to 30): Inherit Without Modifying

During the first 30 days, the CRO takes ownership of the existing OKRs without modifying them. Their job is to read them carefully, observe how the organization executes against them, and identify the gaps between the stated objectives and what is happening on the ground. This observation phase is critical: it makes it possible to understand the organization's implicit logic (who owns what, who measures what, who is not looking at what), and to see whether the OKRs reflect serious work or were thrown together in 10 minutes before a leadership team meeting.

In concrete terms, by day 15 the CRO should be able to answer five questions about the current quarter's OKRs: who wrote these OKRs, when, and under what conditions? Where does each KR currently stand? Which KRs are objectively impossible to hit and already known by everyone to be lost causes? Which KRs are too easy and will be hit without any effort? What is the quality of the data used to measure these KRs?

Phase 2 (Days 31 to 60): Draft the CRO's OKRs

From day 30 onward, the initial diagnostic is advanced enough to begin formalizing the CRO's personal OKRs. These are their own commitments for the next 90 days, not yet the cascade to the organization. The CRO drafts 3 to 5 Objectives, each with 3 Key Results, based strictly on the revenue diagnostic delivered to the CEO on day 30. See our article CRO revenue audit: onboarding method to understand the structure of the diagnostic that serves as the foundation.

Alignment with the CEO happens during a dedicated 1:1, typically on day 50. The CRO presents their personal OKRs, the CEO challenges them, and a finalized version is locked in. This 1:1 is a moment of truth: if the CEO pushes to add 2 or 3 extra Objectives "because it's important," the CRO must hold their ground. A CRO who accepts 8 Objectives in their first quarter ends up with a system that has no priorities. See our article on the agenda for a new CRO's first 1:1 with the CEO for the recommended structure of this conversation.

Phase 3 (Days 61 to 90): Cascade to the Organization

By day 60, the CRO's OKRs are locked in. The cascade to the revenue organization starts immediately. Each revenue leader (VP Sales, Head of BDR, Head of CSM, Head of RevOps) builds their own Objectives that contribute to the CRO's Objectives, with their own Key Results specific to their scope. Then each manager within those teams cascades their own team OKRs.

The cascade is not mechanical. A CRO KR does not automatically translate into an identical VP Sales KR. The cascade preserves the coherence of the parent Objective, but each level adapts the KRs to its own scope of control.

Archetypal CRO OKRs by Maturity Stage

A CRO's OKRs vary significantly depending on the company's stage. What makes sense in a growth-stage company at €15M ARR is disconnected from reality in a scale-up at €80M ARR. Three archetypes recur in our observations.

Growth-Stage (€10-30M ARR): Scaling the Acquisition Machine

At this stage, the CRO inherits a sales machine that has found product-market fit but has not yet scaled. The priorities are ARR growth, new logo acquisition, and building the operational foundations that will allow the company to reach €50M without everything breaking. CRO OKRs at this stage typically look like this:

See our article Sales forecast: aiming for precision to dig deeper into the forecast KR.

Scale-Up (€30-100M ARR): Diversifying Growth

At this stage, new logo acquisition alone is no longer enough to fuel growth. The CRO must diversify revenue engines: expansion on the existing book, entry into new segments, profitability of the sales teams. Typical OKRs become:

See our article Expansion revenue: CSM and upsell to dig deeper into the first Objective.

Pre-IPO (€100M+ ARR): Industrializing Predictability

At this stage, the challenge is no longer speed but execution quality: forecast accuracy, cohort predictability, operational maturity. Investors and the board scrutinize every decimal. Typical OKRs focus on:

See our article Revenue reporting: the essential metrics for the reporting framework at this stage.

Cascading OKRs to the Revenue Organization

Cascading CRO OKRs down to the revenue leaders is the step that makes or breaks the system. A mechanical cascade that simply copies the CRO's KRs at every level is useless. A misaligned cascade where each leader pursues their own logic without contributing to the CRO's Objectives is worse.

The Logic of the Cascade: Contribution, Not Copying

A KR at the CRO level translates into one or more KRs at the revenue leader level that contribute to it. Example: if the CRO's KR is "generate €5M in new ARR," the VP Sales will have their own KR "sign €4M in new ARR on the mid-market segment" and the Head of BDR will have "generate €7M in qualified SQL pipeline." Both contribute to the CRO's KR without copying it. What matters is that the sum of the contributions makes it possible to hit the parent KR.

Who Owns What: The Cascade Map

The 4 Critical Roles and Their Typical OKRs

VP Sales: their OKRs must reflect the core of the new business sales operation: new ARR, win rate, ACV, velocity. They are the first person responsible for direct sales execution. Their KRs are systematically aligned with at least one CRO KR on growth.

Head of BDR: their OKRs concern top-of-funnel pipeline generation and qualification. Qualified SQL pipeline, SDR to SQL conversion rate, new BDR ramp-up. Their role sits at the pivot between marketing and sales. See our article Pipeline management and forecast hygiene to understand how pipeline and forecast connect.

Head of CSM: their OKRs cover retention and expansion. NRR, GRR, renewal rate, upsell revenue, product adoption, customer satisfaction. They are increasingly a net contributor to revenue, not just a cost center. See our article NRR: net revenue retention, the king metric.

Head of RevOps: their OKRs concern the quality of the operational execution that makes everything else possible. Forecast accuracy, pipeline hygiene, tooling rollout, CRM data quality. It is a multiplier role, not a direct contributor to revenue.

The OKR Rituals to Install From Day One

An OKR system that is not backed by documented review rituals dies within 6 months. The CRO must install three distinct levels of rituals, each with its own frequency and granularity.

The Weekly Team Review

Every revenue manager (VP Sales, Head of BDR, Head of CSM) holds a one-hour weekly review with their team, in which progress on the Key Results is reviewed. The format is deliberately short and operational: what percentage of progress on each KR, what blockers have been identified, what actions have been decided for the following week. This is not a strategic review, it is an execution ritual.

The Monthly CRO Review

Once a month, the CRO holds a 90-minute OKR review with their revenue leaders. The format is more analytical: confidence percentage of hitting each KR (the color-coded green/yellow/red forecast method), gap analysis, resource reallocation decisions, identification of the KRs at risk of being missed and the available options. This review is summarized and passed up to the CEO in the weekly 1:1.

The Quarterly Leadership Team Review

At the end of each quarter, the CRO presents the final OKR scoring to the leadership team and proposes the OKRs for the next quarter. The format follows a discipline: honest scoring on each KR (0 to 1.0 in the Google tradition, or green/yellow/red in simplified versions), lessons learned from the quarter, and the proposed cascade for the next quarter. See our article Executive Review: the management ritual that makes the difference for the full structure of this review.

The Mistakes That Kill an OKR System in Under 90 Days

Five mistakes recur systematically in organizations where the OKR system collapses. Knowing them makes it possible to avoid them when taking on a new role.

Too Many OKRs

The first mistake is setting 7, 8, or 10 Objectives at the CRO level. Each one seems "important," each one is defended by a leadership team member who wants their topic among the priorities. The result: no real priority, everyone pursuing their own piece without alignment, and by the end of the quarter, half the KRs have been abandoned along the way. The discipline of 3 to 5 Objectives maximum is non-negotiable. Anything that does not fit on that list is a background KPI, not an OKR.

Activity KRs

The second mistake is measuring effort rather than result. A KR "make 5,000 outbound calls" says nothing about business impact. Teams hit the number mechanically without the business moving forward. A correct KR would be "generate €2M in qualified pipeline via outbound." Effort then becomes an adjustment variable in service of the result, not an objective in itself.

Duplication With Quotas

The third mistake is turning individual sales quotas into team Key Results. Quotas are an individual contractual tool, assigned per sales rep, used to drive variable compensation. OKRs are collective, ambitious, and used to steer the organization. Putting the sales team's overall quota into a KR amounts to setting "hit the contractual minimum" as an ambitious objective, which is absurd.

Non-Measurable KRs

The fourth mistake is accepting qualitative KRs such as "improve marketing-sales collaboration" or "strengthen team engagement." A KR that cannot be measured with a number at the end of the quarter is not a KR. It is an intention. Intentions cannot be managed. If team engagement is a real topic, the KR becomes "sales team eNPS at 45+ (vs 28)" or "sales team voluntary turnover rate < 5% for the quarter."

The Absence of Review

The fifth mistake is setting the OKRs at the start of the quarter and never discussing them again until the end. Without a monthly review, the OKRs become a dead document. Teams work on their daily operational priorities without referring back to the OKRs, and by the end of the quarter, nobody really knows where each KR stands. The review ritual is not optional, it is the condition for the system's existence.

Communicating OKRs to the Organization: The First CRO All-Hands

A CRO's first public communication about their OKRs is as much a political moment as a strategic one. It frames the ambition of the mandate and positions the CRO relative to the organization.

The OKR Kickoff Format

A good OKR launch all-hands lasts 45 minutes and follows a structured outline. Contextual introduction (10 min): the CRO recaps the diagnostic shared with the leadership team, the three structuring initiatives identified, and the ambition for the quarter. CRO OKR presentation (15 min): the 3 to 5 Objectives are presented with their KRs, their logic, and their contribution to the overall strategy. Cascade by leader (15 min): each revenue leader presents their own OKRs in 3 minutes, which makes the cascade visible to the entire organization. Honest Q&A (5 min): hard questions are not dodged, they are an opportunity to demonstrate the rigor of the system.

Communication Mistakes to Avoid

Three communication mistakes can sink an OKR kickoff. First: overselling the ambition to impress. Blatantly unrealistic KRs discredit the CRO from the outset. Second: underselling to play it safe. KRs that will be hit easily signal a lack of courage. Third: talking too long without leaving room for the leaders. A CRO who monopolizes the all-hands sends the signal that everything depends on them, which is the opposite of the intended message.

See our article New CRO: winning the trust of the leadership team to dig deeper into the communication posture when taking on a new role.

Template: Ready-to-Use CRO OKRs by Stage

Here are three templates that can be used as-is, to be adapted to each organization's specific context.

Growth-Stage Template (€10-30M ARR)

Objective 1: Scale the new business acquisition machine

• KR1: Generate €X M in new ARR (vs €Y M in Q-1), i.e. Z% growth
• KR2: Sign N new logos with an average ACV above €M k
• KR3: Bring pipeline coverage from A.Bx to C.Dx by the end of the quarter

Objective 2: Industrialize the BDR engine

• KR1: Reach €X M in qualified SQL pipeline (vs €Y M)
• KR2: Move the average BDR ramp-up time from N days to M days
• KR3: Bring BDR's contribution to pipeline from A% to B%

Objective 3: Lay the RevOps foundations

• KR1: Roll out an automated pipeline dashboard used by 100% of sales managers
• KR2: Reach N% Q+1 forecast accuracy (vs M%)
• KR3: Deliver ICP segmentation v1 applied to 100% of new deals

Scale-Up Template (€30-100M ARR)

Objective 1: Grow expansion revenue on the existing book

• KR1: Bring consolidated NRR to N% (vs M%)
• KR2: Generate €X M in upsell revenue (vs €Y M)
• KR3: Roll out the QBR ritual on 100% of accounts > €Z k ARR

Objective 2: Optimize profitability by segment

• KR1: Bring the mid-market LTV/CAC ratio to N (vs M)
• KR2: Reduce SMB segment CAC payback to N months (vs M months)
• KR3: Deliver the profitability matrix by segment, validated by the leadership team

Objective 3: Penetrate the enterprise segment

• KR1: Sign the first N enterprise logos > €X k ACV
• KR2: Build a qualified enterprise pipeline of €Y M
• KR3: Finalize the enterprise playbook with 3 client case studies

Pre-IPO Template (€100M+ ARR)

Objective 1: Bring reliability to revenue predictability

• KR1: Reach N% Q+1 forecast accuracy (vs M%)
• KR2: Reach P% Q+2 forecast accuracy (vs Q%)
• KR3: Deploy the scenario forecasting methodology across 100% of VP Sales

Objective 2: Consolidate unit economics

• KR1: Bring consolidated LTV/CAC to N (vs M)
• KR2: Reach P% group-level NRR
• KR3: Stabilize CAC payback at N months (vs M months)

Objective 3: Install operational maturity

• KR1: Move 100% of revenue teams onto a documented QBR cadence
• KR2: Deploy AI deal-prioritization scoring across 100% of the pipeline
• KR3: Cut monthly close time to N business days (vs M days)

Additional Resources

To dig deeper into the structuring elements covered in this article, we recommend the following reads from our knowledge hub:

• CRO 100-day plan: taking on the role: the complete method within which setting OKRs fits
• CRO revenue audit: onboarding method: the diagnostic that serves as the foundation for the OKRs
• First CRO-CEO 1:1: the agenda: structuring the conversation that validates the OKRs
• New CRO: winning the trust of the leadership team: the communication posture for the cascade
• Essential revenue KPIs for a B2B CEO: the background metrics that OKRs push forward
• Sales forecast: aiming for precision: a recurring topic in pre-IPO OKRs
• Revenue reporting: the essential metrics: the reporting framework that backs the OKRs
• BDR performance: the KPIs that matter: distinguishing activities from outcomes
• NRR: net revenue retention, the king metric: a recurring KR for scale-ups
• B2B CAC: the real cost of acquisition: the unit economics building block
• Pipeline management and forecast hygiene: how pipeline and forecast connect
• Expansion revenue: CSM and upsell: the expansion initiative within scale-up OKRs
• Executive Review: the ritual that makes the difference: the quarterly OKR review
• Real-time steering and CEO dashboards: the dashboards that support the OKRs
• Our revenue diagnostic methodology: the ACROSS method applied to new leadership roles

Sources Cited

• John Doerr, Measure What Matters: How Google, Bono, and the Gates Foundation Rock the World with OKRs, Portfolio Penguin
• Andy Grove, High Output Management, Vintage Books
• Proprietary ACROSS INSIGHT data from our Revenue Health Score diagnostics conducted with B2B scale-ups between €10M and €100M ARR

Article written by Charles-Alexandre Peretz, co-founder of ACROSS INSIGHT, based on the analysis of our Revenue Health Score diagnostics conducted with hypergrowth B2B companies. Last updated: August 14, 2026.