Product · 11 August 2026 · 7 min
Building bilingual from day one: what Arabic-first really requires
Translation is the cheapest part. Mirroring, type, numerals and forms are where bilingual products break.
Ask five Dubai studios what an MVP costs and you will get five numbers between AED 30,000 and AED 400,000. That spread is not a market failure. It is what happens when the word "MVP" is doing too much work.
Here is what the number is actually made of.
For a first version that real customers can use — accounts, a core workflow, payments if you need them, and an admin view so you can run it — expect AED 80,000 to 150,000 in 2026, excl. 5% VAT.
Below AED 50,000 you are buying a prototype: something that demos well and cannot take a real customer. Above AED 200,000 you are usually buying either genuine complexity, or a team that has not cut the scope.
Every hour spent building is downstream of a decision. The single biggest cost driver is how many decisions are still open when the build starts.
A project with a settled scope moves at roughly twice the speed of one where screens are still being argued about in week 4. Not because anyone works harder, but because rework disappears. If you take one thing from this article: pay for the scoping, then hold the scope.
A senior developer in Dubai costs roughly two to three times a junior. They also finish the same feature in a fraction of the time, and leave behind something a second person can pick up.
Agencies that quote low usually staff low. The saving is real on the invoice and imaginary in practice, because you pay it back in the second month, and again when you hire someone to take it over.
An English-only product costs less than a bilingual one — but the gap is much smaller than people assume, if Arabic is planned from day one. Roughly 10–15% extra.
Retrofitting Arabic after launch costs far more, because right-to-left is a layout property, not a text property. Every hardcoded margin, every icon that points somewhere, every date format, every form gets revisited. See our note on what Arabic-first really requires.
Taking money in the UAE adds real work: a gateway integration, tested failure paths, and refunds. Budget AED 10,000–20,000 on top for a straightforward integration, more if you need instalments or multi-currency.
When you compare two proposals, check four things before you compare prices:
These are real and they are yours, whoever builds the product:
Sometimes, yes. If you are testing whether anyone wants the thing at all, a no-code tool and a landing page will answer that in a fortnight for a few thousand dirhams. Do that first if the demand is the open question.
No-code stops paying off at a predictable point: when you need a data model that does not fit the tool, when per-record pricing overtakes the cost of building, when you need real control over performance, or when a buyer or investor asks what exactly you own. Most teams hit one of those in the first year of real usage.
The mistake is not starting with no-code. The mistake is rebuilding twice — once badly in a tool that was never going to hold it, then again properly under time pressure. Decide up front which question you are answering: does anyone want this, or can we run this as a business.
Take a marketplace connecting two sides — the shape we see most often. A realistic first release is:
That is roughly 14 to 18 screens once you count the empty states, the error states, and the admin. At Dubai senior rates in 2026 it lands between AED 90,000 and 130,000, built and launched.
Strip the payment and the admin view and you are near AED 60,000 — but you have also built something you cannot operate, which is usually a false economy.
In order, from largest effect to smallest:
Notice that four of the five are scope decisions, not technology decisions. That is the point: the number is mostly a function of what you decide to build, and only slightly a function of who builds it.
Write one page before you talk to anyone. Not a spec — a page. What it does, who it is for, what happens on the very first screen, and how you will know in month two whether it worked.
Then ask for a fixed price against that page, plus a written list of what is excluded. A studio that cannot give you one is telling you the scope is not settled yet, which is useful information on its own.
Our own starting prices are on the pricing page, in AED, with the exclusions written down. If your page does not fit seven weeks, we will say so before you pay anything.
Send a short brief. We reply within one business day, Sunday to Thursday.
Product · 11 August 2026 · 7 min
Translation is the cheapest part. Mirroring, type, numerals and forms are where bilingual products break.
Product · 28 July 2026 · 6 min
Seven weeks is a constraint, not a slogan. Here is what it buys, and the projects we turn down.