If you are buying custom software development in Dubai, sort out the contract terms before you compare prices. When a bespoke project goes badly for the client, the contract usually missed something basic. Often nobody pinned down the scope or checked the vendor’s licence and VAT status. Or the contract said nothing about who owns the code and which court hears a dispute.
Before you sign for custom software development in Dubai, get a written scope with milestones you can test. Check the vendor’s trade licence and VAT status, and have the contract assign the code to you on payment. The same contract should name the governing law and the forum for disputes. Free zone and mainland vendors can both do good work, though they invoice, contract and get sued differently.
We link the official pages we read on 19 November 2026. Most of our advice for UK buyers carries over. The licence, VAT, court and data questions are what make custom software development in Dubai different.
Licences to check before buying custom software development in Dubai
UAE software vendors trade either on the mainland or in a free zone. According to the UAE government portal , a mainland trade licence goes through the economic department of the emirate, which in Dubai is the Department of Economy and Tourism. A free zone company is set up inside its zone instead.
Ask every firm quoting for your custom software development in Dubai for a copy of its trade licence, then read three details on it. The legal name should match the entity on the quote. Its licensed activities should cover software or IT services. The expiry date should fall after your project ends, because a licence that lapses mid-build does you no good.
Free zone or mainland vendors for custom software development in Dubai
The same portal’s page on free zone businesses says free zone companies sit outside mainland jurisdiction. To sell goods or services locally, it says, they work through a licensed mainland distributor or set up a mainland branch or company, and direct sales on the mainland are generally not permitted without the required mainland licences or approvals. If your company is on the mainland and the vendor is in a free zone, get it to confirm in writing which licence or approval covers this contract.
Free zone and mainland firms both do good custom software development in Dubai, and neither is cheaper or safer by default. We would sooner sign with a small free zone studio offering a clear contract than with a large mainland firm whose template keeps the source code. Judge each vendor on its references and the contract it will actually sign.
VAT invoices and the vendor’s TRN
Finance will want to reclaim the VAT. The Federal Tax Authority (FTA) publishes a 2022 guide to tax invoices that lists what one must contain. That guide gives the supplier 14 calendar days from the taxable supply to issue and deliver it. The VAT Executive Regulation has been amended since. Its current Article 59 still sets a limit of 14 days from the date of supply, with some exceptions. A standard full tax invoice shows the words “tax invoice” and the supplier’s name, address and Tax Registration Number (TRN). It also carries your name and address, with your TRN if you are registered. Then it needs a description of the supply and the amounts in UAE dirham.
Not every firm selling custom software development in Dubai will have a TRN. As of November 2026, the FTA sets a mandatory registration threshold of AED 375,000 and a voluntary threshold of AED 187,500 . A small studio below the threshold may have no TRN and charge no VAT, quite legitimately. That alone isn’t a warning sign, but it changes your VAT position and your budget. The FTA registration page we read says nothing about free zones, so check how a free zone vendor’s status affects your invoices before you budget.
Put the vendor’s TRN in the contract, or a statement that it has none. The contract should also say whether prices include VAT, and oblige the vendor to issue a valid tax invoice for each milestone.
Scope and payment for custom software development in Dubai
Writing the scope
A vague scope gets you a vague price. Before you ask anyone for quotes, write down what the system must do. Start with the people who will use it and the devices they log in from. A brief for custom software development in Dubai should say early on whether any users work in Arabic. Right-to-left layout and Arabic data entry cost a lot to add late in a build.
The scope should list every integration, such as payment providers and accounting software, and who owns each account. Note what data the system stores, where it must live and who may export it. Each milestone also needs an acceptance test that shows it works.
Finally, write down what you are deliberately not buying yet. That out-of-scope list stops a fixed quote from quietly growing, and it hands you a ready list for phase two.
Paying by milestone
Vendors here offer a fixed price, a day rate or a mix. We have written separately about fixed price versus time and materials and about budgeting for custom software .
Quotes for custom software development in Dubai tend to start with a large deposit, followed by instalments on fixed calendar dates. We would tie every payment to a milestone you can test instead. A schedule built on dates pays the vendor whether the work moved or not.
Currency is the other thing to settle. If the vendor pays for cloud services or tools in another currency, ask who carries the exchange rate risk. Write the answer into the contract whichever way it falls.
A hypothetical milestone plan for a bilingual booking portal
The following example is hypothetical and made up for illustration. A services company wants a booking portal with Arabic and English screens. It takes card payments and exports to the company’s accounting package. A milestone plan for this imaginary portal, without prices, could run like this.
| Milestone | Deliverable | Acceptance test | Payment trigger |
|---|---|---|---|
| Discovery | Written scope, wireframes, data model | You sign off the scope document | On sign-off |
| Core build | Booking flow in both languages on a staging site | Scripted test cases pass | On passing the tests |
| Integrations | Payment and accounting connections in test mode | Test transactions reconcile | On reconciliation |
| Launch | Production release and monitoring | Agreed checklist completed | On go-live |
| Handover | Code, documentation and credentials transferred | Your team can rebuild and deploy | On a successful rebuild |
We would also hold back a small final percentage until the handover milestone passes.
Who owns the code when the project ends
Paying for custom software development in Dubai doesn’t by itself make the code yours. We won’t try to summarise UAE copyright law here. Whatever the default position, spell ownership out in the contract.
A contract for custom software development in Dubai should say which rights pass to you and when. It should also say what the vendor keeps. We think code written specifically for you should pass to you in full once you have paid the relevant invoices. The vendor keeps its existing tools and libraries and licenses you to use them inside your system. Open source components stay under their own licences, and the vendor should list each one.
Ask for the full source repository with its build scripts and deployment notes. A compiled package alone lets you run the system and do little else. Every account the system depends on should end up in your company’s name. That covers domains, cloud accounts, app store accounts and the merchant account with your payment gateway.
Some vendors prefer to keep the source and license you a hosted service. That is a legitimate model. It turns the deal into a subscription, though, so price and negotiate it as one. If the source has to sit with a third party, read our notes on software escrow first.
Choosing a court for disputes over custom software development in Dubai
A contract for custom software development in Dubai should name a governing law. It should also name a forum for disputes. Leave them out and you may end up in a court you would never have picked. The usual options are the onshore UAE courts, a financial free zone’s courts, or arbitration.
The Dubai International Financial Centre (DIFC) has its own courts. Their opt-in page describes a route where parties agree in writing to file a civil or commercial claim there. They can make that agreement before or after a dispute starts. The page requires the agreement to rest on “specific, clear and express provisions”. A loose reference to “the courts of Dubai” won’t meet that, so have a lawyer draft the jurisdiction clause. The same page describes a Small Claims Tribunal for claims up to AED 500,000, which it says can be used in commercial contracts even by parties based outside the DIFC.
The Abu Dhabi Global Market (ADGM) runs its own courts too. According to the ADGM Courts page , they rest on English common law. That page doesn’t say whether parties from outside ADGM can opt in, so check the courts’ own rules before you name them in a contract. Arbitration suits parties in different countries, and you will need to agree the seat, rules, language and cost.
Where your data may live
Data rules for custom software development in Dubai can differ from one sector to the next, and a regulated business such as a clinic or a bank may answer to its own regulator on hosting. We haven’t checked those sector rules for this article, so we won’t summarise them here.
Before the vendor writes any code, note what personal and sensitive data the system will hold. Find out which regulator covers your sector and whether it restricts hosting or transfer abroad. A cloud region outside the UAE might suit a marketing tool and be wrong for a clinic’s patient system. That call belongs to you, and the contract should let the vendor host only where you have agreed.
Handover and support after custom software development in Dubai
The contract doesn’t stop at launch. Before signing, decide who fixes defects, who applies security updates and who is on call during an outage. Keep the warranty period separate from a support plan. Under the warranty, the vendor fixes defects in the delivered work at no charge.
A good handover pack holds the repository, a README, deployment instructions, environments, credentials and a recorded walkthrough. Test it by asking someone outside the vendor’s team to build and deploy the system from the pack alone. If an earlier attempt at custom software development in Dubai has gone wrong, our notes on taking over a software project explain how to audit what you have. We also take over stalled projects from other vendors. We can run that test on your handover pack before you accept it.
Getting a second opinion on your brief
Our software development team can review a brief for custom software development in Dubai before it goes out to vendors. We’ll go through the scope, milestones and handover terms with you. Send us your scope and we’ll tell you what we would ask the vendors, ourselves included.