AI Consulting
An advisory engagement that reviews the tasks you are considering AI for, judges what your data actually supports, and hands you a written, prioritised roadmap before any build begins.
What AI Consulting Covers
Before any assistant, bot or model gets built, this engagement looks at the specific tasks you are considering, the documents and systems available for each, and produces a plain judgement on what is feasible, what is risky, and what to leave alone.
What You Get From an Assessment
Feasibility Findings Per Task
Each candidate task is checked against the data and systems you actually have, not against what AI can do in general.
Risk and Data-Readiness Rating
A rating of how exposed the task is if the AI gets something wrong, and how ready your documents and records are to support it.
Prioritised Roadmap
A ranked order of what to build first, what to hold for later, and what is not worth pursuing at all.
Rough Scope for the First Project
Enough definition on the top-ranked task to move straight into a prototype or fixed-scope build.
How We Run the Engagement
Working Sessions With the People Doing the Task
We talk to the staff who actually handle the work today, not just the person requesting the project.
Review of the Documents and Data Available
We look at what you actually have to work with — messy, partial or scattered included.
Scoring Against Value, Feasibility and Risk
Every candidate task is scored on the same basis so the list can be compared fairly.
A Written Report With a Plain Recommendation
A document you can take to leadership or a budget conversation, stating clearly what we recommend and why.
When Consulting Makes Sense
- You are about to spend on AI without knowing which of several ideas is actually feasible.
- You have a shortlist — a chatbot, forecasting, document reading — and no way to rank them.
- An earlier AI attempt was shelved and nobody is sure whether it was the idea or the execution that failed.
- You need a written case to justify budget or leadership sign-off before committing.
When to Skip Straight to a Build
If you already know exactly what you want built and the data to support it is ready, go directly to a fixed-scope build instead — consulting exists for when the target task or the risk is not yet clear.
Frequently asked questions
Is this useful if we already have one clear idea?
Yes. Even a single idea benefits from being checked against your actual data and systems before you commit budget to building it.
What drives the cost of an assessment?
Mainly the number of candidate tasks reviewed and how many different teams or systems have to be examined to judge each one.
What drives how long an assessment takes?
How available the staff who do the work are for working sessions, and how scattered the current documentation is.
Do our systems need to be ready first?
No. This stage happens before any integration and works with what exists today, including incomplete or messy documentation.
Who owns the output?
The assessment report and roadmap belong to you outright, and you can take them to any vendor, including us.
What do we need from you for the sessions?
Access to the people who do the task day to day, and honest examples of how it actually goes, including the difficult ones.
Does this commit us to building anything?
No. A fair outcome of the assessment can be a recommendation to build nothing yet, or to build something other than what was first proposed.
Tell us what you need.
Send a short brief and one of our engineers will come back to you — usually the same day.
- No obligation
- We reply the same working day
- Your details stay private