Insights · Point of view
Regulation is the key to innovation.
Regulation is the key to innovation. Not the obstacle, not the tax: the key. Innovation’s scarcest input is permission, and regulation is how permission is earned at scale. Our model follows from it: we innovate, and bring highly trusted partners in for deployment when required.
Why does everyone believe the opposite?
Because the complaint is loudest exactly where innovation dies, and it is easier to blame the rules than the readiness. The market consensus says regulation is strangling AI: too many frameworks, too much caution, Europe legislating while others ship.
Look closer at where innovation actually fails, though, and it is rarely the regulator holding the door shut. Pilots do not die from a lack of ideas. They die because nobody will own the consequence of deployment. A demo impresses everyone and changes nothing, because the organisation cannot answer the only question that matters at the threshold of production: who is accountable if this goes wrong, and how would we know?
Ideas are abundant. Permission is scarce. That is the real economics of innovation, and it is the part the consensus gets backwards.
What does regulation actually give you?
Three things innovation cannot ship without.
First, named consequence. Regulation forces the question every unregulated pilot avoids: what happens if this fails, and who owns that? Answering it is uncomfortable and clarifying in equal measure, and it is the difference between a demo and a deployment.
Second, legible trust. An organisation that can show its decisions survive audit is an organisation that is allowed to move. Trust at scale is not a feeling; it is a paper trail. Regulation is the format that makes your trustworthiness readable by boards, customers and regulators alike.
Third, the muscle. In unregulated settings you must build consequence discipline from scratch, and most never do. Regulated organisations already own it: risk functions, assurance processes, decision trails. The work is not building the muscle. It is pointing it at pace instead of paralysis.
Where is the proof?
Our client list is the argument. The most inventive work we do happens in the most regulated environments, and that is not a coincidence.
In air traffic control, one of the most safety-critical regulated environments in Britain, our work has been on innovation itself: an innovation lab, digital tower tools, the systems that will carry the next generation of airspace. Nobody there treats regulation as the enemy of new ideas. Regulation is the reason new ideas can be trusted near live airspace at all.
In banking, we delivered personalisation inside FCA-regulated communications: creative marketing and compliance tooling in the same system, because the regulated version is the only version that ships. And the platform behind much of our work ran 100 million users and a million transactions a second inside consequence-heavy businesses. What made that possible was engineering excellence and the kind of client trust that regulation exists to formalise.
So how should you work?
The way we do. We innovate, and bring highly trusted partners in for deployment when required.
Innovation needs freedom: fast prototyping, honest judgement about what is worth building, the creative leap. Deployment in regulated environments sometimes needs things a small senior team should not pretend to carry alone: specific certifications, assurance regimes, scale infrastructure. So we keep the two honest. The inventing is ours. Where deployment demands it, we bring in partners we trust completely, under one accountable delivery model. Regulated organisations recognise that division of labour instantly, because it mirrors their own: inventiveness where it belongs, assurance where it is required.
And if you are the one saying “we cannot move quickly because we are regulated”: you are sitting on the advantage. The trust muscle your unregulated competitors lack is already built. Involve assurance in week one, put the controls in the pipeline, and point the discipline at pace. Regulation is not what is stopping you. It is the reason you will be allowed to ship what others can only demo.
Common questions
Is regulation slowing AI innovation down?
It is slowing the deployment of the unready, which is different. The discipline it forces is exactly what lets serious innovation reach production.
How can a regulated organisation innovate quickly?
Treat regulation as a design input. Involve assurance from week one, build controls into the pipeline, use tiered governance so low-risk work moves fast.
What if the regulator has not caught up with AI yet?
Govern yourself to the standard you expect the regulator to reach. Regulators consistently reward legibility.
Does the EU AI Act apply to UK organisations?
Often, in effect, yes: if you place AI systems on the EU market or their outputs are used there, obligations can reach you. Treat the Act’s risk categories as design inputs now.
When do the EU AI Act obligations take effect?
In stages, and the stages have moved. Prohibitions and AI literacy duties already bite. The high-risk requirements were deferred substantially, and the deferral is itself subject to formal adoption, so confirm the current position rather than rely on a summary. What has not moved is the useful part: it is not the deadline that will hurt you. It is building the capability to comply without stopping, and that takes longer than an extension buys you.
How is the UK regulating AI?
Through existing sector regulators applying cross-cutting principles rather than a single act. Design for your sector regulator’s expectations.