Skip to content

Web Development

Conversion-led websites that load fast and rank well.

We design and ship marketing sites and web apps with clean architecture, Core Web Vitals in the green, and analytics wired from day one.

  • Dubai head office, GCC-wide delivery
  • Arabic and English throughout
  • Written scope and fixed timeline before you commit

You walk away with

  • Next.js builds
  • Headless CMS
  • Core Web Vitals
  • Technical SEO

Typical timeline

6–12 weeks

Typical engagements start around

AED 18,000 per project

What good looks like

Largest Contentful Paint on a mid-range phone
<2sLargest Contentful Paint on a mid-range phone
of URLs mapped and redirected on migration
100%of URLs mapped and redirected on migration
deploys required to publish a content change
0deploys required to publish a content change

The problem this solves

Most marketing sites are slow, hard to edit, and impossible to attribute. Marketing cannot ship a landing page without a developer, engineering resents the CMS, and nobody can say which page produced last quarter's pipeline.

Where this usually hurts

  • Marketing cannot ship

    Every landing page needs a developer, so campaigns wait on a sprint and the site slowly stops reflecting what the business actually sells.

  • It is slow on the devices that matter

    Lab scores look fine on a laptop over office wifi. Real users on a mid-range Android on mobile data are waiting five seconds and leaving.

  • Nobody can attribute anything

    Analytics were added late and inconsistently, so no one can say which page produced last quarter's pipeline — which means no one can argue for the budget to improve it.

  • The rebuild is already overdue

    The stack is two frameworks behind, the original developers have gone, and every change costs more than the last one did.

We build marketing sites and web applications on Next.js, with a headless CMS behind them and analytics wired before the first page ships. The point is not the stack — it is that three things hold true at launch and are still true two years later: pages load in under two seconds on a mid-range phone, non-engineers can publish without a deploy, and every conversion is attributable to the page that produced it.

Speed is a feature, not a phase

Performance work bolted on at the end never survives the next quarter of feature work. We enforce a performance budget in CI from the first commit, so a change that would push Largest Contentful Paint past its ceiling fails the build rather than quietly shipping. That is why the sites we hand over are still green a year later.

  • Server-rendered by default, so the first paint does not wait on JavaScript
  • Images, fonts and third-party scripts budgeted individually
  • Core Web Vitals measured on real traffic, not just in the lab
  • A performance regression fails CI, the same as a broken test

Built for the people who edit it

A site nobody can update is a site that decays. Content models are designed around the way your team actually writes — reusable blocks, sensible constraints, previews that match production — so a campaign page takes an afternoon rather than a sprint.

Technical SEO is included, not extra

Rendering strategy, canonical handling, structured data, hreflang for multi-region sites, and an XML sitemap that reflects reality. These are architectural decisions, which is why they belong in the build rather than in a report afterwards.

What is included

  • Architecture and setup

    Repo, environments, CI, preview deploys and a component library your team can extend.

  • Headless CMS

    Content modelling, editor training and previews that match what visitors will see.

  • Performance budget

    Core Web Vitals targets agreed up front and enforced automatically on every pull request.

  • Analytics and attribution

    Events, goals and dashboards wired before launch, so week one produces data rather than guesses.

  • Accessibility

    WCAG 2.2 AA as a build requirement, reviewed on every pull request rather than audited at the end.

  • Handover

    Documentation, a recorded walkthrough and thirty days of support while your team settles in.

What we build with

  • Frontend

    • Next.js
    • React
    • TypeScript
    • Tailwind
  • Content & data

    • Headless CMS
    • PostgreSQL
    • Prisma
    • REST & GraphQL
  • Delivery

    • Vercel
    • GitHub Actions
    • Playwright
    • Lighthouse CI

How engagements are sized

Three sizes, so the scope matches the problem rather than the budget matching a template. Every tier is a starting point — the number moves with what we find in discovery, and you see the revised figure before anything is signed.

  • Essential

    One clear problem, scoped tightly and shipped.

    From

    AED 18,000

    per project

    A marketing site that needs to be fast and editable, without a bespoke design system.

    • Up to 12 page templates
    • CMS and editor training
    • Core Web Vitals budget
    Get a firm number
  • Growth

    The full engagement, with measurement and iteration built in.

    From

    AED 55,000

    per project

    A full site or web app with a design system your team will keep extending.

    • Design system in code
    • Custom integrations
    • Analytics and attribution
    Get a firm number
  • Enterprise

    Multi-entity, regulated, or integrated across several systems.

    From

    AED 140,000

    per project

    Multi-region, multi-language, or a platform with authenticated areas and complex data.

    • Multi-locale with hreflang
    • SSO and gated content
    • Load and security testing
    Get a firm number

Prices are in AED excluding 5% VAT. Other currencies on the pricing page.

How delivery actually runs

The phases below are what a typical engagement moves through, with the durations we plan against. You always know which phase you are in and what leaves it.

See the full process
  1. 1

    Audit and architecture

    1–2 weeks

    We measure what exists, map every URL, agree the content model with the people who write, and set the performance budget CI will enforce.

  2. 2

    Design system in code

    2–3 weeks

    Components built and reviewed in isolation before pages exist, so the library is the source of truth rather than a Figma file nobody opens.

  3. 3

    Build and integrate

    3–6 weeks

    Pages assembled from the library, CMS wired, analytics and consent in place, with performance checked on every pull request.

  4. 4

    Launch and monitor

    1 week + 30 days

    Cutover with redirects live, Search Console watched for four weeks, and a fix cycle for anything the real world surfaces.

  • Audit and architecture · You get

    • URL and redirect map
    • Content model
    • Agreed performance budget
  • Design system in code · You get

    • Component library
    • Accessibility baseline
    • Preview environments
  • Build and integrate · You get

    • Full site in staging
    • CMS with editor training
    • Analytics and goals live
  • Launch and monitor · You get

    • Production launch
    • Four-week ranking watch
    • Documented handover

Built for the UAE

What working with a Dubai partner actually changes

Most of what follows is invisible until it goes wrong — a supplier who cannot keep data in-country, an invoice the FTA rejects, a support rota that is asleep for half of your working day. These are the questions we answer before they become findings.

Bilingual sites are the norm here rather than the exception, so Arabic is built as a first-class locale: right-to-left layout, Arabic typography that actually reads, and hreflang wired for the GCC. We also host in-region where a client's own compliance position requires it.

  • Data residency, decided up front

    AWS me-central-1, Azure UAE North and OCI Dubai are all in scope. We map the whole data path — backups, logs, metrics and support access — rather than the primary database alone, and put the result in writing.

  • PDPL, and the free zones

    Federal Decree-Law No. 45 of 2021 governs most of the mainland; DIFC and ADGM entities fall under their own data protection laws instead. We establish which applies to your entity before we design anything that touches personal data.

  • VAT and e-invoicing that pass

    Five per cent VAT, FTA-compliant tax invoices, the audit file the authority can request, and readiness for e-invoicing as the mandate phases in. Configured in the build, not patched after the first filing is rejected.

  • Your hours, your languages

    Delivery runs on Gulf hours with real overlap with your team, in Arabic and English. Customer-facing interfaces, documents and training are produced in both where you need them, with RTL treated as a design requirement rather than a translation step.

Sectors we do this in most

Not the only sectors we work in — the ones where we have shipped this service enough times to know the regulatory edges and the usual traps.

  • B2B SaaS

    Marketing sites and product UX that feed qualified pipeline.

  • E-commerce & Retail

    Fast storefronts and checkouts engineered to lift AOV.

  • Real Estate

    Listing and portal experiences that turn browsers into leads.

In-house, generalist agency, or us

An honest comparison, including where the other two options are the better call.

Hiring in-houseWorking with us
Time to first outputThree to five months to source, notice-period and onboard, in a market where senior specialists are scarce and expensive.Two to three weeks from signature, with people who have shipped this before.
Cost shapeFixed monthly cost plus visa, insurance, end-of-service and equipment, whether or not there is a full workload.Scoped to the work. Costs stop when the work does.
Breadth of skillOne or two specialisms per hire. Anything outside them gets improvised or outsourced anyway.Design, engineering, security and growth from the same team, without a handoff between vendors.
Institutional knowledgeStays in the building — which is the real advantage, and the reason to hire eventually.Documented and handed over. We write runbooks so you can take it back in-house.
When it is the wrong choiceRarely, once the workload is genuinely full-time and permanent.If you need someone in your standups every day for years, hire. We will say so.

Related work

Questions people ask before starting

Yes — that is a design goal, not an add-on. Pages are assembled from reusable blocks in the CMS, previews match production, and publishing does not require a deploy. We train your editors before handover.

Ready to talk about Web Development?

Tell us what you are building and where it is stuck. We will come back with a scope, a timeline and a number — usually within two working days.

Step 1 of 3 · What you need

Which services are you interested in?