Most businesses have always known things could work better. AI has made that feel more urgent than ever — while doing very little to make it obvious where to actually start.

The reason is rarely a lack of ambition. It's usually the opposite — problems that feel too big to scope, solutions that seem to require turning the whole business upside down, and no one inside with the expertise or confidence to know where to actually begin. The technology being available doesn't help if you can't see a credible path to using it.

And if you've typically relied on agencies, consultancies, or software vendors for your technology, the frustration compounds. You're dependent on people who understand the tools but don't always understand your business — and you end up with solutions that solve the problem they heard, not the problem you actually have.

What I do

I work with businesses as a Fractional CTO and Principal Architect — embedded, hands-on, and focused on understanding how your organisation actually operates before recommending anything.

That means talking to people. Not just senior leaders, but the people doing the work day to day — the ones who know exactly where the friction lives, even if they've never had the chance to articulate it to anyone who could act on it. I'm told I have a way of putting people at ease in those conversations: I don't speak in jargon, I don't make people feel out of their depth, and I don't come in with a solution looking for a problem.

What I'm looking for, in those early conversations, is specificity. Where exactly does work slow down? What gets done twice because systems don't talk to each other? What decisions take longer than they should, and why? And — perhaps most valuably — which parts of the operation are still running on manual processes: things done by hand, in spreadsheets, over email, or through someone's institutional memory, that are time-consuming, error-prone, and quietly fragile. These are often the places where the most straightforward automation wins are hiding, and where the people doing the work feel the pain most acutely.

Once I have a clear picture, I help you prioritise. Not everything is worth fixing, and not everything that feels urgent is actually costing you much. My focus is on finding the friction points that seem small but cascade — the ones that quietly multiply downstream into wasted time, frustrated staff, and problems that are expensive to unpick later.

And the solution isn't always a new piece of software. Sometimes the most valuable thing I can do is work directly with your team — helping them understand how to use the tools already available to them more effectively, building genuine confidence rather than dependence on external help.

On AI — a word of honesty

There is a lot of noise around AI right now, and a lot of pressure to be seen to be doing something with it. I understand that pressure. But I don't believe in using AI for its own sake.

The reality is that many of the best automation opportunities in most businesses are still best served by straightforward, well-built software — code that does exactly what it's told, reliably, every time. Where AI earns its place is in the things that genuinely weren't tractable before: understanding unstructured documents, handling variation in language and intent, extracting meaning from messy inputs. That's where the step-change is real.

That includes knowing when the right answer is neither bespoke software nor a complex AI implementation — but simply helping your people get meaningfully better at using the AI tools they already have access to. The best outcome is a team that's more capable and confident, not one that's more reliant on outside expertise.

The same logic applies to every recommendation I make. If a problem is best solved with deterministic code, that's what I'll recommend. If AI genuinely unlocks something that wasn't possible before, I'll show you exactly why and how. You shouldn't have to take that on faith — and with me, you won't.

Marginal gains, not big bang

One of the things I've seen go wrong repeatedly — in startups and in established businesses — is the instinct to solve everything at once. A sweeping transformation programme, a new platform, a complete overhaul. It sounds ambitious. It rarely works.

The approach that actually moves the needle is different. It's about isolating specific, real pain points and building targeted solutions for them — quickly, without disrupting the rest of the business. Getting something that works into the hands of the people who need it, learning from it, and moving to the next thing. This is how startups win when they're resource-constrained: not by trying to do everything, but by doing the right things in the right order.

It's also how you avoid the paralysis that affects so many organisations when they try to "transform." The typical over-ambition causes procrastination that leaves businesses scratching their heads as to why they can't seem to make improvements that are theoretically available to them.

I don't just advise. I deliver.

This is important to me, because I've seen what the alternative looks like.

There's a version of consultancy where someone spends several weeks learning about your business, produces a glossy document telling you what needs to change, and then leaves you to figure out how to do it. That document might be full of good ideas. It probably won't lead to much.

I'm not that. I'm hands-on. I write code. I build things. I've spent more than twenty years as a practising engineer — and while I've also led teams, shaped strategies, and sat in board meetings, I've never stopped being someone who can roll up their sleeves and deliver. If we agree that a particular problem needs solving, I can help solve it — not just describe the solution.

Whether that means building bespoke software, introducing the right tools, or working directly with your team to develop real capability — I stay involved until something meaningful has actually changed.