Book a call

§ 00 — For technology leaders, moving first or moving carefully

Senior
technology
advisor.

Strategy, architecture and hands-on engineering, alongside your team rather than instead of it. Right now that mostly means two things: adopting AI in a way that keeps your data yours, and security that holds.

§ 01 — Track record

Knowledge is everywhere now. Judgement isn’t.

Any team can now get a credible answer to any technical question in seconds. Deciding which to act on still takes experience. I work with technology leaders to make those calls. About James

  1. 01Then

    Cloud infrastructure

    Building and running platforms in the cloud, all of it defined in code.

  2. 02Then

    Secure systems

    Designing systems that are secure from the first diagram.

  3. 03Then

    Agentic runtimes

    Building the runtimes that let AI agents act on real systems, safely.

  4. 04Now

    Sovereign AI

    Deploying models onto dedicated hardware, for full sovereignty over your data.

§ 02 — The questions I get asked

The same questions come up, wherever you are on the curve.

Q.01

“Where does our data go when we use AI?”

Governed access, private deployments, and models on dedicated hardware when the data must not leave.

Q.02

“What stops an agent doing something it shouldn’t?”

Runtimes with boundaries built in: least privilege, audit trails, and human approval where it matters.

Q.03

“Where do we start with AI, without betting the business on it?”

Small, useful and reversible. Pick one or two uses that earn their place and get them into production properly.

Q.04

“What do we build, and what do we wait for the models to absorb?”

Build what is specific to your business. Rent or wait on the rest. Independent advice, with nothing to resell.

Q.05

“Would we survive a breach?”

Raise the baseline first: identity, access, devices and recovery. Fixed, not just reported.

Q.06

“How should the team change now that AI writes the code?”

Fewer hand-offs, more review, sharper judgement. Coached from daily practice, not theory.

§ 03 — Focus / AI

Adopt AI without losing control.

From deciding where AI earns its place, to agents that act on your own systems within clear boundaries, to models running on hardware you control.

  • Use cases that earn their place
  • Agentic runtimes with boundaries built in
  • Models deployed on dedicated hardware
  • Full sovereignty over your data

AI adoption Sovereign AI

§ 03 — Focus / Security

Raise the baseline. Keep it raised.

Practical security from someone who also builds the systems: designed in from the first diagram, fixed rather than reported, and owned by your team afterwards.

  • Posture review and roadmap
  • Identity, access and devices
  • Secure-by-default platforms
  • Guidance when things go wrong

Security advisory

§ 04 — How it works

Not a solution handed over. A partner who stays in the room.

Most engagements move between all four, often in the same week. Technical leadership

01 · Leadership

Advise

A senior sounding board for technology decisions: what to build, buy or ignore, and what to do first.

02 · Platform

Architect

Whole systems designed and stitched together so the pieces work as one platform. Any stack.

03 · Hard parts

Build

Hands-on engineering in the weeds with your engineers, not a report and a goodbye.

04 · Your team

Mentor

Pairing, reviews and coaching so your people own what gets built.