How I work

Same five steps, in the same order, every single time.

I don't have a methodology I'm trying to sell you. I have a way of working that's been beaten into me by 18 years of seeing what happens when you skip steps.

STEP 01

I learn how the business actually runs

Before architecture, before tools — I sit with the people doing the work. Workflows, approvals, the spreadsheet someone's been quietly maintaining for six years. That's where the real spec lives.

STEP 02

I write it down properly

Functional requirements, process maps, roles, integrations, what the reports actually need to say. Boring document. Saves the project.

STEP 03

I design the architecture

Built around what's going to break in two years, not what's exciting today. Modular, integrated, secure, and survivable when the team that built it has moved on.

STEP 04

I run the build

I'll either write the hard parts myself or supervise the team doing it. Either way, decisions get made, tradeoffs get explained, nothing rots in a backlog.

STEP 05

I stay until it's actually working

Testing, deployment, training, documentation, the first month of production where everything goes weird. I don't disappear at go-live.

How we'd work together

Four shapes an engagement usually takes.

Pick whichever fits. We can also start in one and slide into another as we learn what you actually need.

[01]

Independent Consulting

Direct architecture, advisory, or transformation work where I personally own the technical surface and you have one person to call.

[02]

Specialist Coordination

I bring in a small, vetted team for things I can't or shouldn't do alone — but I stay accountable for what they ship.

[03]

Implementation Supervision

You've got engineers. They're great. They just need senior technical direction and someone to make calls. That's me.

[04]

Fractional CTO / Advisor

Long-running. I sit in your leadership team part-time, set direction, and stay close enough to actually be useful.

Why people end up calling me

Senior depth, without having to bolt another department onto your org chart.

One person, the whole thing

You don't manage a panel. You manage me. I manage everything else.

I speak both languages

Years of sitting between business people and engineers means nothing gets lost in translation on my watch.

I'll personally own the sensitive bits

Financial logic, reconciliation, AI workflows, anything you can't comfortably hand to a junior — that work stops with me.

I'm thinking about year three, not month three

I'd rather under-promise on the demo and over-deliver on the architecture you'll still be running in 2030.

Where the depth sits

An honest map of what I'm strongest at.

No one is genuinely top-tier at everything. These are the areas I keep my hands in regularly enough to be worth your money.

Architecture & Design

Enterprise & Solution Architecture0
Microservices & API Design0
Integration Architecture0

AI & On-Premise LLM

Private LLM Deployment0
RAG & Vector Retrieval0
OCR & Document Intelligence0

Full-Stack Engineering

Backend (Django · APIs · PostgreSQL)0
Frontend (React · PWA)0
DevOps & Infrastructure0

Delivery & Governance

Programme & Delivery Leadership0
Vendor & Risk Management0
Fractional CTO Advisory0

Where I'm headed

I want to be the technology partner you'd recommend to your closest peer — without hesitation.

Not the biggest firm. Not the loudest. Just the person other senior leaders quietly trust to walk into a hard problem and leave the place better than they found it.

Let's talk

If you've got a problem that nobody seems to own — that's usually where I come in.

Architecture work, on-prem AI, Fractional CTO, or a transformation programme that needs someone to actually finish it. Send me a note — I read every email.