State of the data
The biggest cost driver. If the data is collected, labelled and kept in one place, work starts at once. If it is spread across systems, duplicated and contradictory, preparing it takes more work than the model itself.
Cost · Estimate · Payback
The cost of implementing AI depends mostly on the state of your data and the number of systems that have to be connected. The technology matters less. Below: what the budget is made of, what drives it up and how to work out the payback before the project starts.
For people who work out the economics of a decision: executives, finance and technology directors who need to defend a budget with figures.
The same request, “add AI to request processing”, can mean a small job on clean data or a large project across five systems. One price for both would be wrong for at least one of them. So we show the whole cost structure, letting you judge your own case, and name a range after a short diagnostic.
The biggest cost driver. If the data is collected, labelled and kept in one place, work starts at once. If it is spread across systems, duplicated and contradictory, preparing it takes more work than the model itself.
One system with one connection point is one scenario. Five systems with different formats, access rights and failure modes are another. Integrations, more than the model, usually set the scope and the budget.
External models are cheaper to build with, but your data leaves the perimeter. Local deployment keeps it inside and adds infrastructure, hardware requirements and the work of fitting a model to the task.
The more a wrong decision costs, the more checking it needs: test sets, metrics, human confirmation, an action log. That is why an internal assistant and a system that touches a client’s money cost different amounts.
A hundred documents a day and a hundred thousand need different architectures. At high volume you add queues, caching, model-call economics and response-time limits.
AI systems have a running cost: model calls or your own servers, quality monitoring, reacting when model behaviour changes. We put it into the calculation from the start, so it does not surface after launch.
We look at the process and the data, pick scenarios with a calculated effect and give a conclusion: what AI really solves, what plain automation solves more cheaply, and what cannot be solved for now. You get a cost range for the pilot and a payback estimate. The scope is fixed.
A working solution on a limited part of the process, with the metric agreed before the start. The pilot tests a hypothesis on real data and gives you a number to decide whether to go on. Priced by the size of the scenario and the number of integrations.
Integration into your working systems, load, access rights, observability, support and further development. This is where the running cost appears: maintenance and model calls. We work as a project or as a dedicated team, depending on whether you plan to take the system in-house.
We make this calculation during the diagnostic, and you can make it yourself before talking to any contractor. You need four figures from your process:
The monthly saving is the volume times the cost per operation times the share handed over, minus the running cost. The payback period is the project budget divided by that saving. If payback comes out longer than a year, the project usually should not start in that form: narrow the scenario to the part with the most volume and calculate again.
During the diagnostic we do this calculation with you and show all of it, including the assumptions under which it stops holding.
The method in detail, with the typical mistakes that inflate the result several times over, is in the article “How to calculate the ROI of AI implementation”.
AVA calculator: your figures, no form, no price from us.
Because the same request can mean very different amounts of work. “Automate request processing” can be a small scenario on clean data or a large project across five systems. We name a range after a short conversation and confirm it after the diagnostic, before you spend the budget.
It depends on the scenario: how many process steps it covers, how many systems it touches and how much quality checking it needs. We try to narrow a pilot to one testable claim. That makes it cheaper and more useful than trying everything at once.
Yes, for the diagnostic and for a pilot with a clearly bounded scope. That is normal practice. A production budget cannot honestly be fixed before the diagnostic: any such figure would be either a padded safety margin or a promise that would have to be broken.
For most business tasks, a ready-made model with your data and rules is cheaper. Training your own model makes sense when the task is narrow, there is a lot of data and the work must run on-premise. We cost both options during the diagnostic and compare the total cost of ownership, including operation.
Two parts: infrastructure and model calls, priced by volume, and engineers’ time on quality control. Model behaviour changes, and a system nobody watches degrades without anyone noticing, so we build that monitoring into the calculation from the start.
Then we say so and explain how to solve the problem more cheaply. It is a common outcome, and it keeps you from spending on a project that would not pay off.
Describe the process in two paragraphs: what happens now and what gets in the way. We will reply with a rough cost estimate and tell you if the problem can be solved more cheaply without AI.