Founder, ScotiTech • AI Systems Architect
I design products and infrastructure that let organisations adopt AI without losing control of data, auditability, or accountability.
CURRENT FOCUS
Most organisations now face the same problem: AI adoption is moving faster than internal governance capability. I build systems that embed oversight, traceability, and risk awareness directly into workflows rather than treating compliance as an afterthought.
My work is especially relevant in healthcare, finance, government, and other regulated settings where data sovereignty, audit readiness, and operational trust are non-negotiable.
Selected products
Access-Controlled Mobile Distribution
AppDeploy is a ScotiTech product led and developed by me. It keeps organisations operational when traditional app distribution fails by providing a controlled internal distribution layer where organisations retain direct authority over access, availability, and lifecycle of their applications.
Private AI Workspace
AXOS is a ScotiTech product led and developed by me, enabling local AI execution with governance, auditability, and operational control built directly into regulated workflows.
Technology for Assisted Independence
ElderConnect+ applies community-focused system design to independent living, giving families and local support networks a more reliable way to coordinate everyday help for older adults.
Philosophy
I design platforms for environments where software cannot fail silently — regulated teams, long-lived deployments, and systems operated by non-developers.
In these contexts, usability matters, but predictability matters more. The goal is infrastructure teams can depend on without constant supervision.
My work focuses on making advanced technology usable where reliability is mandatory rather than optional.
Technology should quietly prevent problems. The most valuable systems are not the ones people actively use, but the ones they stop worrying about.
If the surrounding ecosystem changes — vendor, policy, device, or location — essential activity should continue uninterrupted.
I build software that reduces dependence rather than increasing usage.
Design for constraints
Compliance rules, deployment boundaries, and ownership requirements are not limitations — they define the system architecture.
Systems reduce effort
A platform should remove operational decisions, not introduce new ones. If teams must constantly manage the software, the architecture is incomplete.
Production is the proof
Software is validated only after long-term use in real environments. Demonstrations measure possibility; operations measure correctness.