Franchesca Michaela Antonio's Blogs

Most conversations about co-managed IT start with an assumption that turns out to be only half right: that the model exists to give a stretched IT team more hands. That is true, but it misses the more interesting problem for businesses spread across several cities.

Copilot does not know anything a user could not already find themselves. That is the part most rollout conversations skip past on the way to the demo. The pitch is usually about speed: draft the email, summarise the meeting, build the slide. What rarely gets mentioned is that Copilot answers questions using exactly the same permissions the person asking already has, which means it will happily surface a salary spreadsheet, a half-finished redundancy list, or a client contract nobody meant to leave open to the whole company, provided the underlying permissions technically allow it.

"IT will handle it" is the most common answer to "what happens if we get hit," and it is also the most incomplete one. IT can isolate a compromised device in minutes. IT cannot decide whether to notify a regulator, whether to engage with a ransom demand, or who speaks to the client base while the situation is still unfolding.

Every accounting firm has a version of the same story. Xero will not talk to the practice management software. The IT provider says it looks like a software issue. The software vendor says it looks like a network issue. Three weeks and one very patient office manager later, someone finally admits fault, usually right around a BAS deadline.

Most businesses don't think much about their IT provider. Things are running, nobody's complaining, the invoices go through. That's usually taken as a good sign.

But if you've never actually sat down and gone through the questions to ask your IT provider, "nothing's broken" and "we're actually covered" might not be the same thing.

Dark web monitoring is a service that watches criminal forums, marketplaces, and breach dumps for any sign that stolen credentials or company data belonging to your business have surfaced. It works by matching your domain against threat intelligence feeds built by specialist firms, not by having someone manually browse hidden corners of the internet looking for your name.

Most business contracts specify a response time for a broken printer more precisely than they specify who responds to a live security incident. That is not an exaggeration to make a point. It is genuinely how a lot of managed service agreements are structured, because printers are simple to define and cybersecurity, until recently, was treated as a single line item rather than a set of distinct obligations.

A server does not know it is Friday. Neither does a firewall, a backup job, or the ransomware group deciding when to press go. This is the part of the "do we really need 24/7 IT support" conversation that most articles skip past, and it is the part that actually matters.

Every business owner has said some version of the same sentence: "We're backed up, we're fine." It usually gets said with real confidence, right up until someone actually needs to use those backups and discovers the honest answer was closer to "we're partially backed up, and we're not entirely sure how long getting everything running again would take.

Ask any hotelier who has been in the industry long enough, and they will probably still remember the sound of it: that soft clink of small keys hanging on hooks behind the desk, each one dangling from a plastic tag with a room number scrawled or stamped on it.

Somewhere along the way, technology developed its own dialect, and nobody sent out the dictionary. You nod along in meetings when someone mentions bandwidth or the API not talking to the database, and you generally get the gist. But if someone stopped and asked you to actually define the word, there is a good chance you would stall somewhere around "it is a, um, thing.

Ask five business owners what IT project management means and you will likely get five different answers. Some picture a Gantt chart nobody updates. Some picture a person whose job is to send meeting invites. A surprising number picture nothing at all, because their business has never actually had one, and every new system, migration, or software rollout has simply happened to whoever was free that week.