Skip to content
Websites and multi-site platforms

A website is easy to build. Keeping it in agreement with the rest of your business is the hard part.

A web development company in Dubai writing real code — which is why the site can talk to whatever you already run: your CRM, your inventory, your calendar, your other brands. Not just to whatever a builder's connector list happens to cover.

Book the first conversationSee what we have built

The spectrum

Ordered by how much the site has to know

Not by budget, and not by page count. What separates these five is how much the site has to know and how many other systems it has to stay in agreement with — a fact about your business, not your spending. You don't pick a shape. You already have one.

01 / 05

  1. A site that only has to be true

    Ours is slow, out of date, and I hesitate before sending the link.

    • Build it fast on a phone on hotel wifi
    • Structure it so search engines read the actual work
    • Render correctly in every browser

    True, quick and current outperforms clever and out of date.

    A marketing site built properly. Fast on a phone on hotel wifi, correct in every browser, structured so search engines can read what you actually do, and editable by your team without a developer in the loop. Nothing on the page depends on another system being right, because nothing else needs to be. There is nothing small about this shape — a site that is true, quick and current outperforms a clever one that has drifted out of date.

    Marketing site · CMS your team runs · SEO foundations · Performance

  2. A site your team ships on

    Every landing page goes through a developer and takes two weeks we don't have.

    • Build the library of section templates
    • Hand composition over, with desktop and mobile previews
    • Publish with no deploy and no developer

    Campaign pages stop being a scheduling negotiation.

    The bottleneck isn't the site — it's that every change routes through whoever built it. So we hand composition over. Your marketing team assembles pages from a library of section templates, previews desktop and mobile, and publishes — no deploy, and no developer involved.

    Page builder · Section library · Preview before publish · No deploy to publish

  3. A site that knows what is happening elsewhere

    The site collects a name and an email, and then the real work starts in a spreadsheet.

    • Read live inventory and write into the CRM
    • Price against rules that keep changing
    • Build a budget profile from every calculation

    Real code has no list.

    Here the site stops being a document and becomes a participant. It reads live inventory, writes into the CRM, checks a calendar, prices something against a rule that keeps changing — and every calculation quietly builds a budget profile the sales team can see before anyone picks up the phone. This is where the builders stop. Wix, Framer and Webflow integrate through a connector list their vendor maintains; the moment you need a system that isn't on that list, or logic that isn't a form, the tool has no next move.

    CRM and internal systems · Live data · Calculators and rules engines · Lead profiles

  4. One codebase, many brands

    We run six brands, and every change has to be made six times.

    • Resolve brand, language and content per request
    • Launch another brand as a configuration change
    • Wall off each brand's editors from the others

    The economics invert — each new site costs a fraction of the first.

    One deployment instead of six codebases. Middleware resolves each request to the right brand, the right language and the right content, so launching another brand site is a configuration change rather than a release. The same deployment carries multiple languages including full RTL, where the layout flips and the typeface changes with it; role-based access so an editor on one brand cannot see or touch another; and per-domain SEO, sitemaps, redirects and tracking scripts.

    Multi-tenant architecture · Arabic and RTL · Role-based access · Per-domain SEO

  5. A platform that runs the operation

    The website is where customers arrive, but the business itself runs somewhere else entirely.

    • Build the lead dashboard into the CMS itself
    • Rank hot leads with a full activity timeline
    • Hand qualified buyers to sales with context attached

    One system from the first line of code. Nothing bolted on.

    At this end the site is no longer marketing. It is where the work happens, and who can see what becomes the product. The lead dashboard lives inside the CMS itself — KPI cards, a hot-lead priority table, per-lead engagement breakdowns and a full activity timeline — so the sales team runs its day in the same system the marketing team edits the site in. An on-site concierge agent answers buyers around the clock and hands the qualified ones over with context attached.

    Operational dashboards · Permissions as the product · On-site agents · One system, not integrations

Being built above your shape costs exactly as much as being built below it.

A page builder nobody opens, permissions nobody needs, a dashboard nobody reads — that is money spent and complexity carried for no return, every month, forever. If your site only has to be true, we will say so on the first call and build you a site that is true. Knowing which shape you are in is most of the value of the conversation.

Delivered work

The same shapes, already built

A Dubai real estate company · Real estate · paid social

Meta ads lead attribution for Dubai real estate, down to the video

The client optimises its ads on what converts, and its team responds to each lead by what that lead did.

All case studies →

Questions worth asking before you brief anyone

It depends which shape you are in, and that is a question about your business rather than your budget. A site that only has to be true is a different piece of work from a platform serving a portfolio of brands. The first conversation is free. If it goes somewhere, a paid discovery produces a written recommendation and a phased quote before any build begins — so the number arrives with the reasoning attached and you can see inside it.

For a straightforward brochure site those tools are fine, and we will tell you so. The argument bites further along the spectrum. Builders integrate through a connector list their vendor maintains. The moment you need a system that isn't on that list, logic that isn't a form, permissions that differ per user, volume economics that only work if one codebase serves many brands, or right-to-left languages handled properly, there is no next move — you are waiting on someone else's roadmap. Custom code has no list.

Yes — that is the whole point of building in code. HubSpot, Salesforce, Zoho, Pipedrive, WhatsApp, email platforms, calendars, booking systems, property portals, and the internal systems and ERPs that were never designed to be connected to anything. If it has an API, a database, or an export, we can put the website in conversation with it.

Yes, and properly means more than a translation file. Multiple languages run side by side; when a right-to-left language is active the entire layout flips and the typeface switches to one designed for it, and each language carries its own SEO metadata. Translations live in the CMS where your own team edits them.

Yes. Content lives in a CMS shaped around how your team actually works rather than a generic admin panel. Depending on the shape, that ranges from editing text and images through to composing whole pages from a section library and publishing without a deploy. Structural work — new features, new page types, new integrations — stays with us.

Not always. Sometimes the right answer is to keep what works and build the missing part behind it. We have also fixed operations where nothing needed building at all — a platform already paid for, used at a fraction of its capability, put right by configuration rather than code. Discovery tells us which of those situations you are in before anyone quotes a build.

Set at discovery and quoted in phases, so something useful goes live before everything is finished. What actually moves a timeline is rarely the code — it is content, approvals, and access to the systems the site has to talk to. We name which of those we need on day one so the dependency is visible from the start.

Tell us what your site has to know.

No pitch deck. The first conversation is free and it is a real one: you describe how the business actually runs, we tell you which shape your site is in and what it would take to build it. If that goes somewhere, a paid discovery turns it into a written recommendation and a phased quote.

Book the first conversation

You leave that first call with a straight answer about which shape you're in — whether or not you build it with us.