Industries · Real estate
Property platforms built to survive an investor audit.
- Case studies
- 0 projects written up: .
- Built for
- Developers, listed property companies, brokerages and holding groups.
- Typical scope
- Corporate and investor relations platforms, project showcases, bilingual content, approval workflows and a headless CMS.
- Rated
- 4.7 / 5 from 23 Google reviews
In short
Property companies need two very different kinds of platform. A listed developer's website is a disclosure surface, where governance documents and financial reporting have to publish on schedule, stay traceable and be right in two languages. A developer's project site is a showcase that the marketing team must be able to update the day a new tower launches. We have built both.
What the sector asks of software
Three things every property build has to get right.
A listed company website is a disclosure surface
Modon Holding
Projects change faster than developers are available
Preatoni
Arabic and English, published together
Modon Holding
Sector notes
What building for developers and listed companies has taught us.
Two property companies, one listed and one private, with different obligations. These are the things we would say to a developer, a holding group or a brokerage before the first sprint.
A listed company's website is a regulated publication
Modon Holding is a listed developer, and its website carries board changes, governance documents and financial reporting that investors and regulators read. Those items publish on a schedule, in English and Arabic, and someone has to be able to show who approved each one and when. A homepage first build would have put that at the bottom of the backlog.
So the platform was built around approval and versioning. Every change is kept with its approver and time, both languages are published together and kept in step, and disclosures go out at the agreed time rather than when someone is free. The homepage is still handsome, but the system underneath is the reason the site survives an investor relations audit.
The marketing team updates projects, not the developer
Preatoni needed a corporate and projects site that could carry projects, vision and news without a developer on call. The front end is Next.js, server rendered for speed and search, and the content lives in Strapi with media in S3. The marketing team adds a project, updates a gallery or posts news themselves, and the site stays fast because the rendering is ours and the content is theirs.
The headless split is the right default for a developer with a changing portfolio. The team gets a structured editor instead of a page builder, and the public site keeps the speed and the indexable pages that a brochure PDF never had.
Arabic and English, kept in step
Property buyers and investors in the Gulf read in both languages, and the English and Arabic editions of a developer's site must say the same thing on the same day. On Modon the two languages publish together, inside the same approval workflow, so a disclosure cannot go out in one language and lag in the other.
The right to left build is the same discipline we apply on school and retail sites: designed from the first commit, with its own typography, never a mirror applied at the end. For listings, search and enquiry flows we draw on the marketplace and classifieds patterns we built for List It and the service marketplaces.
Speed and search are part of the brief
A developer's projects are found through search as often as through a sales agent, which is why Preatoni's pages are server rendered by Next.js rather than assembled in the browser. Every project, vision page and news item is indexable and fast, and the images that make property sell are served from S3 through the CMS rather than embedded in a page builder.
The same architecture carries Modon's disclosure pages, where speed matters less than reliability but search still matters to an analyst looking for last year's report. One stack serves both, which is why we recommend it for a holding group with a corporate site and several project sites to run.
What we build
From the project page to the disclosure calendar.
Investor relations platforms
Governance, reports and announcements with approval workflow, versioning and scheduled release.Disclosures publish on schedule with an approval trail behind each.
Project and portfolio showcases
Projects, locations, galleries and news on a fast, indexable front end the team edits themselves.Marketing adds a project the day it launches, without a developer.
Bilingual corporate sites
Arabic and English editions kept in step, built right to left properly.English and Arabic go live together and stay in step.
Headless CMS and media
Strapi with S3 uploads so pages, documents and galleries are managed without a deployment.Pages, documents and galleries change without a deployment.
Approval and audit trail
Every change recorded with its approver and time, for the day someone asks.Every version is kept with its approver, for the day someone asks.
Enquiry and lead capture
Project enquiries and brochure requests routed to the sales team rather than a shared inbox.Project enquiries land with sales, and in the CRM.
How it ships
How a property platform ships with us.
The path Modon Holding and Preatoni took, from the list of disclosure obligations to a site the marketing team runs.
Discovery
- List the obligationsWhat, when, which languages, who approvesWritten down before design starts.
- Model the contentProjects, documents, newsStructured types with their relationships and versions.
Build
- Headless CMSStrapi with S3 mediaApproval workflow and version history in the content model.
- Fast front endNext.js, server renderedIndexable project and disclosure pages in both languages.
- Enquiry and lead captureRouted to sales and CRMBrochure and project requests reach the right desk.
Quality
- Audit rehearsalWho approved what, whenEvery version traceable before the first real disclosure.
- Bilingual release testEnglish and Arabic in stepBoth editions publish together inside one workflow.
- ApprovedClient sign off per release
- ObserveTwo weeks of live use
- Live and handed overCode, cloud and docs are yours
Numbers from the work
What the property projects delivered.
Taken from the case studies, not rounded up.
Every change
kept on Modon, with who approved it and when
2
languages published together and kept in step
On schedule
disclosures released at the agreed time, not when someone is free
Self-serve
Preatoni projects and news updated without a developer
Questions developers and property groups ask us
Yes, with approval and versioning at its core.
Tell us what the business needs. We will tell you what to build first.
Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.
Get in touchPROVEN RESULTS