Built in Derby, the way Derby builds things
ElementX2 is an AI automation agency run by an engineer, not a sales team. We’re based in Derby — a city that has been engineering things that have to work, from locomotives to aero engines, for two centuries. We hold ourselves to the local standard.
Ref 01 · Where we come from
Heritage: logistics and recruitment
We cut our teeth automating the operational middle of UK logistics and driver recruitment — the world of job boards, screening calls, PODs, Trello boards and shift spreadsheets. That work taught us the discipline this site is built on: describe only what the code does, treat AI output as an unreliable component, and engineer the compliance in from day one.
The proof runs through our own workshop. Rather than decorate this site with borrowed logos, we built five complete systems — a compliance-gated voice-screening agent, a product marketing site, a Trello-based ATS with AI email parsing, an automated social-publishing pipeline, and a real-time voice-persona demo — and documented them as they actually are: pre-launch products, internal tooling and capability demonstrations. Every technical claim on this site can be traced to one of those codebases.
That heritage is proof of depth, not a boundary. The same patterns — voice agents, document pipelines, systems integration — apply to any operations-heavy business, from breweries and manufacturers to professional practices. The work speaks for itself →
Ref 02 · What we believe
The operating principles
Truth over theatre
No invented case studies, no borrowed logos, no metrics we can’t evidence. If a page on this site claims it, the code exists and we can show it.
AI is a component, not a religion
LLMs are powerful and unreliable. We wrap them in deterministic rules, validation and fallbacks — and we’ll tell you plainly when automation is the wrong answer.
You own what we build
Source code, documentation and training are part of the handover. No lock-in, no licence meter, no dependency on us to keep the lights on.
Direct access, no layers
You talk to the engineer doing the work — from the first email to the last commit. That’s why the only contact route on this site is an email address.
