First CRO-CEO 1:1: The Agenda for a New CRO's First Week

The first 1:1 between a CRO and their CEO is the structured 90-minute conversation held within the first 48 hours of taking the role to align expectations, map the invisible constraints, and secure the access and mandate needed for a credible revenue audit. This is not an informal welcome chat. It is the moment when the CRO lays the foundation of the relationship with the person who will decide, six months from now, whether their mandate is extended or cut short.

On the ground, our Revenue Health Score diagnostics conducted with B2B scale-ups reveal a consistent pattern: CROs who succeed in their transition have systematically held a structured first 1:1 with their CEO within the first 48 hours, while those whose mandate is cut short let one to two weeks pass before having this conversation. Among CROs whose mandate exceeds 24 months, nearly all documented this first exchange with a summary email sent the same day.

This article details the 7 blocks of a first CRO-CEO 1:1, the positive and negative signals to decode, the commitments to secure before leaving the room, the adaptations by company size, and the mistakes that turn this meeting into a false start.

Key takeaways

• Timing: within the first 48 hours, never after the first week. Every day that passes without this 1:1 is a day the CRO moves forward without a compass.
• Duration: 90 minutes minimum. A 30-minute slot forces the conversation to stay superficial and leaves no room for the topics that matter.
• Format: in person if possible, never a video call with other participants. This 1:1 is a conversation between two people, not a committee meeting.
• Deliverable: a summary email sent within 2 hours, recapping the 5 to 7 points of alignment, the access requested, and the agreed schedule.
• Hidden objective: understand what the CEO does not say in town halls and official presentations. The real revenue problems surface in what goes unsaid.
• Fatal mistake: showing up with a plan. The first 1:1 is for listening, not for presenting a strategy built without field data.
• Maturity signal: a CEO who easily blocks 90 minutes within the first 48 hours signals that the revenue transition is a real priority, not a topic delegated to HR.

"Leaders who succeed in their transitions spend a disproportionate amount of time understanding the situation before acting. Those who fail do exactly the opposite: they act first and understand too late."

Michael Watkins, The First 90 Days (Harvard Business Review Press)

Why the first 48 hours are critical

A CEO who hires a CRO already has a thesis about what is wrong. This thesis is often partly correct and partly biased. The first 1:1 is the only moment when the CRO can access this thesis before it gets filtered through interactions with the rest of the organization.

The window of candor closes fast

After 48 hours, the CRO starts receiving information from the team, the board, and peers on the leadership team. Every piece of information received from a third party before hearing from the CEO creates a risk of biased framing. The CRO interprets the organization's signals through a lens that is not the CEO's, and the perception gap sets in silently. Our diagnostics show that this gap, when not corrected within the first 10 days, hardens into a permanent filter in the CRO-CEO relationship.

Synchronizing lenses before looking together

The first 1:1 synchronizes the two lenses. Not so the CRO blindly adopts the CEO's view, but so they understand where the CEO is looking from, what their deep frustrations are, and above all what results they expect at 90 days, 6 months, and 12 months. A CRO who knows their CEO's frame of reference can then challenge that frame with data. A CRO who does not know it risks challenging the wrong topics and missing the real points of tension.

The first-anchor effect

The first 1:1 creates a powerful psychological anchor. It is the first real professional impression, beyond the hiring process. A CRO who arrives prepared, with precise questions and strong active listening, anchors the image of a rigorous operator. A CRO who shows up in "tell me everything" mode without structure signals an improvisation that raises concern. This initial anchor colors the following 90 days.

First 1:1 vs. recurring 1:1s: two distinct exercises

The first 1:1 is not an accelerated version of a regular 1:1. Confusing the two leads the CRO to under-invest in preparation or to approach the first exchange with the casualness of a routine check-in.

A CRO who treats their first 1:1 like a recurring one misses the unique opportunity to ask questions that will become harder to ask as the relationship progresses. "What skeletons should I know about?" is a fair question on day 1. By day 30, it sounds naive.

The 7 blocks of the agenda

The first 1:1 agenda is structured into 7 thematic blocks, each with a distinct objective and a recommended timing. The order is not arbitrary: it moves from context toward operational matters, passing through sensitive topics once the conversation has already reached a sufficient level of candor.

Block 1: the context behind the hire (15 min)

The first question is not "what are the objectives" but "what made you decide to hire a CRO now, not 6 months ago or 6 months from now." The answer reveals the real trigger: a missed quarter, board pressure, a VP Sales departure, a funding round that requires scaling, or accumulated frustration that has reached a threshold. Each trigger implies different constraints and a different level of urgency.

In our diagnostics, the most common trigger is the combination of a missed quarter and board pressure. This scenario places the CRO in a position where perceived urgency is high but the patience required to diagnose remains non-negotiable. Being able to identify this scenario in the first 1:1 helps calibrate communication: reassure on pace without promising premature results.

Questions to ask:

• What specifically happened that made this hire a priority?
• Who held this responsibility before, and why didn't it work?
• Did the board push for this hire, or was it your own initiative?
• What alternatives did you consider before hiring a CRO?

Block 2: the CEO's revenue vision (15 min)

The CEO has a vision of what the revenue engine should look like. This vision is rarely documented and often at odds with operational reality. The CRO should hear it as it is, without challenging it at this stage. The classic trap is starting to argue about the feasibility of the targets: this is not the moment.

Our diagnostics show that in 60% of cases, the ARR target announced by the CEO at the first 1:1 is built on a linear extrapolation that ignores seasonality, churn, or the pipeline's real capacity. A CRO who spots this disconnect during the first 1:1 knows they will need to reset expectations with data by day 30.

Questions to ask:

• What does revenue look like in 18 months if everything goes well?
• What ARR or MRR are you targeting at 12 months, and what is that number based on?
• Are there profitability constraints, or is it still "growth at all costs" mode?
• What are the 2-3 revenue topics keeping you up at night?

Block 3: skeletons in the closet (15 min)

Every organization has sensitive topics no one raises in public. An untouchable star sales rep despite toxic behavior. A strategic partnership that delivers nothing but was negotiated by a board member. A CRM tool chosen by the previous VP Sales that everyone knows doesn't fit. The CEO is often the only person willing to speak frankly about it, provided the question is asked directly. The CRO's silence on these topics is not caution: it's a missed opportunity.

This block is the most uncomfortable and the most valuable. Our diagnostics reveal that dependence on a top performer is the most frequent sensitive topic, followed by regretted CRM decisions and unresolved conflicts between functions. Addressing these topics on day 1, in a confidential setting, is more effective than discovering them by accident on day 30.

Questions to ask:

• Are there people on the revenue team I need to handle with care, and why?
• What past decisions do you regret on the sales side?
• Are there ongoing projects that should be stopped but that no one dares to stop?
• What change attempts have already failed, and why do you think that is?

Block 4: stakeholders and internal politics (10 min)

The CRO does not operate in an organizational vacuum. They need to understand the alliances, tensions, and power dynamics within the leadership team before starting to interact with other executives. A CRO who meets the CMO without knowing they were also a candidate for the CRO role starts the relationship on a misunderstanding that will take months to fix.

The CEO is the only reliable source on this topic. Other leadership team members will describe cross-functional relationships in a light favorable to their own position. The CEO, who sees the whole picture and has an interest in the CRO navigating it correctly, is the best cartographer of internal politics. Leadership team alignment is a workstream that begins with this mapping.

Questions to ask:

• Who on the leadership team should I prioritize building a strong relationship with?
• Are there tensions between functions I should know about (marketing-sales, sales-product, finance-sales)?
• How does the board operate on revenue topics? Who asks the questions, who has influence?
• What level of autonomy are you giving me on operational decisions?

Block 5: existing metrics and reporting (10 min)

The CRO needs to know what the CEO currently looks at to steer revenue, even if it's insufficient or incorrect. A CRO who imposes a new dashboard on day 15 without understanding why the CEO was looking at a particular number creates confusion instead of clarity.

In our diagnostics, 70% of CEOs say they look at "the pipeline" and "the number for the month" as their main indicators. Fewer than 30% track NRR, CAC, or conversion rate by funnel stage. This gap between tracked and needed metrics is critical information for the CRO: they already know that part of their job will be educating the CEO on the right revenue KPIs, which requires tact and a gradual approach.

Questions to ask:

• What are the 3 numbers you look at every week to assess revenue health?
• Where do these numbers come from, and how much do you trust them?
• What is the current format of revenue reporting, and how often does it happen?
• How accurate has the forecast been over the last 6 months?

Block 6: 30-60-90-day expectations (10 min)

The most important moment of the 1:1. The CRO must leave with a crystal-clear understanding of what the CEO expects at each milestone of the 100-day plan. Ambiguity is toxic: a CEO expecting a restructuring plan by day 30 and a CRO planning a listening diagnostic will collide head-on.

Our diagnostics show that the most common CEO expectations at 30 days are: a quantified diagnostic, a read on the real pipeline, and an opinion on team quality. At 90 days: measured quick wins, a quarterly roadmap, and a view on the investments needed.

Questions to ask:

• What do you expect from me at 30 days?
• What would make you say, at 90 days, that this hire is a success?
• Is there a specific topic where you expect quick action, independent of the diagnostic?
• What has caused other revenue leaders you've seen in this type of role to fail?

Block 7: access and mandate (15 min)

The operational block. The CRO cannot audit what they cannot see. This block formalizes the access, rights, and commitments from the CEO. It is also a test of willingness: a CEO who hesitates to grant CRM admin access on day 1 signals a trust issue or a data governance problem that will need to be addressed as a priority.

Requests to make:

• Admin access to the CRM and all sales reporting tools
• Access to financial dashboards (P&L by business unit, unit economics, forecasts)
• Authorization to conduct one-on-one interviews with any member of the organization, without going through the hierarchy
• A protected weekly slot of 45 to 60 minutes with the CEO for the first 100 days
• A commitment that the first 30 days will be a listening period free of operational delivery pressure
• The right to meet 3 to 5 key customers directly

Every request not secured in this 1:1 will be harder to obtain later. A CRO without CRM access by day 3 has a mandate problem, not a technical one. And a CRO who doesn't get a weekly slot with the CEO risks steering their transition without feedback, which is the equivalent of driving without a rearview mirror.

Decoding the CEO's signals during the 1:1

The explicit content of the CEO's answers is only part of the information. Implicit signals, hesitations, and avoided topics are just as telling. An experienced CRO listens as much to what is said as to what isn't.

Positive and negative signals

What the CEO doesn't say

The topics a CEO avoids are often the most important ones. A CEO who talks at length about acquisition but never about churn signals a blind spot. A CEO who describes the team as "doing great overall" without naming a single weakness is probably protecting someone. A CEO who never mentions the board potentially has a governance problem. The CRO notes these silences and explores them in subsequent 1:1s.

The summary email: the invisible deliverable

Within 2 hours of the 1:1, the CRO sends a summary email to the CEO. This is not an exhaustive record. It's a structured recap in 5 to 7 points that shows the CRO listened, understood, and retained the essentials. The absence of this email is the most reliable signal of a CRO who won't keep up the documentation pace over the first 100 days.

Structure of the email

The email follows a standard format:

1. Context and trigger behind the hire (as understood)
2. Target revenue vision at 12-18 months
3. Main risks or sensitive topics identified
4. 30-60-90-day expectations (restated)
5. Confirmed access and commitments
6. Next steps (start of interviews, next 1:1)

The email's three functions

This email serves three functions. It validates mutual understanding: the CEO can correct a misunderstanding before it takes root. It creates a written record that will serve as a reference at 90 days. And it shows the CEO that the CRO operates with rigor from day one. A CEO who receives a structured email 90 minutes after a 1:1 knows they hired someone who documents and keeps their commitments.

The mistake of an email that's too long

The summary email fits on one page. An overly long email signals that the CRO failed to prioritize information. Five to seven points, each written in two to three sentences. No attachments, no complex formatting. Simplicity is the message.

The 5 mistakes that sabotage a first 1:1

Showing up with a pre-built strategy

A CRO who opens the 1:1 with "here's my vision for the next 90 days" signals they don't need to listen. The CEO perceives arrogance or naivety, and the relationship starts off unbalanced. The first 1:1 is a listening exercise, not a pitch.

Asking only factual questions

"What is the revenue?" and "How many sales reps do you have?" are questions the CRO should already have answers to. Questions in the first 1:1 must go beyond facts: perceptions, frustrations, unspoken matters, internal politics. If the CRO can find the answer in a document, the question doesn't belong in this 1:1.

Not addressing sensitive topics

A CRO who skips block 3 out of politeness or caution misses the opportunity to understand the real constraints. The CEO prefers a CRO who asks direct questions to one who discovers problems by accident three weeks later.

Underestimating the time needed

A 30-minute 1:1 doesn't allow for covering the 7 blocks. The CRO stays on the surface, the CEO feels like nothing substantial was said, and critical topics get pushed to "a future slot" that never comes. If the CEO can't block 90 minutes, that's a signal about how much priority they give to the revenue transition.

Not sending the summary email

Without a summary email, the 1:1 only exists in the selective memory of two people. At 90 days, when the CEO says "I told you pipeline was the priority" and the CRO replies "no, you said it was churn," there's no reference to settle the dispute. The summary email isn't bureaucratic. It's insurance against the misunderstandings that destroy trust between two executives.

Adapting by company size

The first 1:1 doesn't play out the same way in a 30-person startup as in a 500-person mid-market company. The 7-block format remains the foundation, but the depth, duration, and dominant topics vary significantly.

In a startup, the first 1:1 is often shorter and more informal, but the stakes around the mandate are the same. Blind spots exist in every organization, regardless of size.

After the first 1:1: setting the cadence

The first 1:1 is the first of a series. The CRO must immediately establish a weekly cadence with the CEO for the first 100 days: keeping the CEO informed of progress (they don't like surprises) and continuing to extract information week after week.

The cadence of the first 30 days

The format of subsequent 1:1s is shorter (45-60 minutes) and more operational. The CRO structures each 1:1 around three questions: what did I learn this week, what worries me, and what do I need. This structure keeps the CEO engaged without overloading them.

From diagnostic to formalization (Day 30-60)

By day 30, the weekly 1:1 becomes the venue for presenting the written diagnostic. The CEO isn't surprised by the content, because they've received interim findings every week. The diagnostic is a formalization, not a revelation. This "no surprises" mechanism is fundamental: a CEO who discovers a critical diagnostic without having been prepared feels betrayed, even if the diagnostic is perfectly accurate.

Moving to a biweekly cadence (Day 60+)

By day 60, the cadence can shift to biweekly if a relationship of trust has been established. But never below one 1:1 every 15 days during the first year. A CRO who loses the direct link with the CEO loses their political compass. Formal governance rituals (monthly executive review, QBR) don't replace the 1:1: they complement a direct communication channel that must stay active.

Template: the 20 questions and the 48-hour calendar

For CROs who prefer a directly actionable checklist, here are the 20 essential questions grouped by block, to adapt to context, followed by the recommended calendar for the first 48 hours.

Context: What triggered this hire now? Who was handling revenue before, and why didn't it work? Did the board push for it?

Vision: What ARR are you targeting at 12 months? Growth or profitability as the priority? What revenue topics keep you up at night?

Unspoken matters: Which people do I need to handle with care? What past decisions do you regret? What projects should be stopped?

Politics: Who on the leadership team should I prioritize building with? What tensions between functions should I know about? What level of autonomy are you giving me?

Metrics: What 3 numbers do you look at every week? Where do they come from? How much do you trust them?

Expectations: What do you expect at 30 days? What would make this hire a success at 90 days? What has caused other revenue leaders to fail?

Mandate: CRM admin access, financial access, open interviews, weekly CEO slot, protected listening period, direct customer access.

The first 48-hour calendar

A CRO who starts on Monday morning should have their CEO 1:1 by Monday afternoon at the latest. Pushing it to Tuesday means losing a day of context in a window where every day counts.

Further reading

• 100-day plan for a new CRO: the complete framework this 1:1 kicks off
• Revenue audit for a new CRO: the method: the audit phase this 1:1 prepares and mandates
• Leadership team alignment and revenue rituals: the governance to put in place after the listening phase
• Revenue reporting: essential metrics: the metrics to challenge during block 5
• B2B revenue KPIs: CEO indicators: the indicators the CEO should be tracking
• Sales coaching: the role of managers: the 1:1 rituals to set up with the team
• Pipeline management and forecast hygiene: the pipeline topic to address in block 5
• Our revenue diagnostic methodology: the ACROSS method applied to a new leadership hire

Sources cited

• Michael Watkins, The First 90 Days: Proven Strategies for Getting Up to Speed Faster and Smarter, Harvard Business Review Press
• 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: April 16, 2026.