Named where we may name it, described generically where we may not, with no traffic or revenue claims.
Some agency pages in this market show a case study marked hypothetical. We show the work instead. Two of these pieces are public case studies with a construction client behind them, one is our own product, and one is described without a name because the client has not agreed to be named. None carries a ranking, traffic or revenue figure, because no measurement window has closed yet.
A distributor of electrical, mechanical and architectural building systems, trading arm of the ACC Group (pht.com.sa), with 144 products across 22 brands. Built from the first commit in October 2024, rebuilt in one week in 2026 with 478 bilingual URLs, a content API, an 11-screen admin and attribution on every quotation request, and maintained throughout.
Read the case studyOur own prototype: a workshop assistant that reads scanned repair manuals and answers a technician's question with the document, the page and the figure it came from. No workshop is running it in production yet.
Read the case studyOur own product and the proof behind the follow-up automation: an ad or a form creates the enquiry, the CRM gets it with its source, a voice agent calls, the transcript and summary are stored and the callback is booked, every step a row. Built and demonstrated, never launched to paying customers, and we say so.
Read the case studyIt logs in, collects data from a portal on a schedule, retries when something fails, and shows every run on a screen the team watches. When the portal changes, it is updated in settings, not code. Unnamed at the client's request; it is the pattern behind the portal and back-office side of the automation package.
The first findings in writing, what a buyer cannot find on your site today, and a fixed price for the first step, within one working day.
Or send your site link and a person replies within one working day.