There is one question we ask on almost every first visit, and it is not a technical question. We ask the owner what happens to the business if the computer in the corner stops working tomorrow morning. Not next quarter. Tomorrow. Then we stop talking and wait.
The pause that follows is the most informative thing in the whole meeting. Sometimes it is short, because somebody genuinely thought about this. Far more often it stretches out while the owner works through it in real time, and you can watch them realize that they know the answer to about half of it. That pause is not a sign of a badly run company. It is the completely normal result of running a business where technology was never the point, it was just something you needed in order to do the thing you actually care about. After enough of those conversations around Denton County, the same handful of patterns show up over and over. None of them are about exotic technology. All of them are about assumptions.
Almost Everyone Believes They Have Backups
This is the single most consistent pattern, and it is not because owners are careless. Somebody set up a backup at some point. There is a drive, or a subscription, or a service that a previous vendor turned on. The word backup appears on an invoice. So the box feels checked.
The gap is almost always between backing up and restoring. A backup that nobody has ever restored from is a guess. We regularly find backup jobs that have been silently failing for months, backups running to a drive plugged into the same machine they are protecting, and cloud sync services being used as backups when they are not backups at all. Sync means that when a file changes in one place it changes everywhere, which means when a file gets encrypted by ransomware or deleted by mistake in one place, it gets encrypted or deleted everywhere. The honest test is simple. Pick a file from three weeks ago, ask someone to produce it, and time how long that takes. If nobody can, you do not have backups. You have hope.
The Password Problem Is Never Really About Passwords
Owners tend to describe this as a discipline problem, as if the solution were a sternly worded email about strong passwords. It is almost never that. The real pattern is shared accounts. One login that four people use because the software charges per seat. One email address that the whole front desk shares. Credentials sitting in a spreadsheet or a group text because there was never a better option offered.
Those shared accounts are the thing that actually hurts, because they destroy the ability to know who did what, and because they make it impossible to cleanly remove access when somebody leaves. And the stakes here are not theoretical for small companies. Verizon’s 2025 Data Breach Investigations Report found that ransomware was present in 88 percent of breaches at small and medium sized businesses, compared with 39 percent at large organizations. The FBI’s Internet Crime Complaint Center reported more than 1 million complaints and $20.9 billion in reported losses in its 2025 Internet Crime Report, with business email compromise alone accounting for over $3 billion of that.
The fix is boring and effective. Give every person their own account, put a password manager in place so nobody has to remember anything, and turn on multi factor authentication everywhere it is offered. Multi factor authentication, often shortened to MFA, means a login requires a second proof of identity beyond the password, usually a code from an app on your phone.
Nobody Knows What They Are Actually Paying For
Software sprawl is universal and it is nobody’s fault. Subscriptions accumulate the way junk accumulates in a garage. A department needed a tool three years ago, the person who championed it left, and the charge keeps clearing every month because it is small enough that nobody questions it.
The pattern we find is remarkably consistent in shape. Here is what usually turns up when someone finally goes line by line.
- Licenses for people who no longer work there. Every seat that was never reclaimed is both a monthly charge and a live account somebody could still log into.
- Two tools that do the same job. Usually because two different people solved the same problem independently and neither knew about the other.
- A premium tier nobody uses the premium features of. Someone upgraded for one feature during one project, and the upgrade never came back down.
- A subscription tied to a personal credit card. Which becomes a genuine business continuity problem the day that person is unavailable.
- Something critical with no documented owner. The domain name, the website hosting, or the certificate that expires on a date nobody has on a calendar.
The Loudest Problem Is Rarely the Expensive One
When a business calls us, the stated problem is usually the thing that is annoying people that week. The printer. The slow machine at the front desk. Email that keeps landing in the wrong folder. These are real and they deserve fixing, because a daily irritation compounds into real lost hours.
But the expensive problems are almost always quiet. The server with no monitoring on it. The one internet connection with no backup. The former employee whose account is still active. The critical application running on a version of software the vendor stopped supporting two years ago. None of these make noise until the day they make an enormous amount of noise. A good technology partner should be fixing the loud thing this week and quietly working on the silent things in the background, and should be able to explain in plain language which is which.
Everybody Underestimates an Hour Offline
Ask an owner what an hour of downtime costs and most will guess low, because they are thinking about payroll for the idle hour. The actual cost includes the appointments that did not get booked, the orders that did not get taken, the customer who called a competitor, and the two days of catch up afterward. That last part is the piece almost nobody counts.
Once an owner works through that number honestly, the conversation about a second internet connection and battery backup stops being a debate. A failover connection that does not depend on the same buried cable, paired with an uninterruptible power supply so your network gear survives a flicker, is one of the cheapest pieces of insurance a growing business can buy. Satellite service like Starlink works well in this role specifically because it skips local ground infrastructure, so a backhoe on your street does not take out both connections at once.
The Bottom Line
None of these patterns come from careless companies. They come from good companies that were busy doing their actual work while technology quietly accumulated around them. The fixes are unglamorous. Test a restore. Give everyone their own login and turn on MFA. Read your subscription list once a year. Write down who owns the domain name. Put a second connection at the front door.
If any of this felt uncomfortably familiar, that is a good sign, because recognizing it is most of the work. We are happy to walk through your setup and tell you plainly which of these apply to you and which do not. Reach out at https://harrisonward.com/contact/ and we will start with that same question about tomorrow morning.
Comments are closed