# Vibe coding your own removals software: riskier than it looks

Published: 2026-11-04 · Reading time: 7 min · Bas Software
Web version: https://www.bas.software/uk/blog/vibe-coding-moving-software-risks

With AI you can build a working app in an afternoon without knowing how to program. Handy for small jobs. Building your whole removals software that way, with real customer data in it, is another matter. These are the risks you only see once it’s running.

![A man in a navy polo shirt types on a laptop at a desk by the window in the evening, with a white lorry parked outside a warehouse.](https://www.bas.software/images/blog/vibe-coding-verhuissoftware-hero.jpg)

An AI tool will now build you a diary with jobs you can drag onto crews in a few minutes. Ask for quotes and you’ll have those too. Type “Make me removals software” on a quiet evening and by bedtime you’ll have something that looks like it. It feels like magic, and in a way it is.

What it doesn’t give you is anyone to answer for it. Once real customers’ addresses, survey photos and your porters’ bank details are in it, the app is yours to secure, update, back up and explain to the ICO. Some removal company owners now want to build their whole system this way: quotes, the diary, timesheets, invoices and storage. That carries risks you don’t see in the first few weeks.

## What is vibe coding?

Vibe coding means making software by telling an AI in plain English what you want, and using the result without checking the code yourself. The term comes from the AI researcher Andrej Karpathy, in early 2025. You judge the app by what you see on the screen, not by what’s underneath.

That last part is the whole point. What you see works. What’s underneath, you don’t know.

## What it’s genuinely good for

AI is a fine tool for a removal company, used on the right jobs. Things that used to need a programmer, you can now do yourself:

- A calculator for the number of boxes or the cubic feet in a room.
- A script that renames a job’s photos neatly.
- A simple landing page for a campaign.
- An internal checklist for the warehouse.

What they have in common: there’s no customer data in them, nothing stops if they don’t work for a day, and if something goes wrong you bin it and start again.

## Where it goes wrong: a whole system with real data

Removals software is the opposite of those small jobs. Think about what sits in it at an ordinary removal firm. The names, addresses and phone numbers of every customer who has ever had a quote. A survey of each home, room by room, with photos of the inside. Where the keys will be left on completion day. Your staff’s pay details and bank details. And the diary your whole firm runs on.

### You don’t know what you’ve built

If you can’t read the code, you don’t know whether one customer can see another customer’s survey by changing a link. Whether a porter who left last month can still open the crew app. Or whether a password or key is sitting somewhere in the code for anyone to find.

That isn’t theory. In Veracode’s GenAI Code Security Report, AI-generated code contained a security flaw in 45 percent of the tests. A programmer checks that code. With vibe coding, nobody does.

### The real work starts once it’s running

Building the first version is the easy part. Then comes the work nobody sees:

- **Updates.** The building blocks under your app get security updates. Who installs them, and who checks everything still works afterwards?
- **Changes to real data.** Adding a field to a thousand existing jobs isn’t the same as adding it to an empty test app. One wrong command and the data is gone.
- **Backups.** Do you have them, and have you ever tried restoring one?
- **Outages.** The diary won’t load on a Friday morning in July, with every crew waiting for their jobs. Who fixes it, and how fast?

### No test environment

Professional software has a separate test environment, a sandbox, where changes are tried before they go live. With a home-built app you usually test on the real thing.

We’ve seen what that means ourselves. In a CRM without a test environment, emails once went out to real customers by mistake. It ended well, but it could have been worse. Imagine it had been a payment reminder, or a confirmation with the wrong moving date.

> “Vibe coding makes building easy. Maintaining it, securing it and answering for it is exactly as hard as it always was.”

## UK data protection: it’s on you

As soon as you hold personal data, UK GDPR applies, and the ICO is the body you answer to. With a home-built system, a few duties land entirely on you:

- **Keeping the data secure.** You have to be able to explain how you protect it: who has access, how it’s protected and what happens when something goes wrong.
- **Reporting a breach.** A personal data breach generally has to be reported to the ICO within 72 hours. You have to notice it first.
- **Agreements with suppliers.** The hosting, the email service and the AI tool you build with may all handle the data too. Each needs a proper data processing agreement.

The fines can be heavy. For a removal company the bigger damage is often to your name: a customer who reads that photos of their home were left open to anyone doesn’t come back, and tells the neighbours.

## Trade bodies and commercial customers ask questions

Are you a [BAR member](https://www.bas.software/uk/blog/bar-membership-removals-software) with a code to work to, or do office moves for commercial customers and public bodies? Then you’ll get more and more questions about information security: where is the data, who can see it, is there a data processing agreement, what about backups? With a home-built system you have to answer those yourself. If you can’t, you lose the contract or the tender.

## And if you bring in a professional?

That solves part of the risk. A developer who reads, secures and maintains the code turns your home-built app into something you can rely on. But do the sums. An experienced developer on the payroll costs a full salary plus employer’s NI and pension. A freelancer who checks in now and then bills every hour they spend in your code. And one developer isn’t a team: if they’re off sick, on holiday or hand in their notice, you’re back to code nobody else knows.

With a software package you pay for a whole team that builds, tests, secures and maintains the software, and you share that cost with lots of other removal firms. You pay a subscription instead of a salary. Bas, for example, starts [from £200 a month excluding VAT](https://www.bas.software/uk/pricing). For almost every removal company, that’s far cheaper than building it yourself and employing someone to look after it.

## Build it yourself or not? An honest comparison

| Topic                         | Built yourself with AI             | Existing removals software             |
| ----------------------------- | ---------------------------------- | -------------------------------------- |
| First version                 | Quick and cheap                    | Ready straight away                    |
| Security                      | Unknown, nobody checks             | Tested and maintained by the supplier  |
| Updates and outages           | You                                | The supplier                           |
| Cost over time                | A developer’s salary or hourly rate | A fixed subscription                  |
| Test environment              | Usually not                        | Yes                                    |
| Data protection and contracts | Arrange and justify it yourself    | Data processing agreement with the supplier |
| Who you depend on             | You (and whoever has the code)     | The supplier                           |
| Exactly what you want         | Yes                                | Within what the system can do          |

Building it yourself has one big advantage: it does exactly what you want. For the system your whole firm runs on, from survey to invoice, that rarely outweighs the rest (see [separate tools or one system](https://www.bas.software/uk/blog/erp-for-moving-companies)). Still want something specific? Build a small tool alongside and connect it through your software’s [integrations](https://www.bas.software/uk/solution/integrations), instead of building everything yourself.

## Five questions before you start

**Can you answer yes to all five?**

- I can read the code, or someone who can checks it
- There’s a separate test environment, apart from the real data
- Backups run automatically and I’ve restored one
- I know who updates the app and who fixes it when it stops
- I can explain how the data is secured if a customer or the ICO asks

Five yeses? Then you probably have a developer in-house already, and you’re not really vibe coding any more. One or more noes? Use AI for the small jobs, and keep your customer data in software that’s built and maintained for it.

## Conclusion

Vibe coding is one of the most enjoyable things to come along in years. Use it for calculators, scripts, a checklist or a landing page. But a whole removals system with real customer data, pay details and your entire diary isn’t an afternoon project. The risk isn’t in the first version. It’s in everything after it: security, updates, outages and answering for it.

Weighing up building your own against an existing system? See what [switching](https://www.bas.software/uk/switching) to Bas involves.

Then decide what is still worth building yourself.'
  }
  button={'Book a demo'}
  href={'/uk/contact'}
  coffee
/>

**Sources:** Veracode, 2025 GenAI Code Security Report (July 2025). Andrej Karpathy on vibe coding (February 2025).
