Case studies are where the marketing copy meets the production environment. We publish ours with screenshots, dates, and metrics anyone can verify on demand: PageSpeed reports, Google rankings, AI engine citations, real owner quotes, and ticket-system extracts where the client has consented. No before/after charts that conveniently lose the axis labels.
The articles tagged here cover specific 365i clients (always with consent, often anonymised to a regional descriptor plus first-name initial), the platform and build decisions that produced their results, and the parts of the story that did not work first time. The aim is honesty about what hosting can and cannot do, with proof that survives a sceptical reader.
Most of our case studies share a common shape. We name the client type and sector. We state the situation in plain numbers (visits, page counts, costs, hours of work). We describe the decision we made and why. We publish the outcome with figures, and we admit any parts of the work that needed a second attempt. If a client refuses publication after the work is done, the case is not published; if they request changes, we make them or pull the post. That happens occasionally, which is the point.
Common themes across the cases on this tag: takeover stories where a small business inherited a site from a designer who went quiet; PageSpeed and Core Web Vitals work where a site went from sub-50 mobile scores to 90+ without buying a new theme; AI visibility builds where a site started getting cited in ChatGPT and Google AI Overviews after the right discovery files were put in place; and migration projects where the platform choice and the configuration mattered more than the hardware.