Case studies
Topic
Status
18 case studies
CS-01Building an enterprise visitor management system for Saudi operationsFive roles, one visit. How the data model and the interfaces were separated so a receptionist, a guard, a host and a supervisor could each do their own job from the same record.CS-03Building legal AI that refuses unsupported claimsMaking a model decline is harder than making it answer. The retrieval design, the refusal behaviour, and why "no source, no claim" is an architecture rather than a slogan.CS-06Integrating SAP Ariba using strict cXML validationEnterprise B2B protocols do not forgive. Why validation moved before transmission, and what a push history is actually for.CS-16Running AI agents locally for business workloadsWhat actually happens when you run agents on your own hardware every day, rather than benchmarking them once and writing a post about it.CS-02Designing an Arabic-first visitor management experienceWhat it takes to build software Arabic-speaking staff actually want to use, rather than an English product with a language toggle.CS-04Architecting multi-tenant legal AI with isolation, roles and auditWhen the data is privileged, tenant isolation is a database property rather than a query filter. How the platform is structured, without describing anything that should stay private.CS-05Building AI due diligence around evidence instead of answersDue diligence rewards finding what is missing. That is the opposite of what a summarising model is good at, and it changes the whole design.CS-07Turning physical access logs into an enterprise software workflowGate hardware produces rows. People ask questions about presence. The work is entirely in the distance between those two things.CS-08Building an internal CMMS around real operational workflowsThe honest case for building maintenance software instead of buying it — and the conditions under which that decision is wrong.CS-09Designing an employee IT support system people actually useThe competitor is not another ticketing product. It is a two-second message to whoever sits nearest.CS-10Designing a booking platform with 30-minute slots, holds and staff operationsThe booking form is a weekend's work. Holds, concurrency, arrivals that don't match bookings and the queue that forms when a session overruns are the actual product.CS-11Connecting online and in-person consultations in one booking systemAn online appointment and a physical one look like different products. Treating delivery mode as a property of the appointment keeps them one.CS-12Rebuilding a Framer website without losing the original designA faithful rebuild is not a pixel copy. Deciding which details are the design and which are artefacts of the tool is the entire job.CS-13Why we reworked a CMS to feel more like Framer or WixThe complaint was specific — uploading galleries and video was too complicated. That is a better requirement than most product briefs.CS-14Building route-aware technical SEO for a multi-page corporate websiteMetadata as architecture rather than a content field — generated per route, with structured data describing connected entities instead of isolated fragments.CS-15Building an Arabic/English corporate website without treating Arabic as an afterthoughtBilingual is not a toggle. Direction, typography, navigation and content hierarchy all change, and retrofitting any of them is more expensive than designing for both.CS-17Mac mini versus cloud for client-side AI in Saudi ArabiaThe comparison is not hardware price against instance price. It is total responsibility against total flexibility, and the answer changes per client.CS-18Technical founder workflow: from client problem to production softwareThe recurring shape of the work across enterprise integrations, internal tools and AI products — and the parts that are always harder than planned.