automationAIethicsprocess

Our Honest Position on AI: Human Direction, Machine Execution, Total Transparency

AI is changing how software gets built. Here's how we actually use it, what we don't use it for, and why transparency about those choices matters for independent businesses.

Mark Scott
/19/03/2026/8 min read

AI is being used to build a lot of things that look impressive and aren't. We want to be clear about what we actually do — and why.


There is a phrase that has become almost meaningless through overuse: "AI-powered."

Everything is AI-powered now. Email tools, design tools, project management tools, scheduling tools. Every software vendor has added a chatbot and a generative feature and put "AI" somewhere prominent in the marketing. The word has been stretched so far it no longer tells you anything useful.

We want to be honest about how we use AI, what it actually changes in our work, and — more importantly — where it doesn't feature at all.


What AI Actually Does in Our Work

We use AI tools in two specific areas.

In rapid prototyping: Our Vibe Design Sprint service uses AI-native design tools to explore multiple design directions simultaneously, at a speed that would be impossible through traditional design processes. In 48 hours, we can generate, evaluate, and refine high-fidelity prototype directions that would previously have taken weeks. AI handles the volume of output. The creative director — a human — evaluates every output, decides what works, discards what doesn't, and shapes the direction toward something coherent and worth building on.

In content production: Our content repurposing service uses AI video and audio tools to transform long-form content into cinematic short-form assets. The AI handles the production workload — colour grading, audio scoring, format adaptation. The creative direction — what gets selected, how it's edited, what the narrative arc is, whether the output actually communicates something — comes from a human who has read the brief, understands the brand, and can tell the difference between something that stops a scroll and something that doesn't.

In both cases: AI does the execution work. A human makes the decisions.


What AI Doesn't Do in Our Work

AI does not design your brand.

It doesn't make the strategic decisions about how you should position yourself, who your audience is, what they need to feel before they'll reach out, or what your website needs to communicate.

It doesn't write your copy, unless we're using it as a first-pass draft that gets substantially rewritten by a person who has read your brief, spoken with you, and understands your voice.

It doesn't replace the discovery process — the structured conversation at the start of every project where we try to properly understand your business before we make any decisions about how to represent it.

And it absolutely doesn't make the automation systems we build any less readable, traceable, or transparent. When we build a workflow that triggers when a client signs a contract, or sends an alert when a project milestone is approaching, or populates your CRM from an intake form, every step of that logic is visible and explicable. You can see exactly what it does. If something goes wrong, you can trace where and why. There is no black box.

Opaque system versus visible architecture — closed, inaccessible black box compared to open, transparent, customisable and traceable automation logicOpaque system versus visible architecture — closed, inaccessible black box compared to open, transparent, customisable and traceable automation logic


Why Transparency Is a Non-Negotiable for Us

We didn't start RAAIX because we thought AI was interesting. We started it because we kept working with independent businesses who were drowning in administration they couldn't control.

The businesses that needed help most were the ones with real workflows, specific processes, and genuine craft — people who had built something worth protecting and were spending too much of their time on tasks that existed alongside their work rather than as part of it.

When you automate someone's business workflow, you are inserting your logic into their livelihood. That is a significant responsibility. It means the automation you build has to be:

Understandable. If you can't explain to the business owner exactly what the system does at every step, something has gone wrong in the design process. Complexity is usually a sign that the workflow hasn't been thought through clearly enough. Simplicity is a discipline.

Trustworthy. A business owner should be able to look at their automation and feel confident about what it's doing. Not optimistic. Not hopeful. Confident — based on evidence they can actually examine. That means visible logic, not promises about what the AI "should" do.

Maintainable. Any system we build for a client needs to be something they can adjust when their business changes, understand when something doesn't behave as expected, and hand to another developer if they ever need to. Lock-in is bad engineering and worse ethics.

These principles come from a simple belief: your tools should serve you, not the other way around.

Visible noise versus invisible power of automation — stressed business owner overwhelmed by 156 emails and alerts compared to calm operator with automation handling the background workVisible noise versus invisible power of automation — stressed business owner overwhelmed by 156 emails and alerts compared to calm operator with automation handling the background work


The Silicon Valley Model We're Not Following

The dominant model in the technology industry is to abstract everything into a service, make the internals invisible, and create as many switching costs as possible. You subscribe. You depend. You can never quite leave.

This model is good for technology companies. It is not good for the independent businesses using their products.

We are not a technology company building a scalable SaaS product. We are a small studio in Malmesbury, Wiltshire, that builds specific things for specific businesses. Our relationship with a client ends when the work is done and they have full ownership of what was built. No ongoing subscription. No proprietary dependencies. No leverage we maintain over their operations.

When we finish a project, we give you the code, document the systems, and walk you through everything. If you never speak to us again after that, the work still functions correctly and you understand how it works. That's the outcome we're building toward.

If you want to continue working with us — on a retainer, on a follow-on project, for ongoing support — we'd like that. But it should be because the relationship is valuable, not because we've engineered a dependency.


What This Means in Practice

When you work with us, you can ask — at any point, about anything we're building — "how does this work and why did you make that choice?" We will be able to answer that question clearly.

You won't hear "our AI handles that" as an explanation for a decision we can't justify. You won't be handed a system with magic behaviour and asked to trust it.

You will get work that was designed with intention, built with care, and handed to you with full transparency about what it is and how it works.

That's not a sophisticated position. It's just basic professional respect for the people whose businesses we're touching.


Frequently Asked Questions

Do you use AI to build websites?

We use AI tools to accelerate specific parts of the work — design exploration, code assistance, content production — but every structural and visual decision is made by a human designer who understands your brief. AI helps us work faster. It doesn't make the decisions that determine whether the result is actually good.

Is AI automation reliable for small business workflows?

AI-assisted automation is reliable when the workflow has been properly designed by a human first. The failure mode isn't usually the AI component — it's that the workflow wasn't thought through clearly before tools were connected. We design the workflow logic explicitly before any tools are configured, which is why the systems we build behave predictably.

How do I know I own the code and systems you build for me?

Everything we build is yours. We don't use proprietary platforms that require ongoing licences. We don't create dependencies that make it expensive to leave. When a project is complete, we hand over the full codebase, document the systems, and make sure you understand how everything works. You're not subscribed to us — you've purchased work that belongs to you.

What makes your approach to AI different from other agencies?

Most agencies use AI either invisibly (not disclosing it) or as a marketing claim without substance. We use it specifically, disclosingly, and with a clear boundary: AI handles execution at scale; humans make the decisions that determine quality and direction. We also build everything to be transparent and traceable — so you can see exactly what your automations are doing, rather than trusting a black box.

Do you do anything with my data?

We don't. We don't retain client data after a project, we don't train models on client work, and we don't use your business information for any purpose other than completing the project you've engaged us for. We work to UK GDPR standards as a matter of process, not afterthought.