EngSpace is founder-built software. That is not a stage we hide; it is the reason the product works the way it does.
Engineering Workspace was written by Mohamed Abokhatwa, a mechanical and design manager with more than two decades of delivery on major projects in Saudi Arabia — water infrastructure, seawater RO, pump stations, pipelines and building MEP. It was not designed in a lab and then pointed at construction: it was written inside the delivery of a live mega-project, by the engineer running that delivery, on the days the problems appeared.
The follow-up engine exists because replies went missing. The claims ledger exists because entitlement once had to be reconstructed from twelve folders at the worst possible moment. The outbound check exists because the most expensive mistakes are the ones that leave the office looking confident. Every feature has a scar behind it — the proof page tells that story with numbers.
Big platforms answer to a roadmap. This product answers to the work. When you evaluate EngSpace you talk directly to the engineer who wrote it, who has sat on your side of the table with a consultant response overdue and a claim to evidence.
And where it is going: as the product grows into its company, the roadmap is public and simple — a registered commercial entity, an independent security assessment before the first multi-company rollout, and published customer stories as trials convert. Until then, everything above is signed with a name, not a brand.