1.0 · The short answer

Writing the code was never the hard part.

AI tools have changed how quickly software can be produced. They haven’t changed what it takes to get a product right: understanding the business, weighing up trade-offs, meeting your legal obligations and standing behind the result.

That still takes people. The specialists we bring in, including the developers in our network, work from the full scope of the product rather than in isolation. They can tell good code from bad, and they build with the next release in mind, not just this one.

3.0 · Where it breaks down

Six places AI alone puts a product at risk.

These matter most on large platforms, regulated services and anything that has to keep working for years, which is most of what we do.

3.1

Regulation & compliance

AI can explain UK, EU and US data protection rules in general terms. It can’t tell you what your product has to do about consent, retention or access, because that depends on your data, your users and your sector.

  • It sounds just as confident when it’s wrong as when it’s right
  • It leaves no record of why a decision was made, which is the first thing an auditor asks for
  • We write compliance requirements into the specification, so they’re agreed before anything is built

3.2

Security

AI-generated code often works and is still unsafe. It can skip the checks that stop the wrong person seeing the wrong data, and nothing on screen tells you.

  • Plausible code can miss input validation, access controls and secure defaults
  • Pasting sensitive information into public AI tools can put it outside your control
  • We specify security requirements up front and have the result independently penetration tested

45%of AI-generated code samples tested introduced a known security flaw.Veracode, 2025 GenAI Code Security Report [1]

3.3

Accessibility

AI learns from the web as it is, and most of the web isn’t accessible. Left to its defaults, it reproduces the same failures.

  • Keyboard navigation, focus order and screen reader behaviour are rarely handled unless someone specifies them
  • For public sector services, accessibility is a legal requirement, not a nice-to-have
  • WCAG 2.2 AA is written into every specification we produce and tested during design and build

94.8%of the top million home pages had detectable WCAG failures.WebAIM Million, 2025 [2]

3.4

Large, complex systems

Large platforms have dozens of requirements pulling against each other: integrations, permissions, reporting, performance and years of existing data. AI only sees the part of the problem it’s shown.

  • It solves the part it’s asked about, not the system around it
  • It can’t hold every business rule across every part of the platform at once
  • Trade-offs need someone who understands your commercial priorities and can explain the choice to your stakeholders

3.5

Maintenance over time

A product isn’t finished at launch. Quickly generated code tends to be repetitive and loosely organised, which makes every later change slower, riskier and more expensive.

  • Duplicated logic means fixing the same problem in several places
  • Code nobody on your side understands is code nobody can safely change
  • A clear specification gives every future developer something to work from

8×increase in duplicated blocks of code during 2024, as AI coding assistants became widespread.GitClear, AI Copilot Code Quality research, 2025 [3]

3.6

Protecting your codebase

An AI tool with access to your systems can make sweeping changes in seconds, including ones nobody asked for. On the projects we run, these safeguards are in place:

  • We never give AI tools unsupervised access to live systems or production data
  • Every change we make is reviewed by a member of our team before it’s released
  • We use version control, separate test environments and backups as standard
  • Every change we release traces back to a requirement you’ve signed off

Sources

  1. Veracode, 2025 GenAI Code Security Report.
  2. WebAIM, The WebAIM Million, 2025.
  3. GitClear, AI Copilot Code Quality: 2025 research.

5.0 · The tool isn’t the skill

The best brushes in the world won’t paint the picture.

Give someone professional oil paints, a good canvas and the finest brushes money can buy, and you haven’t given them a masterpiece. You’ve given them materials.

What makes the painting is knowing what to paint, why, and when to stop. AI is an excellent set of tools. The value is still in the judgement of the people using them.

6.0 · How we use it

AI inside a process, not instead of one.

  • 01

    Specification first

    AI works to a brief we’ve written and you’ve signed off, not to a prompt.

  • 02

    People review everything

    Nothing AI produces reaches your product without review by someone accountable for it.

  • 03

    Your data stays protected

    Client data is handled under our ISO 27001 controls and kept out of public AI tools.

  • 04

    Independent testing

    Security is tested by a CREST certified specialist partner, and accessibility is checked against WCAG 2.2 AA.

  • 05

    Decisions on record

    You can see what was decided, by whom and why, long after launch.

change-request · 214REVIEWED
  1. 01
    RequirementSigned off in the specification
  2. 02
    AI-assisted draftFaster first version
  3. 03
    Human reviewChecked against the requirement
  4. 04
    TestingSecurity, accessibility, function
  5. 05
    ReleasedTraceable back to step 01

Already built something with AI?

We can review what you have, specify it properly and make it safe to scale, without starting from scratch unless you need to.

Talk to us about a review

Next step

Use AI. Just don’t bet the product on it.

If you’re weighing up building it yourself with AI against working with us, we’re happy to talk it through honestly.