You type in plain language what you want: "Make a planning board where I drag moves onto crews." A few minutes later, there it is. One more sentence and it has a quoting module. It feels like magic, and in a way it is.
That is called vibe coding: having AI write software without reading or understanding what is being built. For small things it is fantastic. But more and more often we hear from movers who want to build their entire system that way. Quotes, planning, hours, invoices, storage. That comes with risks you do not see in the first weeks.
What is vibe coding?
Vibe coding is making software by telling an AI in plain language what you want and using the result without checking the code yourself. The term comes from AI researcher Andrej Karpathy, early 2025. You judge the app by what you see, not by what is underneath.
That last point is exactly what matters. What you see works. What is underneath, you do not know.
What vibe coding is really good for
To be fair: for a moving company, AI is a great tool. Small things that used to need a programmer, you now do yourself:
- A calculator for the number of boxes or cubic metres.
- A script that renames the photos of a job neatly.
- A simple landing page for a campaign.
- An internal checklist for the warehouse.
What these have in common: there is no customer data in them, nothing depends on them if they do not work for a day, and if something goes wrong you throw it away and start again.
Where it goes wrong: a complete system with real data
Moving software is the opposite of those small things. It holds names, addresses and phone numbers. Inventory lists and photos of the inside of people’s homes. Key arrangements. Your staff’s payroll data and bank details. And your whole business runs on it.
You do not know what you have built
If you cannot read the code, you do not know whether a customer can reach another customer’s data through an edited link. Whether your staff app still works for someone who no longer works for you. Or whether a password or key is sitting somewhere in the code.
That is not theory. In Veracode’s GenAI Code Security Report, AI-generated code contained a security flaw in 45 percent of the tests. A programmer reviews that code. With vibe coding, nobody does.
It only starts once it is running
Building the first version is the easy part. Then comes the work you do not see:
- Updates. The building blocks under your app get security updates. Who installs them, and who tests that everything still works afterwards?
- Changes on real data. Adding a field to a thousand existing projects is different from adding it to an empty test app. One wrong command and data is gone.
- Backups. Do you have them, and have you ever tried restoring one?
- Outages. The planning board does not load on a Monday morning in peak season. Who fixes it, and how fast?
No test environment
Professional software has a separate test environment, a sandbox, where you try changes before they go live. With a self-built app you often test directly in production.
We have experienced ourselves what that means. In a CRM without a test environment, emails went out to real customers by accident. It ended well, but it could have gone worse. Imagine it had been a payment reminder, or a confirmation with the wrong date.
"Vibe coding makes building easy. Maintaining, securing and accounting for it is exactly as hard as it always was."
GDPR: you are responsible
As soon as you process personal data, the GDPR applies. It contains a few obligations you have to meet entirely yourself with a self-built system:
- Appropriate security (Article 32). You must be able to explain how you protect the data: who has access, how it is shielded, what happens when something goes wrong.
- Reporting data breaches (Article 33). A breach must be reported to the supervisory authority within 72 hours. You do have to notice the breach first.
- Agreements with suppliers (Article 28). The hosting, the email service and the AI tool you build with may also process data. That requires a data processing agreement.
Fines can reach 20 million euros or 4 percent of worldwide annual turnover (Article 83). For a moving company the bigger damage is often reputation: a customer who reads that photos of their home were exposed does not come back.
Accreditations and business clients are watching
Do you hold an accreditation, or work for business clients and public bodies? Then you increasingly get questions about information security: where is the data, who can access it, is there a data processing agreement, what about backups. With a self-built system you have to be able to back those answers up yourself. If you cannot, you miss an order or a tender.
And if you bring in a professional?
Then you solve part of the risk. A developer who reads, secures and maintains the code turns your self-built app into something you can rely on. But do the maths. An experienced developer on the payroll costs a full salary plus employer costs. A freelancer checking in part-time charges an hourly rate for every hour in your code. And one developer is not a team: if they fall ill, go on holiday or leave, you are 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 those costs with many other moving companies. You pay a subscription instead of a salary. For almost every moving company, that is many times cheaper than building it yourself and hiring a professional for it.
Build it yourself or not? An honest comparison
| Topic | Built yourself with AI | Existing moving software |
|---|---|---|
| First version | Fast and cheap | Available straight away |
| Security | Unknown, nobody checks | Tested and maintained by the supplier |
| Updates and outages | You | The supplier |
| Costs over time | A developer’s salary or hourly rate | A fixed subscription |
| Test environment | Usually not | Yes |
| GDPR and processing terms | Arrange and justify yourself | Data processing agreement with supplier |
| Dependency | On you (and whoever gets the code) | On 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 an ERP for moving companies that rarely outweighs the rest. Still want something specific? Build a small tool alongside it and connect it through the integrations of your software, instead of building everything yourself.
Five questions before you start
Can you answer yes to these questions?
- I can read the code, or someone who can checks it
- There is a separate test environment, apart from the real data
- Automatic backups run and I have restored one
- I know who updates the app and fixes it when it stops
- I can explain how the data is secured if a customer or the regulator asks
Five times yes? Then you probably already have a developer in-house, and you are not really building a vibe-coded app anymore. One or more no? Then it is wise to use AI for the small things, and keep your customer data in software that is built and maintained for it.
Conclusion
Vibe coding is one of the most enjoyable things to arrive in recent years. Use it: for calculators, scripts, a checklist or a landing page. But a complete moving system with real customer data, payroll data and your entire planning is not an afternoon project. The risk is not in the first version, but in everything that comes after: security, updates, outages and accountability.
Weighing up building yourself against an existing system? See what switching involves.
Shall we grab a coffee?
Let us talk about what you build yourself and what you are better off buying.
Online or on-site, you choose.
Veracode, 2025 GenAI Code Security Report (July 2025). General Data Protection Regulation (GDPR), Articles 28, 32, 33 and 83. Andrej Karpathy on vibe coding (February 2025).