Rolling out Copilot? Run this check first. It reads everything your staff can. →
Automation
Power Automate flows and Power Apps that quietly remove hours of manual work every week, built to be governed and supportable, not a sprawl of personal flows.
Most automation in a tenant is a graveyard of half-finished personal flows that break the moment someone leaves. We build automation as a proper deliverable: mapped to the real process, documented, monitored, and owned by the business rather than one person's account.
Most of what we build sits behind a SharePoint intranet, the flows that run approvals, routing and notifications, but we also build standalone automations for email, finance and operations processes that have nothing to do with SharePoint.
Map the process
We document the real process, the people, the exceptions and the handoffs, before automating anything.
Build
Flows and apps built with proper connections, error handling and naming, on a service account, not a personal one.
Handover
A runbook so the business can see what runs, why, and what to do when something changes.
The outcome
A real business process, mapped and automated: a CRM event provisions a SharePoint site, builds the folder structure and reference number, and logs the outcome. Error handling and an audit trail are built in, so the business can see exactly what ran, and what needs a look.
CRM: opportunity won
polled trigger, native connector
Milestone matches, and not a duplicate
early condition gate
Provision client site
Azure Automation runbook (PnP)
Create project folder + reference no.
unique 5-digit ID
Update project register
SharePoint list
Riverbank Ltd
Active project
Meridian Group
Opportunity
Harbourview
Active project
Unmatched folder
Naming mismatch
47
provisioned
3
skipped (idempotent)
1
manual review
Illustrative of a real client build. Business-owned service account, documented, monitored.
Read-only. The whole tenant. One clear report.