SharePoint & Microsoft 365
Get more from Microsoft 365.
We build SharePoint solutions with the SharePoint Framework, design modern intranets, digitise forms and approvals, and modernise document estates that have grown over the years. That same foundation is what makes AI use cases possible later on.
Services
The extension you have been missing.
Microsoft 365 covers a great deal. It gets interesting where your processes follow their own rules — and where content has to be structured so that people, and later assistants, can reliably find it.
SharePoint Development & SPFx
Custom web parts, extensions, integrations and business components for modern SharePoint environments — built with TypeScript and React on the SharePoint Framework.
- Web parts, application customisers and field customisers
- Business systems connected through REST and Microsoft Graph
- A reusable component library instead of one-off builds
- Clean packaging and a deployment you can retrace
Modern Intranets
Modern employee portals with clear information architecture, polished experiences and integrated business processes — an entry point people actually use.
- Information architecture, navigation and search concept
- Communication sites, hub structure and editorial process
- Audience targeting for sites, roles and departments
- Embedded applications, not just a list of links
Forms & Workflows
Digital forms, approvals, Power Automate processes and custom workflow solutions — from a holiday request to a multi-stage capital approval.
- Forms with validation, saved drafts and status tracking
- Multi-stage approvals with delegation and reminders
- Power Automate for the standard cases, code for the exceptions
- Notifications in Teams and Outlook
Microsoft 365 Migrations
Modernize existing SharePoint, file and document environments and move them into Microsoft 365 — with a target structure built to outlast the migration itself.
- Inventory of content, volumes and permissions
- A target structure built on metadata, not deep folder trees
- A move in agreed waves with defined checkpoints
- Clearing out the legacy instead of carrying it across
The connection
The groundwork for every later AI use case.
A knowledge assistant is only ever as good as the repository it reads from. Where content is tagged, permissions are properly assigned and processes exist as data rather than as email threads, AI can be connected without detours. That is why we treat SharePoint projects as a foundation rather than a closed chapter.
Where your information sits today.
- SharePoint libraries
- Documents and PDFs
- Forms and lists
- Business applications and APIs
Prepared, structured and made searchable.
- Preparation and chunking
- Metadata and permissions
- Semantic and keyword search
- Scheduled refresh
Understands the request and works with context.
- Language model with your context
- Retrieval augmented generation
- Business rules and approvals
- Defined tools and actions
Where the work is actually done.
- Microsoft Teams
- SharePoint intranet
- Service and support inbox
- Web and business applications
This chain is where an assistant turns out to be genuinely useful or merely impressive. Because we build both the AI side and the Microsoft 365 side, the path from document to answer stays in one pair of hands.
Technology
What we build with.
SharePoint & front end
- SharePoint Online
- SharePoint Framework (SPFx)
- TypeScript and React
- Fluent UI
- PnPjs
- Microsoft Graph
Automation
- Power Automate
- Power Apps
- Azure Functions
- Webhooks and Graph change notifications
- REST/OData
- Microsoft Teams as the interface
Structure & governance
- Information architecture and metadata
- Site templates and content types
- Permission concepts
- Microsoft Entra ID
- Migration planning and wave design
- Documentation and handover
A selection of the technologies we use in Microsoft 365 projects. The actual mix depends on your environment and your requirements.
Common questions
What to settle before a Microsoft 365 project.
Will you work in an environment that has grown over the years?
Yes — that is the rule rather than the exception. We start with an inventory of sites, libraries, permissions and existing customisations, then say plainly what should be kept, reworked or retired. You get a solid basis for the decision before any effort goes into building.
What is SPFx, and when do we need it?
The SharePoint Framework is Microsoft’s supported model for extending SharePoint Online with your own interfaces. It makes sense when standard web parts cannot express a requirement: bespoke views on business data, forms with particular logic, or components that bring several systems together in one screen.
How does a migration to Microsoft 365 run?
In four phases: an inventory of the content, a design for the target structure with metadata and permissions, the move in agreed waves, and a final round of checks. We deliberately do not migrate one to one — we first separate out what should be archived, cleaned up or restructured, otherwise the old mess simply moves house with you.
Can existing solutions be extended with AI later?
As a rule yes, and that is the payoff of a clean structure. Where documents are tagged and processes exist as data, an assistant can build on the same content without creating a second copy of your data. We therefore plan Microsoft 365 projects with that extensibility in mind from the outset.
What would make tomorrow’s work easier?
Which task would you like to take off your team’s hands? Tell us how it works today. We will look at the options, the data needed and a sensible first step.