Nobody is looking after your software, and that is normal

There is a good chance something is running your business right now that nobody is really watching. A customer portal. An internal tool. The integration that quietly moves data between two systems you pay for. It works, so you don't think about it. That is exactly how it ends up with no owner.

I see this all the time, and I want to say up front that it's normal. Most systems weren't abandoned on purpose. The person who built it moved on. The agency finished the project and doesn't do upkeep. The employee who knew how it worked took another job. The software kept running, so it slid down the list, until the day it didn't.

The reason this matters more than it used to is boring but real. Attackers don't pick targets by hand anymore. They scan the whole internet for old, unpatched software and go after whatever turns up. In Verizon's 2026 breach report, exploited software vulnerabilities passed stolen passwords as the most common way attackers got in, about a third of all breaches. The same report put the median time to fully patch a known flaw at 43 days. A system nobody owns doesn't get patched in 43 days. It gets patched when something breaks, and by then it's rarely cheap.

What looking after it actually means

When I take over a system, the job is simple to describe. Keep it running, keep it safe, and keep it slowly getting better.

Running is monitoring, patches, backups that actually get tested, and the small fixes that pile up. I'd rather know your site is down before you do. Safe is the security updates, plus having a straight answer when a customer or an auditor asks who maintains this. Better is the occasional improvement, done in small pieces so nothing gets rebuilt from scratch and nothing scary happens on a Friday afternoon.

A few things I won't do, because they're the usual reason these arrangements go bad. I won't hand your system to a junior and disappear. I won't quietly ship the work to an offshore shop you never agreed to. And I won't drop your data into some AI tool I don't control. You get one engineer who knows your system, and I look at every change myself.

You also get a flat monthly fee and a short report each month that says what I did and what I'd watch next. No surprise invoices. That last part sounds small. It isn't. Most maintenance relationships die over a bill nobody expected, not over the work.

How it starts

You don't have to commit to any of this to find out where you stand. I do a free 15-minute system health check. We get on a call, you show me what you're running, and I send you a one-page writeup afterward: what it runs on, how old the pieces are, whether your backups work, and the first few things I'd fix. It's yours to keep whether or not you hire me.

I don't know your setup yet, so I'm not going to promise anything before I've looked. The point of the check is that you get a clear picture either way.

Your four options

If the check turns up work worth doing, there are four ways to pay for it. Three are monthly Care Plans, and one is plain hourly for people who don't want a commitment.

• Essential, $750 a month. Two hours of fixes, security patches, and dependency updates, with next-business-day response. Good for stable sites and apps that mostly need upkeep.
• Standard, $2,350 a month. Ten hours of fixes and small improvements, same-business-day response, and a monthly report and check-in call. Most active products land here.
• Premium, $4,500 a month. Twenty hours, priority response with on-call for the critical stuff, and a written service level agreement. For systems you can't afford to have go down.
• Pay as you go, $175 an hour, two-hour minimum. Best-effort response, no monitoring or patching. Fine if you just want a hand now and then, but nobody is watching the system between calls.

The three plans cost less than the same work billed hourly, roughly 14 percent less on Essential, 16 on Standard, and 20 on Premium, because I can plan the work instead of reacting to it. If a month runs long, extra hours are $160, and I quote them and get your okay before I touch anything, so the bill never catches you off guard.

If any of this sounds like a system you've got, the health check is the easy first step. Tell me what you're running and I'll come back within a business day with where it stands. Worst case, you walk away with a clear one-page picture of something you've been half-worried about for a while.

Brandon