3 November 2026OnDraft

Insight

If one person built it with AI, make sure two people can run it

Build with AI. Just make sure someone else can read what it does and switch it off before it matters.

At the weekend the engineer Arpit Bhayani posted something that a lot of people recognised. "Somewhere in your company, there is probably a service running in production that nobody has actually read." One person built it with AI, it passed a few checks by hand, and it shipped. That person, he wrote, "is the only one who has any 'feel' for how it behaves."

He was writing about software companies. I see the same thing in small businesses, and they've got less cover when it goes wrong.

Why this is happening now

AI coding tools mean one person can build a working system very quickly. I build this way myself. A stock sync between Shopify and the warehouse, an export into Xero, a script that books couriers. Jobs that used to need a developer and a few weeks can now be done by the person who understands the problem.

That's genuinely good. The person closest to the problem usually builds the most useful thing.

The risk is what comes after. The system works, so nobody looks at it again. It becomes part of how the business runs, and the only map of it is in one person's head.

When you find out

You don't find out on the day it goes live. You find out on a busy Saturday when the stock figure on the website doesn't match the shelf, orders are coming in, and the person who built the sync is on holiday.

At that point the questions are simple. What does it touch? Can we stop it? If we stop it, what else stops? If nobody else can answer those, the business is depending on one person without anyone having decided that.

What I'd do before it goes live

None of this needs a development team.

  • Write one page. What it reads and what it changes: stock, orders, invoices, customer records. I've written before about writing down what your AI can touch, and this is the same idea for anything you build.
  • Say where it runs and how to switch it off. The account it lives in, the login, and the one step that stops it.
  • Test it on a copy. Run it on last week's orders and check the totals against Xero before it touches anything live. More on that in test it on a copy first.
  • Give it a second person. Someone who has read the page and could do the switching off without a phone call.
  • Check you could replace it. If it's built on a tool you pay for, make sure you can get your data out. I covered that in check you can leave it.

Where it matters most

The joins between systems are where this bites hardest. Shopify to the warehouse, the warehouse to Xero, orders to the courier. Off-the-shelf tools cover the systems themselves well, but the join is nearly always custom somewhere, and it's the join that breaks quietly. If that's where you are, our Shopify WMS integration page covers the stock side in more detail.

The short version

Build with AI. It's the quickest way to get the system you actually need. Just make sure two people can run it before it matters.

If you've got one of these running and want a second pair of eyes on it, give me a shout.

Sources

  • Arpit Bhayani on X, 2 Nov 2026: x.com/arpit_bhayani/status/2117103655908471238

Show us the bottleneck →

We build systems that power growth.

AI agents, integrations and operational software—built around your business.