Business Analyst + Developer
I bridge structured delivery thinking with hands-on technical implementation, which is a big part of why my AI work is grounded in real execution.
About
I’ve spent much of my career working where delivery had to be structured, understandable, and credible, not just technically interesting.
That background now shapes the way I build AI copilots, workflow orchestration, and extraction pipelines: with real users, real constraints, and real operational use in mind.
I bridge structured delivery thinking with hands-on technical implementation, which is a big part of why my AI work is grounded in real execution.
My background comes from places where clarity, testing, reliability, and stakeholder confidence actually mattered.
I focus on practical copilots, orchestration workflows, and extraction pipelines designed to be useful beyond a demo.
The strongest feedback I get is usually some mix of clarity, reliability, calm delivery, and being an enjoyable person to have on the team.
How I think
It’s the way those environments taught me to think: clearly, practically, and with a strong bias toward systems that people can understand, trust, and actually use.
AI is only useful when it fits into a real workflow.
Good systems need clear requirements, not just clever prompts.
Most delivery problems are really communication problems in disguise.
If something matters in production, it needs structure, testing, and trust.
Recognisable environments
Notable organisations
The University of Law High-stakes enterprise delivery, student systems, process improvement, testing, requirements, implementation, and operational change.
The thread running through it
My route into this work came through years of solving operational problems, building systems, defining requirements, supporting teams, and helping projects move from ambiguity to something usable.
Earlier career
I started on the technical side: building systems, designing databases, solving messy operational problems, and learning what teams actually need from software in the real world.
Delivery years
I spent years working across planning, requirements, process design, UAT, implementation, and stakeholder communication, especially in environments where failure would have been expensive, disruptive, or very visible.
Today
That combination is now what I bring to AI: not just ideas, but systems shaped by workflow reality, operational constraints, and the standards real organisations expect.
Working style
I’m good at taking messy processes, technical constraints, and competing stakeholder views, then turning them into something understandable and actionable.
I can think with technical people, talk with business stakeholders, and help both sides stay aligned without unnecessary theatre.
I care about doing the work well, being easy to collaborate with, and helping a team look good in front of users, leaders, and clients.
What people noticed
Skills matter. So does fit. The feedback that means the most to me is the kind that reflects both.
“You need look no further than Ian.”
Senior project stakeholder, The University of Law
“Exceptional expertise, diligence, and reliability.”
Senior Project Manager, The University of Law
“He was also a lot of fun.”
Colleague, Pfizer
Work together
My demos and writing can show the technical side. This page is the simpler truth: I care about building useful things well, and I’m good at helping teams turn complexity into something workable.