A website development price in Dubai only tells you something once you can see the work sitting behind it. Two suppliers reading the same brief land a long way apart because one has priced content migration, a staging environment, a redirect map and twelve months of security updates, and the other has priced a design and a theme. The first job is not to compare totals. It is to make both quotes describe the same project, then read each line for what it commits the supplier to do.
Key takeaways
- Under Article 27 of the VAT Executive Regulations, a published price must be inclusive of tax unless you are VAT registered or the supply is an export, and an exclusive price has to say so on the face of the document.
- Article 59 of the same regulations requires the eventual tax invoice to show a unit price, a quantity and a tax amount for each service, so a supplier who refuses to itemise a quote will have to itemise the invoice anyway.
- UAE copyright law treats software and databases as protected works, and any written transfer of those rights has to name the right, the purpose, the duration and the place of exploitation.
- Speed and accessibility belong in a quote as thresholds you can measure, not as adjectives: 2.5 seconds, 200 milliseconds, 0.1, WCAG 2.2 level AA.
- Put the domain and the hosting account in your own company name before the build starts, not during a disagreement.
Why one brief produces such different numbers
There is no UAE authority that publishes a reference rate for web development, which is why every average website cost figure you meet online traces back to somebody’s survey or price list rather than to a standard. The spread between quotes is usually real, and it is usually about scope.
Take a Business Bay brokerage with 400 listings arriving from a portal feed. One supplier reads that as a template, a feed integration, a search index and a set of filters. Another reads it as a page count. The second quote is cheaper and wrong, and you find out in month three.
Five variables move the number more than anything else. The count of distinct templates rather than pages. Whether you supply finished content or the supplier migrates it. Whether the site ships in Arabic as well as English, which affects layout, fonts and editing workflow rather than translation alone. The integrations, where feeds, payment, CRM and booking live. And whether this is a rebuild of a site that already ranks, because preserving that is a workstream in itself. Ask every bidder to price against the same template and integration list. If the quotes still differ, the difference means something.
How the price has to be presented under UAE VAT rules
Most buyers skip this part, and it is written into the regulations. Article 27 of Cabinet Decision No. 52 of 2017 on the Executive Regulations of the VAT Decree-Law says that in the case of a taxable supply, “the published prices shall be inclusive of Tax”. Clause 2 lets a supplier declare prices exclusive of tax in two situations: supplies for export, and cases where the customer is a registrant. Where that applies, clause 3 requires the price to be “clearly identified as being exclusive of Tax”.
The practical effect is that a Dubai agency quoting a VAT registered company can show figures before tax, but the document has to say so. Quoting a number with no indication either way does not meet the rule.
Read that against your own situation. If your company holds a TRN, a quote showing figures before 5% VAT is normal and correct, provided the document says they are exclusive. If you are below the mandatory registration threshold, or buying personally, the published price should already carry the tax, so the number you sign is the number you pay.
One issue we often see is a quote with a clean total, no VAT line anywhere, and an invoice that arrives 5% higher. The fix takes one sentence in an email: ask in writing whether the figures are inclusive or exclusive. Whether your supplier can issue a valid tax invoice at all is covered in our piece on choosing between an agency and a freelancer in Dubai.
Figures and rules here are indicative and change. This is general information for buyers of development work, not tax or legal advice, and a registered tax agent should confirm anything affecting your filing.
The line items a serious quote breaks out
Here is the useful consequence of the same regulation. Article 59 sets out what a tax invoice must contain, and clause 1(h), as amended by Cabinet Decision No. 100 of 2024, requires that for each good or service the invoice shows “the unit price, the quantity or volume supplied, the rate of Tax and the amount payable expressed in AED”. Your supplier has to break the project into priced lines at invoicing anyway. One who cannot do it at quote stage is telling you how the paperwork will look later.
| Line item | What it should state | The version that hides work |
|---|---|---|
| Design | Number of unique templates, number of revision rounds, whether mobile layouts are drawn or inferred | “UI/UX design” |
| Front end build | The same template list, browser and device targets, the CMS the markup is wired into | “Development” |
| CMS and training | Which fields an editor can change without a developer, and a named handover session | “Easy to manage” |
| Content | Who writes, who migrates, how many pages, and what happens to PDFs and images | Silence |
| Integrations | Each system by name, the direction of data, who pays for the third party account | “API integration” |
| Testing | Devices, forms, payment paths, and who signs off | “QA” |
| Launch | Redirect map, analytics and Search Console handover, DNS cutover window | “Go live” |
| Support | Response time, hours covered, what counts as a fix and what counts as a change | “Free support” |
Who owns the site once the last invoice clears
Federal Decree-Law No. 38 of 2021 on Copyright and Neighbouring Rights lists protected works in Article 2, and clause 2 of that article names “smart applications, software and applications, databases”. Your website is not a folder of files. It is a set of copyright works.
Article 28 deals with the author’s financial rights in relation to third parties. Clause 1 states that where the author “makes his creation for the benefit of another person, the copyright belongs to the person in whose favor it was made”. That sounds like the client wins by default, and often the client does. The trap is the article’s opening words: unless otherwise agreed in writing. A development contract is exactly such a writing, and its licence clauses routinely keep ownership with the supplier.
Article 9 sets the shape any transfer takes. A disposal of financial rights must be in writing and must “specify the right subject of the disposal, with a statement of the purpose, the duration and place of the exploitation thereof”. A clause reading “the client is granted a licence to use the website” is therefore incomplete on its face. Ask for four things by name: which rights, for what purpose, for how long, in which territory. If the answer is a full assignment on final payment, have it say so.
The practical version of that question
Ask for repository access rather than a zip file at handover, because a zip tells you nothing about history or about who can rebuild the site. Ask which parts of the build sit on licences registered to the agency, particularly premium plugins, page builders and commercial fonts, because those follow the account holder rather than the site. If a font licence sits in your supplier’s name, your brand depends on that supplier staying in business.
The domain deserves its own line. The TDRA’s .aeDA rules for changing a .ae registrant require the registrar to receive a written transfer request signed by the registrant contact, and a move between registrars completes within three working days once the auth code is provided. Workable, but not something to learn during a dispute. Register the domain in your company’s name at the start and keep the registrar login. Our domain and hosting pages cover how that is normally arranged.
The recurring costs that belong in the quote
A build price is a one off. A website is not. The quote should name the annual and monthly items even where the supplier is not charging for them.
- Hosting, backups and the certificate, with the renewal date and account holder stated.
- Commercial licences for plugins, themes, page builders and fonts, listed individually with who renews them.
- Transactional email for forms and order confirmations, a separate service from your mailbox.
- Payment processing on any site that takes money.
Price that last one honestly before you build. Stripe’s published UAE pricing, read on 12 September 2026, is 2.9% plus AED 1.00 per successful domestic card charge, with an additional 1% for international cards and a further 1% where currency conversion applies. For a Dubai Marina restaurant taking online orders at a low average basket, that fixed AED 1.00 changes the economics of the channel, and it is better discussed at quote stage.
Turning fast and accessible into something testable
Most quotes promise a fast, mobile friendly, accessible site. None of those words can be tested, so replace them with numbers that can. Google’s Core Web Vitals give the speed criteria directly: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint at 200 milliseconds or less, Cumulative Layout Shift at 0.1 or less. Interaction to Next Paint became a stable Core Web Vital in 2024, replacing First Input Delay, so a supplier still quoting the old metric has not looked recently. Assessment uses the 75th percentile of page views, which matters for the wording: ask for the thresholds to be met at the 75th percentile on real visits, not for one green score from a lab test on a desktop connection.
For accessibility, name the standard and the level. WCAG 2.2 is a W3C Recommendation, most recently published on 12 December 2024, with conformance levels A, AA and AAA. Level AA is the usual commercial target. A clinic in Jumeirah Lakes Towers with an online booking form has more reason to care than a brochure site, because the form is where an inaccessible control stops a real appointment.
On a rebuild, add the redirects. Google’s guidance on URL changes is to use a permanent server side redirect, a 301 or a 308, whenever a page moves. Ask for the redirect map as a named deliverable with an owner and a sign off before the DNS change, not as something the developer will handle at launch. It is one of the most common ways a Dubai company loses rankings during a website redesign.
Payments, changes and what happens when it stalls
Tie payments to deliverables rather than dates. Design sign off, template build complete, content loaded, user acceptance passed, launch. Dates slip for reasons that belong to both sides; deliverables do not.
The change request procedure matters more than the deposit. It should say what counts as a change rather than a fix, what the rate is, and how one is approved. Without it, every request becomes a negotiation and the goodwill runs out around week six.
One issue we often see is a project priced in three payments with the last due at launch, where launch depends on client content that never arrives. The build sits finished for months, the supplier has stopped being paid, and the relationship sours over something neither party wrote down. A clause covering a stall on either side, with a defined pause and a defined restart cost, prevents most of it.
Nine things that should stop your signature
- A single line reading “website development” against one number, with no template count and no integration list.
- No statement of whether the figures include VAT, when Article 27 requires the published price to be inclusive unless you are a registrant and the document says so.
- Ownership described as full rights on final payment, with none of the rights, purpose, duration and territory that Article 9 asks for.
- The domain or the hosting account to be held in the supplier’s name.
- Unlimited revisions, which means there is no change control and the schedule has no floor.
- Any promise of a specific position in Google results, which nobody is in a position to promise.
- No redirect plan on a rebuild of a site that already ranks.
- Speed and accessibility written as adjectives instead of the thresholds above.
- No named project contact and no stated response time for support after launch.
None of these means the supplier is dishonest. Most mean the quote was written quickly. Either way, the questions are cheap before signature and expensive after it.
