our office hasn't had a major IT disaster. That doesn't mean your technology is healthy. It might just mean you've been lucky.
There's a phrase we hear in almost every initial conversation with a prospective client: "Everything seems to be working fine."
And they're usually right. The internet works. Email works. People can print most of the time. The property management software loads. Files are accessible. Nobody's screaming.
But "working" and "set up right" are two very different things. And the distance between them is where every IT disaster lives, waiting for a trigger.
What "working" actually means
"Working" means functional. The system does what you ask it to do in the moment. You click send and the email goes. You open a file and it opens. You print something and it prints eventually, after the second try, on the printer down the hall.
"Working" tells you nothing about whether your systems are secure. It tells you nothing about whether your backup would actually restore if you needed it. It tells you nothing about whether former employees still have active accounts. It tells you nothing about whether your network is segmented or whether every device in your office is sharing the same flat network including the smart TV and the guest laptop in the lobby.
"Working" is the absence of a visible problem. It is not the presence of proper configuration.
What "set up right" actually means
Set up right means someone has intentionally designed your environment with security, efficiency and reliability in mind not just gotten things to the point where they technically function.
Here's what that looks like in practice, using a typical 20 person property management office as an example.
Email: "working" means people can send and receive. "Set up right" means every account has multi-factor authentication enabled, email filtering is catching phishing attempts before they reach inboxes, SPF and DKIM records are configured so your domain can't be easily spoofed and there's a retention policy so you're not storing seven years of email you don't need and can't afford to lose.
File sharing: "working" means people can access files on the shared drive. "Set up right" means the folder structure mirrors your business workflows, permissions are configured so people can access what they need and nothing more, files are syncing to the cloud with versioning so accidental deletions can be reversed and there's a clear process for where new documents go.
Network: "working" means devices connect to Wi-Fi and the internet loads. "Set up right" means you're running commercial grade access points, your business traffic is on a separate network from personal devices and IoT gadgets, your firewall rules are current and your DNS is configured to block known malicious domains.
Backups: "working" means backup software is installed and appears to be running. "Set up right" means backups complete successfully every day, the data is stored offsite with encryption, retention policies match your business needs and someone has tested a restore within the last quarter to confirm it actually works.
User accounts: "working" means everyone can log in. "Set up right" means every employee has their own credentials for every platform, access levels match their role, shared accounts have been eliminated, former employees have been fully offboarded and there's a documented process for adding and removing access.
The gap is where disasters live
The reason this matters isn't theoretical. The gap between "working" and "set up right" is exactly where security breaches, data loss and operational failures come from.
The backup that's been failing silently for months it was "working" because the software was installed. The former employee who still has access to your accounting platform the platform was "working" because current employees could log in. The flat network where a compromised IoT device gives an attacker access to your file server the network was "working" because everyone could connect.
Every IT disaster we've seen at a small business followed the same pattern: everything was "working" right up until the moment it catastrophically wasn't. And the root cause was always something that would have been caught by a proper setup or a proper review of the existing setup.
The audit nobody wants until they need it
We understand why this isn't at the top of anyone's priority list. When things are working, there's no urgency. You've got tenants to manage, projects to coordinate, payroll to run. Nobody wants to spend time thinking about whether their DKIM records are configured correctly when the email is sending just fine.
But a proper IT assessment a real one, not a scare tactic sales pitch takes a few hours and gives you a complete picture of where you actually stand. What's genuinely secure and what just appears to be. What would survive a failure and what wouldn't. What's properly configured and what's held together by luck and habit.
The businesses that get this assessment before the disaster are the ones that avoid the disaster. The ones that get it after are the ones that wish they'd done it sooner.
If everything in your office is "working" right now, that's great. But if nobody has verified that it's set up right, that confidence might be built on a foundation you haven't actually inspected.
It's worth checking. We can help with that.
