Jump to a section⌄
AI tools have made it easier for businesses to build their own software. Instead of hiring a developer, someone can describe what they need and let AI produce the code. This approach, known as vibe coding, can be a useful way to solve an immediate problem.
But there's a difference between getting an app to work and knowing what happens when it becomes part of your everyday operations. Vibe-coded business apps can introduce risks that aren't immediately obvious. We use AI-assisted development ourselves, so we understand the benefits. We also know where experience makes a difference.
Why businesses are turning to vibe coding
When something in the business is becoming difficult to manage, building an app can seem like a sensible next step. Someone in the business understands the problem and has an idea for making the work easier. AI gives them a way to try it without learning to write software.
And sometimes the result is genuinely useful. A member of staff might create something that removes a repetitive task or makes information easier to find. They've identified a problem and found a way to tackle it, which is something worth encouraging.
The difficulty comes when that app starts handling important business processes. At that point, it needs to do more than perform the task it was created for. Someone also needs to understand what it connects to, what happens when something goes wrong and how it will be maintained.
The risks of limited development experience
A retailer we work with experienced this firsthand. An employee without software development experience had built an app using an AI tool to help with their work. It connected to the retailer's courier system, which allows businesses to book shipments, print labels and check parcel tracking.
The app worked, but there was a problem. It kept checking parcel tracking far more often than the courier allowed. Eventually, the courier blocked the retailer's access to its system for the day, leaving staff unable to print shipping labels.
Orders had been sold and packed, but the team couldn't print the labels needed to send them. Parcels were waiting at the door, and the courier couldn't take them. Staff then faced a scramble to get the labels printed and the orders dispatched.
Our team quickly worked out the likely cause and advised what needed changing in the app. An experienced developer would have known to check the courier's usage terms and build within those limits. Someone without software development experience might not realise those rules exist.
The app had been working, but the consequences of getting something wrong were felt across the business.
Security risks of vibe-coded business apps
Security is another concern with apps built using AI tools. The code might work, but that doesn't mean it's secure. There are several things that can be overlooked when someone builds an app without software development experience, such as:
- Unprotected information: Passwords and access keys may be stored without adequate protection.
- Weaknesses in the code: AI-generated code can contain security problems that aren't immediately obvious.
- Missed updates: The person maintaining the app may not know which software it uses or when security fixes are needed.
In October 2026, two critical security flaws were discovered in PHP, a programming language widely used for websites and web apps. The UK's National Cyber Security Centre issued an alert urging organisations to take action.
We patched immediately when the fixes became available. But someone who built an app using AI might not even know it runs on PHP, let alone recognise when an update is needed. This is why understanding what an app relies on matters just as much as getting it working in the first place.
Disconnected systems and inconsistent data
Building an app to solve one business problem doesn't necessarily mean it will work well with everything else. An app might perform its intended task perfectly but still create problems when information needs to move between different systems.
For example, a business might build an app to manage customer enquiries, track jobs or process orders. But if that information isn't connected to the systems used by other departments, employees may still need to transfer details manually and check that everything matches.
The business has gained another tool, but not necessarily a better way of working. And if the app holds information that other departments need, staff may find themselves copying figures between systems or waiting for someone else to provide an update.
As we explored in our article on running a business on spreadsheets, separate records can create problems as a business grows. A single source of truth means sales, stock, orders, customers and invoices share the same information rather than relying on separate files.
The risks of relying on one person
There's another problem when one employee builds an app that nobody else understands. They might know which prompts they used and how everything fits together, but that knowledge isn't necessarily documented. If they leave the business or something stops working, colleagues can struggle to make even a small change.
The problem isn't limited to fixing errors. Businesses change, and software needs to change with them. A new sales channel, different working process or updated requirement might mean the app needs modifying. Without someone who understands how it was built, even a straightforward request can become difficult.
What started as a useful solution can become difficult to maintain, particularly when nobody else understands how it was built or what it depends on.
Why software development experience matters
Businesses don't necessarily need to build a separate app every time an existing process becomes difficult to manage. Sometimes, the better approach is to bring those processes together in one system.
MPX is business operating software developed by Stark Wayne that brings sales, stock, orders, customers, invoicing and reporting together. Everyone works from the same information, rather than relying on disconnected systems and separate records.
For example, orders can come in automatically from platforms such as Amazon, Shopify and WooCommerce. Once an order is packed, MPX can also book the courier and print the label using shipping rules you've set.
Experienced developers consider more than whether an app performs its intended task. They also look at:
- Existing systems: How the software connects to other tools and what limitations need to be considered.
- Testing: Whether changes could affect other parts of the business.
- Ongoing maintenance: How the software will be updated and supported as requirements change.
Where a business needs something more specific, Stark Wayne's software developers can build solutions around those requirements. We use AI-assisted development ourselves, which has accelerated what we can build and how quickly we can do it. Our developers understand how the software needs to work alongside existing business processes.
We work alongside you as an extension of your team, helping set up MPX around your processes and providing ongoing support.
Ready to Get Started?
If your business is developing its own apps to manage everyday operations, it's worth considering whether a connected business system or professionally developed software would be a better fit.
Book a demo to explore how MPX could work for your business, or see pricing.
