Website design that works in Arabic and English.

Four things move it more than anything else: the number of page types rather than pages, whether the layout has to be drawn in both reading directions, whether the content and photography already exist, and how much of the system you want documented for your own team. There is no standard rate in this market, which is why quotes for the same brief arrive orders of magnitude apart and why a price alone tells you almost nothing about what you are buying. We scope against those four and put the figure in writing before any design work starts.

At wireframe stage, before anything is styled. Mirroring changes the reading order, the side labels and icons sit on, the direction of arrows and progress steps, and how numerals behave inside a right-to-left line. A layout drawn in one direction and mirrored afterwards usually comes back as a redraw, which is why we specify both states inside the same component. Deciding late is what makes Arabic expensive, not Arabic itself.

4 weeks for the design of a first site, sitting inside the first 6 weeks of a build engagement rather than running after it. Week 1 is the structure, weeks 2 and 3 are the wireframes and the system, and week 4 is the screens and the handover. A larger sitemap or a second language extends it, and content readiness is the thing that moves the date most often. The remaining weeks belong to website development, and what the finished site has to do for a visitor is answered at build a high-converting website.

The proof sections get replaced in the wireframe rather than left empty. What replaces them is the work itself: the method set out as a sequence, artefacts a buyer can open, the entity facts a stranger can check, and named people with real roles. A Hub71 SaaS company three months into its ADGM licence has a product screen, a founder and a licence number, and those read better on a page than a logo wall with four placeholders in it. What we will not do is draw a testimonial band you cannot fill, because a section reserved for an asset that does not exist is a hole the day the site goes live.

It changes the sitemap, which is the most expensive thing to change later. A free-zone entity that cannot serve mainland customers directly should not carry a service page written for mainland demand, and an enquiry form on a group site has to route to the entity that can actually take the work. Both are settled before a wireframe is drawn, alongside a column for the branch or the activity you expect to add. That column is why the structure survives the change.

The level named nationally is WCAG 2.1 Level AA. The National Policy for Digital Accessibility, published in March 2024 and supported by TDRA alongside the UAE Design System 2.0, sets it for federal websites, e-services, mobile apps and kiosks. A private company is not directly bound by it, but any supplier bidding for federal or emirate-level work inherits the bar through procurement, and designing to it costs far less than retrofitting it. We set contrast, focus order and target sizes inside the components rather than checking them at the end.

The working file, the token set and the documented component library, all of it yours. Another studio can build from it because the handover is the system rather than a folder of exported screens, and the spec states measurements, states and behaviour instead of leaving them to be read off an image. Fonts are the one part that is licensed rather than owned, so we tell you what the licence covers before a typeface is chosen.

No, and it should not. The structure is drawn now with the second entity in it: a route that can be published once the branch exists, an enquiry path that can point at either entity, and page types that accept a new activity without reopening the navigation. What you cannot do is claim the branch before it is licensed, so the copy for those routes stays unpublished until it is true. Waiting is the version that turns an addition into a rebuild.