SOS Trading and Contracting
Complete digital presence for an industrial fire-safety contractor.
Systems architect · Egypt
Ezz Ashater
I build the digital infrastructure that decides whether a business gets found, trusted, and chosen — and then I operate it.
Building systems since 1994. Seven digital entities built and operated — four of them documented below, plate by plate.
Real businesses, still operated.
Running systems with real customers — I built each one and still operate it. Three are public today; the fourth is in client review. The captures are real and dated.
MAXIM Group
Digital foundation for a group holding company.
Wave Builders
Brand and bilingual Arabic–English site for a construction company operating in Saudi Arabia.
KOTIVA
Brand and product site, iterated across successive versions without breaking the live entity.
The dossiers — plan, record, corrections, per entity →
The fleet — seven entities, one index
Entity Since Live In review Workshop
KOTIVA · client review 2026-05 · client review 2026-05 current stage: in client review
Awaiting launch approval · named at launch 2026-06 · named at launch 2026-06 current stage: in client review
In the workshop · named at launch 2026-07 · named at launch 2026-07 current stage: in the workshop
The unnamed row is real — an entity in the workshop is counted, not named, until its owner says so. Other engagements aren't public yet; I'll walk you through those in a conversation.
Two ideas I keep coming back to.
The Technical Credibility Gap
The distance between how credible a business is in the room and how legible it is to the systems that now decide who gets found. It has four failure modes, and every one of them is diagnosable.
Paint vs Plumbing
Most businesses buy paint: a redesign, a new logo, more posting. The problem is usually plumbing — infrastructure, entity structure, the connections between systems. Paint fades on a schedule. Plumbing compounds.
It's also the first question I ask: is this a technical problem or a perception problem? I only take the technical ones.
I run my own practice as a documented system.
One person can operate several live businesses only if the practice itself is a system — documented, checked, and allowed to be boring.
Every decision is written down
Why a thing was built the way it was, what was rejected, and what would have to change to revisit it. Nothing important lives only in someone's head.
Every defect becomes a check
When something breaks once, it becomes an automated test that runs before every release. The same mistake doesn't get to happen twice.
Nothing ships past a gate
Performance, accessibility, security, structured data, and cross-browser behaviour are checked and recorded before anyone sees the result — including this site.
The operating record
decisions 535 on record — each with rationale, rejected options, and a rollback path
patterns 46 documented failure patterns, from real incidents
checks every pattern is enforced by an automated release check
Release gate — this site, 2026-07-30
browsers Chromium + WebKit · 0 blocking findings
a11y 0 critical · 0 serious
lighthouse 98 · 100 · 100 · 100 — mobile, real network
The Lab measures this page in your own browser — the schema, the speed, the cost of restraint. Nothing there is a mockup.
Working together
Client work starts with a conversation — no commitment, no pitch. If it turns out I'm not the right fit, I'll say so.
The practice runs its own storefront the same way it runs client work — built on the same platform, passed through the same gate, operated from the same record.
