Let's talk.

Currently taking 1–2 advisory engagements this quarter - architecture review, cloud-cost audit, modernisation roadmap, or fractional CTO.

The useful version of a first message: what the system does, where it hurts (latency, cost, audit pressure, a launch date), and what you have already tried. Two or three sentences is plenty - I read everything myself and reply within a working day, usually with either a direct answer or a short list of questions before we book a call. If it is not a fit, I will say so on the first call and, where I can, point you at someone better placed.

For speaking, podcasts, or writing collaborations, the same inbox works - include the date and format. For anything sensitive, ask for a signed NDA in the first message and we will sort it before any details change hands.

A typical engagement starts small on purpose: a one-hour call to frame the problem, then a short written assessment before any larger commitment. Architecture reviews usually run two to three weeks; cloud-cost audits produce a prioritised savings list you can action with your own team; fractional CTO work is a standing weekly cadence. If you are earlier than any of that and just want a second opinion on a design, say so - those conversations are often the most useful ones, and there is no charge for the first call.