Geotechnical field-services site
A soil-injection contractor was winning work through reputation and losing it through an unsearchable presence. We shipped the public engineering site and a parallel surface for the same offer.
The situation & problem
Hamat United sells soil injection, dewatering, and lab-backed geotechnical reports. The commercial claim — 10-year warranty, before/after inspection — was not on a durable site.
The operational constraints
Technical Arabic content, service taxonomy, and a lead path that can carry project location and warranty questions.
Architectural tradeoffs & what was refused
A contractor template with stock photos and no service model. Two unrelated brands for the same company.
What I built & shipped
Production site on hamatunited.net plus hamatex.vercel.app, service catalog, process steps, and WhatsApp / call intake.
Architecture & stack
TypeScript, Next.js, bilingual pages, form + WhatsApp intake.
Result & measurable impact
Engineering claims and warranty terms now live on a page operations can send instead of a PDF.
Next iterations & roadmap
Job-site report upload so inspection photos attach to the same lead record.
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 me where your current operational system or product is breaking.