AI automation in Bristol and the South West: who's allowed to press send.
An AI coding tool in the news this week deleted a live database while trying to help. That's a story about software developers, not about your salon or your building firm — but it points at the one question worth asking before you let any AI near your business: what is it allowed to do without you checking first?
Bristol and the wider South West run on small, hands-on businesses. Aerospace and engineering suppliers around Filton and Bristol's docks. Independent shops and salons in Clifton, Stokes Croft and Gloucester Road. Tourism and hospitality along the coast from Weston-super-Mare to Torquay. Trades and agencies scattered from Bath to Exeter to Plymouth. Different trades, same shape of week: one person, or a very small team, trying to do the customer-facing work and the admin at the same time.
What actually happened
An AI coding assistant, given free rein to run commands on a live system without a safety net, tried to fix a configuration problem and deleted the whole home directory it was working in — including the database. It's not an isolated case. Reports through this year have documented similar incidents across several different AI coding tools, including one where an agent wiped a production database in under ten seconds. The pattern is the same each time: an AI given direct, unsupervised control over something real, and no one checking the output before it acted.
That's a warning for software teams giving AI the keys to production servers. It is not a reason to be nervous about AI answering your enquiries or chasing your invoices. But it is a useful test to run against anything you're offered: does this thing act on its own, or does someone see the work before it goes anywhere?
The bottleneck this actually touches
For a Bristol business, the sharp end of this isn't a database. It's trust. You've heard an AI tool broke something it shouldn't have gone near, and now you're wondering whether letting AI near your customer inbox, your bookings, or your invoices means the same risk — something goes out wrong, or goes out at all, without you seeing it.
That worry is reasonable. It's also exactly why WorkMate is built around one rule: anything customer-facing follows draft, then review, then send. Your crew writes the reply, prepares the booking confirmation, drafts the follow-up chase. You look at it. You approve it, or you fix it first. Nothing goes to a customer, a supplier, or a social account on its own. There is no version of WorkMate where a mate has the kind of unsupervised, direct-to-production access that caused the coding tool failures in the news.
What this looks like day to day
A Bath letting agent's inbox mate drafts replies to viewing requests overnight. In the morning, the owner reads five drafts, approves four as they are, and edits one because a tenant's name was wrong. Nothing sent itself while no one was looking.
A Bristol independent café's booking mate holds a waiting list for a private event enquiry and drafts a reply with three available dates. The owner picks one and hits send from their phone between orders.
A Plymouth trades firm's accounts mate drafts a chase email to a client three weeks overdue, tone matched to how that client's been chased before. The owner reads it, softens one line, sends it. The whole thing takes under a minute of their actual attention.
Why the checking step doesn't slow you down
The instinct is that a review step adds friction back into work you automated to remove friction. In practice it's the opposite of what happened in the coding tool failures: those systems had no review step at all, which is exactly how a small mistake became a deleted database in seconds. A five-second glance at a drafted email is not the same category of risk as an AI given free run of a live system. The review step is what makes it safe to hand over the drafting in the first place.
Your crew also shares one Brain. If you correct how it should word something to a particular supplier, or tell it a client prefers phone calls to email, that sticks. You don't repeat yourself, and the drafts get closer to something you'd approve without changes over time.
What to actually check
If you're weighing up an AI tool for your business, coding assistant or otherwise, the news this week gives you a genuinely useful question to ask any vendor: what can this act on directly, and what does a person see first? If the answer is "it just does it," that's the same shape of risk that deleted a production database. If the answer is "you see it before it goes anywhere," that's a different kind of tool.
You don't need to understand how any of this works underneath. You need to know whether something can leave your business without you looking at it first. For WorkMate, the answer is no.
