Most SharePoint estates were never designed as a whole. Sites were added project by project, each library got its own columns, and the term store, if anyone set one up, holds three spellings of every department. Search returns too much, filters only work on one library, and documents are found by people who remember where they were saved.
We fix the information architecture of the estate you have. We agree how content should be described, put content types, taxonomy and structure in place to match, then use AutoTag to apply that metadata to the documents already there.
What We Work On
Content types
One set of content types used across the tenant, so a contract has the same columns on every site.
Taxonomy
Term sets in the term store for what people search by, such as client, product, region and document type, each with an owner.
Site structure
Hub sites, navigation and a clear rule for when something needs a new site, a new library or neither.
Search
Search refiners and filtered views built on your metadata, so people narrow results instead of scrolling through them.
Deep folders
Folder paths turned into columns, so the library can be flattened without losing what the folders said.
Duplicates and dead sites
Duplicate libraries, abandoned sites and stray copies merged, archived or removed with their owners’ agreement.
Tagging What’s Already There
A new taxonomy is only useful once content carries it, and nobody tags years of existing documents by hand.
AutoTag is our automated metadata tagging platform for Microsoft 365. Its Metadata Bots run inside your tenant and write terms from your term store into the right columns, across sites and libraries. A Bot can look values up from a reference list, use AI to read the document and match what it finds against your term set, or do both. Scanned documents are read with OCR.
Bots work back through the existing estate, tag new documents within seconds of arrival and check again when a document changes. The metadata stays complete without anyone having to remember it.
How It Works
Review
sites · columns · term store · search
We look at what you have and talk to the people who use it, to learn how they look for things and where they give up.
Design
taxonomy · content types · structure
We design the taxonomy, content types and site structure, and you approve them before anything changes.
Restructure
publish · consolidate · flatten
We publish the content types and terms, and move or merge content where the structure needs it, starting with the areas that matter most.
Tag
AutoTag · backfill · new content
We set up AutoTag to tag the existing content and everything that arrives after it.
Ready for Copilot
Microsoft 365 Copilot can use anything the person asking is allowed to open, so two questions matter before rollout: is it finding the right document, and should that person see it at all? Consistent metadata helps with the first. For the second, our Copilot readiness assessment measures how widely your content is shared and our oversharing clean-up fixes it. AutoTag can apply Microsoft Purview sensitivity and retention labels in the same pass as the metadata.
Why JFDI
Our SharePoint work goes back to the platform’s origins, and we built AutoTag, which has been in production with customers for more than a decade. For Countryside Properties, each of more than 250 developments had its own legal documents repository. We brought the existing contract and legal documents, metadata intact, into one structure where they are easy to save, categorise and find. Read the case study.
Still on file shares? See file share to SharePoint migration.
SharePoint Metadata FAQs
Can your people find what’s in SharePoint?
Tell us how your estate is organised today. We’ll review it and quote the work from what we find.

