Why aren’t sales and marketing in the same office, at the same table? That question followed me through my first management role. Both teams were chasing the same prospect, the same pipeline, the same customer — and describing it in two different languages. Marketing talked awareness, engagement, brand equity. Sales talked quota, close rate, deal velocity. Same destination, different maps.
Revenue Operations gave that instinct a name. It confirmed what the divide had always been: not a fact of organisational life, but a design choice — and an increasingly expensive one, especially in a region where marketing and sales teams are being asked to move at GCC speed without a shared operating model to move on.
The cost of running two languages
Customers don’t experience an organisation through departments. They experience one continuous journey. Most businesses still manage it through functions with different metrics, different incentives, and different definitions of a win.
Marketing gets measured on reach and lead volume. Sales gets measured on closed revenue. Both metrics are valid in isolation. Together, they drive opposite behaviours — volume against conversion — and the pipeline pays for it.
Add disconnected data, fragmented handovers, and compensation structures that reward activity over outcome, and misalignment stops being a communication problem. It becomes a structural one.
RevOps doesn’t try to align two functions that were built apart. It dissolves the boundary — marketing, sales, and customer success operating on shared data, shared process, shared accountability for revenue. Marketing stops being the lead-supplier upstream of sales. It becomes a function directly accountable for commercial outcomes.
Independent research keeps landing on the same conclusion: businesses that run marketing and sales as one revenue system consistently outgrow those that run them as two. The exact figures shift by study and year, but the direction never does.
RevOps isn’t a universal prescription. Early-stage companies, small teams, low-touch B2C — the governance can cost more than it returns. The real test is complexity: multiple funnels, multiple teams, multiple handoffs. Revenue is always a system. How formally that system needs managing simply scales with the business itself.
The harder problem: who actually leads it
Here’s what doesn’t show up in most RevOps playbooks. Across the region’s larger organisations, combined sales-and-marketing functions are more often led by someone fluent in pipeline and forecast than someone fluent in brand and positioning. That’s not a criticism of sales leadership. It’s a structural pattern — and a costly one, particularly for agencies and brand teams whose value is hardest to defend in numbers a sales-fluent leader instinctively trusts.
A leader who can’t fully read marketing’s language tends, without intending to, to narrow it down to “lead supplier for sales.” The function stays in the room. Its logic doesn’t always make it into the decision.
I call this: marketing missing in translation.
Shared dashboards don’t fix it. A shared KPI doesn’t make a sales-fluent leader fluent in marketing’s logic, or the reverse. What fixes it is leadership and governance that’s genuinely bilingual — able to translate marketing’s contribution into commercial terms without flattening it into sales vocabulary.
The shift that actually matters
Sales versus marketing was always the wrong framing. Revenue isn’t a sequence handed from one department to the next, and it isn’t a baton passed between runners in a relay race. It’s a system. Misalignment isn’t what happens when teams disagree — it’s what happens when an interconnected system is run like a sequence of separate steps.
The question I carried into my first management role was really a question about system design, long before I had the language for it. What I didn’t have a name for yet was the deeper problem underneath: even when the table is shared, the languages spoken across it often aren’t.
Because revenue rarely stalls inside the systems. It’s lost in translation between them.
By Mohamed Hassan Abukashawa, CIM MCIM Member.
