Every data set has an owner. When Copilot arrives, it reads a governed estate.
A firm of 50-200 people holds information that mostly belongs to other people: client files, payroll, the pipeline, the archive. AI reads through the same permissions your people do, so an estate where data is ungoverned is where adoption fails first.
Data is one of the ten domains of The Technology Framework. One dimension of one framework, made AI-ready and owned by a named Head of IT.
Data governance is unglamorous and specific. When this dimension of the framework is owned, four things are true and stay true.
None of this needs a new department. It needs an owner, a map, and a rhythm.
The starting point is usually familiar.
The work starts with the map: what the firm holds, where it lives, who touches it. Everything else is decided from there.
Who can see the client files? These people, for these reasons. How long do we keep this? This long, then it goes. What would Copilot read? Whatever the labels and permissions allow, and both are governed. The numbers the board reads inherit the same discipline: that is the neighbouring domain, Analytics.
Copilot, and every agent that follows it, answers from whatever your permissions expose. Point it at a governed estate and it works from the right files. Point it at an overshared drive and it reads the oversharing. Making data AI-ready is the same governance work, done before the pilot rather than after the incident.
The sequence matters. Map what the firm holds. Name the owners. Apply labels and retention. Fix the access. Then switch the pilot on, measured, on the seats that need it.
Skip the sequence and the pilot stalls on the first awkward answer. Run it in order and the pilot starts on an estate that can support it.
Proof you can dial: the voice that answers 0117 456 5486 is our own AI call agent, in production, on our own line. AI as a domain has its own page.
Data is one of the ten domains the seat governs.
A named Head of IT, one or two days a week, owns the data map, the owners, the retention schedule and the access reviews, alongside the other nine domains. The MSP applies settings. The board gets the paper.
Read the offer →Purview and labels are the entry point.
A fixed sprint on the Microsoft 365 tenant: Purview, oversharing, sensitivity labels, the right seats. It is sold as Copilot readiness, and the same work is the working start of data governance, whether or not Copilot follows.
Read the sprint →We sit with the people who actually run the estate. MSP, finance, operations, whoever holds the passwords, and whoever holds the files.
Visible progress in weeks, with a board-readable outcome. For data, often the map, the named owners, the retention position and the first access review.
It's your call. Keep the seat filled at one or two days a week, or keep the gains and run it yourselves. Either way the place is stronger.
The same rhythm as how we work across the whole practice, applied to one domain.
Four things, written down and owned. A named owner for every significant data set. A retention position that is applied on a schedule. Sensitivity labels people actually use. Access that can be explained: who sees what and why.
No. Most of the work runs on the Microsoft 365 tenant you already pay for: Purview, sensitivity labels, access reviews. The hard part is decisions and ownership. Tooling comes second.
Copilot reads whatever your permissions let it read. If the shared drive is overshared, so is Copilot. That is why the Copilot readiness sprint treats Purview and labels as the entry point: the same work that makes Copilot safe is the working start of data governance.
No. Your DPO or legal adviser owns the legal position. We implement the practical side: the map, the owners, retention that is actually applied, labels and access. That gives whoever owns the legal position an estate they can describe accurately.
A named senior leads it. Owners inside the firm hold their own data sets: the practice manager, the head of finance, whoever genuinely owns the set. The MSP applies technical settings under that governance. Nothing here creates a new department.
Yes. Any single domain of the framework can be owned on its own, priced in conversation. The two published routes into data are the seat, from £4,750 a month, and Microsoft Copilot readiness, from £7,500 fixed, where Purview and labels are the entry point.
The first conversation costs nothing and changes what happens next. Bring the thing that hurts, or the thing you want to build.
Talk to an agent starts a voice conversation with our own AI agent, right here on the page. Prefer email? Pick the thing that hurts above and your mail app opens with the subject filled in. Nothing sends from this page.
The practice is UK-wide. The public number is 0117. The registered office is in London.
