Digital Operations, Systems & Processes Audit
Map. Understand. Design. Then build.
A structured engagement that tells you what to change, in what order, and what to leave alone. Before anyone builds anything, we sit with the people who do the work, walk the processes, and put one version of the truth on the table.
The engagement at a glance
Purpose
Understand how the business actually runs today, where it hurts, and what the right-sized response is - before money is spent on building anything.
Approach
Interviews, process walks, workshops and evidence review. We work from what people do and what the systems show, not from what the org chart says.
Who we meet
Sponsors, managers and doers. The people who approve the work, the people who run it, and the people who actually do it, at every site in scope.
Duration
Agreed at the outset, based on your size, number of sites and the processes in focus. The estimator below shows you the likely shape before you talk to anyone.
Outputs
A findings report, current and future state process maps, a systems register, a ranked pain point register, and a 90 day plan you can act on with or without us.
Decision
A defined, controlled scope for whatever comes next - or a clear, evidenced recommendation to change nothing. "Don't build this" is a legitimate finding.
What the audit gives you
Decisions you can defend.
01
One version of the truth
Everyone argues from the same maps, the same registers and the same evidence, instead of from memory and opinion.
02
Root causes, not symptoms
The pain point register separates what hurts from why it hurts, so you fix causes once instead of symptoms repeatedly.
03
The right size of answer
Every finding is tested against the intervention ladder, from fixing the process to building new systems. You get the smallest change that solves the problem.
04
Confidence before commitment
You decide on the next step with a fixed, evidenced picture in front of you, not a vendor's pitch.
05
Nothing lost in handover
The maps, registers and plan are written to be usable by anyone - your team, another supplier, or us. The knowledge is yours.
How it runs
Four phases, no surprises.
Phase 01
Mobilise
We agree the engagement plan with your sponsor, name a coordinator on your side, and book the interviews and process walks so the audit lands with minimum disruption.
Engagement plan · named sponsor and coordinator
Phase 02
Discover
Interviews with the people in the work, process walks at each site in scope, and review of the documents and systems you actually use. Everything is captured as evidence.
Evidence base · interview and walk notes
Phase 03
Analyse
We draw the current state maps, build the systems register and the ranked pain point register, then validate all of it with your team in a workshop. Nothing goes in the report your people haven't seen.
Current state maps · systems register · ranked pain points · validation workshop
Phase 04
Design
Each pain point is taken up the intervention ladder to the smallest change that solves it. You get future state options, a findings report and a 90 day plan in priority order.
Future state options · findings report · 90 day plan
How we gather evidence
Interviews
Structured one-hour conversations with sponsors, managers and doers about how the work actually happens.
Process walks
We follow real work through the business, end to end, at each site in scope, and watch where it waits.
Workshops
Your team validates the maps and registers before anything is reported. The findings are yours, not ours.
Evidence review
The documents, spreadsheets, systems and reports you actually run on, reviewed for duplication, re-keying and gaps.
The intervention ladder
The smallest change that solves it.
Every finding is tested against the ladder before it reaches the report. Most problems resolve lower down the ladder than people expect, and that's the point: software you don't build costs nothing to maintain.
"Don't build this" is a legitimate finding. If the evidence says change nothing, the report says change nothing.
01
Fix the process
Would this problem disappear if the work were done in a different order, by the right person, at the right time?
02
Use what you have better
Does a system you already pay for do this, switched off, unconfigured or unknown?
03
Connect what you have
Would the problem disappear if two systems you already own simply talked to each other?
04
Extend with AI or automation
Is this repetitive, rule-based work a machine should be doing alongside your existing systems?
05
Build or replace
Only when everything below is exhausted: is a new system genuinely the smallest change that solves the problem?
How we use AI in the audit
AI organises the evidence. People make the findings.
AI structures the interview transcripts, cross-references the evidence and keeps nothing from being lost - it's how a small senior team covers a lot of ground quickly. A consultant reviews everything, and every finding in your report was made by a person who sat in your business, not by a model.
Where it leads
Three honest outcomes.
Outcome A
Fix the process
The evidence says the systems are fine and the process is the problem. You get the redesigned process, the plan, and no software bill.
Outcome B
Connect what you have
The systems are right but they don't talk. We scope the integrations and automations that remove the re-keying, usually the fastest payback of all.
Outcome C
Build or replace
Something genuinely needs to be built or replaced. You go into that decision with maps, a register and a controlled scope, so the build is sized by evidence, not by a sales demo.
Scope your audit
Tell us how you run. We'll size the audit as you type.
Five short steps: your business, your systems, where it hurts, who we should sit with, and your details. The estimate on the right updates live, and nothing is committed by submitting - a senior consultant reviews everything and confirms a fixed quote with you personally.
Your business
This sets the overall shape: how many people, how many places, and what kind of work.
Good to know
How long does the audit take?
It depends on your size, sites and the number of people we interview - the estimator above shows the likely number of consulting days as you type. Elapsed time is usually two to five weeks, because we work around your team's day jobs.
How is it priced?
By consulting day, at €1,500 per day with a five day minimum. The estimator above shows how your size drives the day count, and the quote we confirm in writing before anything starts doesn't move once agreed.
How disruptive is it?
Interviews take about an hour per person and process walks happen alongside normal work. We plan the calendar with your coordinator so nobody's day is derailed.
Do we need to prepare anything?
No. The audit works from how things actually run. If documentation exists we'll read it; if it doesn't, that's a finding, not a problem.
What if the answer is 'change nothing'?
Then that's what the report says, with the evidence behind it. "Don't build this" is a legitimate finding, and hearing it before you spend is exactly what the audit is for.
Is our information confidential?
Yes. We're happy to sign your NDA before anything starts, and everything you enter here goes only to our consulting team.
On site or remote?
Both. Process walks are best in person at each site; many interviews and all workshops can run over video. The split is agreed in the engagement plan.
What happens after the audit?
You own the findings, maps and 90 day plan outright. Act on them with your own team, another supplier, or with us - the audit is designed to stand alone either way.
Rather talk it through first?
Book an hour with our Managing Director, or just call. The audit usually starts with a conversation anyway.