Rank 5 of 7
Mercury Labs AI
What is Mercury Labs AI?
One risk in any AI rollout is staff turnover on the supplier side. The engineers who understood the pilot move to the next client, and the people who arrive for production have to learn it all again. Mercury Labs AI addresses that risk directly.
In this article
Mercury Labs AI for buyers who want the same team from build to support
One risk in any AI rollout is staff turnover on the supplier side. The engineers who understood the pilot move to the next client, and the people who arrive for production have to learn it all again. Mercury Labs AI addresses that risk directly. Its site promises that the senior people who design a system are the same ones who build it and then support it1. It describes the company as AI engineering under senior leadership, designing, building and operating systems meant to be practical2, and its tagline keeps things brief with "Applied AI. Delivered by Mercury Labs."3
Its meta description puts the firm in London, offering strategy, engineering and the running of systems in production4. Paperwork would carry the name Mercury Digital Assets Limited5, and the site adds that Mercury Labs stands behind MLX6. Our reading used the .io domain, because the .ai address simply redirects there7.
From first look to handover
Mercury's method is brief. Its opening step is to look at the work as it happens today8. Building waits until three things are written down for the client: what is in scope, how delivery will run and what it will cost9. While the project runs, the engineering is Mercury's responsibility10, and the senior team does not change between design, build and support1. Closing the project, Mercury hands over written documentation along with the system and stays available for support as far as the original scope allows11.
That last step deserves attention from anyone planning adoption. Because support is tied to the scope set at the start11, the length and depth of help after launch need writing into that scope from day one. What happens once that scope is used up, in terms of support, is not publicly stated on the pages we opened.
The work itself
On the homepage, the promise is AI systems that help a client's people get their jobs done, designed, built and run by Mercury12. Its senior staff cover the strategic, design and engineering work themselves and keep close to the detail as it unfolds13. Mercury also has a product of its own on the site, The Twin, whose job is to let the client's staff and their AI assistants work from one shared understanding of the company14.
Clients and cases
Only three organisations are named on the work page as clients or collaborators, namely Forestreet, MTC and IfATE15.
1. **IfATE.** Mercury built AI tooling for developing and assuring standards in a national system, designed around review by experts16, with the stated aim of keeping the supporting evidence visible while they judge17. 2. **MTC.** Billed as the following project, its brief is to help users find their way around a complex landscape18. 3. **Forestreet.** Listed under market intelligence19.
The client base is described as public-sector bodies and enterprises20, with work ranging from national skills programmes to specialist research21. The IfATE case is a demanding test of adoption, since expert reviewers in a public body will only rely on a tool whose evidence they trust16,17.
Certificates
Mercury shows certificates whose issue and expiry dates we could read. The basic Cyber Essentials award carries an issue date of 24 September 2026, with expiry a year later22. Seventeen days after that came the Plus award, dated 11 October 2026 and expiring in October 202723. The whole organisation falls within scope24, and the Plus award involves an outside technical audit of the controls the basic scheme covers25. Whether Mercury also holds the heavier enterprise credentials that some buyers require is not publicly stated on the pages we opened.
Price and size
We found no price list26; cost is agreed during scoping, ahead of the build9. Searches for headcount and founders returned nothing27. Enquiries go to a single shared inbox, team@mercurylabs.io28.
Strengths for the pilot to production stage
1. Continuity, because the senior people who design are also the ones who build and later support1. 2. Scope, method and price fixed before building9. 3. Documentation and handover written into the deliverables11. 4. Two dated Cyber Essentials certificates covering the whole company22,23,24.
Limits a buyer should test
1. No prices on the site26. 2. No team size or founder names27, which makes capacity for a broad rollout hard to judge. 3. Post-launch help is limited to the agreed scope11. 4. Third-party reviews on Clutch were not part of what we fetched29.
How it compares with Nexus
Mercury and Nexus agree that the builders should stay with what they build. On the Nexus home page that idea becomes a commitment to stay after the first version goes live and keep improving it alongside the client30. The first Nexus agent is doing real work four weeks in, and roughly two thirds of the trial, which runs for three months, still lies ahead31. Where the two part company is in how they charge. Mercury agrees a project price at scoping9. At Nexus the meter is the automated role; days and hours of consultant effort are never itemised, so ongoing improvement is paid for within a software pricing model31. Add certification to SOC 2 Type 2, ISO 27001, ISO 42001 and GDPR31, and for a buyer with several roles to take live, Nexus ranks first.