Write-ups from deployments we have actually run, organised by section. Specific problems, the reasoning behind the approach, and what it cost to get wrong. Client names are withheld under confidentiality.
Page 5 of 6
Disabling someone's account is the visible part of offboarding and the smallest part. What survives is the access nobody recorded: certificates, service accounts, shared credentials, and integrations built under a named person's login.
Most businesses keep everything forever because deleting requires a decision and keeping does not. That default is a growing storage bill, a growing breach exposure, and in several jurisdictions a compliance failure.
A firewall's value is not what it blocks. It is whether anyone can still state, accurately, what it permits — and in most rule bases over a few years old, nobody can.
A password committed to a repository is compromised the moment it lands, and deleting the line does not undo it. Rotation is the only remedy, which is why most businesses cannot actually respond to a leak.
Someone edits a prompt, the output looks better, and it ships. Without evaluation there is no way to tell an improvement from a regression, which makes every change to an AI feature a guess that nobody can audit.
Most businesses that believe they are segmented have VLANs and a router that permits everything between them. Separating broadcast domains is not the same as controlling what can reach what.
Voice has no retry, no cache and no error page. A call centre outage is revenue lost in the moment and agents paid to sit idle, which makes reliability an architecture decision rather than a product feature.
A VPN answers whether someone can reach your network. The question that decides whether you are secure is what they should reach once they are on it, and most remote access designs never ask it.
Support fails long before AI arrives, and AI applied to a broken support operation produces confident wrong answers faster. What actually determines success: knowledge quality, escalation design, and an honest definition of a resolution.
AI is the first component most businesses integrate that does not return the same answer twice. That single property, not the technology, is what determines how it should be built into an architecture you already have.
Automation converts a labour cost into an engineering liability. That is usually a good trade, but only when it is made deliberately. A decision guide to when automation pays, when it does not, and what has to be in place before it scales.
Moving the records is the easy part. The decisions that determine whether anyone trusts the new system are about which data does not move, what counts as the same customer, and how you prove afterwards that nothing was lost.
We typically respond within 4–8 business hours.