
The process that lives in one person's head
When that person leaves, the process doesn't slow down. It disappears. Documentation is not a compliance exercise — it is continuity infrastructure.
Read post →

What we build
Everything we deliver lives inside Microsoft 365. No new vendors. No migration risk. No additional licensing. We work within what your organisation already pays for and build systems that actually get used.
Service lines
M365 native
Additional licensing
Average deployment
01 — SERVICES

Automate
Power Automate workflows that handle routing, approvals, reminders, and reporting without anyone having to chase, copy, or consolidate by hand. Built for recurring reporting cycles, approval chains, onboarding sequences, escalation workflows, and any process where someone is currently doing the same manual step on a schedule.
Stream 1 — zero-touch audit pipeline
02 — AUTOMATE

Architect
SharePoint environments designed as operational systems — not just file storage. Permission-controlled, region-visible, and built to scale with your team. The foundation everything else reads from.
Stream 2 — SharePoint as operational hub
03 — ARCHITECT

Document
Every system we build is documented properly and handed over. Written for the people who will actually use it — not the person who built it. When the project ends, you own everything. No dependency built in.
Every workflow documented before automation begins
Process logic validated with the people who use it
System built and tested in staging before go-live
Full handover documentation on delivery
Client owns every component — no ongoing dependency
Our delivery standard — every engagement
04 — DOCUMENT

Consult
Operations audits for teams that know something is broken but are not sure where to start. We map what is actually happening — not what is supposed to be happening. Those two things are rarely the same. The automation comes second. The process design comes first.
Operational health — before and after MxN
05 — CONSULT

Optimise
Before any automation work begins, we map the current process in full. Every step, every decision point, every exception. Inefficiencies get removed at the process level first — then the clean process gets automated. The result is a system that works correctly at speed, not one that fails faster.
Before
After
The same process. A different outcome.
06 — OPTIMISE

How we work
Both start with a conversation. Both end with a system you own.
FIXED SCOPE
One project. Clean delivery.
Best for
Specific automation builds, SharePoint environments, reporting pipelines, one-time documentation projects
RETAINER
Ongoing support. No full-time hire.
Best for
Teams scaling faster than their processes, organisations needing a specialist on call, post-project ongoing support
Not sure which fits? Book a call and we will figure it out together.
07 — HOW WE WORK
Work with us
Book a call. We’ll figure out if we’re the right fit.
Book a call
From the journal

When that person leaves, the process doesn't slow down. It disappears. Documentation is not a compliance exercise — it is continuity infrastructure.
Read post →

Most teams use SharePoint the way they used shared drives. That is like using a database to store Post-it notes.
Read post →

Before any automation work begins, map what is actually happening — not what is supposed to be happening. Those two things are rarely the same.
Read post →
Made Ex Nihilo · madexnihilo.com