Saudi Arabia & the Gulf · Remote from Istanbul

UI/UX Design & Front-End Development for Saudi and Gulf Businesses

I design and build Arabic and English websites and digital products for companies in Saudi Arabia and the wider Gulf, working remotely from Istanbul. Design and front-end come from the same person, the Arabic version is designed in Arabic rather than mirrored from English, everyday communication runs on WhatsApp in Arabic or English, and the scope is agreed in writing before any build work starts. There is no office in Saudi Arabia and none is claimed. Two of the projects on this site were delivered for Saudi companies, and both are live today.

Yes, Saudi companies can work with me remotely

Istanbul is one to two hours behind Riyadh, so the working day overlaps almost completely — no overnight gap waiting for a reply. Companies in Riyadh, Jeddah, Dammam or anywhere else in the Kingdom work with me the same way a local supplier would be managed: WhatsApp for day-to-day questions in Arabic or English, calls when a decision needs a conversation, and every agreement confirmed in writing so nothing important lives only in a chat thread. Payments are handled in USD, split across project phases. The one thing that is different from hiring locally is that meetings happen on a screen instead of in an office.

Which Saudi companies this fits

  • Service and contracting companies whose clients judge them by the website before the first call
  • Companies whose customers decide on a phone, in Arabic, and whose current site was clearly built for desktop
  • Businesses whose Arabic site was translated from English rather than designed, and reads that way
  • Companies replacing a WhatsApp-and-spreadsheet booking or enquiry process with a real digital journey
  • Businesses presenting to Arabic-first customers and English-reading partners or investors at the same time
  • Software teams in the region with backend capability that need product design and front-end craft

Delivered for Saudi companies

ONE PASS (onepassevent.com) is a delivered project for a Saudi event execution company: a bilingual English/Arabic site with full RTL support, built to work as a credibility document for clients evaluating the company and for candidates browsing careers. KH Agilearch (kh-agilearch.com), the website of Smart Architect / المعماري الذكي, is a delivered project for a contracting company based in Riyadh that works in construction, facility management and industrial services across Saudi Arabia: a responsive Next.js corporate site presenting a broad, multi-division service list in one clear structure. Both case studies state exactly which parts were designed and built here and which content came from the client. Beyond those two engagements, Mo Al-Asala (moalasala.com) is a bilingual AR/EN storefront with RTL throughout — my own brand rather than a client project, which is worth stating plainly. No traffic, ranking or sales figure is published for any project on this site, because none has been independently verified.

How Arabic and English are handled

The common failure in bilingual Saudi and Gulf products is an English product with an Arabic layer bolted on: navigation running the wrong way, forms fighting the input, dates and numbers behaving oddly, Arabic typography too tight to read comfortably. Your customers notice it immediately, even when they cannot name what is wrong. Both directions are designed here from one component system, with direction set in the HTML and handled through logical CSS properties, per-language URLs, correct hreflang and self-referencing canonicals. The result is one product in two languages instead of two sites drifting apart. Arabic copy is written in Arabic, not machine-translated. The reasoning is set out in full on multilingual and RTL product design.

What an engagement includes

  • Discovery and product direction: who your customers are and what they are actually trying to complete
  • User flows, information architecture and wireframes agreed before any visual design
  • Responsive UI design in Figma as a component system, including empty, loading, error and success states
  • Arabic RTL and English LTR designed together, not retrofitted afterwards
  • Production front-end in React or Next.js, built API-ready for your existing backend or booking system
  • Technical SEO, GEO and AEO foundations built into the site, never sold as a ranking promise
  • Analytics events planned so enquiries and drop-off can be measured after launch
  • Launch preparation: cross-device checks, a performance pass, and a checklist actually worked through

Where projects start, in numbers

Engagements are priced in USD around the outcome, not by page count. A paid UX and product audit starts from $600 and ends in a written product direction document. UI/UX product design starts from $1,500. Design-to-launch, which covers direction, design and production front-end in one engagement, starts from $2,500. Larger booking platforms, dashboards and multi-role systems are scoped custom after discovery, because quoting a fixed price before understanding the product is how projects go wrong. Final scope and price are confirmed in writing after discovery, and nothing starts on a verbal scope.

What happens after you get in touch

  • You send the website link or the idea in a few lines, on WhatsApp or through the contact form, in Arabic or English. No long brief needed.
  • You get a reply with what it needs, whether it is a fit for how I work, and the expected starting range — including when the honest answer is that you need less than you thought.
  • If it fits, a short discovery conversation defines the real scope, timeline and price, confirmed in writing.
  • Work starts in phases, each ending in something you can review, with progress on WhatsApp or email, whichever you prefer.

Beyond Saudi Arabia

Availability covers the UAE, Qatar, Kuwait, Bahrain and Oman on exactly the same remote basis, alongside clients in Turkey and Europe. The distinction worth keeping clear is between availability and evidence: the delivered client projects in the Gulf today are the two Saudi ones above. The rest of the portfolio documents Arabic, RTL and bilingual work rather than other Gulf clients.

Frequently asked questions

Do you have an office in Saudi Arabia?

No. I am based in Istanbul, Turkey, and every Saudi and Gulf engagement runs remotely. No office, branch or local presence in Saudi Arabia or any other Gulf country is claimed. In practice the time zones overlap by one to two hours, so the working day is effectively shared, and communication runs over WhatsApp, calls and written scope documents.

Which Saudi projects have you actually delivered?

Two, both live: ONE PASS (onepassevent.com), a bilingual English/Arabic site with full RTL for a Saudi event execution company, and KH Agilearch (kh-agilearch.com), the site of Smart Architect, a Riyadh-based contracting company working in construction, facility management and industrial services across Saudi Arabia. Each case study states exactly what was designed and built and what came from the client. No traffic, lead or ranking figures are published, because none has been independently verified.

Can you work in Arabic?

Yes. Arabic, English and Turkish are all working languages, for client communication and for the interfaces themselves. Arabic RTL product design is a core specialty rather than an add-on, and the Arabic version of this website is written in Arabic rather than machine-translated from the English.

How do payments and contracts work across countries?

Scope is agreed in writing before build work starts, with pricing in USD and payment split across project phases. Nothing begins on a verbal scope, which protects both sides in a remote engagement more than any contract clause does.

Do you work with Gulf businesses outside Saudi Arabia?

Yes, availability covers the UAE, Qatar, Kuwait, Bahrain and Oman on the same remote basis. To be precise about evidence rather than availability: the delivered Gulf client projects so far are the two Saudi ones, ONE PASS and KH Agilearch. The rest of the portfolio documents Arabic, RTL and bilingual work rather than other Gulf clients.

Is a separate Arabic website needed, or one bilingual site?

One product with per-language URLs, in almost every case. Separate sites drift apart: content updates land on one and not the other, and search engines end up with two partial products instead of one complete one. A single codebase with per-language routes, correct hreflang and direction-aware components keeps both versions equal.

Can you guarantee we rank in Saudi search results?

No. What is delivered is the structural layer that makes a product readable to search engines and AI systems: semantic HTML, correct headings, canonicals, hreflang, structured data matching visible content, sitemap and fast mobile pages. Rankings depend on competition and demand outside any provider’s control, and any provider guaranteeing them is guaranteeing something they do not control.

Building for Arabic and English customers in Saudi Arabia?

Send your website link or your idea, in Arabic or English. You get a straight answer on what it needs, whether it is a fit, and the expected starting range.