Developer project pipeline site
Development work was a paragraph in a company profile. We shipped a bilingual developer site that separates development, project control, opportunity study, and marketing.
The situation
Al-Ameriya sells the development process, not a brokerage catalog. The site had to carry projects and a consultation path.
The constraint
Arabic / English, a service taxonomy that is not a listings portal, and projects used as proof rather than inventory.
What we refused
A scraped listings theme. An agency template that hid the development process.
What we shipped
Service pages, project showcase, bilingual switch, and consultation intake.
Stack, on purpose
TypeScript, Next.js, bilingual content model. Services as records, not a single contact form.
What changed
Inbound leads can point at a named service line instead of “real estate help.”
What we would do next
Project-level inventory and payment-plan objects when a development goes to market.
System surfaces & interface captures
Hover and click any record to open the full-resolution pixel inspector with zoom lens and 1:1 precision.
Have a similar constraint?
Tell us where your current operational system is breaking.