The limitations of vibe coding and why don’t we make our own bread

Does anyone make their own bread? I know it’s a weird question … but, hold that thought.

I’ve spent a long time, almost three decades working with SMEs… making them more efficient at what they do.

And these are businesses, they’re no fools… they’ve tried the conventional products and services, but there’s something…something intangible, there’s something wrong, something doesn’t fit! It’s that instinct, that sort of… itch they don’t know how to scratch. And so they reach out to people like me.

I have built all sorts of different things. Everything from:

  • stock management and… invoicing systems
  • event management and accommodation systems
  • PAYE systems
  • print management systems

I’ve built a lot of systems!

Yeast rising: AI and the birth of vibe coding

But then artificial intelligence came along and that put… a bit of a wrinkle in things. Or did it?

WARNING: MIXED METAPHORS AHEAD!

Baking bread is a lot like building software… we’ve got to keep doing it!

Building software is a lot like sprinting up a steep climb… it’s hard work! We’ve got to maintain it.

When it comes to software we’ve got to fix bugs, we’ve got to run updates, add new features, it doesn’t stop!

And, let’s face it, why should someone running their own business — unless they’re a software developer — become a software developer? Or, a vibe coder. It doesn’t make any sense to me.

Yes, of course vibe coding can add new features and fix bugs! But without that background in software development it’s less like baking bread and more like building a black box. Because you’re not in a position to ask pointed questions, such as…

  • Are you sharing confidential customer and client data with the AI?
  • Is the code safe?

Data sovereignty. Data governance.

These are important questions with legal implications. Not fun!

British businesses bringing home the bread

SMEs are the backbone of Britain, performing minor miracles with meagre resources, keeping everything in motion.

So why don’t we make our own bread? We have these things called “bread-making machines”, and most of the supermarkets stock the principal ingredients.

But then, do we have the time? And the chances are our kids wouldn’t like it, and most of the supermarkets do a better job of it!

You see, there’s a bit of a parallel here with SMEs: armed with AI, they could build any number of things.

But could they fix the problems with their businesses if they don’t know what those problems are?

And that’s the thing: this is a human-shaped problem… and no amount of AI is going to fix that because AI doesn’t get a guided tour of a workshop or a factory floor.

It doesn’t get to ask questions based on decades of experience, it won’t do any of those things… at least for now!

But I’m confident enough, that before AI grows legs and sprouts arms, and starts doing the job that I do… then… there’s a really good argument for people like me!


Running a business is a lot like juggling

SMEs are the backbone of Britain, performing minor miracles with modest resources, keeping everything in motion…

Problem is, keeping things in motion is a lot like jugging — moving things around isn’t the same as moving them forward.

Having business processes that depend on physical copies of important things like invoices, items in stock, sales forecasts and so on risk data loss when shifting between them and their digital counterparts.

Good old Bob’s retiring next month, taking with him three decades of knowledge because strategies don’t exist to hold onto it.

And that’s before we talk about sprawling workflows comprised of legacy systems and different cloud products with essential features that cost extra, questions about data governance because most of them are based abroad, and what about sharing data with AI?

In time, all this going around in circles builds up so much process debt, we don’t know if we’re going forwards or backwards.

Octane Interactive Limited builds custom-fit precision workflows for businesses like yours.

Octane’s approach is about understanding where the pain is, what makes your business unique, and how we create a workflow that’s an exact match.


Why the AI Act’s Article 50 Isn’t a Section 230 for AI

As artificial intelligence continues to expand, subsuming the Age of Information, we as consumers of AI are caught in a mad scramble to first understand it (and it’s potential), and then harness it to our own benefit.

On the 2nd of August 2026, the Article 50 of the AI Act came into force. Who cares what happens in the European Union? Anyone providing services to the 452 million citizens of the European Union, I would imagine.

Once detected, AI-generated assets are getting the down vote:

… a long-established online marketplace for 3D assets used by video game developers, film editors, and 3D printing nerds, users are sending a clear message … the marketplace is being flooded by AI-generated assets, representing one in six models — but they only account for only $1 out of every $90 in revenue.

Here, the covenant between those flooding the marketplace with low-grade AI slop (the Provider), and not labelling their creations as AI-generated, they’re placing the owners of said marketplace (the Deployer) in a bad place from a legal perspective.

I’m reminded of Section 230 of the Communications Decency Act of 1996, and both pieces of legislation revolve around the same question: Who is responsible when a system delivers something harmful, fraudulent, or illegal to an end-user?

Regulatory FeatureUS Social Media Era (Section 230)EU AI Act Era (Article 50)
The Legal SplitDifferentiates between the Platform (e.g., Facebook) and the Third-Party User who posted.Differentiates between the Provider (who built the AI tool) and the Deployer (who sells the output).
The Liability ShieldThe Platform is entirely immune if a user posts something illegal, provided the platform did not create it.The Provider is largely shielded from consumer-facing disclosure fines if the Deployer fails to label the content at checkout.
The “Active Role” LineIf a platform materially contributes to creating the illegal content, it loses immunity.If a Deployer significantly alters the AI model, they lose “Deployer” status and are legally reclassified as the “Provider”.

Do the major AI vendors sit outside the legal protection of Section 230? At the moment, no such ruling has been made, but there are some signals:

  • Garcia v. Character Technologies, where a federal court treated chatbot output as a product rather than protected third-party speech — a narrow, non-binding decision.
  • Raine v. OpenAI, which tests the same question against OpenAI, is still pre-trial.

You create an unlabelled horrible deepfake, share it on Facebook, and Section 230 swoops in to protect Facebook.

You create an unlabelled low grade digital asset for sale on a digital storefront, and Article 50 ensures no such protection for the storefront.

Here, we see how fragile the covenant between the Provider and the Deployer is, weakened — some (me) would argue — by that implicit thing known as trust, but I’m a cynic. But what mechanisms could we use to enforce appropriate labelling? Since we are the AI, the challenge(s) grow with each successive sweep of the web by the mechanisms that populate these models.

As both consumers and the owners of businesses, the Age of Artificial Intelligence is making a difference, no doubt, but are we buying it?


Octane’s approach

First published as a white paper “How the Hidden Costs of Inefficient Workflows Drain SME Profits — and How to Fix Them” on the 2nd of November 2025 “Octane’s approach” is the sixth and final chapter, following on from “Route Forward”

Octane’s long been an advocate of digital transformation — not the fragmented spreadsheet here and an email there approach, but a coherent and comprehensive whole that unifies processes into a cohesive precision workflow.

Our approach has three distinct phases:

First, we discuss with the directors and managers what it is the business does, and examine the existing workflow.

Second, we speak with the team to establish what the ideal workflow should look like.

Third, we build a workflow that’s as near a fit as is practical.

At this point the relationship is nascent and the burden of proof rests with Octane. Having identified the core parts, we take a MVP approach. MVP? We build a minimal viable product — a working prototype to demonstrate our understanding of the job.

Our approach is modular, in that we don’t build one big thing but a group of little things, charging for each stage of the build as we go along.

Having arrived at this point, it’s possible you’re thinking at least one of the following…

Common Objections & Misconceptions

“We already use Microsoft 365 / Google Workspace.” → Tools are great for documents, but they’re not workflows.

“We have a CRM already.” → CRMs track customers, but they don’t manage operational workflow.

“Off-the-shelf is cheaper.” → True upfront, but inefficiencies and costs compound over time, multiplied by n number of services used by the business.

“We don’t want disruption.” → Who does? Our MVP approach involves incremental and low-risk improvements, with a good ROI over time.

“We’re good as we are, thanks!” → So much as one instance of “Task X” could cost upwards of £4k per year.

“How much would something like this cost?” → A typical spend would be between £4k-20k depending on the specific requirements.

The average SME is already spending somewhere between ~£800-£16k per month on cloud services.

Octane stems the cost bleed by replacing and retiring some services, while reducing the time spent on existing tasks.

You take control of the workflow.

Building tools to fit the hands that wield them

Walk into a workshop and pick up a hammer, a screwdriver, a spoke shave and the ergonomics of their design speaks to their purpose.

Our expectation is that the tool should fit the hand that wields it, but that’s not always the case with software.

Workflows often become a fragile and tangled composite of tools that don’t seem to fit the business: a bit of learning curve; required features cost extra; difficulties sharing critical data; US-centric; questions regarding data governance…

What begins as a cost saving and a convenience becomes an expensive burden.

Does a business need umpteen cloud services when one could do the same job?

Imagine a workflow that’s an exact fit for the business: no feature bloat; no unexpected price hikes; no vendor lock-in.

✓ Time reclaimed: less steps, faster decisions, greater focus.

✓ Costs reduced: fewer subscriptions and a reduction in errors.

✓ Control regained: confidence in the data, compliance, and the workflow.

Octane creates precision workflows for the SME.

Visit: octane.uk.net/contact and let’s begin shaping a workflow that works for you.


Route Forward

First published as a white paper “How the Hidden Costs of Inefficient Workflows Drain SME Profits — and How to Fix Them” on the 2nd of November 2025 “Route Forward” is the fifth chapter, following on from “Case Studies”

Realising the extent of the challenges we face is one thing, but we must also contextualise the nature of them, too — little by little we risk forfeiting control for convenience, making our own businesses a terrain that’s difficult to navigate.

Becoming more efficient:

“A Deloitte study found that businesses implementing custom-built systems saw a 20–30% increase in efficiency within the first year, highlighting why the benefits of customisation can’t be overlooked.” — How SMEs can unlock growth through automation.

Taking control:

“The UK’s appetite for Bespoke business software has grown markedly over the last few years. Firms are seeking systems that reflect how they actually operate — integrating data end-to-end, automating fiddly processes, and carving out competitive advantage rather than tolerating the constraints of off-the-shelf tools.” — The rise of Bespoke Enterprise Software.

Reducing costs and risk is what happens when we take a critical look at our existing workflows and go beyond the financial triage of pausing services, hunting down discounts, and negotiating preferential rates.

Off-the-Shelf Tools versus a Custom-Fit Workflow

Off-the-shelf cloud services:

  • convenient monthly cost, quick to adopt;
  • tried and tested, often come with mobile apps;
  • rarely a perfect fit;
  • feature flux (swapping, changing, and removing);
  • premium features and extra seats add cost;
  • competitors use the same tools;
  • workflow must adapt to the tool;
  • vendor lock-in;
  • unexpected price hikes.

Your data is locked into their systems, obfuscating vital business intelligence. Compliance isn’t optional for those businesses working in regulated sectors, and data stored outside the UK and EU could be the cause of potential GDPR issues.

Combining these services to work in unison and share critical data often requires technical understanding.

Octane’s custom-fit approach:

✓ custom fit to existing or improved workflows;

✓ complete control of the specification;

✓ no wasteful feature bloat;

✓ ROI over the lifetime of the software;

✓ option to integrate with internal and third-party services;

✓ data ownership and control;

✓ possible funding support from local government;

✓ support and maintenance on agreed terms.