Software
AI consulting
An engineering assessment of what is worth building, what is not, and what it would take — before you commit a budget to it.
What this is
The work, described plainly
The most useful thing we can tell some clients is that the project they came for is not worth doing. That answer is cheap to get now and expensive to discover in month four.
A consulting engagement looks at your processes, your data, and your systems, and returns a written assessment: what could be automated or improved, what the prerequisites are, roughly what each would take, and which ones we would do first.
It is deliberately separable from the build. You can take the assessment to any competent team, and you should feel free to. An assessment written to justify a build we have already scoped is worth nothing.
What you get
What is actually handed over
Concrete deliverables, not phases on a timeline.
Process and data review
What you run, what you record, and what state it is in — assessed rather than assumed.
Opportunity assessment
Candidate projects with prerequisites, rough effort, and the honest cases against each one.
Recommended sequence
What to do first, and what depends on something else being in place.
Written report
Yours to keep and to take elsewhere, with no obligation to build with us.
Is this you
Signals this is the right fit
- You are being sold AI and cannot evaluate the claims.
- You have a budget and competing internal opinions about where it goes.
- A previous AI project did not deliver and nobody agrees why.
- You want to know if your data is ready before committing.
Typical stack
Chosen per project against your constraints, not applied by default. This is what the work usually involves.
- Process mapping
- Data quality assessment
- Architecture review
- Build-versus-buy analysis
- Written reporting
FAQ
Questions people actually ask
Will you recommend doing nothing?
When that is the honest answer, yes. Several processes are cheaper to fix with a form and a rule than with a model, and we would rather say so than sell a build.
Do we have to build with you afterwards?
No. The report is written to be useful to any competent engineering team, and that is deliberate.
How long does an assessment take?
It depends on how many processes are in scope and how accessible your data is. We agree the scope and the timeline before starting rather than quoting a number that fits every engagement.
Related
Work that usually comes with this
Start here
Tell us what is slow, manual, or breaking.
Answer a few questions and get a written brief back — scope, proposed architecture, and what it would take to build.