Techbanq

Web · platforms

When the fifth website is commissioned, the problem is the platform

A second brand, a third market, a customer portal, a campaign microsite — each one built from scratch because nothing is shared. Past a certain multiplicity, the question stops being who builds the next site and becomes what platform makes the next site cheap.

Information security for software delivery

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The turning point

The moment a website strategy quietly becomes a portfolio problem

We do not have an office in Saudi Arabia

We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.

No one decides to run a fleet of disconnected websites; organisations arrive there one reasonable decision at a time. The corporate site came first. A product line earned its own domain. An acquisition brought two more. A government-facing portal, an events microsite, an Arabic build that lagged the English one — each commissioned separately, each on its own stack, each with its own agency. Every individual decision was defensible. The estate they add up to is not: the same content maintained in many places, no shared identity, and every launch starting from zero.

A digital experience platform is the structural answer: one content model, one design and component layer, one set of shared services — search, consent, analytics, identity — that every property consumes rather than rebuilds. The honest boundary matters just as much. One brand with one site does not have this problem, and a platform would hand it complexity with nothing to spend it on; that organisation is better served by a well-built site, or by the lighter decoupling a headless CMS provides. The case for a DXP is made by multiplicity, and by nothing else.

The signals

The costs that appear once every site, brand and market is an island

None of these shows up on an invoice, which is why the estate can bleed for years before anyone prices it. If three of the four are familiar, the platform conversation is due.

  1. 01

    Every launch waits on engineering

    A campaign page, a new market, a product announcement — each becomes a ticket in a development queue, and the market moment it was built for passes while it waits.

  2. 02

    One fact, maintained five times

    A product detail or a policy change is edited on every property separately — and the version that gets missed keeps publishing the old truth under your name.

  3. 03

    The Arabic estate trails the English one

    With no shared localisation layer, every property solves Arabic separately — so some sites are current in one language and stale in the other, and the gap widens with each release.

  4. 04

    A new market restarts the build

    Entering a new country or launching a new brand means procuring, designing and building again from nothing — when it should mean configuring what already exists.

The programme

One platform, reached one property at a time, with nothing switched off early

A platform migration that stops the estate to rebuild it has failed before it starts. The programme runs beside the sites that earn, and each phase pays for the next.

STAGE 01

Model the content once

An inventory across every property finds the content types that repeat — products, locations, articles, people — and defines each once, with its Arabic and English variants built into the model rather than bolted on. A single definition of every content type the estate uses.

STAGE 02

Build the shared layer

The design tokens, components and shared services — search, consent, analytics, identity — are built once as the layer every property will consume, on the suite or composable stack the selection chose. The foundation the first migrated property proves.

STAGE 03

Migrate property by property

Sites move one at a time, sequenced by value and risk, while the rest of the estate runs untouched — and each migration is cheaper than the one before it, which is the platform beginning to pay. A running property on the platform, and a measured drop in the cost of the next.

STAGE 04

Retire the duplicates

As each migration lands, the parallel builds, redundant licences and duplicate content copies behind it are switched off deliberately — because an estate that keeps its old islands running has consolidated nothing. A shrinking old estate, and one platform carrying more with each phase.

Our role

What we assemble into the platform and what your editors run on it

  1. 01

    The selection, argued from your estate

    Commercial suite or assembled composable stack — we argue the choice from your properties, teams and licensing exposure, and we take no vendor commission that would tilt the answer.

  2. 02

    The architecture and the migration

    The content model, the shared layer and the property-by-property sequence are ours to design and deliver, with the estate’s revenue-earning sites running throughout.

  3. 03

    A publishing operation, not a dependency

    Templates, workflows and permissions are set up so marketing teams launch pages, campaigns and markets themselves — the measure of the platform is how rarely they need engineering, or us.

Which brands, journeys and markets the platform serves first is a commercial call that stays in your leadership; we make each property cheaper to run and faster to launch than the one before it, and hand your teams the keys.

Common questions

What buyers ask

How do we tell whether we have outgrown a website and actually need a platform?+

Count three things: properties, journeys and languages. One brand, one site, two languages is a website problem, and a good build solves it. Several brands or markets, sites that share content but not infrastructure, launches that queue behind engineering, and an Arabic estate that lags its English counterpart — that combination is a platform problem, because the cost is no longer in any one site but in the multiplication between them. The test we apply in an assessment is blunt: if the next property would be built mostly from scratch, the estate has outgrown its architecture.

Is a digital experience platform overkill for a single brand with one main site?+

Almost always, yes — and we say so in assessments even when it costs us the larger project. A DXP is an answer to multiplicity: many properties, many journeys, many markets drawing on shared content and shared services. A single-brand organisation gets the platform’s complexity, licensing and governance overhead with nothing to amortise them across. If the real need is separating content from presentation so several channels can draw on it, a headless CMS delivers that at a fraction of the weight — and if the need is simply a better site, build a better site.

Do we have to license a commercial DXP suite, or can the platform be assembled?+

Both are legitimate routes, and the estate decides. A commercial suite buys integration out of the box and one vendor to hold accountable, priced accordingly and with the switching costs that follow. An assembled, composable platform — a headless CMS, search, analytics and personalisation chosen separately behind one delivery layer — costs more to integrate up front and less to license forever, and lets each part be replaced without replacing the whole. The variables that settle it are your engineering capacity, your licensing appetite and how unusual your integration surface is. We hold no implementation partnership with any vendor, so the recommendation carries no commission.

Start the assessment

A platform assessment that counts your properties, journeys and languages and says plainly whether a DXP pays for itself or a simpler stack wins.

Start the conversation