Practical IT for mid-sized companies: backups you have actually restored, networks with boundaries, laptops that outlast the lease, and when sovereignty is not worth it.
An agent factory is the old work cycle closed into a loop. Eight stages, shown on IT requests in a mid-sized company: why each one matters and where to start.
The valuable part of an agent factory is not the model but what it learns about your company. Check what stays with you when you want to change vendor.
Developers are moving from a single agent to a loop where agents carry the work and people approve it. The back office is next, and the precondition sits in company IT.
A laptop that runs agents locally, or an ordinary laptop with the agent on a station or a managed workspace. Decide by where the agent works when the lid is closed.
A mid-sized company rarely knows how many seats it pays for or uses. The vendor knows, and the audit letter arrives whether or not anyone kept an inventory.
Disabling the directory account is the visible half of a leaver. The SaaS logins, shared passwords, API keys and supplier portals are the other half, and nobody owns them.
Android XR builds the assistant into the operating system. Where that ties a company to one vendor's accounts and services, what stays yours, and how to plan the exit.
Display glasses with an AI agent are a computer with a camera worn on the face. Identity, device management, network, spares and camera rules come before the first pair.
A green tick says data was copied somewhere. It does not say you can get it back, how long it takes, or whether what you lost was included. How to find out.
Most company laptops are retired by a finance product, not by the hardware. What decides whether a device lasts five years, and how to check your fleet.
An assistant that searches your documents reads every permission literally. Years of folders shared with everyone stop being hidden overnight. What to fix first.
Networks built one device at a time end up flat: every printer, camera and guest can talk to everything. How that fails, and what a designed network looks like.
Most support contracts measure how fast the supplier replies, not how fast things work again. Where the promise and the expectation part, and what to ask for.
Most mid-sized companies have a single point of failure with a name, a laptop and a set of passwords nobody else has. It is rarely on the risk register.
Ask what leaving your current suite would cost in money, weeks and data that does not come out cleanly. The absence of an answer is itself the finding.
Companies worry about moving their documents. The thing that actually holds them in place is the directory every other system trusts to say who you are.
Shadow AI is the current state in most companies, and a ban produces the same usage with worse visibility. What a workable policy looks like instead.
A company selling sovereign IT should be able to say when not to buy it. Four situations where the honest recommendation is to leave things where they are.
