Services
SharePoint services, in the order they usually happen
TechRam runs seven kinds of engagement on SharePoint and Microsoft 365: an environment baseline, governance and permissions cleanup, storage and migration, an intranet and knowledge layer, AI workflows and agents, custom operational apps, and an ongoing run and improve retainer. Each one is scoped to your tenant as it stands today.
-
Environment Baseline
A fixed-scope read of your tenant: permissions, external sharing, sprawl, storage and what it's costing you. Ends with a prioritised plan.
What this does for your AI: Copilot can only be trusted where permissions are known. This is where that starts.
See what's involved → in Environment BaselineTypical timeframe
2–3 weeks
-
Governance & Cleanup
Permissions, external sharing, site sprawl and lifecycle brought under a policy your people can actually follow.
What this does for your AI: An agent inherits whatever the permission model allows. Fixing the model is what stops it answering from somewhere it shouldn't.
See what's involved → in Governance & CleanupTypical timeframe
4–8 weeks
-
Intranet & Knowledge Layer
One place your people look first, and a knowledge base your AI can be grounded in rather than guess from.
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.
See what's involved → in Intranet & Knowledge LayerTypical timeframe
8–14 weeks
-
Storage & Archive Lifecycle
Migration, archive tiers and retention, so content you must keep costs less and content you must not keep is gone. Includes SharePoint migration.
What this does for your AI: Content an assistant should never surface has to be archived rather than left in place. Retention is what makes that a rule instead of a hope.
See what's involved → in Storage & Archive LifecycleTypical timeframe
4–10 weeks
-
AI Workflows & Agents
Copilot and agents put to work on the operational system underneath, scoped to named tasks, with the permissions and grounding checked first.
What this does for your AI: This is the step everything else was for. The agent answers from a system with owners and states, not from a folder.
See what's involved → in AI Workflows & AgentsTypical timeframe
4–10 weeks
-
Custom Operational Apps
The registers, trackers and apps your operation is missing — incidents, assets, renewals, approvals — built as real systems with owners, states and reminders, on the Microsoft licences you already pay for.
What this does for your AI: An app writes the record as the work happens, which is the only way an assistant can answer about work in progress.
See what's involved → in Custom Operational AppsTypical timeframe
2–16 weeks
-
Run & Improve
We keep what we built working, and we keep improving it. Monthly reviews, fixed tiers, outcomes named up front.
What this does for your AI: A system that drifts stops being a reliable source. Keeping it current is what keeps the AI on top of it honest.
See what's involved → in Run & ImproveTypical timeframe
Monthly, no lock-in
Beyond SharePoint
Four lines we sell from inside existing accounts. Real revenue, real search terms, never the lead.
-
Azure Cost & Cloud Management
Cost drift caught monthly, not at renewal. Reviews, right-sizing and a QBR you can take to the board. See what's involved → -
Technology & Digital Strategy
Where you are, what to fix first, and the business case to fund it. Yours to keep. See what's involved → -
Data & Reporting
Live dashboards and scheduled reports built on the data you already hold, so decisions stop waiting for someone to update a spreadsheet. See what's involved → -
Integration
Your systems connected so data moves once and flows everywhere it needs to go. One page, covering both application and data integration. See what's involved →
There is a second set of work that runs on the same Microsoft estate and is scoped on its own: Azure cost, Power BI reporting, integration and strategy. None of it needs the SharePoint build to happen first.
Common questions
01. Which service should we start with?
Almost always the Environment Baseline. It is read-only, it takes the guesswork out of scoping everything else, and it tells you what to fix first rather than what we'd like to sell.
02. Can you do one piece of work rather than a programme?
Yes. Each engagement stands on its own. Most clients start with one and decide about the next once they can see what changed.
03. Do you work alongside our existing IT provider?
Regularly. We do the SharePoint and Microsoft 365 build; your managed service provider keeps running the things they already run. We'll tell you where the line should sit.
04. What happens after a build is finished?
Either you run it yourselves with the documentation we hand over, or we keep it current on a Run & Improve retainer. Both are fine. Neither is a lock-in.
Not sure which one? Nobody is, before the Baseline.
It is read-only, it takes two to three weeks, and it ends in a prioritised plan you own. Everything scoped after it is scoped against what is actually in your tenant.
Start with the Environment Baseline →