Verdantia Group is the directory's clearest example of enterprise Web4 adoption that is neither cosmetic nor PR-driven. The company is a mid-market enterprise software vendor headquartered in Manchester. They are not a startup. They have been operating since 2014, they have a meaningful customer base in the British and Irish mid-market, and they have published more about their internal agentic rollout than almost any company of their size in the directory.

The rollout was authorized in mid-2024 by the company's CTO, Ines Holroyd, after an internal review concluded that a portfolio of internal back-office tools — many of them aging, many of them stitched together in ways that produced more friction than value — could be replaced by a single agentic operations layer. The published rollout plan covers seven internal workflows across three business units. As of the most recent public update, two of the business units have completed the transition and the third is in pilot.

The Bulletin tracks Verdantia because the rollout is the inverse of the venture-startup Web4 story. Verdantia is not building an agentic platform to sell. They are not arguing in print that the operating-system metaphor is the right one. They are not in the directory because of a thesis announcement. They are in the directory because they have quietly done one of the things the broader Web4 thesis predicts mid-market companies will do, and they have done it publicly enough to be evaluated.

The published rollout has three editorial features the Bulletin has cited repeatedly. First, Holroyd has been explicit that the agentic layer is replacing internal apps rather than augmenting them. That is the structural Web4 move — the apps themselves go away, and the operations layer carries the work. Second, the rollout has preserved an explicit audit trail. Every agent action is logged in a structured form, with a clear chain back to the human owner who authorized the workflow, and Verdantia's compliance team signed off on the schema before the rollout began. Third, the company has published a quarterly retrospective on the rollout. The retrospectives are short. They are not promotional. They are an unusual public artifact for a company of Verdantia's size and they have been the basis for several of the Bulletin's essays on enterprise Web4 patterns.

What is harder to evaluate is whether Verdantia's rollout is portable. The published patterns are useful, but they are patterns drawn from a specific company in a specific market with a specific compliance posture. The Bulletin's editorial position is that the rollout is informative about what enterprise Web4 can look like rather than prescriptive about what every enterprise Web4 deployment should do. Holroyd has said the same thing in print, which we appreciated.

We have also not been able to confirm [TKTK: the orchestration platform Verdantia chose for the rollout], which is the question Bulletin readers have asked most often. The published rollout documentation describes the layer architecturally but does not name the underlying platform. The Bulletin has chosen not to speculate.

Verdantia is the directory's reference for what real enterprise Web4 adoption looks like outside of pilots and pilots-of-pilots. The directory entry will be updated as the third business unit's rollout completes and as the next retrospective is published.