Demonstration version · the deployed Keel is built for your environment
Find out what shape your AI programme should actually take.
Not whether to use AI. Whether one team should build it, whether business units should build their own, or something in between, and whether your organisation is actually ready to start either way.
This isn't a maturity score. It's a short conversation, the same questions we'd ask in the first week of standing up a governed AI function, scored against a fixed rule, then written up properly, not just handed back as a chart.
The centre that never lets go
Centralised was meant to be scaffolding while trust was being built. Eighteen months later it's a permanent department, and every team tired of waiting has built something of its own nobody in the centre can see.
Governance nobody enforces
Federated works if the light-touch centre is actually reviewing the highest-risk work. Without that, it isn't federated, it's just ungoverned with a nicer name.
The model that hides the real question
Hybrid looks like the safe middle option. Run without an explicit rule for which work goes where, it quietly becomes an excuse never to decide.
Three different failure modes, one shared cause: the operating model was never actually decided, just assumed.
What you'll come away with
- Whether to centralise, federate, or run hybrid, and why
- Where you're genuinely ready, and where you're not
- What a minimum viable team looks like for you
- What your risk gate should check on day one
- A concrete first ninety days
- A written report, not just a score
A short demonstration conversation, about five minutes. Then a short wait while your report is actually written, not templated. Please don't share anything genuinely confidential, this is a public assessment.
A demonstration, and what the deployed version does
This demonstration
Runs in your browser on what you tell it, in one short sitting. A free account lets you save your results and compare runs.
Deployed in your organisation
Connects to your intake, approval and delivery tooling, scores each use case against a fixed rule, checks that the gates were actually followed, and watches live use cases for drift and incidents. The operating model stays the same; which controls are switched on is configured to your regulator.
Already saved a readiness report? Sign in
First, the organisation.
This shapes the questions. It takes a few seconds.
Your report's being written.
No account and no password. Just your work email, so we can send you a copy and get in touch if useful.
Your Keel readiness report
Readiness, dimension by dimension
The full report
The formalised version
The free report tells you the shape and the reasoning. The formalised version makes it something you can actually hand to your team and start running.
- A specific RACI for your organisation, not a template
- Decision rights: what your CoE lead can approve alone, what needs sponsor sign-off
- The intake form and risk scoring sheet, structured for your answers
- A one-page version for your sponsor
The foundation, plus where to take it
This assessment tells you where to start. It doesn't tell you how to get from a centralised first year to whatever comes after, that's a conversation, built with you, not a report you read alone.
Keel gives a structured view based only on your answers, using a fixed scoring rule: the same answers always produce the same recommendation. The narrative report is generated from that score and your own evidence, and grounded to it, but it is not legal, financial or regulatory advice.
Loading…