Approach
The model is short on purpose. Survey what is actually there, change the few things that move risk, and leave someone on staff able to run it.
01
Start from what is deployed, not from what the last diagram claimed.
Directories, remote access, the firewall, the backups, the logging that may or may not be landing anywhere, the shares that have been open longer than anyone’s tenure. The survey is a shared picture. It is not a surprise report dropped on a table.
02
A long findings list is a way to avoid choosing.
The next step is a short sequence: what gets closed, what gets watched, what gets an owner, and what is explicitly left. Work is ordered so the environment stays runnable while it gets tighter. New tools have to earn a place against something already in the rack.
03
Finished means someone who works there can run it.
They can explain the setup, keep the routine, and know what to do when the routine is not enough. Notes, rules, and ownership stay behind. A dependency on the consultant does not. If the only copy of the reasoning lives in someone’s head, the engagement is not done.
It is not a retained army, and it is not a license to a platform with our name on it. Where a client already has monitoring, a firewall, a directory, or a backup product, the work starts there. Replacing it is a decision, not the default.
Engagements are not being taken through this site yet. The contact page shows where an address, a phone number, and a form will sit when they are real.
See the unpublished contact page