How we work
Four working rules we set before starting, so they can be checked once the project ends.
Scope is closed in writing before the first interview
Which systems are in, which are out, and on what criterion the line was drawn. It is what prevents the awkward conversation at the end, when a plant nobody mentioned turns up, or a third party turns out to have been inside all along.
Every finding travels with its evidence
A finding without backing is an opinion. Ours are tied to what supports them: an exported configuration, a traffic capture, a dated log entry, an interview with a name and a role attached. Where something could not be verified, the report says so.
Nothing of yours is published without your approval
We work under NDA. If at some point we want to use the engagement as a reference, we ask you first, and you review and approve the text before it exists. Until that conversation happens, your name appears nowhere.
The deliverable has to outlive us
Report, roadmap, ceremony scripts, runbooks. The proof they are any good is that your team can defend them in front of an auditor with none of us in the room.