Growth4 min read

How to read a website quotation in Dubai

How to read a website quotation in the Dubai market. The eight variables that actually move a number, why Arabic is a build decision rather than a translation line, the recurring costs proposals leave out, and the four questions that expose a quote which looks too cheap.

Danial AhmedFounder & engineering manager

A laptop showing growth charts on a desk with notes beside it
On this page

Two quotations written against the same brief can differ by an order of magnitude, which makes any single "average website cost" figure worthless. Price tracks three measurable things: how many distinct templates have to be designed, how many external systems the site has to talk to, and who is contractually accountable when it breaks at 2am. Here is what moves a web development quotation, and the recurring costs most proposals leave out.

The eight variables that actually move the number

Page count is the weakest predictor of price. Templates, integrations and accountability are the strongest. In order of impact:

  1. Template count, not page count. Forty pages built from six templates cost less than nine bespoke layouts. Ask any bidder to quote template count; it is the only page number that maps to effort.
  2. Integrations. Every external system — CRM, ERP, payment gateway, WhatsApp Business API, Dubai REST for property listings — is a fixed block of work with its own sandbox, credentials and failure modes. Each one is its own estimate, and the thinner the vendor's documentation the larger it gets.
  3. Bilingual English/Arabic. A substantial addition to design and front-end, and not a translation line item (see below).
  4. Content model depth. A CMS that editors can actually use — reusable blocks, validation, preview, draft workflow — costs considerably more than a flat page-body field, and earns it back in editor time.
  5. Design originality. A themed template refresh, a bespoke design system, and an art-directed site are three different products. The middle option is where most UAE corporate budgets belong.
  6. Accessibility target. WCAG 2.2 AA as a stated deliverable adds real hours: focus management, contrast, keyboard paths, screen-reader labelling, and a test pass. It is also a procurement gate for government-adjacent buyers.
  7. Performance budget. Committing to Core Web Vitals thresholds in the contract changes the build — image pipeline, font strategy, third-party script discipline. See Core Web Vitals for UAE e-commerce.
  8. Ownership and handover. Owning the source, the history and the IP outright, documented environments, a written runbook, and a handover at every milestone rather than one release at final payment. It is a small line in a quotation and the difference between a website and a hostage.

Arabic is a build decision, not a translation line

Adding Arabic after launch costs more than building for it from the start. Right-to-left is a layout mirror, not a text swap: every horizontal margin, icon direction, form field and chart axis flips. Arabic type has its own line-height and font-loading profile, numerals may need to be Eastern Arabic in some contexts and Western in others, and content workflow doubles.

Built in from the start, bilingual is a planned cost. Retrofitted onto a site whose CSS uses fixed left/right spacing, it can approach a rebuild of the front-end.

The recurring costs nobody itemises

The build price is not what a site costs in its first year. The rest is recurring, predictable, and almost never in the proposal: the .ae domain and its renewal, application hosting, headless CMS hosting or licence, transactional email and uptime monitoring, content and translation updates, and a support arrangement for patches and small changes. Ask every bidder for all of them as a separate annual figure before you compare anything.

TLS certificates are free and should never appear as a line item. If a proposal charges annually for an SSL certificate, read the rest of it more carefully.

How to read a quote that looks too cheap

A quote far below the others is usually not a discount — it is a different scope. Four questions expose it in under ten minutes: How many unique templates are included? Which integrations are in scope and which are "phase two"? Who owns the source and the IP, and what is handed over at each milestone? What happens, in writing, if a bug appears three weeks after launch?

The answers separate a fixed-price build from a fixed-price start. The second one ends in change requests priced without competition.

What to do before you sign

Get every bidder to price the same written scope — template count, integrations, languages, accessibility target, performance thresholds, warranty period. Ask for the hosting and licence costs as a separate annual figure. Then compare. A structured comparison collapses most of the spread between quotes, and the difference that survives it is the part you are actually deciding on.

If you want the same treatment applied to a system rather than a site, custom software versus off-the-shelf covers how the same maths works when licences enter the picture.

Keep reading

All articles

Turn the reading into a scope.

One fixed-price week, and you keep the brief whether you build with us or not.