Process and value
Define the task, its volume, current effort, exception rate and business owner. Establish what a meaningful improvement would look like.
Before you invest in AI.
Know where you stand.
An AI readiness assessment turns an interesting idea into a decision with evidence behind it. We examine the process, information, systems and people involved, then show you what is ready, what needs work and what to test first.
Discuss a readiness review- A focused evidence review
- Dependencies made visible
- A practical pilot brief
The right time to discover a blocker is before the build.
A convincing demo may use clean documents and a straightforward task. Your actual business might have incomplete records, restricted supplier access and no clear owner for the process. Those differences can change the effort and value of a project.
Our assessment starts with one proposed use case or an agreed group of workflows. We review evidence with your team and distinguish facts from assumptions. The output is an actionable gap analysis and a decision about the next step, including the option to improve the process before adding AI.
Look at the whole job, before choosing a tool.
Data and knowledge
Inspect representative sources for quality, completeness, ownership and permitted use. Identify what is missing or out of date.
Systems and access
Check integration methods, identity, supplier restrictions and the practical route from a pilot to a maintained system.
People and operating model
Review who will use, check and support the system, what training they need and what happens when the output is wrong.
A knowledge assistant, assessed before it is commissioned.
The starting point
A team wants to search all company documents but has not agreed which are authoritative or who should be able to see them.
A better way forward
The review identifies a suitable first collection, access gaps and document owners. A limited pilot can be priced and evaluated against specific questions.
- 1
Gather evidence
Review sample documents and the questions people need to answer.
- 2
Resolve dependencies
Assign ownership and identify permission or content changes needed first.
- 3
Define the decision
Agree the pilot boundary and the evidence that would justify further investment.
An illustrative engagement. We agree the actual scope, access and success measures with your business.
Something useful.
Yours to put to work.
The engagement has a clear scope and a tangible handover. We agree the deliverables before work starts.
Discuss the scopeA readiness findings report
Observed strengths, gaps and open questions across the agreed assessment areas.
A prioritised action list
Specific preparation work with suggested owners, dependencies and the reason each item matters.
A scoped experiment
A pilot brief covering inputs, access, evaluation cases and a stop-or-continue decision.
A decision workshop
A walkthrough with the people responsible for investment, delivery and day-to-day use.
How we work with you.
Agree the question
Define the decision the assessment must support and the evidence available.
Review the reality
Talk to process owners and inspect representative systems and information.
Identify the gaps
Separate blockers, manageable constraints and assumptions that need testing.
Plan a first step
Choose preparation work, a pilot or a different approach, with explicit reasons.
A few things
you might be wondering.
Questions about your own setup?
Let’s talk it through
What is included in an AI readiness assessment?
The scope normally covers process suitability, data quality and ownership, systems access, staff capability and the operating model for a proposed use case. We agree the evidence and deliverables before the assessment starts.
How is it different from an AI strategy?
A readiness assessment tests whether particular ideas are feasible and what needs preparing. A broader AI strategy compares opportunities across the business and sets an investment direction. The assessment can be a first stage of that work.
Do we need a large dataset?
Not every AI project needs one. An internal assistant may depend on a small, well-maintained document collection. A prediction project has different data requirements. We assess the information needed for the specific task.
What should we prepare for the review?
Bring a description of the work, representative inputs and outputs, the tools involved and the people who know the exceptions. We agree how to handle access and avoid collecting information that is not needed for the review.
Is the readiness checklist a formal audit?
No. Our online checklist is a self-assessment to structure your thinking. A commissioned review examines evidence and constraints with your team. Neither is a certification or a guarantee that a project will succeed.
Will we be committed to a build afterwards?
No. The assessment should support your decision. You can act on the preparation work, commission a pilot, use the brief with an existing supplier or decide that the proposed application is not worthwhile.
A little clarity before the next step.
A clearer decision starts with the right questions.
Tell us what you’re working on. We’ll help you find a practical next step.
Discuss a readiness review