Consulting
Deciding well, with someone who has seen the case before
Consulting is for decisions that are expensive to get wrong: leaving a cloud, changing vendor, rebuilding an infrastructure, achieving compliance, knowing what happens if everything stops tomorrow. You leave with a written, argued recommendation, clear enough to defend to your board.
The subjects I handle
Ending a dependency
A cloud whose costs drift, a vendor who stopped answering, a licence gone unreasonable. The method, the traps and the real numbers before moving.
Continuity and recovery
What happens if your system stops tomorrow? We test it for real, price the cost of an outage, and fix what must be fixed.
Compliance and security
Data protection, card payments, hardening a production infrastructure. Treated as an architecture question, not an end-of-project document.
What you receive
A written study, not a slide deck. It runs to a few pages, names the options, recommends one, and states what happens if you do nothing. It is written to be read by an owner and defended to a board, not to impress an engineer.
Every figure carries its source. If it comes from your system it is dated and reproducible; if it comes from elsewhere, the source is named.
Frequently asked
- Do we need a CIO or a CTO?
- If there is one, we work with them, not in their place. If there is not, we go ahead with you: you the trade, me the technique. I bring what I have already seen elsewhere; if I have not seen it yet, we work it out together.
- What if the right choice is to change nothing?
- Then that is good news. I write it down, with the why. You know where you stand, and you keep your means for what really matters.
Tell me the decision you face
Thirty minutes is often enough to know whether the subject needs a study or just an opinion.