Challenging a Portfolio CEO: The Operating Partner Grid

Challenging a portfolio company CEO is the governance act by which a PE or VC Operating Partner contests a decision, an assumption, or a revenue trajectory put forward by the CEO, precisely enough to add value to the investment thesis, without crossing the line that turns challenge into micromanagement and causes the executive to disengage. It is the hardest exercise in the OP's job, because it plays out on a knife's edge: too little challenge, and the OP becomes a rubber stamp who validates everything the CEO brings and no longer justifies the cost to the fund. Too much challenge, and the CEO becomes defensive, filters information upward, and the quality of the relationship degrades to the point of making the thesis unplayable.

OPs who master this exercise share the same reflex: they always know which zone they are legitimate to operate in, at what intensity, and in what context. Our Revenue Health Score diagnostics, conducted with B2B scale-ups, a significant share of which are backed by Operating Partners, reveal a consistent pattern. The OPs who create the most added value are not the ones who challenge the hardest, they are the ones who challenge at the right level of detail, at the right time, and on the right subject. The CEOs interviewed in these same diagnostics converge on one point: they expect to be challenged, and they get irritated when they are challenged badly.

This article details the three postures an OP can take with a CEO, the five zones where challenge is legitimate and the five zones where it is not, a grid of thirty operational questions to ask when preparing for a board meeting, the questioning techniques that open dialogue rather than shut it down, the timing of intervention across the holding cycle, the red lines that should never be crossed, and the protocol for rebuilding a relationship after a poorly calibrated challenge.

Key takeaways

• Challenging is not micromanaging: the OP challenges assumptions and trade-offs, never execution. The day the OP starts writing sales emails in place of the CRO, they have lost their mandate.
• 5 legitimate zones: revenue assumptions, resource allocation, leadership calls, market positioning, capital deployment. Everything that impacts the investment thesis over a 3 to 5 year horizon.
• 5 off limits zones: detailed product roadmap, day to day operations, HR below VP level, technical architecture, account level tactics. Everything that falls under internal operational expertise.
• Timing: in a 1:1 ahead of the board, almost never during it. An unprepared public challenge is a signal of distrust, not an act of governance.
• Variable intensity across the cycle: heavy challenge during the calibration phase (days 1 to 100) and pre-exit. Light challenge during normal execution.
• Red line: a structural disagreement that persists after three iterations goes to the Investment Committee, not to a fourth round of direct challenge.
• Rebuilding: after a poorly calibrated challenge, the OP regains the initiative through listening, never through counter argument. Time is the only recovery mechanism.

« Teams that perform are not the ones where disagreement is absent. They are the ones where disagreement is possible, fast, and leads to a decision everyone executes. »

Patrick Lencioni, The Five Dysfunctions of a Team (Jossey-Bass)

Why challenging the CEO is the most structural act of an Operating Partner

The Operating Partner is judged by the fund on the portfolio's cumulative performance, and by CEOs on the quality of the sparring they provide. These two criteria converge on a single act: the ability to challenge usefully. Everything else (benchmarks, pattern library, network, introductions) only has value if it feeds a challenge that shifts a portfolio company's trajectory.

The paradox of the OP mandate

The OP has no hierarchical authority over the CEO. Their legitimacy comes from the capital deployed by the fund, their cross portfolio pattern library, and their access to the network. This legitimacy is only activated through challenge. An OP who validates everything the CEO presents implicitly signals that they have nothing to offer beyond goodwill, which is exactly what the CEO is not looking for in a fund representative. Conversely, an OP who challenges everything, all the time, signals a distrust that makes collaboration untenable and pushes the CEO to filter information.

What a CEO looks for in an OP

Our diagnostics reveal a very precise expectation among CEOs of PE and VC backed portfolio companies: they look for a counterpart able to ask them the questions they don't dare ask themselves, in a setting where candor is possible without political consequence. This function is valuable because no one else in the CEO's ecosystem can perform it. Leadership teams are politicized, boards are formatted, retail investors are too distant. The OP is the only figure who combines privileged access, operational understanding, and relative neutrality. An OP who does not challenge wastes this unique position.

The cost of a poorly calibrated challenge

A poorly calibrated challenge has a direct, measurable cost. In our diagnostics, portfolio companies where the OP-CEO relationship is degraded systematically show a 15 to 25 point gap between the revenue score reported at board level and the score observed on the ground. The CEO filters the information that reaches the fund, the OP builds their judgment on truncated data, and the investment thesis drifts silently. This mechanism is one of the leading causes of impairment observed over 3 to 5 year holding periods.

The 3 postures toward a CEO: challenge vs. micromanagement vs. rubber stamping

An OP constantly oscillates between three postures. Mastery consists of knowing which one they are adopting at any given moment, and why. Confusing the three is the root cause of nearly all the dysfunctions we observe.

The rubber stamp

The rubber stamp validates everything, praises everything, contests nothing. It can be spotted by a verbal tic: "we trust the team," repeated at board meetings without ever qualifying what that trust actually means. This posture suits everyone in the short term and destroys value in the medium term. It is especially dangerous on portfolio companies that appear to be outperforming, where it prevents the detection of early warning signs of a downturn.

The micromanager

The micromanager challenges everything, including day to day operations. They ask for the detail of the week's sales calls, criticize the wording of a marketing campaign, suggest tweaks to a product wireframe. This posture destroys the CEO's legitimacy with their teams and always ends up triggering the departure of one or more leadership team members. It is often the symptom of an OP who has not fully made the transition from operator to sparring partner.

The challenger

The challenger intervenes in the zones where they add value, at an intensity calibrated to the portfolio company's stage and the CEO's maturity. They ask questions that force the CEO to make their assumptions explicit, without prescribing the answer. They bring benchmark data without turning it into a verdict. They know when to stay silent, when the decision belongs to the CEO and the challenge would add nothing new.

For an OP taking on a new portfolio company, see 100 day portfolio plan: the OP method. For the mirror view from the CRO side who has to manage an OP's interventions, see First CRO-CEO 1:1: agenda.

The 5 zones where the OP is legitimate to challenge

An OP is legitimate to challenge only the zones that impact the investment thesis over the holding period. These five zones cover the bulk of a B2B scale-up CEO's decision making field. Everything else, however tempting, falls outside their mandate.

Zone 1: revenue assumptions

This is the most legitimate and most underused zone. The OP should systematically challenge the assumptions underlying the forecast, the budget plan, and the ARR trajectory. Planned growth rate vs. historical cohorts, pipeline coverage vs. observed conversion, planned NRR vs. performance by cohort, forecast churn vs. churn observed over the last 24 months. Each of these assumptions can be challenged with factual data without touching the CEO's operational autonomy.

Zone 2: resource allocation

Headcount, budget, tech stack. The OP is legitimate to ask why 40% of the marketing budget goes to a channel that produces 12% of the pipeline, why the sales team is hiring 8 SDRs when the SDR to AE ratio is already saturated, why an 800k€ Salesforce license renewal goes through without a CRM governance audit. These questions open a dialogue on the consistency between the stated strategy and the actual allocation of capital.

Zone 3: leadership calls

Hires and replacements at VP and C-level are always a legitimate subject for challenge. The OP should be able to raise the question of a VP's fit with the target trajectory, the timing of a painful replacement, or the succession plan for a top performer who has become too much of a single point of risk. This zone also includes restructuring decisions, new business unit creation, and geographic splits. It stops clearly at manager level, however: an OP who challenges a team lead hire is out of scope.

Zone 4: market positioning

Target segment, pricing, competitive differentiation. The OP brings particular value here because they see several portfolio companies operating in adjacent markets. They can challenge a segment choice that is not aligned with the best performing cohorts, pricing that undervalues the product, a head on battle strategy against a competitor that the portfolio has already shown to be a losing fight. These questions should always be backed by benchmark data, never launched on intuition.

Zone 5: capital deployment

Add-on acquisitions, geographic expansion, entry into a new segment. These are decisions that commit capital for 12 to 36 months and directly impact MOIC at exit. The OP is not only legitimate but obligated to intervene on these subjects. An OP who lets a poorly framed acquisition go through without a structured challenge has not fulfilled their role, even though the final decision belongs to the CEO and the board.

The 5 zones where the OP should not challenge

Just as structural as the list of legitimate zones, the list of off limits zones is what distinguishes a senior OP. An OP who does not respect these boundaries destroys the CEO's operational legitimacy and sets a precedent that makes collaboration untenable.

Detailed product roadmap

The OP can challenge the product direction (should we accelerate, which target segment, what positioning), but not the sprint by sprint trade-offs or intra roadmap priorities. An OP who comments on the priority between two features enters territory where their technical incompetence quickly becomes visible, and where their intervention creates tension between the CEO, the CTO, and the CPO.

Day to day operations

Running sales calls, facilitating stand-ups, the day to day relationship with a client, handling a support incident. These subjects should never reach the OP unless there is a systemic warning signal. An OP who gets involved in day to day operations kills the chain of command and ends up owning decisions they have no way of following through on.

HR decisions below VP level

Hires, promotions, raises, or departures of employees who are not VP or C-level fall under the portfolio company's internal governance. An OP who comments on these decisions enters a field where they have neither the necessary information nor the mandated legitimacy, and sets a precedent that forces everything to be escalated.

Technical architecture

Choice of language, cloud infrastructure, framework. The OP is not competent on these subjects, even with a tech background. Architecture decisions belong to the CTO and the CEO, not the fund. The rare cases where an OP is legitimate to intervene involve structural choices that commit MOIC (a 2M€ cloud migration, a stack choice that locks the company in for 5 years), and even then, only through questioning, never through prescription.

Account level tactics

How to handle a specific account, what concession to make on a deal in progress, how to respond to an RFP. These decisions are operational and should never reach the OP, except in the exceptional case of an account representing more than 10% of ARR where a loss would have an impact on the thesis.

An OP who feels drawn to one of these zones should ask themselves a simple question: if I say something about this subject, am I bringing information the CEO cannot get elsewhere? If the answer is no, silence is the only professional posture.

The 30 question grid to ask when preparing for a board

The grid below is the industrialized version of OP challenge. It covers the five legitimate zones through thirty operational questions the OP should be able to ask without preparation, whether in board prep or in a 1:1 with the CEO. Each question opens a dialogue rather than imposing an answer.

Questions on revenue assumptions (8)

Questions on resource allocation (6)

Questions on leadership calls (5)

Questions on market positioning (6)

Questions on capital deployment (5)

This grid is not meant to be used exhaustively at every board meeting. It is a reservoir. The OP draws the three to five questions most relevant to the context, and prepares them finely enough for each one to open a real dialogue.

Questioning techniques that open rather than close

How a challenge is posed matters as much as its content. An OP who has mastered the technique can challenge hard subjects without shutting the CEO down. An OP who has not turns the smallest question into a trial.

Open and neutral rather than closed or leading

A closed question calls for a yes or no and shuts down dialogue ("is the pipeline sufficient?"). An open question calls for an explanation ("how are we building the target pipeline over the next six months?"). A leading question suggests the answer ("don't you think you should replace your VP Sales?") and triggers a defensive reflex, regardless of intent. The rule: to challenge, always open and stay neutral. Closed questions are reserved for moments when the OP wants to lock in a commitment (yes we launch, no we wait).

Public vs. private, and silence as a tool

The same challenge produces a radically different effect depending on whether it is posed at board level or in a 1:1. In a 1:1 it can be hard, specific, personal. At board level it must be prepared with the CEO beforehand. An unprepared public challenge is experienced as an act of sabotage, and our diagnostics show that the most severe CEO-OP breakdowns crystallize almost entirely around this pattern. Three to five seconds of silence after a superficial answer is the most underused technique: in 70% of cases the CEO fills the gap themselves with far greater depth. Calibrated reformulation (restating with 10 to 15% more precision) forces a second pass on the assumption and preserves the CEO's standing, more effective than a direct question.

The pre-board: the ritual that prevents 90% of the damage

The pre-board ritual between the OP and the CEO, 24 to 72 hours before the quarterly board meeting, is the mechanism that allows the relationship to function without crystallizing into conflict. OPs who skip this ritual invariably create tensions in the room that then take weeks to defuse.

The purpose of the pre-board

The pre-board is not a rehearsal of the board. It is an alignment on two questions: which subjects does the OP intend to challenge in the meeting, and is the CEO ready to address them publicly. If the CEO would rather handle a subject in a 1:1 before the board, the OP adjusts. If the OP believes the subject absolutely must be raised in the meeting, they say so clearly and let the CEO prepare their response. This discipline prevents ambushes, which are the antithesis of sound governance.

The pre-board checklist

This ritual takes 45 to 60 minutes. It nearly always pays off. OPs who skip it under the pretext of a lack of time pay for that shortcut a hundredfold in post-board crisis management.

Timing: when to challenge more, when to challenge less

Challenge intensity should evolve across the holding cycle. An OP who applies the same pressure for 5 years becomes unbearable or invisible, depending on the CEO's temperament. Senior OPs calibrate intensity to the phase.

Phase 1: the first 100 days (heavy challenge)

This is the phase where the OP challenges the most, and the most directly. Diligence assumptions must be tested against ground reality, value creation levers must be arbitrated, governance must be calibrated. A CEO who does not feel the pressure during this phase will struggle to accept a challenge later on. Good OPs establish their credibility as challengers within the first 90 days, then adjust.

Phase 2: execution cadence (targeted challenge)

Between day 100 and the following 18 months, challenge becomes more selective. The OP follows the cadence of the value creation plan, challenges quarterly variances against plan, and intervenes occasionally on structural subjects. They avoid constant challenge, which would wear down the relationship. The agenda is driven by KPIs, not intuition.

Phase 3: mid-holding (strategic challenge)

Between 18 and 36 months, challenge focuses on strategic inflection points. Should we accelerate or consolidate? Open a new market? Prepare an add-on? Change the CRO? These are structural decisions that commit the exit. The OP returns to a high level of challenge, but on a narrower scope.

Phase 4: pre-exit (heavy challenge again)

In the 12 to 18 months preceding exit, challenge returns to Phase 1 intensity. Everything that could weigh on valuation must be challenged: quality of metrics, key dependencies, blind spots in buyer diligence, preparation of the management story. A CEO who eased off discipline in Phases 2 and 3 must be brought back to a level of rigor that will let them hold up under buyer diligence.

When the CEO pushes back: how to re-engage without caving or digging in

A successful challenge often produces pushback from the CEO. That is normal, and often healthy. What distinguishes a senior OP is how they handle that pushback according to its nature.

The three types of pushback and how to handle them

Pushback can be rational, emotional, or political. Rational: the CEO brings a new element that invalidates the challenge. The OP should concede explicitly ("you're right, I didn't have that angle"). This ability to concede when warranted is what builds long term credibility. Emotional: the CEO feels personally called into question. The OP should not press their advantage, even if they are right. They postpone by a week and pick it back up in a 1:1. Our diagnostics show that OPs who insist in the face of an emotional reaction trigger a lasting breakdown 80% of the time. Political: the CEO is protecting a past decision. The OP cannot win head on; they formalize in writing and escalate to the IC if the disagreement persists.

The three iteration rule

A challenge that has not been resolved after three iterations (three 1:1s or three consecutive board meetings) should be escalated or dropped. An OP who keeps circling back beyond that point destroys the relationship without making progress. Either the OP is wrong and lets it go cleanly, or they are right and escalate to the IC. Dwelling on it is never an option.

The red lines: when challenge becomes an escalation to the IC

There is a threshold beyond which direct CEO-OP challenge is no longer enough and must be escalated to the Investment Committee. Identifying that threshold is a critical skill.

The three triggers for an escalation

The first: a structural disagreement that impacts the thesis over a 12 month horizon and has not been resolved after three iterations. The second: an integrity signal (fraud, concealment, conflict of interest) that exceeds the scope of the CEO-OP relationship. The third: a rapid deterioration of a key metric that threatens exit valuation without the CEO providing a credible response.

The mechanics of escalation

An escalation to the IC is not a hostile act. It should be formalized, pre-announced to the CEO, and backed by data. The golden rule: never escalate without warning the CEO at least 72 hours in advance, never without giving them the opportunity to respond within the file that is escalated. This discipline preserves the relationship even when escalation is necessary.

What an escalation changes

Once an escalation has taken place, the CEO-OP relationship is different. It is not necessarily destroyed, but it takes on a more formal character. OPs who escalate too early or too often lose their direct channel; those who escalate too late let the thesis drift past the point of no return. Getting the balance right is a matter of experience and judgment.

For the revenue governance mechanisms downstream of escalation, see Executive review: a management ritual and Aligning the leadership team on revenue: rituals.

Rebuilding after a poorly calibrated challenge, and classic mistakes to avoid

Every experienced OP has made at least one poorly calibrated challenge. What separates senior OPs from junior ones is not the absence of error, it is the ability to rebuild afterward, and to avoid repeating the classic mistakes that undermine the mandate's credibility.

Recognize and repair quickly

The first rule is speed. A poorly calibrated challenge acknowledged within 24 to 48 hours can be recovered. The OP should call the CEO, explicitly acknowledge the miscalibration, without trying to save face. The temptation to double down (insisting because you think you're right) is the most destructive. Even if the OP is right on substance, the delivery may need correcting. Acknowledging the miscalibration does not mean abandoning the substance: that is exactly the distinction the CEO is looking for.

Shift into extended listening mode

After a poorly calibrated challenge, the OP shifts into listening mode for several weeks. No new major challenges, no new initiative imposed. Time is the only recovery mechanism. An asymmetric repair gesture (a qualified introduction, a facilitated hire, useful intervention with the board) signals a willingness to start over on healthy footing, provided it is real and useful, not symbolic. In 10 to 15% of cases, trust does not come back: mature funds then switch the OP on the portfolio company rather than let the relationship fester.

The recurring mistakes that undermine credibility

Six mistakes come up regularly among OPs early in their careers. Playing the expert when you are not one, because CEOs spot a fake expert very quickly. Applying a portfolio pattern without qualifying the local context. Letting the CEO game the answers by accepting superficial formulations. Challenging to demonstrate one's own legitimacy rather than to add value. Showing up unprepared, when a board level challenge demands 2 to 3 hours of work. Confusing challenge (improving a decision) with control (verifying an execution), which turns the OP either into an unbearable controller or a disarmed challenger.

Template: annual challenge cadence and adapting to the CEO's profile

For an OP supporting a portfolio company over a full year, the typical cadence combines a fixed quarterly tempo with adaptation to the CEO's profile. Applying the same intensity to an emotionally invested founder and to an external CEO hired to scale the business is a methodological mistake: the cadence stays stable, the register adapts.

Founder vs. external CEO

A founder CEO is emotionally invested. The challenge should be precise, prepared, and respectful of that emotional capital. Founders absorb blunt challenges poorly; they absorb well documented challenges very well. An external CEO hired to scale expects peer level challenge, with higher intensity and less hand holding. An OP who holds back their challenge with this type of CEO is perceived as soft.

CEO in crisis, and background profile

A CEO in a crisis context is in a psychologically fragile state. The challenge should not be dropped, but recalibrated: more structural, less frequent, more solution oriented than diagnostic. On background, a tech CEO is often under calibrated on revenue KPIs and forecast discipline. A sales background CEO is often under calibrated on product issues and CRM data quality. The challenge targets the zones of relative fragility, not the zones of comfort.

Further reading

To go deeper on the structural elements covered in this article, we recommend the following reads from our knowledge hub:

• 100 day portfolio plan: the OP method: the 100 day sequence that frames the OP-CEO relationship from closing onward
• Revenue due diligence: the OP method: the grid that feeds the first post-closing challenge
• Revenue red flags: OP detection: the signals that trigger a structural challenge
• Revenue portfolio benchmark: method: the pattern library that feeds the challenge
• CRO and leadership team trust: the mirror image on the CRO side, who has to absorb OP challenges
• First CRO-CEO 1:1: agenda: the CEO-CRO alignment mechanics that condition OP challenge
• CEO revenue blind spots: the recurring blind spots that deserve systematic challenge
• Aligning the leadership team on revenue: rituals: the internal governance the OP can rely on
• Executive review: a management ritual: the cadence that absorbs and structures the challenge
• Real time CEO steering: dashboards: the dashboard that makes the challenge objective
• B2B revenue KPIs: CEO indicators: the metrics that feed challenge on assumptions
• Sales forecast: accuracy: the forecast rigor to challenge every quarter
• NRR: Net Revenue Retention: the central metric to cross check regularly
• Revenue financial control: unit economics: the financial foundation for capital deployment challenge
• Our revenue diagnostic methodology: the ACROSS method applied to OP-CEO sparring

Sources cited

• Patrick Lencioni, The Five Dysfunctions of a Team: A Leadership Fable, Jossey-Bass
• Proprietary ACROSS INSIGHT data from our Revenue Health Score diagnostics conducted with B2B scale-ups between €10M and €100M ARR, including portfolio companies backed by PE and VC Operating Partners

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, including portfolio companies backed by PE and VC Operating Partners. Last updated: September 1, 2026.