I run IT for companies even if they don't have an IT department. Help desk, user accounts, endpoint security, monitoring, and the documentation that keeps all of it from living in one person's head.

Most of my work is with distributed teams, where there's no office network to fall back on and every laptop sits on someone's home connection. That changes what matters. Access grants stay live until somebody deliberately kills them. A machine that drops off endpoint protection doesn't announce itself. Onboarding either follows a runbook or it follows whoever set up the last hire and half-remembers what they did.

Day-to-day support across Windows, macOS, and Linux. Hardware, software, network issues, vendor escalation when it isn't ours to fix.

Identity and access in Microsoft 365, Google Workspace, Active Directory, and HR tooling like Personio. Onboarding and offboarding as documented processes rather than improvisation.

Endpoint protection across the fleet, access controls, and periodic auditing. I hold Security+ and a Google Cybersecurity Professional certification, so security isn't a separate engagement, it's how the support runs.

Uptime monitoring and alerting, currently holding 99%+ availability for the distributed team I support day to day.

Web infrastructure where it's in scope: hosting, security hardening, performance. Useful if your site and your IT are the same problem.

IT SOPs and technical documentation. This is the part clients tend to skip and later wish they hadn't.

Remote, from Lagos, and used to overlapping with European hours. I currently do this for a Berlin-based company, so I'm comfortable being the only technical person in the room and explaining things to people who don't want the detail.

I'd rather prevent tickets than close them fast. If that's the wrong priority for what you need, I'm probably not the right fit.