How we built Etman Group a platform with a real search engine

Etman Group develops residential and mixed use projects out of Heliopolis. By 2024 the company was carrying a portfolio too large for a brochure site.

Buyers arriving from a launch campaign wanted to browse inventory. Partners and institutional visitors wanted the corporate story. Those are two different readers with two different questions.

Most developer sites pick one of those audiences and quietly disappoint the other. The usual move is to hide real listings behind an inquiry form, which protects the sales team and loses the buyer.

The brief was to serve both from a single platform. Brand led presentation on the surface, a working property search underneath, and the two connected closely enough that nobody feels handed off.

We designed the corporate layer first, because it sets the tone for everything a buyer reads afterwards. Company story, project portfolio and completed work, presented with the confidence a developer of this size has earned.

Underneath it sits the search engine the sales side actually needed. Listings are structured data rather than page content, with real fields for area, project status and built up area. The filters query attributes instead of guessing at a text match.

A buyer can narrow to delivered units in a specific area at a specific size. The result set appears immediately, and any card opens the project page behind it. The interface is bilingual, so one source of listing truth serves Arabic and English visitors.

Two copies of a listing always drift apart within a year. One record with two languages does not. The build came out of our website and app development practice, with the brand layer from graphic design and brand identity.

The unglamorous work was the data structure. It is also the part that decides whether a property site is still usable two years later.

We modeled projects and units so that adding a development is a content operation. Moving a status from under construction to delivered is one field. Changing an available size range is another. The search index follows automatically.

Filters stayed limited to the criteria buyers really use. A panel with twelve controls gets abandoned, while one with four gets used. Result cards carry enough to shortlist at a glance, so browsing does not turn into ten open tabs.

Bilingual consistency needed its own discipline. Field names, status labels and sort orders had to mean the same thing in both languages. Otherwise the same search returns two different result sets.

The rest is craft. Responsive templates keep the filter controls reachable on a phone. Gallery handling keeps render heavy project pages quick. Typography stays consistent across the Arabic and English builds, so neither one reads like a translation of the other. More work like it sits on our success stories page.