Bottle theme
Birmingham Worked from Barcelona UK GDPR · ICO One hour behind us

Birmingham.
Supply chain AI.

Most of what arrives from Birmingham starts as paper. A supplier sends a certificate of conformity as a scanned PDF, a haulier sends a delivery note as a photograph, and somewhere downstream a person retypes both into a system that will not accept either. That is not a glamorous AI problem. It is the one that pays.

Last reviewed 5 September 2026 · Engineering guidance, not legal advice.
WHAT IS ACTUALLY DIFFERENT HERE
01

The ICO, and mostly not much personal data

Birmingham companies operate under the UK GDPR and the Data Protection Act 2018, with the ICO as supervisor. What is unusual about industrial work here is how little of the interesting data is personal: torque readings, batch numbers and despatch notes are commercial confidences rather than personal data, and the governance conversation is correspondingly shorter. The exception is anything touching drivers, employees or customers, which lands squarely back in scope.
02

Adequacy, and why we design around it

UK to EEA transfers currently rest on adequacy decisions that are reviewed rather than permanent. For a supplier with plants or customers on the continent that is a real planning question, so we prefer architectures that keep the data where it already is and move the computation to it instead. The legal call is your counsel's; not making it harder is ours.
03

UK regions, or the factory floor

The providers run UK regions in the south of the country, which settles residency for anything cloud-hosted. A good deal of Midlands work does not go to the cloud at all: line-side inspection wants the inference next to the camera, and some plants will not put a network cable near the machine. Both are ordinary deployments, not special cases.
04

Your customer is your regulator

In an automotive or aerospace supply chain the binding constraints usually arrive by contract rather than by statute — traceability obligations flowed down from the manufacturer, audit rights, retention periods, export-control restrictions on drawings, and clauses about where data may be processed. We read those clauses before designing, because they decide more of the architecture than any general principle does.
THE WORK THAT COMES OUT OF THIS CITY

The Midlands is where things are made and where things are moved. Birmingham sits at the crossing point of the motorway network, so a large share of the country's distribution capacity is within an hour of it, and around that sit the tiers of engineering suppliers that feed vehicle and equipment manufacturers, plus the second-largest concentration of professional services firms in the UK.

The most common engagement is a document pipeline. A supplier quality team receives certificates, test reports and non-conformance notices in a dozen formats from hundreds of firms, and someone reads every one. Extraction that is right ninety per cent of the time is worse than useless here, so the design work is in the routing: what the system handles alone, what it escalates, and how a reviewer sees why it was unsure. Our logistics document pipeline is that pattern written out end to end.

Second is inspection. Cameras on a line generate more images in a shift than a quality engineer will see in a career, and the useful question is almost never can a model detect the defect but what happens on a false negative and who signs off a model change. Quality inspection covers how we handle that.

Third is planning. Demand and supply signals in this region are spread across an ERP, a planner's spreadsheet and several decades of a scheduler's memory, and the last of those retires. Supply chain planning and, on the retail side, demand forecasting describe the two shapes that takes.

Professional services firms arrive with a quieter version of the same thing: bundles of documents, a deadline, and a chargeable hour that is being spent on reading rather than judgement.

HOW A BIRMINGHAM PROJECT ACTUALLY RUNS
01

We come to the site, not the boardroom

For industrial work the discovery visit is worth doing where the documents and the machines actually are. Barcelona to Birmingham is a direct flight, and on a normal engagement we do not bill it separately.
02

Remote, one hour ahead of you

We work an hour ahead of UK time, which in practice means our morning is already underway when yours starts and nothing waits overnight for an answer.
03

Handover on the floor

The final visit is your engineers running the system with us watching rather than the reverse. After that it is yours: your repositories, your accounts, your maintenance schedule.
QUESTIONS
QUESTIONS — 5

No. One office, in Barcelona. We travel to the Midlands for discovery and handover, and for site visits when a plant needs seeing rather than describing. We would rather say that plainly than list an address we visit twice a year.

No, and it is a common starting condition. The system runs in your cloud accounts or on your hardware, in a UK region or on the site itself, and the data does not come to us. What crosses the border is our access to your environment under your controls, which is a different thing from a transfer of the data — though it is worth confirming with whoever wrote the clause.

Yes, for a good deal of this work. Open-weight models are now capable enough that inspection and document extraction can run on hardware inside the plant with nothing leaving it. That is covered under air-gapped deployment. The trade-off is that you own the GPUs and the update cycle, which we will size honestly rather than optimistically.

The ICO, under UK GDPR. For most Midlands industrial projects the personal-data footprint is small — the sensitive material is commercial, not personal — but the moment employee monitoring, driver data or customer records enter the design, the full regime applies and we treat it accordingly.

The published ranges on our pricing page, in euros and exclusive of VAT. They do not vary by region. What does vary is integration effort: connecting to a twenty-year-old MES is genuinely more work than connecting to a modern API, and we would rather scope that honestly than discover it later.

Keep reading
30-minute technical call · no deck

Got a process
buried in paper?

Thirty minutes on where the documents come from and what happens to them. That conversation usually settles whether this is worth doing.

CASE STUDIES

Shipped work.
Go and check it.

The work we can name, with the live site, our scope and the boundary made explicit. Select a project to see the evidence; each is a full case study, not a logo or a claim.

sonora.com
The Sonora homepage on desktop: a full-bleed dune landscape behind the headline “Transform Your Life with Sound”, with App Store and Google Play download buttons.
sonora.com — homepage, 1440×900 sonora.com →
Live Consumer wellness · Mobile + web

Sonora

Cognitive AI Ltd · 2026

A free sound-wellness app, described by its publisher as AI sound therapy that reads a short vocal sample at the start of a session and generates a soundscape for that moment. We designed and built the website and its backend, produced assets for the iOS and Android apps, and supported the application prototype.

Read the case study →

See every published project →

WHO WE HAVE BUILT FOR

Twenty-one years of applications, platforms and campaigns for names you know.

See all of our work →