Case Studies

Four engagements, described with real numbers and without client names. That is a deliberate constraint of this site rather than a gap: sectors are described instead, and every figure comes from a connected analytics property or a count of work actually delivered.

Each one includes what did not work as well as what did, because a case study that reads as uninterrupted success is not describing a real project.

The work

Search and AEO for an Industrial Components Distributor

Industrial fasteners and components distribution, United States. A distributor whose catalogue was effectively invisible to search and unreadable to AI assistants, rebuilt around the way engineers actually specify parts.

Organic Growth for Two GPS Fleet Tracking Properties

GPS fleet tracking, two properties run as one programme. Two related properties in the same category, run as a single programme so they complement rather than compete, across a combined estate of nearly 600 URLs.

Running a Content Programme Across Six Estates

Multi-site content operations. A content operation covering six separate estates, where the hard problem is not producing articles but stopping defective ones from reaching a live client site.

A Lakehouse Pilot for an Awards Manufacturer

Awards and recognition manufacturing, United States. A proof of concept that put scattered CRM, web and order data into one governed lakehouse, and immediately overturned an assumption the business had been running on.

How to read these

The numbers are 90-day totals to 25 August 2026 where they come from Search Console, and delivery counts where they do not. Nothing is annualised, projected or rounded up, and where a figure would flatter the result by hiding a difference between two properties it is reported separately instead.

Talk about your situation

The first conversation is short and mostly questions. Get in touch and tell me what you are trying to fix.