One team. Six disciplines. Zero hand-off gaps.

What we actually staff

Each discipline is held by people who have shipped production systems — and who sit in the same delivery, not as a chain of subcontractors.

01

Software & Platform Engineering

Multi-tenant platforms, operational workspaces and high-reliability software with a release train that still works at version forty.

• Modular architectures, APIs and service boundaries
• SaaS and operational workspaces with tenant isolation
• Release discipline: contracts versioned, rollbacks rehearsed
• For Business — the organisational host we run ourselves

02

Artificial Intelligence

Grounded copilots that propose. Named people who Confirm. Placement decided by latency, secrecy, cost and continuity — not by a vendor’s region.

• RAG and knowledge-grounded assistants, not chat bolted on
• Local, edge, private and frontier models behind one gate
• Computer vision and document intelligence at the cell
• Writes happen only after a responsible person Confirms

03

Data & Knowledge

A keep-set the organisation still owns after people leave: decisions, context, evidence, owners and versions — searchable by humans and by agents.

• Knowledge graphs, ontologies and semantic search
• Enterprise and industrial Knowledge Engines
• Operational analytics connected to the same record
• Nothing locked in a chat log or a personal drive

04

Hardware & Software Integration

Intelligence next to machines, cameras and sensors — including air-gapped cells that keep working when the link drops.

• IoT, cameras, PLCs and embedded edge nodes
• Industrial equipment and monitoring at the cell
• Local cabinets and air-gapped deployments
• Hardware–software contracts that survive a shift change

05

Product, Design & Communication

Clarity is an economic decision. Interfaces people adopt, authoring for walls and totems, audience counts that never hold a face.

• Product strategy, research and operational UI/UX
• Design systems that keep quality as the product grows
• Digital signage, LED walls and interactive spaces
• Anonymous flow analytics — counts, not identities

06

Governance, Quality & Compliance

A control system, not a PDF at the end: inventory, classification, oversight, literacy and an exportable dossier.

• EU AI Act — inventory, classification, literacy, FRIA
• GDPR-aligned data design and model versioning
• ISO 9001, process design and audit-ready records
• Named owners. Confirm on write. Evidence you can export

Where the work lands

Expertise has to live in a host you own.

We do not leave a slide deck. The same contract sits on a Knowledge Engine, on For Smart Manufacturing and on For Business — change the environment without rebuilding the control system.

Environments we already know

The same engineering, different constraints.

Industries is not a gallery of logos. It is where this team has already had to place intelligence, name an owner and keep a record.

All industries

EU AI Act & responsible AI

Governance is engineering — not paperwork at the end.

The AI Act is often discussed as a compliance problem. We treat it as an architectural constraint: know which systems you use, understand their risk, assign responsibility, keep humans in control, train the people who use them — and keep the evidence.

Those capabilities live in For Business: inventory, classification, literacy, oversight, transparency, FRIA, incidents, suppliers, models and dossier export. We also design the surrounding systems so those obligations are possible from the first decision, not after go-live.

Operating model

How the disciplines actually connect

Classification, placement and Confirm are decided before code is written — so the operating system you ship is the one you can still show an auditor.

Across current and previous work, this team has shipped university ERP, healthcare and risk platforms, AI-first manufacturing, security systems, smart-city analytics, digital signage, institutional platforms and EU AI Act deployer governance.

Where to go next