Community suits
A standard requirement the included applications already cover, with someone to host and maintain it. Genuinely capable rather than a trial.
Enterprise Platforms · Odoo
Odoo in Dubai: editions, hosting, and the customisation trap
Community against Enterprise, where to host it, how UAE VAT is handled, and the customisation decisions that determine whether you can ever upgrade.
- 4.7 Google rating
- 200+ clients
- In Dubai since 2018
45 minutesto a fixed written quote
Odoo development in Dubai is attractive for a reason that is genuinely true: one system covering sales, inventory, accounting, purchasing and more, at a licence cost well below the enterprise alternatives, with an open source edition that costs nothing to licence at all.
It is also the platform where we see the most expensive mistakes, and they share one cause. Odoo is highly customisable, so it gets customised heavily, and heavy customisation is what makes an Odoo deployment impossible to upgrade. Businesses end up on a version years behind, unable to move, dependent on whoever wrote the code.
This page covers the decisions that determine which of those two outcomes you get. Editions, hosting, UAE specifics, and how much customisation is safe. We are not an official Odoo partner and will not describe ourselves as one; Odoo publishes its partner directory and any claim is checkable.
Editions
Odoo Community or Enterprise for Dubai development
A real decision with a real cost difference, and the answer is not automatically the free one.
Odoo Community is open source, carries no licence fee, and includes a substantial set of applications covering sales, inventory, purchasing, manufacturing basics and accounting fundamentals. It is genuinely usable, not a crippled demonstration version.
Enterprise for Odoo development in Dubai is licensed per user per month and adds applications, the mobile interface, Studio for building customisations without code, and official support. Odoo publishes the current comparison and the specifics move between versions.
The practical differences that decide it for most UAE businesses are accounting depth, which is noticeably fuller in Enterprise, the mobile interface if your people work away from a desk, and Studio, which materially changes who can make changes.
That last point deserves attention. Studio lets a capable non developer adjust forms, fields and simple logic without writing code, and changes made in Studio survive upgrades far better than custom modules do. For a business that expects to keep adjusting the system, this alone can justify Enterprise.
The argument that Community is free is true about licences and not about total cost. Someone still implements it, hosts it, maintains it and upgrades it. Choosing Community to avoid licence cost and then paying for extensive custom development to replace Enterprise features is a common and expensive route.
The honest Odoo development test in Dubai: if the gap between the editions can be closed with a few days of configuration, Community is reasonable. If closing it needs custom modules, pay for Enterprise.
Enterprise suits
Fuller accounting, mobile use, official support, and Studio. The last changes who can adjust the system and how well changes survive upgrades.
The false economy
Choosing Community for the licence saving then commissioning custom modules to replace Enterprise features. Common, and it costs more.
The main risk
Customisation, and why Odoo deployments in Dubai get stuck
This is the most important section on this page about Odoo development in Dubai. Odoo’s flexibility is its best feature and the source of nearly every failure we are called to look at.
Custom modules are written against a specific Odoo version. When a new version arrives, the standard upgrade path handles core data, and your custom code does not come along automatically. It has to be reviewed, reworked and tested.
The consequence compounds. A deployment with a little customisation upgrades with modest effort. One with a great deal faces a rework bill at every version, so the business defers, and after a few versions deferred the gap is large enough that upgrading becomes a project nobody will fund. At that point you are on an unsupported version, cannot take security fixes easily, and are dependent on whoever understands the custom code.
We have seen UAE businesses several versions behind for exactly this reason, paying to maintain something they cannot move.
The discipline that avoids it is unglamorous. Use standard Odoo first and genuinely live with it for a period. Where something must change, prefer configuration, then Studio if you have Enterprise, then a custom module only when nothing else will do. Every custom module should have a written justification, because at the next upgrade somebody will ask why it exists.
The question worth asking any Odoo supplier in Dubai is how they handle upgrades and what their customisations cost at version change. A supplier who has not thought about it is selling you the version you are on.
The Odoo customisation ladder
- Change the process to fit standard Odoo
- Configuration within the application
- Studio, on Enterprise, which survives upgrades better
- A custom module, with written justification
- Never core modifications
- Every customisation reviewed at each upgrade
Hosting
Hosting for Odoo development in Dubai
Three options with genuinely different consequences, and the right one depends on whether you have a systems administrator.
Hosting shapes every later Odoo development decision in Dubai. Odoo documents its options and the choice affects cost, control and who is responsible when something breaks at two in the morning.
Odoo Online. Fully managed by Odoo. No server administration, updates handled, backups handled. The trade off is that you cannot install custom modules, which makes it suitable for businesses running standard Odoo and unsuitable the moment you need code.
Odoo.sh. A managed platform that does allow custom modules, with staging environments and version control built in. For most UAE businesses that need customisation, this is the sensible middle, because you get custom code without owning the infrastructure.
Self hosted. Full control, lowest hosting cost, and every operational responsibility becomes yours: security patching, backups, restores, uptime, performance, upgrades. Appropriate if you have a systems administrator. Not appropriate because it looked least expensive on a spreadsheet.
Self hosting is where Odoo development projects in Dubai most often go wrong quietly. A business chooses it to save money, nobody is assigned to run it, and eighteen months later the server is unpatched, the backups have not been tested, and nobody is certain they could restore after a failure.
Two local considerations for Odoo development in Dubai. Server location affects performance for a Gulf audience, so a server far from your users adds latency to every screen in a system people use all day. And if your sector carries a data residency requirement, that may determine the hosting choice before anything else does.
Odoo Online
Fully managed, no custom modules. Right for standard deployments, wrong the moment you need code, and the constraint is absolute rather than negotiable.
Odoo.sh
Managed platform that permits custom modules, with staging and version control. The sensible middle for most Dubai businesses needing customisation.
Self hosted
Full control and full responsibility for patching, backups, restores and uptime. Choose it because you have an administrator, not because it looked least expensive.
Locally
UAE specifics for Odoo development in Dubai
Odoo is used widely across the UAE and a few local matters need settling during scoping rather than after.
VAT and the localisation. Odoo development in Dubai has to account for this first. There is a UAE localisation covering tax configuration and reporting. How completely it fits depends on your business, and invoices the system issues must carry what the Federal Tax Authority requires. Treat this as an accounting exercise your accountant signs off, not a configuration the implementer confirms alone.
Arabic. Odoo supports Arabic and right to left layout in the interface. The more frequent requirement here is customer facing documents in Arabic, quotations and invoices, which is a template exercise and is routinely discovered late. Raise it during scoping, because retrofitting Arabic templates after go live is more work than building them.
Multi company. Odoo handles multiple companies in one database, which suits UAE groups holding several licences across free zones and the mainland. It also complicates the accounting setup considerably, and it is worth deciding early whether you genuinely need one database or several.
Multi currency. Common here, supported, and the configuration decisions around rates and revaluation belong with your accountant.
The working week. Affects scheduling, leave calculations and any service measurement. Configure it rather than accepting a default built elsewhere.
Payroll. Check carefully. Payroll localisation varies by country and UAE specifics including gratuity and WPS handling need confirming against your actual obligations rather than assumed from the module list.
Settle during Odoo scoping
- VAT configuration, signed off by your accountant
- Arabic templates for customer facing documents
- One database or several, for a group structure
- Multi currency handling and revaluation
- The working week and leave calculation
- Whether payroll genuinely covers UAE requirements
Scope
Which Odoo applications to start Dubai development with
The platform’s breadth is the attraction and the trap.
Odoo development in Dubai covers a great deal, which tempts businesses into deploying everything at once. That is the single most reliable way to produce a project that runs late and lands badly.
The Odoo development approach that works in Dubai is to pick the one process that hurts most and deploy that properly. Usually it is sales and invoicing, or inventory, or purchasing. Get it live, let people use it for a couple of months, then add the next thing informed by what you learned.
This is more important on Odoo than on platforms with narrower scope, precisely because everything is available. A phase one of eight applications means eight sets of configuration decisions, eight sets of training, and eight places for the project to stall, before anyone has validated that the approach works at all.
The counterargument is that modules are interdependent and deploying in isolation causes rework. There is something in that, and it is usually overstated by whoever is selling the larger scope. Sales and invoicing together make sense. Sales, inventory, manufacturing, purchasing, accounting, HR and website in one phase does not.
One genuine sequencing constraint: accounting should go live at a sensible point in your financial year rather than mid period, because opening balances and part year reporting are awkward otherwise. Your accountant will have a view and it is worth asking before fixing a date.
One painful process first
Deployed properly and used for a couple of months. Everything else waits until there is real evidence about how the system behaves.
Pairs, not suites
Sales and invoicing together is sensible. Seven applications in phase one is eight places for the project to stall at once.
Time accounting carefully
Go live at a sensible point in the financial year. Mid period means awkward opening balances and split reporting.
Let use inform phase two
Two months of real work tells you more about what to build next than any workshop held before anything existed.
Choosing a supplier
Assessing an Odoo development supplier in Dubai
There are a great many Odoo development suppliers in Dubai and the quality range is wide, partly because the platform is accessible enough that a small team can start offering it quickly.
Ask about upgrades specifically. How they handle version changes, what their customisations cost at each upgrade, and whether they have actually taken a client through one. This question separates experienced implementers from the rest faster than anything else.
Ask to see their partner listing, if they claim one. Odoo publishes its directory. We are not listed and say so. The issue is not whether partner status is essential; it is that an unverifiable claim tells you about the rest of the proposal.
Ask what they would do with configuration instead of code. A supplier reaching for custom modules early is building you something that will be expensive at every future version.
Ask who owns the code. Custom modules written for you should be yours, in a repository you control. Modules a supplier retains are a dependency you cannot escape.
Ask about the database. Whether you can take a backup and move to another provider. With Odoo you generally can, and a supplier making that difficult is worth avoiding.
Ask who trains your administrator. Odoo rewards an internal person who understands it. A supplier uninterested in creating one is selling a permanent dependency.
Answers that should concern you
- No clear answer on how upgrades are handled
- A partner claim they will not evidence
- Custom modules proposed before configuration
- Ambiguity about who owns custom code
- Reluctance about database portability
- No plan to train anyone on your side
Sequence
What an Odoo project in Dubai actually involves
Five stages, and the data stage is the one that decides whether people trust the result.
Discovery. Odoo development in Dubai starts with the process as it actually runs today rather than as the manual describes it, who performs each step, and where it breaks. Output is a scope, and occasionally a recommendation that Odoo development in Dubai is not what you need, which is a real finding rather than a lost sale.
Configuration against standard. Building the process in unmodified Odoo and showing it to the people who will use it. This is the stage that reveals whether a requirement is genuine or merely habitual, and it saves far more than it costs.
Data preparation. Products, customers, suppliers, opening balances and stock. Almost always the longest stage, almost always underestimated, and entirely the client’s data to decide about. Dirty data imported into a new system destroys confidence in week one and is close to impossible to recover from.
Customisation, only what survived. Whatever configuration genuinely could not handle, built as proper modules with written justification, in a repository you own. Each one gets reviewed again at the next version.
Go live and settle. A defined date chosen with your accountant where accounting is involved, the previous system available for a period, and intensive support for the first weeks. Then a review at month three to define phase two from evidence.
The stage most frequently compressed is data preparation, because it feels like delay and produces nothing visible. It is the stage that determines whether the system is used.
Discovery
The process as it runs, not as documented. Produces a scope and sometimes an honest recommendation against proceeding.
Standard first
Built in unmodified Odoo and shown to real users. Reveals which requirements are genuine and which are habit.
Data preparation
The longest stage and the most underestimated. Dirty data imported on day one destroys trust that is hard to rebuild.
Then customise
Only what configuration genuinely could not do, justified in writing, in a repository you own, reviewed at every upgrade.
Cost
What Odoo development in Dubai costs
Odoo development in Dubai attracts people with the licence line and the licence line is the smallest of four, which is where expectations and reality separate.
Licences. Nothing on Community, per user per month on Enterprise, with Odoo’s published pricing varying by region and application count. Work from the current figure rather than a number in an old proposal.
Hosting. Odoo Online or Odoo.sh carry their own cost. Self hosting looks least expensive and carries the administration burden discussed above, which is a cost in someone’s time even when it is not an invoice.
Implementation. Normally the largest first year line, driven by how many applications, how much customisation and what condition your data is in. Two companies of the same size can differ by a multiple on data condition alone.
Ongoing. Support, administration, and the upgrade work that arrives with each version. The upgrade line is the one specific to Odoo and the one most often omitted, because at the time of purchase the first upgrade feels distant.
Ask any supplier what an upgrade will cost given the customisation they are proposing. A supplier who cannot answer has not planned for one, and that answer tells you more about the real cost of the project than the implementation quote does.
Against that, Odoo genuinely does replace several subscriptions for many businesses. Listing what you currently pay for separately is worth doing, because the offset is often substantial.
The four Odoo cost lines
- Licences, nothing on Community, per user on Enterprise
- Hosting, or the administration time if self hosted
- Implementation, driven by scope and data condition
- Ongoing support and administration
- Upgrade work at each version, priced in advance
- Minus the subscriptions Odoo replaces
Inheriting one
Taking over an existing Odoo system in Dubai
Frequently how Odoo development in Dubai begins, and the first question is what version you are on.
Businesses reach us running an Odoo somebody else built, usually because that supplier is unresponsive or the cost of staying with them stopped making sense. The assessment follows a specific order.
Which version, and how far behind. This single fact shapes everything. A system one or two versions back is routine. One several versions behind, with custom modules, is a project rather than a handover, and the honest estimate depends on reading the code rather than counting users.
What is customised and who owns it. Whether custom modules exist, whether they are in a repository you control, and whether anyone documented why they exist. Undocumented custom code written against an old version is the thing that makes an Odoo system expensive to inherit.
Whether core was modified. The worst case. Changes made directly to Odoo’s own code rather than in separate modules, which makes upgrading close to impossible without unpicking them first. Rare, and genuinely serious when found.
Where it is hosted and who has access. Self hosted on a server only the previous supplier can reach is a different conversation from Odoo.sh under your own account.
What the data looks like. Whether people have actually been using it properly, or whether half the fields are empty and the real work still happens in spreadsheets alongside.
The outcome is one of three: continue and upgrade, continue on the current version while planning a move, or rebuild on current Odoo and migrate the data. Only the assessment distinguishes them, and a supplier quoting before doing it is guessing.
Version first
How far behind you are shapes every other answer. One or two versions is routine; several with customisation is a project.
Custom code and ownership
In a repository you control, with documented reasons. Undocumented modules against an old version are what make inheritance expensive.
Check for core changes
Modifications to Odoo’s own code rather than separate modules. Rare, serious, and it has to be unpicked before any upgrade.
Afterwards
Running Odoo in Dubai once it is live
Odoo development in Dubai does not end at go live, and the ongoing routine is what separates a system still in use at year three from one quietly abandoned.
An internal owner. The same point as any business platform, and sharper here because Odoo is so configurable. Without someone deciding how it is used, configuration drifts, people add fields nobody agreed, and within a year the system reflects six different opinions.
A version policy. Decide how far behind you are willing to be, and hold to it. Odoo releases regularly, and the decision to upgrade is easier taken as policy in advance than as a debate each time with a growing backlog behind it.
Customisation under review. Every custom module reconsidered at each version. Some exist because standard Odoo lacked something that it has since added, and removing them is the least costly upgrade work available.
Backups tested by restoring. An untested backup is an assumption. Restore to a staging environment periodically and confirm the system actually comes up.
Data discipline. Duplicate customers and products accumulate quietly in any ERP and degrade reporting before anyone notices the reports are wrong.
Where this is absent, Odoo does not break dramatically. It drifts out of date, people build spreadsheets alongside it for the things it no longer does properly, and eventually somebody proposes replacing it, which starts the whole cycle again.
The ongoing routine
- A named internal owner with time allocated
- A stated version policy, decided in advance
- Every customisation reviewed at each upgrade
- Backups verified by restoring, not assumed
- Duplicate records checked periodically
- Phase two defined from real use
In short
The Odoo decisions in Dubai worth getting right
Five, and the first one accounts for most failures we are asked to fix.
Keep customisation to the minimum that works. This is the whole of the Odoo development risk in Dubai in one line. Every custom module is a cost at every future version, and the deployments that get stuck are the ones that customised early and heavily because it was possible.
Choose the edition on capability, not licence cost. Community to save money, then custom development to replace Enterprise features, costs more and upgrades worse.
Choose hosting on who will administer it. Self hosting is right when you have an administrator and wrong when you chose it on price. The responsibility does not disappear because nobody was assigned it.
Phase the rollout. One painful process first, properly, then the next informed by use. The breadth of the platform is the attraction and deploying all of it at once is the commonest cause of a stalled project.
Prepare the data properly. The stage everyone compresses, and the one that decides whether people trust the system from week one or quietly keep their spreadsheets.
If a system already exists and these were not followed, the position is recoverable more often than people expect. The assessment described above tells you whether you are upgrading, planning a move, or rebuilding, and those are very different costs with very different timelines.
The one situation worth treating as urgent is a deployment several versions behind with undocumented custom code and no internal owner. Every month that passes adds another release to the gap and makes the eventual move larger, while the people who understood the original build get further away. That is the one case where Odoo development in Dubai genuinely should not wait for a convenient quarter, because the cost of waiting is visible and compounding rather than theoretical. Getting the assessment done tells you how large the gap already is, which is worth knowing even if the work then waits. It is a few days of reading rather than a project.
Against the alternatives
Odoo compared with what else a Dubai business considers
Honest positions, including where this platform loses.
Odoo development in Dubai is rarely evaluated alone. These are the comparisons that come up.
Against Dynamics 365. Odoo development in Dubai covers more ground in one system at lower licence cost and is quicker to stand up. Dynamics goes deeper in each area, has a larger implementer market here, and integrates tightly with Microsoft tooling you may already run. If breadth at low cost is the constraint, Odoo. If depth and Microsoft integration matter, Dynamics.
Against SAP or Oracle. Those are enterprise systems for organisations with the scale and the internal team to carry them. For a UAE business under a few hundred people, they are usually more system than the problem requires, and Odoo is the more proportionate answer.
Against separate best of breed tools. A dedicated CRM, separate accounting software and a separate inventory tool, each better at its own job than Odoo’s equivalent. The trade off is integration: three systems that do not talk produce re entry and disagreement. Odoo wins on coherence rather than on any individual module.
Against accounting software plus spreadsheets. More defensible than vendors admit for a genuinely small operation. The signal to move is the same as always: the same information being entered in several places, and nobody able to answer a basic question without asking a colleague.
The comparison least worth having is Community against Enterprise framed as free against paid. They are the same platform with different capability, and the decision is about what you need rather than about licence cost.
Against Dynamics
Odoo for breadth at lower licence cost and faster deployment. Dynamics for depth and Microsoft integration. Both are reasonable answers.
Against SAP or Oracle
Those suit scale and an internal team. Below a few hundred people, Odoo is usually the proportionate choice.
Against separate tools
Each may be better alone. Odoo wins on coherence, because three systems that do not talk produce re entry and disagreement.
Against spreadsheets
Defensible while genuinely small. Move when the same data is entered in three places and nobody can answer simple questions.
Working with us
How we handle Odoo development in Dubai
The same structure whether it is a new deployment or a system we are inheriting.
We begin any Odoo development in Dubai by asking whether you should be on Odoo at all. For a meaningful share of the businesses that ask us, the answer is a smaller tool, and saying so costs us work and is the right answer.
Where Odoo fits, we configure standard first and show it to the people who will use it before anything is written as code. That stage settles more requirements than any workshop does, because people respond to a working screen rather than to a description.
Customisation is the last resort rather than the first move, and every module we write gets a written justification, lives in a repository you own, and is listed for review at the next version. You will also get our honest estimate of what each one costs you at future upgrades, because that is the number that matters and it is rarely quoted.
On data, we assess before importing and show you what we propose to discard. On hosting, we will tell you plainly whether self hosting suits your situation, and in most cases it does not. On UAE specifics, VAT configuration goes to your accountant for sign off rather than being confirmed by us.
We are not an official Odoo partner, we say so wherever it is relevant, and if partner status is a requirement for your procurement we will tell you we do not meet it rather than finding a form of words that implies otherwise.
You get a fixed written quote within 45 minutes during business hours once the scope is understood, and everything produced belongs to you.
We ask if you should
Often the answer is a smaller tool. Saying so costs us the work and it is the only useful starting point.
Standard before code
Configured and shown to real users first. People respond to a working screen in a way they never do to a requirements document.
Custom code is yours
In your repository, justified in writing, with an honest estimate of what it costs you at each future upgrade.
No partner claim
We are not listed in Odoo’s partner directory and will not imply otherwise. If that is a procurement requirement, we will say we do not meet it.
Adoption
Getting a Dubai team to actually use Odoo
Odoo development in Dubai meets its hardest problem here, because an ERP is the hardest kind of system to get adopted, because it changes how several departments work at once and the benefit is felt by the business rather than by the individual entering the data.
That asymmetry is the core problem and it is worth naming. The warehouse person scanning items carefully gains nothing personally; the finance team gets accurate stock figures. If the person doing the work sees no return, the data quality falls, and poor data is how an Odoo deployment in Dubai becomes something people work around.
Show people the output of their own input. Odoo development in Dubai lives or dies on this. The warehouse team seeing the stock report their scanning produces understands why it matters in a way no training session achieves.
Remove the old route. If the previous spreadsheet still exists and still works, a proportion of people will keep using it, and you will have two sources of truth permanently. Retire it on an agreed date.
Make data entry fast. Odoo can be configured to require a great deal at each step. Every mandatory field somebody does not understand is a reason to enter something false to get past it. Require only what is genuinely needed.
Train by department on their real work. Not a tour of the system. The specific sequence that person performs every day, in the system, with their own records.
Where a department resists hard, there is usually a requirement nobody captured. Hearing it during rollout is considerably better than discovering it in the shadow spreadsheet six months later.
Adoption checks
- Each team sees the output their input produces
- The previous system retired on a set date
- Mandatory fields limited to what is genuinely needed
- Training by department on their actual task
- Someone internal who answers day to day questions
- Resistance treated as a missing requirement
When Odoo development in Dubai is the wrong choice
If you need a CRM and nothing else, Odoo development in Dubai is more system than the problem requires. A dedicated CRM will be simpler to run than a full ERP platform, and Dynamics 365 or a lighter product is the better comparison.
If nobody will own it internally, do not start. This applies to any business system and it applies with particular force to a platform this configurable, because an unowned Odoo accumulates inconsistent configuration faster than a more rigid product would.
If your processes are genuinely unusual and you know they will require extensive custom code, understand what that means for upgrades before committing. Sometimes the honest answer is a purpose built system that was always meant to be bespoke, rather than a platform bent until it cannot move.
If you are a very small team and spreadsheets plus accounting software currently work, Odoo may be premature. The signal to move is when the same information is being re entered in three places and people cannot answer basic questions without asking a colleague.
Tell us which process is actually hurting and we will say what tier of answer it needs, including when that answer is smaller than Odoo or is not a system at all. Our team works with businesses across Dubai and the wider UAE in Arabic and English, and a fixed written proposal follows within 45 minutes during business hours with no obligation.
Straight answers
Frequently asked questions
Are you an official Odoo partner?
No, and we will not claim to be. We implement and develop on Odoo. Official partner status is a formal designation Odoo publishes, and any supplier claiming it can be checked on Odoo's own partner directory. Ask anyone who claims it, including us, to show you the listing.
What is the difference between Odoo Community and Enterprise?
Community is open source and free of licence cost, with a smaller set of applications. Enterprise is licensed per user and adds applications, the mobile interface, studio tools and official support. Odoo publishes a feature comparison, and the practical difference is usually fewer applications rather than a crippled core.
Why do people warn about Odoo upgrades?
Because heavy customisation is what makes upgrades painful, not Odoo itself. Custom modules written against one version frequently need rework for the next. A deployment that stays close to standard upgrades reasonably; one with extensive custom code can find itself stuck on an old version.
Does Odoo handle UAE VAT?
There is UAE localisation covering tax configuration and reporting, and how completely it fits your situation depends on your business and how it is configured. Treat tax setup as an accounting exercise your accountant signs off rather than something the implementer confirms alone.
Should we host Odoo ourselves?
Only if you have someone to run it. Self hosting gives full control and hands you backups, updates, security and uptime. Odoo's own hosting options remove that burden at a cost. For most UAE businesses without a systems administrator, managed hosting is the honest answer.
Sources
- Odoo: Pricing and editions accessed 7 October 2026
- Odoo documentation accessed 7 October 2026
- Odoo: Find a partner accessed 7 October 2026
- Odoo documentation: Hosting accessed 7 October 2026
- Odoo documentation: Upgrade accessed 7 October 2026
- UAE Federal Tax Authority accessed 7 October 2026
Fixed price, in writing
Send your brief. Get a scope and a price within 45 minutes.
- One fixed number, agreed in writing before work starts
- No obligation, and no pressure to sign
- English and Arabic work, with proper right to left layout
- One team for design, marketing, web, media and copy
Got it. Your quote is being written now.
In business hours you will have it within 45 minutes. Check your inbox for the confirmation.