Information security for software delivery

ISO/IEC 27001
ISO/IEC 27001 certified
The consolidation
Many commissioned sites, one governed platform, and what comes out the other side
Each input arrived for a reasonable reason. The control layer is what stops the next reasonable reason producing yet another island.
Corporate, subsidiary, market and microsite properties converge into one governed platform — one content model, one component library, one workflow with defined rights — producing a single identity, cheap new sites and bilingual parity.
The corporate site
The flagship that carries the organisation’s claims — and quietly diverges from every site built after it.
Brand and subsidiary sites
Each commissioned by its own team, on its own stack, with its own agency and its own version of the shared facts.
Market and campaign sites
Launched fast for a country or a quarter, then left running long after the reason for them has ended.
Portals and microsites
Careers, investors, events, suppliers — each holding a fragment of the organisation’s identity and none of its discipline.
What we do
The governed platform
One content model, one component library, one publishing workflow with rights defined per role, per brand and per language — so autonomy is granted deliberately instead of leaking by default.
One identity, everywhere
The organisation’s facts and voice hold across every property, because they are maintained once.
The next site becomes configuration
A new brand, market or campaign site is assembled from the shared layer in weeks, not commissioned from zero.
Two languages at parity by default
Arabic and English publish through the same workflow on every site, so parity is a property of the estate rather than a per-site struggle.
Governance
Who may publish what — the question that decides whether the estate stays coherent
Every organisation that runs many sites has a governance model; most have never written it down, which means it is whatever each team can get away with. The visible result is drift: a subsidiary describing the group in words the group retired two years ago, legal text updated on one site and not the other six, a claim that survives on a campaign page long after compliance withdrew it. None of this is malice. It is the absence of an answer to a simple question — who may change which content, on which site, with whose review — enforced by nothing.
We treat the governance model as a deliverable with the same weight as the platform. The rules are designed with you — a subsidiary’s marketing team edits its own pages freely but not the shared corporate claims; regulated statements route through a named review; a market site may vary imagery and offers but not the organisation’s facts — and then they are implemented as roles, permissions and workflow in the platform itself. A rule that lives in a PDF is a suggestion. A rule the publish button enforces is governance.
The same workflow carries the two languages. At enterprise scale, bilingual content is an operations problem before it is a translation problem: dozens of editors, hundreds of pages, and a change a week on each site. The estate runs one content operation producing two first-class outputs — a page ships when both its languages ship — because any weaker rule quietly rebuilds the lag the consolidation was meant to end.
The commitments
What an enterprise estate promises its organisation before any page is designed
These are requirements, not aspirations: each one is testable, each one is wired into the platform, and each one fails a release rather than a retrospective.
Editors sign in through corporate identity
The platform authenticates against your identity provider, so access follows the joiner–mover–leaver process the organisation already runs.
What that buys the organisation: No orphaned agency logins, and publishing rights that expire with the contract.
Content reads from the systems that own it
Vacancies from the HR system, enquiries into the CRM, product and branch data from the systems of record — integrated once at the platform layer, inherited by every site.
What that buys the organisation: Facts that cannot drift, because no site keeps its own copy.
Accessibility is an acceptance criterion
Accessible components in the shared library, automated checks in the build, and manual testing of the journeys that matter — because a public organisation’s site is used by everyone or it is failing someone.
What that buys the organisation: Every new site inherits accessibility instead of re-earning it.
Performance is budgeted per site, per release
Weight and timing budgets run in the pipeline for every property, so a heavy campaign asset on one site fails its own release without touching its siblings.
What that buys the organisation: An estate whose speed is defended by machinery, not by memory.
Our role
What we engineer into the estate and what your organisation keeps governing on it
- 01
The platform and its content model
We build the shared layer — content model, component library, site assembly — argued from your actual inventory of sites and the ones the next three years will demand, not from a vendor’s reference architecture.
- 02
Governance as software
The publishing-rights model is designed with your teams and then implemented as roles, workflows and review gates in the platform, so the rules run without anyone having to police them.
- 03
Consolidation without a stoppage
Existing sites move onto the platform one at a time, in the order of pain, with the old site running until its replacement has proven itself — the estate is consolidated while every property stays open.
What each brand says, which sites deserve to exist and who holds which rights are decisions that stay with your organisation; we build the estate that makes those decisions enforceable, and leave your teams operating it without us.
Common questions
What buyers ask
We have a dozen sites built by different agencies. Does consolidation mean replacing them all at once?+
No, and it should not. The platform and its governance are built first, then existing sites move onto it one at a time — usually starting where the pain is worst or a rebuild was due anyway, because that is where consolidation pays immediately. Each site keeps running until its replacement on the platform has proven itself, and sites near the end of their life may simply be retired rather than migrated. A consolidation that demands a simultaneous relaunch of twelve properties is a risk no estate needs to take, and the incremental route reaches the same destination with every site open along the way.
Can our subsidiaries keep their own look and voice on a shared platform?+
Yes — that is what the governance model is for. A shared platform does not mean identical sites; it means the variation is deliberate. The component library carries themes, so a subsidiary’s colours, typography and imagery can differ within a system that still holds together, and the publishing rights say which content is the subsidiary’s to shape and which facts are the group’s and maintained once. The failure mode consolidation prevents is not variety; it is contradiction — two sites describing the same organisation differently because neither knows the other exists.
How does a multi-site estate keep its Arabic content at the level of its English content?+
By making parity a property of the workflow rather than a target for each site. On a consolidated estate, every site publishes through the same content operation, and that operation treats Arabic and English as two required outputs of one process: a page is not done until both languages are done, and shared facts live in one bilingual content model so they cannot be updated in one language and forgotten in the other. Spread across a dozen separately built sites, that discipline is a dozen battles; on one platform it is a single rule, set once and enforced by the publish workflow everywhere.
Is building an enterprise web estate the same as buying a digital experience platform?+
The platform is one decision inside the estate, not the estate itself. A DXP — commercial suite or assembled stack — answers the tooling question, and our platform-selection work covers it. This work covers what the tooling cannot: the inventory of sites and their fate, the governance of who publishes what, the bilingual content operation, the integrations with identity and internal systems, and the migration order. Organisations that buy the platform first and design the estate second usually end up running the old sprawl on newer software. The sequence that works is estate first, platform chosen to serve it.
In this cluster
Discuss your estate with us
An estate review that counts your sites, names where they contradict each other, and scopes the platform and the governance that would consolidate them.
Start the conversation