These are honest starting figures, not anchors designed to make a quote feel reasonable. Every project is scoped properly before a price is agreed, and if the scope should be smaller than you asked for, we will tell you that instead.
For organisations who know something is wrong but not what to build. We work through the data you hold, what a model could realistically add, and what it would cost to run.
Design and build, delivered in reviewable increments, handed over with the documentation and tests to run it yourself. The engagement most clients end up in.
Our engineers work inside your team, on your roadmap, using your tooling, for the period you need the capability rather than the headcount.
Ongoing maintenance, monitoring, model retraining and enhancement for systems we built or inherited, under a plain agreement with no lock-in.
All figures exclude VAT. Prices are indicative starting points for UK engagements and are confirmed in writing before any work begins.
Rough, deliberately. It uses the same drivers we use when scoping, so it will get you inside the right order of magnitude before you speak to anyone.
This is a sketch, not a quote. A real figure comes after a discovery sprint, and it is put in writing.
If you want a rough figure before speaking to us, these are what to think about. Data quality dominates everything else.
The single biggest driver. Clean, labelled, accessible data can halve a project. Data that needs collecting, cleaning or labelling can double it.
Rules, a better report or a fixed integration solve more problems than people expect, at a fraction of the cost. We check this before quoting a model.
One system is straightforward. Six systems, two of them undocumented and one of them owned by a supplier who will not answer email, is the expensive version.
Audit trails, data residency, accessibility conformance and information governance review are real engineering, and we price them as such rather than pretending they are free.
Building for your team to maintain costs more up front than building for us to maintain. It is usually the cheaper decision over three years.
Not because we are virtuous, but because each one costs the client more than it saves.
The engineers named in a proposal are the engineers who do the work. If that has to change, we tell you before it happens.
Scope changes are re-agreed in writing before the work happens. Nothing arrives on an invoice you have not already seen.
Handover documentation is written so another supplier could take the system over. That is the only real test of whether you are free to leave.
Describe the decision you are trying to improve and what data you hold. We will come back with a scope and a figure, or an honest reason not to proceed.