What we have solved
When the IT Keys Leave With the Technician
This anonymized example is drawn from real past technology-recovery work.
The problem
The previous technician knew where the keys were. The business did not.
Important systems were still operating, but ownership, credentials, vendors, and recovery paths were fragmented or undocumented. The business could use its technology day to day without being certain who controlled the domain, hosting, Microsoft 365 administration, backups, network equipment, recovery contacts, or recurring technology services.
Where we started
One of the most useful places to begin was not the server room. It was accounting.
Past invoices and recurring charges can reveal the hidden map of a company’s technology environment: internet providers, cloud services, Microsoft subscriptions, hosting, domain services, backup vendors, software providers, hardware purchases, support companies, phone systems, and security services.
Those records do not contain every answer, but they identify relationships that can be verified. They help turn “we think somebody handles that” into a list of vendors, services, accounts, and questions.
What we did
With the business’s authorization, we traced the technology relationships outward from the records that remained. We identified vendors and services, established the business or its authorized representative as the correct point of contact, and used legitimate vendor recovery procedures to recover or reset administrative access.
As access returned, we traced dependencies between systems, documented equipment, accounts, vendors, and recovery paths, replaced obsolete contacts, and established business-controlled credential storage. The work respected authentication and vendor security controls; it was about proving legitimate ownership and rebuilding recoverability, not bypassing safeguards.
The result
The goal was not merely to regain access. It was to leave the business with a technology environment it actually controlled: clearer ownership, documented vendors, known recovery paths, and less dependency on any one individual.
The keys belong in the castle.
A business should never lose control of its technology because one technician disappears. Ownership and recoverability are part of the Small Business Technology Checkup, along with the practical question: If the person who handles your technology disappeared tomorrow, could you still access everything?