Enterprise · Step 1
Know where AI pays off before you fund it.
In two to four weeks we score where you stand, rank the opportunities by value and risk, and hand you a costed roadmap with the first project already scoped. One fixed fee, one clear decision at the end.
- Duration
- 2–4 weeks
- Commercials
- Fixed scope, fixed fee
- Led by
- Our senior AI architects
- Your team’s time
- A few hours a week, mostly async
Is this you?
This is the right start if…
- Leadership has asked for “an AI strategy” and you have a list of ideas, not a ranked plan.
- Pilots have run, demos looked good, and nothing has reached production.
- Legal, risk or security will ask hard questions and you want the answers written down first.
- You need a number and a timeline to take to a budget meeting.
- Different teams are buying AI tools on their own and nobody owns the whole picture.
What you get
What you hold at the end
Four documents, written for the people who have to approve and build the work. Yours to keep, whether or not you continue with us.
Current-state and readiness scoring
Where your data, systems, people and governance stand today, scored against what production AI needs. Gaps are named with an owner, not buried in an appendix.
A ranked opportunity list
Each candidate use case scored for business value, feasibility with your data, and risk. You see why number one is number one, and why some popular ideas are at the bottom.
A costed roadmap
Sequenced work with effort, cost ranges and dependencies, in a form a steering committee can read in ten minutes.
A scoped first project
One first win, defined tightly enough to start: what it does, what data it uses, how success is measured, and what it will not do.
How it works
How the weeks run
Designed to cost your team as little time as possible. Most of the intake is asynchronous.
Before day 1
Scoping call and paperwork
We agree the business areas in scope, who we need to speak to, and the confidentiality terms. You get a written scope and a fixed fee.
Week 1
Intake and interviews
Short conversations with the people who run the workflows, plus a review of the systems and data behind them. We ask for read access or samples only where it is needed.
Weeks 2–3
Scoring and options
We score readiness, size each opportunity, and test the top candidates against your real constraints: data quality, privacy rules, integration effort.
Final week
Roadmap and readout
A working session with your sponsors to walk the roadmap, pressure-test the first project, and agree what happens next.
Clear boundaries
What is and isn’t in an assessment
Included
- Stakeholder interviews across the agreed business areas
- Review of the relevant systems, data sources and existing AI tools
- Readiness scoring for data, technology, people and governance
- Opportunity ranking with value, feasibility and risk
- Costed, sequenced roadmap and an executive readout
- A written scope for the first project
Not included
- Building or deploying software (that is the Sprint)
- A security audit or a compliance certification
- Legal advice on AI regulation
- Vendor selection on commission: we take none
An assessment is our judgment at a point in time, based on what we were shown. It is not a guarantee of results.
Questions
What people ask us first
How much of our team’s time does it take?
Plan for a sponsor at about two hours a week and 45-minute conversations with five to ten people who run the workflows in scope. The rest is our time. Intake questionnaires and document review are asynchronous.
Do you need access to production data?
Usually not. Schemas, samples and a walkthrough are enough to judge feasibility. Where real data matters, we work inside your environment under your access rules, with confidentiality terms agreed first.
What if the honest answer is “not yet”?
Then the roadmap says so, and lists what has to be true first: usually data access, ownership or a governance decision. Knowing what to fix before you fund a build is a useful result in its own right.
Are we committed to building with you afterwards?
No. The roadmap and the first-project scope are written so that your own team or another vendor could execute them. If you do continue into a Sprint, the scope is already agreed and no rediscovery is needed.
How is this different from a strategy deck from a large consultancy?
It is written by the people who would build it. Every item on the roadmap has been checked against your actual data and systems, and the first project is scoped to a level an engineering team can start from.
Next step
Scope an assessment
Tell us the business area and what prompted the question. We aim to reply within one business day with whether an assessment fits, and what it would cover.
