Where SharePoint work usually starts
Almost every engagement begins from one of a few recognizable situations, and knowing which one you are in tells you most of what the project will be.
A firm is exhausted by its shared drive — or by Box, or Dropbox — and wants somewhere documents can actually be organized. A team is paying for Microsoft 365 and using a fraction of it. A marketing or communications group needs a real channel for organizational news. Or an organization already on SharePoint wants to push past what the platform does out of the box.
They overlap more often than not. The migration is usually the moment the other three become possible.
Migration is a reorganization, not a move
The reason people leave shared drives, Box, and Dropbox is rarely the tool itself. It is that fifteen years of folders have no structure anyone can explain, permissions nobody can account for, and six versions of the same document in five locations.
Moving that as-is into SharePoint produces the same mess with a Microsoft logo on it. So the migration is where the restructuring happens: content gets owners, sensitive material gets a real permission model, metadata gets applied, and duplicates get resolved — while every file is already in hand and being touched anyway. It is the cheapest moment you will ever have to fix it.
The licensing you already pay for
A surprising share of the value here is not new software. It is the software already sitting in your subscription that nobody has been shown.
Planner for the work currently tracked in a spreadsheet someone emails around. Forms for the requests arriving as unstructured email. Shared mailboxes for the inbox three people are all half-watching. Teams structured to match how the organization is actually shaped, rather than a few hundred channels created ad hoc and never cleaned up.
We work through what your licensing entitles you to, what your teams do all day, and where those two things fail to meet — then roll out the pieces that close a real gap, with enough enablement that people keep using them after we leave.
SharePoint as the communication layer
For marketing and internal comms teams, SharePoint is a publishing platform. Organizational news that reaches everyone, departmental spaces that let each group communicate on its own terms, and information hubs people use to navigate an organization that has grown past the point where everyone knows where anything is.
The design work is the same as any communications channel: who publishes, who reads, what belongs on the front page, and what happens to it in six months. The technical build is the easy half. An intranet that fails almost never fails because SharePoint could not do it.
When the out-of-box experience is not enough
SharePoint covers a great deal on its own, and then occasionally it does not.
SPFx lets us extend the interface itself with custom web parts and experiences built for a specific need. Where we have built a Power App for a client, we can embed it directly into the SharePoint sites their people already spend the day in, so there is no separate destination to remember. And Copilot adoption lands here too — the AI layer over content that, by this point, is finally structured well enough to be worth asking questions of.
The sequence matters. Customization on top of a good foundation compounds. Customization used to paper over a bad one just makes the bad one harder to fix.
The structure Copilot reads from
This is the part that has changed most in the last two years. Copilot answers from what it can access, inheriting SharePoint’s permissions and content quality exactly as they are.
Good metadata and a correct permission model produce grounded answers with the right sources. A careless migration produces confident answers drawn from a document superseded three years ago, or a result nobody should have been able to see because the folder it landed in was open to the whole tenant. Getting this right during the migration costs almost nothing extra. Getting it wrong is discovered later, usually by the wrong person.
Ten users, or tens of thousands
The same design problem scales in both directions, which is why the range of this work is so wide. We have run a Teams and internal communications workshop for a thirty-person business and watched it change how the whole company talked to itself. We have also handled SharePoint adoption across organizations with tens of thousands of users, where governance, rollout sequencing, and content ownership carry far more weight than any single site design.
What scales is the rigor. What stays constant is the question underneath all of it: can people find what they need, and do they trust it when they find it.