GCC e-commerce brands rarely lack traffic. What they lack is the infrastructure to turn that traffic into measured, defensible revenue — catalog content that ships before the campaign window closes, campaign creative that can match peak-season velocity, and reporting that distinguishes gross orders from money that actually cleared after returns and COD rejections. I build the AI marketing systems that deliver all three.
My name is Ahmed Ayoutty. I spent 13 years building marketing for the Saudi market and ran three agency groups before moving full-time into AI-native marketing infrastructure. I work fully remotely across the GCC and the US. I am not an agency adding a retainer to your stack; I build the system, hand you the controls, and report numbers you can defend to a founder or a board — gross and delivered, always both.
The real pain in GCC e-commerce is not reach. Meta and TikTok and Google Shopping can put products in front of millions of people in a week. The problems are faster and more expensive:
Catalogs outrun the team. A brand with 500 SKUs and a new collection dropping every month cannot write bilingual Arabic-English product copy by hand at launch speed, so either the copy is thin, the Arabic is missing, or both. Seasonal campaigns — Ramadan, National Day, DSF, 11.11 — require creative, audience segments, and landing-page copy to be ready weeks in advance, but the brief-to-publish cycle still runs through a human bottleneck that breaks under pressure. COD markets — still significant in Saudi Arabia and Egypt — mean a meaningful share of “sales” are never actually collected: the order ships, the customer refuses delivery, and the gross-ROAS number on the dashboard still looks fine. And when campaign post-mortems happen, the conversation is almost always about cost per click or ROAS at the ad-platform level, never about which spend produced revenue that cleared the bank.
None of that is fixed by a better creative agency or a bigger media budget. It is fixed by building a system around the spend.
I do not sell “an AI tool.” I build a small set of agents that each own one job in your funnel, wired to your catalog, your ad platforms, and your order management system, with a human keeping editorial and approval control. In practice that is five roles working together:
Monitors category trends, competitor positioning, trending search queries by market, and the seasonal content calendar — so every campaign and product page starts from evidence, not a blank brief.
Turns a product data sheet or SKU spec into bilingual listings, category page copy, ad creative briefs, and email segments in minutes — Arabic written as Arabic for GCC audiences, not machine-translated as an afterthought.
Checks every draft against brand voice, factual product data, prohibited claims, and platform-specific policies before anything reaches publish or goes live in an ad set.
Stages approved content across channels on the campaign calendar, manages seasonal batch-publishing at peak periods, and flags scheduling conflicts before they become live errors.
The fifth role is the measure agent: it reconciles ad-platform ROAS and gross order value against your OMS and payment gateway records to surface the two numbers that matter — gross revenue and collected revenue after returns and COD rejections. That is the number most e-commerce dashboards quietly leave out, because it is always smaller than the headline ROAS.
I have a documented e-commerce result I can point to directly, from a COD-market DTC brand.
A DTC store operating in a cash-on-delivery market ran WhatsApp and Messenger commerce at scale. The result was 137,000 EGP of ad spend turned into 564,000 EGP of gross orders — a 4.1× gross ROAS — and a 1.9× delivered ROAS after accounting for returns and refused COD orders. Both numbers are in the case study because the honest number is what matters operationally: gross tells you whether the creative and targeting worked; delivered tells you whether the business model works.
The transferable lesson for GCC e-commerce and retail: COD and high-return categories require a reporting discipline that most platforms do not default to. Building the measure agent into the system from day one means the team is making decisions on collected revenue, not on a dashboard number that flatters the ad spend.
Picture a GCC fashion retailer with 800 active SKUs, a new collection every six weeks, and Ramadan three months away. The marketing team of four writes product descriptions manually, publishes Arabic copy a week after English (if at all), and builds campaign briefs in a shared Google Doc that arrives late to the creative team. When Ramadan launches, everyone is reactive: briefs are rushed, the Arabic landing pages are thin, and the post-campaign report shows a strong platform ROAS that nobody trusts because they know returns ran high.
With a system in place, the draft and QA agents process the new collection the day assets arrive from the buyer — bilingual, brand-consistent, platform-ready. The seasonal campaign calendar is pre-loaded with brief templates; the draft agent fills them from research outputs two weeks before the creative team needs them. After launch, the measure agent pulls gross orders and delivered revenue from the OMS side by side, so the Ramadan post-mortem is about what the system actually earned, not what the platform reported.
That is the shape of the work. The exact gains depend on your catalog size, your team, and your data infrastructure — which is why I scope before I promise.
E-commerce marketing in the Gulf does not need another agency with a retainer and a content team to feed. It needs deep AI marketing capability you can switch on for a defined build, then own. Remote means you pay for the system and the judgment, not the overhead — and it means I am not locked into one market’s platform norms. I have built bilingual content systems for brands selling across Saudi Arabia, the UAE, and Kuwait simultaneously, and I understand the differences in buyer behaviour, platform weighting, and COD exposure between markets.
I can also plug into an in-house e-commerce team or an existing performance agency without displacing what is already working. The deliverable is a working system and a team that knows how to run it, not a dependency.
Around them, not instead of them. Performance campaigns bring the traffic; the system makes that traffic faster to brief, cleaner to publish, and honest to measure. The biggest gap in most e-commerce setups is between the ROAS reported by ad platforms and the revenue that actually cleared after returns — that is where the measure agent earns its place.
That is exactly the use case the draft agent is designed for. Static catalogs do not need AI. It is the high-velocity, bilingual, multi-channel catalog — new SKUs weekly, seasonal variants, Arabic and English copy needed simultaneously — where the system pays for itself quickly, because the alternative is either a large content team or thin, delayed copy.
It starts with a scoped diagnostic, then a defined build with clear milestones — typically four to ten weeks depending on catalog size, channel count, and existing data infrastructure. Fractional strategy retainers run monthly for teams that want ongoing direction. I do not do open-ended retainers without deliverables.
A Ramadan campaign brief that always ships late, product pages that are live in English but not yet in Arabic, or a ROAS number you do not fully trust. We will figure out what to build, what it should measure, and whether I am the right person to build it.
Request a diagnostic →