All services

Web & platforms

Websites and web apps, built in the UAE

We build marketing sites and web applications in Next.js — fast on a phone, and easy for your team to edit without calling us. Arabic here is a routing decision, not a second website.

Atlas Properties, a concept build: a listings dashboard showing 1,240 live listings, filtered results for Business Bay, Dubai Marina and JLT with AED asking prices, a map panel, and an English–Arabic language toggle.

Concept build — Atlas Properties, engineered in-house

<48h

Brief to fixed proposal

Live

Preview URL from the first build

AA

WCAG 2.2 level we test to

30 days

Warranty after go-live

What we build

Eight pieces of the job, quoted separately

Eight pieces of work, quoted separately or as one build.

How we build it

Three decisions we make early

Three decisions that set the cost of everything after them.

Content model before pixels

We work out what a page actually is — a service, a project, a person — before anyone opens a design tool. Get that wrong and every later change is a rebuild; get it right and your team adds a whole new section without calling us. It is the cheapest hour on the project and the one most often skipped.

A budget, written down

We agree a page-weight and a load-time target in scoping, then enforce it in the pipeline. A pull request that pushes the homepage past the budget fails before it merges, not after launch. That single rule is why a site stays fast in month eighteen, when the tracking scripts and the hero video have arrived.

Arabic decided at the start

Every layout uses logical properties from the outset, so direction is a route decision rather than a rewrite. You may not launch bilingual — most clients do not — but the version that does is then a font, a translation file and a routing switch, instead of a second website scoped from scratch.

What you get

What is in your hands once the site is live.

  • A design system built on your own brand
  • CMS pages your team edits without us
  • Arabic-ready layout from the first screen
  • A performance budget agreed before design starts
  • Analytics and cookie consent, configured properly
  • Accessibility tested to WCAG 2.2 AA
  • A redirect map and a rehearsed launch
  • The full repository, history included, handed over
  • Hosting, domain and analytics accounts in your name
  • Thirty days of warranty after go-live

Stack

What this work actually runs on

The parts of our stack this work actually runs on.

What the browser actually runs.

10 tools

  • Next.js
  • React
  • TypeScript
  • Tailwind CSS
  • Astro
  • Vite
  • Radix UI
  • shadcn/ui
  • GSAP
  • Storybook

A drawing of an interface assembling itself: a header, a navigation rail, a wide panel and two tiles arriving one after another into a finished layout.

Names, not logos. Everything listed is something we build with or integrate, not a category page we copied.

Where it lands

Six sectors this work is bought in

Where this work usually lands across the UAE.

  • Real estate

    Listing portals, broker CRMs and owner dashboards.

  • Hospitality

    Booking engines, guest apps and property dashboards.

  • Education

    Enrolment portals, course platforms and parent apps.

  • Government

    Service portals, bilingual forms and accessibility work.

  • Professional services

    Practice management, billing and client portals.

  • Healthcare

    Clinic systems, patient portals and careful data handling.

All ten sectors we build for

Process

Five stages, and what you hold at each

The same five stages on every build, whatever the size.

  1. 01

    Scope

    One workshop, a written brief, one fixed quote.

    Scoped brief and quote

  2. 02

    Prototype

    Clickable screens before a line of production code exists.

    Clickable prototype

  3. 03

    Build

    Demos on a preview URL, at whatever rhythm you set.

    Preview URL you own

  4. 04

    Launch

    Redirects, a performance pass, then the DNS switch.

    Launch checklist

  5. 05

    Run

    Patching, small changes and a quarterly review with numbers.

    Monthly report

How we quote it

We quote a website as one scope — pages, CMS, languages and integrations, itemised line by line.

  • Pick the pieces you need and the quotation follows
  • You pay against demos you can open, not calendar dates
  • Defects found in the first thirty days are fixed free

Quoted as corporate website: five to fifteen pages, cms, seo structure, bilingual-ready. We publish no bands — pick the pieces you need and one itemised quotation comes back within 48 hours, free either way.

Get a quote

Questions

Before you send the brief

How long does a website take?

It depends on the page count, the languages and how many systems it has to talk to, so we will not pretend one figure covers a landing page and a fifteen-page bilingual site. Tell us the date you are working to and the plan is built backwards from it. The variable is almost never engineering: it is how quickly content, photography and legal sign-off arrive from your side, which is why the schedule names who owes what and when.

Do you build in WordPress?

Not by default. We build in Next.js with a headless CMS, so your team edits content in a friendly editor while the public site stays static and fast. We do migrate off WordPress often, and we still read PHP when the old site has logic worth keeping. If your existing WordPress site genuinely works and only needs a theme rebuild, we will tell you that instead of quoting a rewrite.

What does Arabic-ready actually mean?

Every layout uses logical CSS properties — start and end rather than left and right — so switching direction mirrors the page instead of breaking it. Icons that carry direction are flipped, numerals and dates use the right locale, and the type scale is checked against an Arabic face. Adding Arabic later is then routing, a font and translated copy: days of work rather than a second website.

Who owns the code and the accounts?

You do — the source, the commit history, the designs and the accounts, outright and in writing. The whole repository is handed over at every milestone rather than released at final payment, so you always hold a complete, buildable copy. Hosting, domain, analytics and CMS accounts are registered to your company with your billing details, and we hold delegated access you can revoke in one click. Nothing about the handover requires our cooperation, which is the point of doing it this way.

How do you keep it fast after launch?

The performance budget is written into the build, so a pull request that pushes the page past it fails in CI rather than in production. After go-live we watch field data from real visitors rather than lab scores alone, because a Dubai phone on a busy network is the device that matters. Third-party scripts are the usual cause of regressions, so every new tag goes through a measurement step first.

Related

Where this shows up

Two builds of ours where the same decisions came up.

  • Property listing platform

    Atlas Properties

    A bilingual property portal: 1,240 listings, faceted search and an agent-facing CMS.

    LCP on a filtered results page
    0.9s
    Lighthouse performance
    100
  • E-commerce storefront

    Soukone

    An AED storefront with card and instalment payments, VAT-correct invoices and a steady checkout.

    LCP on a product page
    1.0s
    Cumulative layout shift
    0.00

Bought alongside

What usually gets bought alongside it.

  • Custom software

    CRM and internal systems shaped around how you already work.

    Explore
  • E-commerce

    AED storefronts with UAE payment rails and VAT handled properly.

    Explore
  • IT & networking

    Office networks, cloud infrastructure, and support that answers.

    Explore

Scope your website with us.

Pick the pieces you need and tell us the date you need them. You get a written brief and one fixed quotation before anyone writes code.