Adoption and strategy
An AI readiness checklist for firms of 5 to 250 people
You do not need to be AI-ready in the abstract. You need to be ready for one workflow. This honest checklist covers the four things that actually matter: data, governance, skills, and a use case worth building.
By Seb Lawson · 10 February 2026 · 4 min read
You do not need to be ready for AI in general. You need to be ready for one specific workflow, and that is a far smaller test. The firms that stall are usually waiting to be ready for everything. The firms that move check four things against one use case, find they are more ready than they feared, and start. This is that checklist, written to be honest rather than reassuring.
Treat it as a diagnostic, not a gate. You do not need every box ticked before you begin. You need to know which boxes are empty, because the empty ones tell you what to fix first and what to keep a human in front of while you fix it.
Data: can the system get to what it needs
AI is only as good as what you can feed it. You do not need a data lake. You need the specific inputs for your first workflow to be reachable and reasonably consistent.
- The documents or records the workflow needs live somewhere a system can reach, not only in someone’s head or a paper file.
- The inputs are consistent enough to work with. Messy is fine. Genuinely unpredictable, with no pattern, is a problem to solve before you automate.
- You know where that data may and may not go, especially anything that would leave the island or a controlled environment. Our note on data protection under UK GDPR and Jersey law covers the lines that matter.
- You can get to the data without breaching a contract or a client confidentiality term. Check before you connect, not after.
Governance: can you show your working
For a regulated firm this is the section that decides whether a pilot ever becomes a system. None of it is heavy. All of it has to exist.
- One senior person is willing to put their name against AI adoption, with the authority to stop a system going live.
- You have, or can build in a day, a simple register of what AI is already in use across the firm. Most firms find more than they expected once they look.
- You can sort a use case into low, medium, or high stakes by what a wrong output could reach, and match the oversight to the tier.
- You accept that every material AI decision needs a record: the input, the model and prompt version, the output, and who approved it. Our AI governance framework sets out the whole spine, and it is lighter than you think.
Skills: enough to govern, not to build
You do not need engineers on staff. You need enough understanding to make good decisions and keep an honest hand on the wheel.
- At least one person accountable actually understands what the technology can and cannot do. ‘The vendor said it was fine’ is not a control.
- The people who will use the workflow are willing to try it and honest enough to say when it is wrong.
- Someone will own the system after go-live, because a system nobody tends drifts and breaks. If that owner is not on your staff, we can be that hand for you.
- Your team knows the difference between a system that assists a human and one that decides on its own, and knows which one they are being handed.
One good use case: the box that matters most
You can have every other box ticked and go nowhere without this one. A good first use case is frequent, rule-bound, and forgiving of the occasional error because a human checks it before it counts. It is small enough to finish in weeks and painful enough that people will actually use it. If you cannot name one, that is your first piece of work, and it is a conversation, not a project.
- It happens weekly or more often, so small savings add up to a real number.
- You can describe the logic in a couple of sentences a new joiner could follow.
- A wrong output is caught by a human before it reaches a client, a payment, or a regulatory return.
- You can put a pound figure on what it costs you today. If you cannot, it is not your first case yet.
Reading your score
If most of the data and use-case boxes are ticked and the governance ones are thin, you are ready to start and should build the governance alongside the first workflow, not before it. If the data is not reachable or you cannot name a use case, fix that first, and it is usually a fortnight of work, not a transformation programme. Perfect readiness is a myth. Enough readiness for one workflow is a Tuesday.
If you want the checklist run properly against your firm, book a review and we will tell you honestly which boxes are empty and which one to fill first.