UAE pricing, and what the Gulf genuinely adds to a build

Most UAE quotes are priced as though the market were a single language market with a different currency, and that is where the number goes wrong. Arabic is not a translation line at the end of a project, it is a second design direction, a second content set and a second round of testing, because right to left changes layout rather than just text. Add VAT and TRN requirements on invoices, multi-currency selling across the Gulf, and the difference between free zone and mainland trading, and you have several cost lines that simply do not exist elsewhere. This page sets out each of them.

Bilingual is the word that does the most damage in a UAE scope, because it sounds like a setting and behaves like a second project.

A site quoted in English and later made bilingual is usually rebuilt rather than extended. Right to left is not a stylesheet toggle: it inverts layout, navigation, form alignment, icons that imply direction, and the reading order that the whole design was composed around. Typography has to be chosen for both scripts, since a font that carries an English brand well may have no usable Arabic companion. Doing this from the start is a moderate addition. Doing it afterwards frequently means starting again, and that is the single most expensive mistake available in this market.

Who this is for

When this work makes sense

  • Businesses in the UAE selling to a genuinely bilingual audience
  • Companies trading across the GCC in more than one currency
  • Anyone quoted for an English site and told that Arabic can be added later
  • Retailers handling cash on delivery who need the return costs in the model
How to choose

Questions worth asking any supplier

Whether Arabic is in scope now or later. Later is not a smaller decision, it is usually a larger one, and it belongs in the first conversation rather than the second phase.

Whether you are free zone or mainland, which affects invoicing, VAT treatment and in some cases what you may sell and to whom.

Whether you hold a TRN, since invoices and the tax lines on them differ depending on your registration status.

Which currencies you actually need to present and settle in, which are frequently not the same list.

Whether content exists in both languages or only one, because translation of existing copy and writing fresh Arabic copy are different pieces of work at different costs.

What you get

Deliverables

A bilingual architecture from the first design, with right to left treated as a layout requirement rather than a late setting

Typography selected to work in both scripts, rather than an English face with an Arabic fallback nobody chose

VAT shown at the applicable rate with our TRN on every invoice, and yours recorded where you hold one

Invoicing in AED, with other currencies quoted where the engagement requires it

Currency presentation configured for the markets you actually sell to, separate from the currency you settle in

Testing on both language versions, which is two passes rather than one

Full transfer of code, domain, hosting and analytics access on completion

How we work

Process

UAE projects run the language decision first, before design begins, because it is the decision that constrains everything after it. Where both languages are in scope, the design direction is produced and reviewed in both from the outset, so nobody approves an English composition that Arabic will later break. Where only English is in scope for now, the build is still structured so that Arabic can be added without a rebuild, and we say plainly what that preparation costs and what it saves, so the choice is made with the numbers visible rather than as an assumption.

The standard nine stages, discovery, strategy, UX/UI, development, content and SEO, testing, launch, measurement and continuous improvement, apply to every project. The paragraph above is what differs for this one.

Pricing

What moves the number

Pricing depends on scope, functionality, integrations and content requirements. These are the factors that change it most:

  • Whether Arabic is included, which affects design, content, typography, testing and timeline rather than a single line item
  • Whether Arabic content is being translated from existing English or written fresh, since fresh writing costs more and usually reads better
  • Number of currencies presented, and whether settlement happens in one currency or several
  • Payment gateway choice, since Gulf gateways differ substantially in fees, settlement periods and supported currencies
  • Whether the business is free zone or mainland, which can affect hosting, invoicing and compliance requirements
  • Cash on delivery handling if you sell physical goods, which carries return to origin costs that belong in the model rather than as a surprise
Comparison

Three ways to handle Arabic, and what each one costs later

Bilingual from the first design

Fits: Any business whose customers genuinely read Arabic

Limits: A meaningful addition to design, content and testing at the start, and the cheapest of the three overall

English now, Arabic later

Fits: Only when the build is structured for it deliberately and you accept the preparation cost

Limits: Without that preparation it usually means rebuilding the front end, not extending it

English only

Fits: B2B and free zone businesses whose buyers genuinely work in English

Limits: Closes off a large part of the local audience, and reopening it later is the expensive path above

Proof

Case studies

No client figures are published here. What can be pointed at is the team's existing practice in local search and Google Business Profile work, and the bilingual and right to left architecture described on this page, which is the approach the UAE pages themselves are built on.

MBGDesk operates from 4 offices in India, United States, United Kingdom, United Arab Emirates. We hold no industry certifications and do not imply otherwise.

Questions

Frequently asked questions

How much does adding Arabic cost?

It depends on whether it is designed in from the start or added afterwards, and the gap between those two is large enough that it is the first thing worth deciding. Built in, it is a meaningful addition to design, content and testing. Retrofitted onto a site composed entirely in English, it frequently means rebuilding the front end, which is why this page leads with it.

Do you charge VAT?

VAT is shown at the applicable rate as a separate line, with our TRN on the invoice. Treatment can differ depending on your registration status and whether you are free zone or mainland, so we state the position for your engagement rather than assuming one. Your own adviser should confirm what applies to you. Nothing here is tax advice.

Can you invoice in AED?

Yes, and it is the default for UAE engagements. Other currencies can be quoted where the engagement requires it, and the currency you are invoiced in is a separate decision from the currencies your site presents to customers.

We sell across the GCC. Does that change the price?

It can. Presenting several currencies is straightforward. Settling in several, handling country specific payment methods, and managing delivery and returns across borders are each real work, and they are priced separately rather than folded into a single multi-currency line that hides which part is expensive.

Does being in a free zone change anything?

It can affect invoicing, VAT treatment and occasionally hosting or compliance requirements. Tell us at the start, because it is straightforward to accommodate and awkward to discover after an invoice has been raised incorrectly.

Will the Arabic version be a machine translation?

No. Machine translation is visible to any native reader and it undermines exactly the credibility a bilingual site is built to establish. Arabic content is either written or professionally translated and reviewed, and that is a named cost in the quote rather than something absorbed silently.

Related

Talk to us about this

Tell us what you are trying to build and we will come back with scope, approach and an estimate.