An inventory of your team’s tools
Document the tools your team shares, the systems they connect to, and the people responsible for them. Identify where the information is incomplete.
AI governance consultancy
An internal tool that started as an experiment is now handling company data or shaping daily decisions. We help you review how it works and agree who maintains it. Start with one tool and a clear decision about what needs attention.
Discuss a tool reviewWhat does AI governance involve for internal tools?
It means agreeing who owns a tool, what information it may use, and what needs checking before people rely on it. We review the software and the way your team builds and runs it, then help put suitable controls in place. The scope covers applications built with AI, workflows that use AI, and agents connected to business systems.
What we work towards.
Findings with owners and next steps
Get a written review of selected workflows, with the issues prioritised and an owner for each next step. Keep the findings with the tool’s documentation.
Working rules your team can follow
Set out when people can experiment, when a tool needs review, and how it becomes supported software. Apply those rules to the team's actual tools and release process.
A good fit when...
- Colleagues are building applications or automations, and nobody has a complete picture of what is in use.
- An internal tool has started handling company data or become part of everyday work.
- You need a practical review process for new tools, including those built outside the engineering team.
- An AI agent can change records or take actions, and its permissions need a closer look.
Related reading and services
Before we begin.
Can we start with something we have already built?
Yes. We can start by reviewing one tool with the people who build and use it. We agree the scope first, then provide written findings and next steps. The review can identify changes needed before the tool is shared more widely.
Does this cover software that was built with AI but does not use AI itself?
Yes. That software still needs appropriate access controls, testing, and someone responsible for maintenance. If a tool also uses an AI model while running, we review its outputs and the actions it can take.
How is this different from AI rollout consultancy?
AI rollout consultancy helps you choose a use case and introduce it through a focused pilot. Governance consultancy helps you oversee the tools people are building and using, including experiments that have already become part of the business.
Does a review certify that a tool is secure or legally compliant?
A review produces findings and practical next steps. It does not provide certification. We agree where specialist security testing, privacy advice, or legal assessment is needed with your team.
What’s your
next move?
Tell me what you want to build or improve.
A short description is enough to start.