Service 03
SharePoint Intranet & Knowledge Base, Built for Operations and AI
TechRam builds the SharePoint intranet and knowledge layer your operation actually uses — policies, procedures, forms and the answers people currently ask each other for. It's structured so there's one authoritative version of each document, which is what lets both a new starter and Copilot find the right one.
- 8–14 weeks
Who it's for
Organisations where the answer exists but nobody can find it, and where the same question is asked every week.
What we do
- One place your people look first, structured around the work
- A knowledge base with owners and review dates on every page
- Search that returns the current version, not eleven of them
- A grounded source your Copilot can answer from
How it works
Step 1
Workshop what people actually look for
Step 2
Structure the information architecture around that
Step 3
Build, migrate the current content and retire the rest
Step 4
Hand over with owners and a review cycle
The problem it answers
The answer exists. Somebody wrote it down. It’s in a document in a library that three people know about, and there are four versions of it with no way to tell which one is current.
So the same question gets asked in Teams every week, and the person who knows answers it again. That’s a cost nobody measures, and it’s the same cost that makes an AI assistant useless: a model grounded in four versions of a policy will confidently quote the wrong one.
What changes
One place people look first, structured around the work rather than around the org chart. One authoritative version of each policy, with an owner and a review date. A knowledge base an assistant can be grounded in, because there’s now a single answer for it to find.
Related reading
How do you build an org chart that stays up to date?
Read it → — An org chart that stays currentHow do you turn SharePoint into the system your operation runs on?
Read it → — How do you turn SharePoint into the system your operation runs on?
Start here for free
Org Chart Web Part
Deploys in under 30 min
Deploy it in your own tenant → — Org Chart Web Part
What this does for your AI
A knowledge base with one authoritative version of each policy is the difference between Copilot citing your procedure and citing a draft.
Common questions
01. How is building an intranet different from what our MSP already does?
Nobody's MSP owns the information architecture. This is a content and structure job with a build behind it, and the hard part is deciding what the single current version of each thing is.
02. We already have an intranet nobody uses. Is this a rebuild?
Sometimes, but start by assuming not. An intranet goes unused because the answers on it are out of date, and that's an ownership problem a redesign doesn't fix.
03. Can we start the intranet with one department rather than the whole organisation?
Usually yes, and it's often the better way in. One department that works is a more persuasive business case internally than a plan covering all of them, and it gives us a real cost to scope the rest against.
04. What does a SharePoint intranet cost?
Fixed scope, quoted in writing before work starts, and the number doesn't move because the work turned out harder than we expected. We don't publish a range, because the scope is what sets it and a range without a scope is a guess you would have to unlearn.
05. Do we need to buy anything new for an intranet?
Almost never. We start with what is already in your Microsoft 365 licensing, and we don't resell licences or earn a margin on them. Where something genuinely isn't covered we'll say so before you commit, not after.
06. What happens when the intranet is live?
You own it: the systems, the documentation, and the ability to maintain them without us. Run & Improve exists if you would rather we kept it current, and it's monthly with no lock-in.