Work / dossier
SOS Trading and Contracting
An industrial fire-safety contractor whose credibility is technical before it is visual. Complete digital presence, built from nothing and still operated.
The record.
Launched — 11 pages, structured data and agent-readable signals from day one, on infrastructure the client owns.
Contact routing wired end-to-end and tested — a message reaches a person, not an unread inbox.
First fully pipelined release: build, validate, deploy, and verify with no hands on the server.
Redirect and not-found behaviour hardened; the fix was verified against the live production responses the same day.
Corrections, left visible.
What broke on this entity, left visible — struck through, corrected in red, and turned into a check that now runs for every entity.
Security headers were configured once at the top level, so every page inherits them.
One page-level header declaration silently cancelled the entire inherited set — a documented behaviour of the web server that no error message reports.
Shared header include, explicitly imported wherever a local header exists, plus config validation in the deploy pipeline.
The deploy succeeded, so visitors have the new version.
The CDN kept serving month-old files — cached as immutable under the same address.
Versioned asset addresses, and a release check that fetches the exact URLs the live page requests and inspects the cache headers.
A redirect is a detail.
Secure pages were redirecting visitors to their insecure counterparts, and missing pages answered "found".
An estate-wide automated check now walks every redirect and not-found path on every site, every release.
A fire-safety contractor is judged by inspectors, procurement engineers, and — increasingly — machines. This entity is built to be legible to all three, and the correction record above is how it stays that way.
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.