CTO at GoSim · Engineering Leader · Systems Builder

I've built software for factories, bookmakers, investment platforms, theatres, lawyers, and electric motors. This was apparently a plan.

Side quests include quantum random numbers, space debris, motorcycle dashboards, and giving language models root access. Scope control remains a work in progress.

I'm the CTO and current Lead Engineer at GoSim, a deep-tech startup developing a new approach to computational engineering design. We combine simulation, optimisation, and a less restrictive representation of geometry to explore manufacturable designs beyond predefined parametric templates, initially for electric motors.

I'm building the engineering organisation from scratch: setting technical strategy, shaping the architecture, writing plenty of the code, and trying to prove that delivering quickly is compatible with paying people properly, respecting their lives, and making work somewhere they actually enjoy being.

My natural habitat is the awkward space between systems design, software architecture, hands-on engineering, and technical leadership. I'm a polyglot by necessity and a C# developer by default. I like complex systems, clear boundaries, useful abstractions, and organisations that do not require heroics to function.

I'm particularly interested in AI where it earns its keep: useful systems, honest evaluation, and proportionate risk—without the benchmark theatre, apocalyptic hyperbole, or appeasing Roko's basilisk.

Before GoSim, I built FinLegal's AI team and product vertical from scratch, including a custom multi-agent framework integrated into its claims platform. That work became a major part of the company's wider transformation and growth. I joined FinLegal's CTO to discuss the system and its design in Why Law Firms Need Agents & How We Built Them for AWS.

I'm awaiting the viva for an MPhil at Aston University on orbital environment monitoring and long-term simulation. The work examines how to model the evolution of space-debris populations and collision cascades over decades, with the aim of comparing mitigation strategies before we spend rather a lot of money launching them.

The project began as a PhD. Work won the scheduling argument; the research survived.

Most of these exist because I needed a tool, discovered it did not exist, and made that everyone else's problem too. Help maintaining them is always welcome.

I scuba dive, ride motorbikes, play ice hockey, and climb rocks. Best make sure I don't live to regret my lack of pension contributions.