ChallengeWhat goes wrongHow we help
Wrong, biased or manipulated output
AI can produce confident errors, treat people differently because of a name or background, or be steered by instructions hidden in a document it reads. Nobody notices until a customer or a regulator does.
We decide where a person must make the decision, test for bias and hidden instructions before release, and set up monitoring after it.
Unclear regulatory obligations
The EU AI Act, GDPR, DORA and sector rules can all apply to one use case. Firms often cannot say which apply, or what evidence each one expects.
We list your AI use cases, work out which rules apply to each, and set out the evidence you need to hold.
No owner and no approval route
Pilots start in business teams without a named owner, a risk sign-off or a policy. By the time risk is asked about, the system is already in use.
We write the AI policy, roles and approval process, and set up a register of AI use cases with an owner for each.
Dependence on AI providers
Most AI features run on a third party's model. That raises questions about contracts, data protection, concentration and exit. Under DORA, the provider is generally an ICT third-party service provider.
We assess providers against DORA's third-party requirements, review contract terms, and design systems so the model can be swapped.
Personal and confidential data
Documents sent to a model may contain personal data. Where it goes, who can see it and how long it is kept all have to be known and documented.
We map the data flows, advise on lawful basis and retention, and build systems that keep each customer's data in its own database.
Moving from pilot to production
Pilots run on clean examples. In production, costs, edge cases and failures appear, and there is no record of what the AI did or who approved the result.
We set spend limits, evaluation tests and monitoring before launch, and log each AI call and decision in an audit trail that cannot be edited.