Every consultancy in this market describes itself as leading. Almost none of them will tell you who you would actually be working with. Here are ours – what each of them does, how long they have been doing it, and what they have published.
The person who scopes your project is the person who runs it.
What we do
SharePoint consulting services covering strategy, information architecture, build, migration and adoption on SharePoint and Microsoft 365. A specialist consultancy, not a general IT provider.
Who you get
Named consultants with between 17 and 28 years each in the industry. The same people from the first conversation through to launch, working as part of your team rather than around it.
How it works
Either a fixed fee project with a defined scope, or a twelve month retainer of professional service hours, bought up front and drawn down as and when you need them.
Track record
Since 2005. Over 500 projects delivered, for clients across the UK, Europe, the Middle East, North America and Asia-Pacific. Rated 4.9 on Google.
How we deliver
UK-based, working remotely with clients internationally. In person for UK clients where it helps.
Jeremy takes the first conversation. That is deliberate – the person working out whether we are the right fit should be someone who has scoped hundreds of these projects, not someone whose job is to book a meeting.
John runs the user experience practice and has worked on SharePoint since the year after the company was founded. If your problem is that people cannot find anything, this is whose work that is.
Adam leads technical consultancy and client training. He came through full-stack development rather than consultancy, which means design decisions get pressure-tested against what will actually work in delivery.
Joe is where the difficult technical problems go. When a requirement sits outside what SharePoint does natively, he is the one who works out whether it can be built properly or whether the requirement is wrong.
Dan spent six years as knowledge management manager at Johnson & Johnson before founding Content Formula in 2005. He still works on client problems himself and is reachable throughout a project. He is also the founder of Xoralia, our policy management product, which came directly out of compliance problems clients kept describing.
The five above are the consultants you would work with directly. More about Content Formula and how we work.
Continuity
Senior people win the work. The project then moves to a delivery team who were not in the room when the decisions were made, and by month three you are explaining your own organisation to someone new. Two things stop that happening here, and both are checkable rather than asserted.
Dan founded the company in 2005. John joined in 2006 and still runs the UX practice. Joe has been here twelve years and is now technical director. The institutional memory is not in a document, it is in the people who are still here.
That matters most three years after launch, when you need someone who remembers why a decision was made rather than someone reading the handover notes.
We do not tie clients into long contracts and never have. Our eight longest-standing support relationships have run between five and seven years, across aviation, water, transport, certification, real estate, law and architecture, in the UK, Europe and North America. The longest began in 2019.
Length of relationship is the only endorsement worth quoting when there was nothing stopping anyone leaving at the end of a year.
In practice that means the consultant who scopes your project runs it. When the architecture needs a technical judgement, Joe makes it. When the structure needs testing with your employees, John runs it. Nobody is introduced at kick-off and replaced afterwards.
On a retainer it works the other way round, deliberately. You are not assigned a consultant – you draw on whoever the question needs, which is the point of buying hours rather than a person. In practice that still gives you consistency by discipline: if the question is user experience, it will be John, every time.
Either way we carry the consequences. The people who recommend an approach are the people who have to make it work, and who will still be here when it needs revisiting. That produces more cautious recommendations than a pitch team is incentivised to give.
The quickest way to test any of this is to talk to one of them rather than read about it.
How to compare us
We are a certified Microsoft Cloud Solution Provider and have been a Microsoft partner throughout. We work only within the Microsoft 365 ecosystem - we will not advise you across platforms we do not deliver.
Over 500 projects since 2005 across financial services, healthcare, pharmaceuticals, transport, water, law, education and not for profit. The case studies name the clients. Rated 4.9 on Google across 22 reviews.
A platform nobody uses is a failed project however well it was built. Adam trains administrators, site owners and content editors; John trains content teams on writing pages people will read. Both are part of delivery, not an upsell afterwards.
Engagements
The difference is whether you have a defined piece of work or an ongoing need for senior input.
You know roughly what you need delivered - a discovery, an information architecture phase, a build, a migration.
We scope before we quote. A number produced before anyone understands the problem is a guess, and guesses get corrected later at your expense.
You have capability in house but want senior specialist input available without raising a purchase order every time you need an hour of it.
We will tell you what we think you will realistically use. A client who never draws down their hours does not renew, so there is nothing in it for us in selling you more than you need.
We are a UK consultancy working remotely with clients across Europe, the Middle East, North America and Asia-Pacific – the same way we advise our clients to work, so it would be strange to do otherwise. Workshops, research sessions and training all run well remotely. For UK clients we are happy to run them in person where being in the room genuinely adds something.
How we work with you
Most of the organisations we work with already have an IT function, a managed service provider, or both. We are not there to replace either. We bring the SharePoint and Microsoft 365 depth that is hard to justify as a full-time hire, and we fit around the people who will still be running the platform long after we have finished.
We work inside your governance and your change process, to your standards rather than ours. We do not ask to own the tenant, and we do not go around your administrators to get something done faster.
We work with incumbent managed service providers, internal development teams and other Microsoft partners regularly. Where responsibility for something sits with them, we say so rather than quietly absorbing it.
Training administrators, site owners and content editors is part of delivery, not an upsell afterwards. The measure of a good engagement is that your team can run the thing without calling us.
where we stop
Working alongside your IT team only means anything if we are clear about what is not ours. Not everything in Microsoft 365 is. If your problem sits on the right, we will say so early and point you somewhere better.
Where the governance line falls
We do governance as a content and structure problem – who owns which sites, how new ones get created without eroding the architecture, how content gets reviewed before it goes stale. We do not do governance as a security or regulatory problem. Other Microsoft partners specialise in that and do it better than we would.
IT Manager
The Specialist Works
The Institute of Cancer Research
IT Manager
Valeo Foods
Each of these was written by the consultant who ran the project, not by a marketing team afterwards.
Discovery, information architecture, development, migration, adoption and support each have their own page with deliverables and timescales. They all sit one level up.
A short call with one of the consultants above. We will work out what you actually need, whether a fixed fee project or a retainer fits better, and whether you need us at all. If your internal team can handle it, we will say so.
Common questions
A SharePoint consultant advises on how an organisation should structure, build and use SharePoint rather than simply configuring it. In practice that covers establishing what employees need, designing the information architecture and navigation, deciding what should be built natively versus customised, planning migrations, and putting governance in place so the environment does not degrade after launch. The distinction from a developer is that a consultant is accountable for whether the approach is right, not only whether the build works.
Nothing is replacing it. SharePoint remains the content and document layer of Microsoft 365, and Microsoft continues to invest in it – Copilot, SharePoint Premium and the agent capabilities all depend on content held in SharePoint. What has changed is that SharePoint is now less often the interface people use directly: content lives in SharePoint while employees reach it through Teams, Viva Connections, search or Copilot. That shifts where the effort goes, from page design toward structure and metadata, because those are what determine whether the other surfaces work.
SharePoint Online is not going end of life. The confusion usually comes from on-premises versions, which do have published support end dates, and from individual features being retired – Delve and SharePoint Syntex branding are recent examples. If you are on SharePoint Server rather than SharePoint Online, the support dates are worth checking against your upgrade plans. If you are on SharePoint Online, the platform is not the risk; the risk is an environment nobody has structured or governed.
We scope before we quote. That means a conversation and usually a short piece of structured work to establish what the problem actually is, after which the engagement is either a fixed fee project with a defined deliverable or a twelve month retainer, where you buy professional service hours up front and draw down against them as you need them. Retainer hours are bought in increments of 25 upwards. We do not publish rates because the shape of the work varies too much for a list price to be useful, but you will have a fixed number before you commit to anything.
Yes, and it is the main reason to work with a specialist firm of our size. The consultant who scopes your project runs it, and the technical director and UX director who make the architectural calls are the same people through delivery, launch and any ongoing support agreement. There is no separate delivery team to hand over to.
Yes, and it is how most of our engagements run. Most organisations we work with already have an IT function, a managed service provider, or both, and we are brought in for SharePoint and Microsoft 365 depth rather than to replace either. In practice that means working inside your governance and change process, to your standards, and being explicit about where responsibility sits with your own team or your incumbent provider rather than quietly absorbing it. Training your administrators, site owners and content editors is part of delivery, so the intention is always that your team can run the platform without us.
