Every time I open LinkedIn, I get the impression that everyone has their go-to-market operations figured out.

  • CRMs are optimized.
  • Sales processes are streamlined.
  • Reporting is automated.
  • AI agents are prospecting, qualifying, forecasting, and apparently doing everything in between.

The modern revenue engine seems to be running itself.

And yet, having spent years working across Revenue Operations, Sales Operations, and GTM infrastructure, I can't help wondering what things actually look like under the hood.

Because there's a fundamental difference between implementing operational capabilities and maintaining operational excellence.

And I suspect many organizations are investing heavily in the former while struggling with the latter.

The operational reality rarely makes it onto LinkedIn

In most companies, operations have evolved organically over time, and few of them are fundamentally broken.

  • A CRM implemented three years ago, when the company had half the sales team.
  • A sales process designed around a business model that has since changed.
  • Reporting built on definitions that different departments interpret differently.
  • A forecasting methodology that works reasonably well, provided someone spends several hours manually validating the numbers before the executive meeting.
  • An integration that was supposed to be temporary but somehow became business-critical.
  • Or my personal favorite: a Google Sheet that leadership checks first, before looking at the dashboards the BI team spent months building.

None of these problems is particularly unusual.

In fact, they're often the natural consequences of growth.

Businesses evolve faster than the processes and systems supporting them.

And because operational problems rarely announce themselves as major strategic risks, they accumulate quietly.

Until they start affecting business performance.

Revenue Operations is much bigger than the CRM

One of the persistent misconceptions about Revenue Operations is that it's primarily a technical or administrative function: CRM administration, reporting, workflow automation and data hygiene.

These are important responsibilities, but they're only part of the picture.

Modern Revenue Operations sits at the intersection of several business functions.

  • Sales Operations ensures commercial teams have the processes, tools, and structures they need to sell effectively.
  • Marketing Operations connects demand generation with the commercial pipeline and helps measure the effectiveness of marketing investments.
  • Customer Operations supports the processes governing onboarding, adoption, retention, and expansion.
  • Finance becomes involved through revenue recognition, billing, commercial forecasting, and the financial implications of how deals are structured.
  • People Operations intersects with sales compensation, organizational design, capacity planning, and performance management.
  • Product teams influence what can be sold, how it can be delivered, and whether customer expectations align with product capabilities.
  • And increasingly, IT and Security become critical partners as organizations introduce AI, new integrations, and automated decision-making into their commercial infrastructure.

Revenue Operations doesn't need to own all these functions, but it does need to understand how they interact.

Because revenue performance is rarely determined by one department operating in isolation.

A perfectly executed sales process means little if the business cannot deliver what was promised. An excellent marketing campaign creates limited value if the leads it generates are not converted effectively. And a successful acquisition strategy can become expensive if customer retention is poorly managed.

Operational excellence requires looking beyond departmental boundaries.

The hidden cost of operational inconsistency

Consider a relatively simple question:

Can your leadership team trust its revenue forecast?

For many companies, the answer is more complicated than it should be.

Maybe the opportunity stages are inconsistently applied. Or sales representatives interpret probability differently. Or expected close dates are updated based on gut feeling rather than customer commitment.

Perhaps renewals, expansions, and new business follow different processes, but their forecasts are combined without sufficient distinction.

The immediate symptom is an unreliable forecast.

But the underlying problem usually sits in the operational system that generates the information.

And the consequences extend far beyond an inaccurate dashboard.

Leadershipmakes hiring decisionsbased on expectedrevenueFinanceplans cash flow andinvestmentSales managementallocates resourcesMarketingadjusts spendingWhen the underlyinginformation isunreliable, everysubsequent decisionbecomes moredifficult.
  1. Leadership makes hiring decisions based on expected revenue
  2. Finance plans cash flow and investment
  3. Sales management allocates resources
  4. Marketing adjusts spending

When the underlying information is unreliable, every subsequent decision becomes more difficult.

The same applies to other operational weaknesses.

  • Poor handovers between Sales and Customer Success create friction during onboarding.
  • Inconsistent qualification wastes sales capacity.
  • Unclear ownership creates delays within the Customer Journey.
  • Disconnected systems require manual reconciliation.

Individually, these problems might seem manageable.

Collectively, they create an operational tax on the entire business.

And that tax grows as the organization scales.

So what happens when we add AI to the equation?

The interesting thing is that none of this is particularly new.

Companies have struggled with inconsistent processes, unreliable reporting, and disconnected systems long before AI entered the conversation.

What's changing is the speed at which we're introducing new technology into these environments.

We're investing in automation, AI agents, predictive forecasting, and increasingly sophisticated GTM tools.

But here's what I keep wondering:

What happens when we start automating processes we haven't properly designed, feeding AI with data we don't fully trust, and scaling operations we haven't taken the time to understand?

And perhaps more importantly, can better technology compensate for weak operational foundations?

I have some thoughts on that.

I'll post about that next.