The Next-Generation CRO: From Sales Leader to Revenue Operator

For a long time, the path to becoming a Chief Revenue Officer was fairly predictable.

Become a strong seller. Lead a team. Run a larger team. Own the forecast. Carry the number.

Those skills still matter.

But the job waiting at the end of that path is changing.

Today's CRO is making decisions about headcount, AI, pricing, forecasting, pipeline efficiency, customer feedback, marketing investment and GTM systems and Today's CRO is making decisions about headcount, AI, pricing, forecasting, pipeline efficiency, customer feedback, marketing investment, and GTM systems- often at the same time. Sales remains central, but knowing how to run a sales organization is no longer enough on its own.

Chad Compton has seen the role from several sides. He has led large technology sales teams, spent time at Microsoft following its acquisition of Nuance, served as a CRO, and now advises companies as a fractional revenue leader.

His view of the next generation of CROs isn't that they become less human or less sales-oriented.

It's that they become better operators.

The core CRO skills aren't disappearing

Ask what the future CRO needs, and it is tempting to start with AI fluency, data science or technical skills.

Compton starts somewhere more familiar.

High EQ.

Competitiveness.

The ability to deal with different people and lead them toward a result.

Those qualities haven't suddenly become obsolete because revenue teams have better technology.

A CRO still has to coach executives through difficult decisions, communicate with sellers, understand customers, manage conflict and keep a team moving when the quarter isn't going according to plan.

And they still have to want to win.

What has changed is what sits on top of those qualities.

Compton's third characteristic is increasingly important: analytical judgment.

Not the ability to stare at more dashboards.

The ability to take more information than any executive can reasonably consume, decide what actually matters, and turn it into an action the organization can understand.

Being analytical is becoming a leadership skill

Revenue teams are not short on information.

CRM data. Forecasts. Call recordings. intent data. Product usage. Marketing attribution. Customer feedback. Competitive intelligence. AI-generated summaries.

The problem is increasingly deciding what deserves attention.

Compton describes the analytical CRO as someone capable of reducing that noise into something both they and their team can consume.

Consider a fairly normal executive decision:

Should the company invest the next dollar in another seller, a marketing campaign or something else?

Each option has data behind it. Each has an internal advocate. Each has assumptions attached to the projected return.

The CRO's job isn't simply to locate a metric supporting one of them.

It's to weigh the evidence, make the trade-off and explain the decision clearly enough that the people whose proposal didn't win still understand why.

That is an operating skill as much as an analytical one.

And AI is making it more important, not less.

As AI increases how much analysis a revenue organization can produce, the bottleneck shifts from access to information toward judgment about information.

Recent research into the changing CRO role points in the same direction. Spencer Stuart's survey of nearly 100 B2B CROs found that commercial leaders are still at very different stages of AI adoption, even as expectations grow for CROs to understand how AI could reshape the commercial model.

The next-generation CRO doesn't need to personally build every AI workflow.

They do need to know enough to decide where one belongs.

Revenue leadership still needs both science and art

Better data doesn't make every revenue decision objective.

That distinction matters.

A forecast model may detect that a deal has stalled. Conversation data may show a pattern in buyer objections. Pipeline analytics may reveal an unusual conversion drop.

Those are valuable signals.

They still need interpretation.

Compton describes revenue management as a mix of science and art. The science gives leaders evidence. The art provides context: what changed, what the data doesn't know, what happened inside the customer organization and which exception actually matters.

AI doesn't eliminate that tension.

It gives CROs more science to work with.

The difficult part becomes knowing when to trust the pattern and when the situation in front of you deserves a different interpretation.

That may become one of the defining leadership abilities of AI-era revenue executives: not blindly trusting intuition, but not outsourcing judgment to the dashboard either.

The CRO is becoming more cross-functional

The role is also expanding horizontally.

Revenue isn't created by sales alone.

Marketing determines who enters the funnel and with what expectation. Product shapes what can actually be sold. Customer success influences retention and expansion. Finance shapes pricing, investment and efficiency. RevOps connects much of the underlying infrastructure.

The CRO increasingly operates across all of them.

That doesn't mean the CRO needs formal ownership of every function.

Compton's approach is simpler: be present.

Join other teams' calls periodically. Give them access to the revenue leader. Let them question what sales is doing. Understand what they're seeing from their side of the customer journey.

It sounds basic, but distributed work has made spontaneous cross-functional interaction less automatic.

The operating CRO has to recreate it deliberately.

That shift is also visible in the broader market. Current thinking about the CRO increasingly describes the role as an orchestrator of the full revenue system rather than simply the executive responsible for sales.

Cross-functional leadership therefore becomes less about controlling every function and more about creating a system where the functions can make compatible decisions.

RevOps can become more than the team that reports what happened

That same operating mindset changes the relationship between the CRO and RevOps.

Traditionally, sales operations often concentrated heavily on reporting, forecasting, CRM administration and accounting for what had already happened.

Compton sees an opportunity for something more proactive.

What if RevOps helps the sales organization determine where top-of-funnel opportunities exist?

What if it analyzes customer lists and identifies where sellers should focus?

What if the function doesn't simply report the pipeline but actively helps the revenue organization improve it?

That is the distinction between operations as administration and operations as an operating advantage.

Exactly where RevOps reports may vary. Compton sees reasonable arguments for keeping it close to finance or closer to sales.

What's more important is that the data moves across those boundaries—and that the people doing the analysis understand the business well enough to help change the outcome rather than simply record it.

AI changes how CROs get to the number

Compton makes an important distinction when discussing whether sales experience will matter less to future CROs.

Sales doesn't become less important.

How the organization produces sales changes.

Should the company create more top-of-funnel volume?

Improve conversion?

Change the sales process?

Deploy AI somewhere in the workflow?

Invest in another rep?

Improve forecast quality?

Give managers better visibility into customer conversations?

The number remains the destination.

The operating system underneath it becomes much more sophisticated.

That is why AI literacy for a CRO shouldn't be reduced to memorizing a list of tools.

Compton's recommendation is to stay close to the trends. Try the major technologies. Take the demos. Understand what tools such as large language models and revenue platforms can actually do.

Not because every tool belongs in the stack.

Because you can't make good decisions about technology you don't understand.

Revenue Brew recently described a similar pattern among CROs leading AI adoption: curiosity and willingness to experiment are increasingly part of the modern revenue executive profile, alongside the ability to win alignment and actually operationalize the technology.

Better conversation data gives CROs another input—not another answer

Customer conversations are a good example of how this change plays out.

Historically, much of what happened inside those conversations was difficult to analyze at scale.

A manager could join some calls.

Reps could summarize what happened.

CRM fields could capture parts of the outcome.

But turning thousands of individual conversations into something a revenue leader could systematically inspect was difficult.

AI conversation intelligence changes that.

Compton points to tools such as Spiky as one way revenue teams can bring more analysis to customer conversations that historically depended heavily on subjective interpretation.

The important part isn't removing the subjective layer.

It's giving the CRO another evidence source.

Pipeline says what is moving.

Forecasting estimates what may happen.

Customer-conversation analysis can help explain what is actually happening between the buyer and seller.

A strong operator can combine those views rather than relying on one of them in isolation.

The future CRO leads without owning everything

As the role broadens, formal authority becomes less useful as a definition of leadership.

A CRO may influence product decisions without owning product.

They may rely heavily on finance without controlling finance.

They may need marketing to change something they cannot mandate themselves.

They may need RevOps to investigate a problem before anyone knows whether the cause belongs to sales at all.

The job therefore becomes partly about building enough trust across the organization that those teams are willing to solve the same problem together.

Compton's approach—show up, make yourself available, explain decisions and let teams challenge what revenue is doing—isn't sophisticated organizational theory.

That's part of why it works.

Cross-functional alignment often fails less because companies don't understand its importance and more because functions stop talking to one another except when something has gone wrong.

The next-generation CRO has to actively prevent that.

What should future CROs learn now?

If you are preparing for the CRO role, the answer probably isn't to abandon traditional sales leadership and reinvent yourself as a data scientist.

The foundation still matters.

Learn customers.

Learn how good sellers behave.

Learn how to lead people.

Learn how to carry a number.

Then expand the operating range around those skills.

Become more comfortable with data.
Not simply reading dashboards, but questioning what the numbers mean and where they may be incomplete.

Understand AI well enough to make decisions about it.
You don't have to know every tool. You should understand how major technological shifts might change your team's workflows and economics.

Learn to communicate trade-offs.
Operating a revenue organization means choosing between investments that may all look reasonable in isolation.

Work outside sales.
Build relationships with product, marketing, CS, RevOps and finance before you need something from them.

Keep your judgment.
More intelligence doesn't mean every decision should become automated.

The CRO role isn't becoming less about sales.

It's becoming more about the system that creates sales.

And the executives who adapt to that shift won't just know how to manage a revenue team.

They'll know how to operate a revenue engine.