How Al Rostamani Group Scaled Six Division Websites and Grew Enquiries 3.2x

TechnBrains standardized six multi-brand websites around reusable components, bilingual publishing, and division-managed content.

Project Highlights & Key Metrics

Industry
Diversified Conglomerate
Platform
Web
Region
UAE
Engagement Model
Staff Augmentation
Timeline
10 months
Team Size
4 specialists
Team Composition
  • Business Analyst
  • Software Developer
  • QA Engineer
  • DevOps Engineer
Tech Stack
  • WordPress
  • Java
  • HTML5/CSS3
  • MySQL
Focus Areas
  • Website Modernization
  • Multi-Site Architecture
  • Performance Optimization
  • Accessibility Compliance
  • Centralized CMS
About Al Rostamani Group

A Diversified UAE Conglomerate

Al Rostamani Group is a UAE family business conglomerate founded in the early 1950s and headquartered on Sheikh Zayed Road, Dubai. Six of its divisions market through their own websites, each serving a different buyer and publishing in both Arabic and English.

  • Six division websites serving different markets and customer groups

  • Separate content ownership within each division

  • Arabic and English content published across the portfolio

  • Property listings managed through the real estate website

Client Review image
We had six divisions, each with its own content, campaigns, and priorities. We needed the sites to work consistently without taking control away from the teams managing them. TechnBrains gave us the capacity to make that happen.
Digital Lead
Al Rostamani Group
★★★★★
Problem
The Challenge

A group campaign meant three to six separate builds

The sites had been created at different times, with different page structures and development decisions. A campaign running across automotive, real estate, and travel could require three separate implementations. A group-wide brand update could require six. Routine content changes also depended heavily on developer availability, while Arabic publishing, enquiry capture, and release processes varied between divisions. Built at different times by different hands, no template from one site helped another.

Key Challenges
  • 01

    Common page functionality rebuilt across multiple sites

  • 02

    Content changes waiting on developer availability

  • 03

    Arabic and English handled differently between divisions

  • 04

    Enquiry data captured in inconsistent formats

  • 05

    Campaign traffic placing uneven pressure on hosting

Every campaign that ran across divisions had to be built more than once.

Solution
Our Solution

Common Building Blocks Across Six Division Websites

Shared behaviour went into a build library. Identity, listings and campaign pages stayed local.

Shared Component Library

Forms, navigation, language switching and content blocks built once, styled per division.

Divisions reuse page types they once commissioned.

Editor-Managed Pages

Pages assembled from existing components, including listings the property team maintains.

~68% less content update time.

Bilingual Templates

Every template carries Arabic and English, with right-to-left handling in the components.

Both languages publish from the same screen.

Enquiry Capture and Tracking

Forms rebuilt to a common structure, wired to analytics and campaign tools.

Enquiry volume up 3.2x across six divisions.

Deployment and Hosting Pipeline

An automated release pipeline across all six sites, hosting sized for campaigns.

~47% faster page loads.
Engineering Approach

Behaviour is shared, appearance stays local

Share too little and the six sites drift apart again within a year. Share too much and a division loses the identity its buyers recognise, which the automotive and real estate teams objected to. Forms, navigation, language handling, accessibility and deployment are identical across all six. Layout, imagery, tone and division modules such as property listings stay local. A division can change how its site looks without touching what the other five depend on.

Impact
The Impact

Division editors publish without raising a ticket

A division that wants a campaign page builds it from existing components, in both languages, and publishes it. Development time went back to development work.

What changed, before and after the engagement
Before After
Common functionality rebuilt per site Reusable components across six sites
Content changes as dev tickets Division editors manage their own pages
Arabic handled site by site Bilingual behaviour built into templates
Enquiries captured in different formats Comparable lead structure across divisions
Separate release processes Coordinated deployment across the portfolio
Our Engagement

Why Al Rostamani Group Partnered With TechnBrains

Al Rostamani Group already had internal stakeholders defining what each division needed. The capacity gap was execution across several disciplines at the same time. For 10 months, a TechnBrains Business Analyst, Software Developer, QA Engineer, and DevOps Engineer worked alongside the group’s teams. Requirements had to account for six division owners, while development, testing, and deployment needed enough consistency that each new site or campaign did not restart the technical discussion. The resulting codebase was handed over for the group’s own teams to manage.

Business Outcomes
  • 3.2xMore enquiries
  • ~68%Less content update time
  • ~47%Faster page loads
  • ~42%More site traffic
PropTech Expert at TechnBrains image
The main decision was simple: what should work the same across all six sites, and what should stay specific to each division? Once that was clear, we stopped rebuilding the same features six times.
PropTech Product Strategy Lead TechnBrains

Building Software Across Multiple Brands or Business Units?

Outsource the full build or add engineers who know how to share the right technology without forcing every team into the same process.

Shared foundation. Room for every business to work differently.

Talk to a PropTech Expert Start Your Project