Every engagement starts with understanding what needs to change. From there, work may take the shape of a focused review, a defined project, or an agreed number of days each month.
Each engagement is scoped to the specific need, within the bounds of what's agreed - a focused review, a defined project, or continuing involvement for an agreed number of days.
Defining an IT project's scope and success criteria, assigning clear ownership, and coordinating the internal teams and suppliers doing the work. Useful where a project has stalled, or where one is about to start without anyone accountable for seeing it through.
Identifying which cyber gaps actually matter, in priority order, and helping see the fixes through to implementation. Covers control gaps, incident response readiness, and the practical steps to close the most material exposures first, rather than working through a generic checklist.
Understanding how AI is actually being used across the business, then agreeing approved tools, data boundaries, and practical controls. Aimed at controlled, working adoption rather than a blanket ban or an unmanaged free-for-all.
Mapping the supplier and vendor estate, clarifying who owns each relationship, and flagging contracts due for a renewal or consolidation decision. Useful where suppliers have accumulated over time without a consistent owner.
A focused review answers a specific question and sets out the options, without committing to anything further. A defined project has an agreed scope and outcome, delivered from start to finish. Where continuing involvement is genuinely useful, that's an agreed number of days each month, not a default outcome sold upfront.
I work on the agreed scope directly, alongside my other commitments. Which of these fits best depends entirely on the problem, and that's agreed after we've understood it, not before.
Send a short description of the problem, or book a 30-minute call to establish whether there's a fit and what the right starting point looks like.