Most digital teams in the GCC are cost centres pretending to be growth engines, and the diagnostic for which one you have takes 20 minutes.
I scaled a digital function inside a GCC enterprise from zero contribution to 33% of total organisational revenue. I did not do it with a bigger budget, a bigger team, or a louder agency. I did it by refusing, from day one, to treat the function as a cost line. Everything that followed was downstream of that single decision.
Cost centre or digital function revenue engine: the structural distinction
A cost centre produces activity. A revenue engine produces a number. The distinction is not semantic. It governs how the function is structured, what it reports, who it hires, and how it is funded. Cost-centre digital functions report impressions, sessions, follower growth, “engagement”. Revenue-engine digital functions report pipeline, qualified opportunities, closed revenue, payback period, and lifetime value against acquisition cost. If your digital team’s monthly report leads with reach, you have a cost centre. If it leads with revenue contribution, you have an engine. Most GCC enterprise digital teams I have seen are running cost-centre dashboards while their CEOs assume they are running engines. That gap is where careers and budgets quietly die.
The three structural decisions that made 33% possible
The function I scaled hit 33% of revenue because of three decisions, made early, defended hard, and never reversed.
- Decision one: the function owned a number. Not a vanity metric. Not a soft contribution credit. A hard revenue number, pulled from the same finance system the CFO used, reconciled monthly. When you own a number, every decision downstream gets simpler. You hire against the number. You spend against the number. You cut what does not move the number. Most GCC digital functions are funded against budget, not against outcomes. That is the original sin.
- Decision two: attribution was built before campaigns ran. I refused to spend a meaningful budget until I could trace every dirham through to a deal. That meant six weeks of unsexy work installing tracking, defining stages, integrating CRM, and documenting the model. Six weeks where the function looked slow. After that, every campaign had a defensible ROI. I have never met a GCC marketing team that built attribution first and regretted it. I have met dozens that skipped it and spent two years arguing about which channel “really” drove the deal.
- Decision three: I refused vendor-led strategy. Agencies and platforms in this region are exceptionally good at convincing CMOs that the next quarter’s strategy is whatever the vendor sells. The function I built had a strategy that pre-existed any vendor conversation. Vendors fit into the strategy or they did not get a contract. That posture alone removed 60% of the wasted spend I see in peer organisations.
Why most GCC digital hires fail to produce revenue
The hiring market in the region produces three archetypes that struggle to deliver revenue. The agency-trained operator who has run campaigns but never owned a P&L. The brand-trained operator who can produce beautiful work but cannot trace a dirham to a deal. The platform-certified operator who knows the tool but not the business. None of these hires is incompetent. They are mismatched. A revenue-engine function needs operators who think in unit economics first and creative or platform second. Those operators are rarer in this market and command a premium, and most enterprises baulk at the salary because the JD was written for an activity hire, not an outcome hire.
The fix is not to find a unicorn. The fix is to design the role around the number first, then write the JD, then go to market. Most GCC enterprises do this in reverse: they write the JD around historic responsibilities, hire to it, and then ask the new hire to produce revenue the role was never structured to produce.
The 20-minute diagnostic
If you are a CEO or CMO and you want to know which kind of function you have, run this diagnostic. It takes twenty minutes.
One. Ask your head of digital what their revenue contribution was last quarter, in absolute dirhams, reconciled to finance. If the answer involves “branded search lift” or “awareness uplift”, it is a cost centre.
Two. Ask to see the attribution model. Not the dashboard. The document that defines what counts as a digital-influenced deal. If it does not exist as a written, signed-off document, you do not have attribution, you have a story.
Three. Ask what gets cut first if budget is reduced 30%. A revenue-engine head will name the lowest-ROI line items in seconds because they are already ranked. A cost-centre head will say “we would need to discuss” because nothing is ranked.
Four. Ask how the function decides what to build next. If the answer is “we follow the brand calendar” or “we react to campaigns”, it is a cost centre. If the answer is “we model the next dirham of revenue and back into what produces it”, it is an engine.
Five. Ask the CFO whether they would describe the function as an investment or an expense. The CFO’s posture is the truest signal. CFOs do not pretend.
If the function fails on three or more of these, you are running a cost centre with growth-engine ambitions, and the gap will not close on its own.
The fix is structural, not motivational
The temptation, when this diagnostic returns badly, is to motivate the team harder, hire a coach, run a workshop, or replace the head. None of that fixes the underlying architecture. The fix is structural. Reset the function around a number. Build attribution before campaigns. Remove vendor-led strategy. Re-write the head-of-digital JD around outcomes, not activities. Re-pace hiring against the new design. The function that emerges twelve months later will not look like the one you have. It will look like a P&L line that earns its budget, defends its margin, and asks for more.
Thirty-three percent of revenue is not the ceiling. It is what happens when you take the structural decisions seriously for three consecutive years. Most GCC enterprises will never test that ceiling because the structural fix requires admitting that the current function was designed for a different game. That admission is the actual cost of the transformation, and it is paid in conversation, not in budget. Naumaan Khan is a Digital Growth and Transformation consultant in Muscat, Oman. He builds AI-native growth systems for enterprise organisations across the GCC.