About
Nick Marfleet – Nick has over 25 years of experience helping legal, professional services, and enterprise clients align technology with business strategy. He has led multi-million-pound projects across digital communications, workflow automation, and document management, consistently delivering high-value outcomes for clients.
Nick is passionate about practical innovation and has contributed thought leadership to publications including the Financial Times. He holds certifications in ECM, AI, and project management.
BSI-certified ISO/IEC 42001:2023 Lead Implementer · 25 years in UK outsourcing & tech · Microsoft 365 & Azure · Complex technical project management
How I work
Clear scope. Sound design. Evidence at every step.
Every engagement follows the same disciplined path, whether it’s an ISO 42001 programme or an automation built on Microsoft 365 and Azure. You’ll always know what’s being delivered, why it’s designed the way it is, and how it works.
1. Scope
Before any build starts, I work with you to pin down the problem, the required outcome, and what’s out of bounds. That means understanding your processes, your data, your constraints and the people affected. The result is a written scope with defined deliverables, assumptions and acceptance criteria, so the fixed fee means something and there are no surprises for either of us halfway through.
2. Architect
I design the solution before it’s built. That covers how data moves, whether it needs cleansing, where it’s stored, who can access it, and how it fits with the systems you already run. Wherever possible I build inside your existing Microsoft 365 and Azure environment rather than adding new platforms to manage. You’ll see and sign off the design before development begins.
3. Build and iterate
Work is delivered in short, visible stages rather than one big reveal. You review real progress early and often, which means feedback shapes the solution while changes are still cheap. Ambiguities get raised and resolved as they appear, not worked through at the end.
4. Test
Nothing goes live on the assumption that it works. Each element is tested against the acceptance criteria agreed at scoping, using realistic data and edge cases. You get a clear record of what was tested and the outcome, and final sign-off sits with you.
5. Document
Every engagement ends with documentation your team need: how the solution works, how to run and maintain it, what to do when something goes wrong, and the decisions behind the design. The aim is that you’re never dependent on me to understand your own systems and can comfortably manage them without me.
6. Security, governance and compliance
These are built in from the first conversation, as a matter of principle. This future proofs the solution during any future compliance requirements.
Security. Access is granted on a least-privilege basis and removed when the work ends. Client data stays within your own environment wherever possible, and is never used with public AI tools without your explicit agreement.
Governance. As a BSI-certified ISO/IEC 42001 Lead Implementer, I apply the same structured thinking to every project that I bring to AI management systems: defined ownership, documented risk assessment, and clear accountability for how automated and AI-driven decisions are made.
Compliance. Solutions are designed with UK GDPR and your regulatory obligations in mind, and every stage leaves an auditable trail. That way, if a regulator, insurer, auditor or client asks how something works and why, you have the answer.
