Three Years, One Number to Call

How It Started

Wendy found me in the fall of 2022 through a freelancing platform. She was running Florida Digital Reporting solo at the time and was about to bring on her first employee, and she needed someone to get a computer ready for another person to use. That sounds simple — but getting a machine ready for an employee means setting up a user account, configuring email access, deciding what that person can and can't do on the system, structuring shared files in a way that actually makes sense, and thinking ahead to what happens to that access if the relationship ends.

We configured a new profile with email and shared folder access, and I removed local administrator rights from the employee account — which matters more than most people realize. Local admin rights are the single biggest foothold ransomware needs to do real damage. Without them, malware that gets onto a machine hits a wall before it can spread. It's a simple setting that gets skipped constantly because it occasionally makes software installs slightly less convenient, and it's one of the first things I address on any new setup. After that, I installed the necessary software and set up remote access so I could get back in when she needed me — which she would. They always do.

What Three Years Actually Looks Like

Most people imagine long-term IT support as a series of big dramatic fixes, but the real value is quieter than that. It's having someone who already knows your setup when something goes wrong at 9am on a Tuesday, and having a history of working through problems together so neither person has to start from scratch.

Over three years, the work has covered a lot of ground. When Wendy's laptop died, I migrated her software, OneDrive, and remote access to the new machine with minimal disruption to her day. When Dragon dictation — the voice software she uses for transcription — stopped working correctly after a Windows update, I configured the mic sensitivity and set her headset as the primary input. When her office manager left and then returned some time later, I offboarded and re-onboarded access both times, including untangling shared folder permissions that had drifted in between. When I noticed an admin password had expired before Wendy did — something I should have caught proactively — I fixed it at no charge and made sure it was documented going forward. When a new employee joined, I set up the account, email, and shared access and got her bookmarks in order for day one. When the business standardized the role title to "Office Manager," I went back in and renamed accounts, profile folders, and the relevant system entries cleanly, so nothing would break down the road.

The Florida Problem

I'm in Ohio. Wendy's in Florida. I've never been to her office, never touched her hardware, never met her employees in person — and it hasn't mattered. The tools that make remote IT work — remote access software, centrally managed antivirus, Microsoft 365 as the collaboration backbone — mean geography stopped being a real constraint a long time ago. What matters is access and trust, and those are things built over time.

When Wendy reaches out with an issue, I respond and we get to work. I have a day job, so I'm not promising one-hour resolutions — but I'm reachable, I know her environment, and I don't need thirty minutes of context-setting before I can be useful. That's the value of continuity. It's not about proximity.

What Annual Renewals Actually Mean

Every year, Wendy's remote access and antivirus renew, and the services keep running. Windows updates happen automatically, antivirus definitions stay current, and I get alerts if something needs attention. That's not exciting to describe, and it's not supposed to be — the goal is that nothing exciting happens, because exciting in IT usually means something broke.

Three years in, that's the shape of the relationship: something needs attention, she reaches out, we handle it. Something needs upgrading, we talk it through. Renewals come around, nothing changes because nothing needed to. It works from a thousand miles away just fine.