Book an intro callIntro call
What does AI cost for retyped orders, inventory and planning?
Retyping orders, a spreadsheet next to the ERP, a planning that lives in one head: the price of a first project depends on how many systems it touches and how clean the data is. At a wholesaler, nobody retypes over 3,300 of 5,017 order emails anymore. The price is fixed after the Data Impact Scan, and a proposal only comes when the saving clearly outweighs it.
- 2 out of 3Order emails at a wholesaler nobody retypes anymore
- FixedPrice, after the Data Impact Scan
- 36-50%Back via WBSO on development
- FreeFeasibility study upfront
Put the company's own situation in first.
The range hangs on two things: how many systems this touches and how clean the data is. Answer those two and the amount moves with them. Want the reasoning in writing? Leave an email under the calculation.
What does this cost in your situation?
Three questions. The range comes straight from our experience figures.
One-off, fixed price
€ 19.000 - € 29.000
Then roughly € 200 - € 600 per month for hosting and monitoring.
How is the data doing?
Calculated with our experience figures: €15,000-€40,000 for a first scoped project, €50,000-€150,000 across multiple systems, and 36-50% WBSO on the development part. The monthly figure follows the 'a few hundred euros a month' for hosting and model usage and scales with the number of systems. The fixed price comes out of the free feasibility study.
Sound familiar?
One quote for a trial, another for something that runs
One party quotes a trial on sample data and another a system that runs inside the ERP, without saying so. That is why quotes differ by a factor of ten.
The price is clear, what it returns is not
A number without a return is just a cost. What decides it is what this saves per year in hours and errors, and whether that survives daily practice.
The real bill arrives after go-live
Hosting, upkeep and the person who keeps it running. A quote that stops at delivery hides what comes back every month afterwards.
Rather talk it through right away?
No sales team reading from a rate card. In 30 minutes we go through the case and you leave with the reasoning behind the price, and a straight answer on whether the return justifies it. That answer is free even when it is no.
The Data Impact Scan
Curious what this looks like on your data?
Book an intro call with the solution architect who also builds the work. You walk through your processes together and get an honest answer on where the numbers are for you, and where they are not.
30 minutes, no obligation, directly with the builder.
How it works, without risk
- 01
1. Thirty minutes on this case
We go through the process, the data that exists, and what it would be worth if it worked. Out of that comes a reasoned view of what drives the price, not a number pulled from a price list.
- 02
2. Feasibility on the company's own data, free
Before anything is invoiced we test the assumption on a share of the real data. That is what leads to a fixed price, and occasionally to the advice not to start. If there is nothing to gain, there is no proposal.
- 03
3. Fixed price, including what comes after
The quote covers build, integration and the running costs, so the monthly bill after go-live is not a surprise. WBSO can take 36-50% off the development part.
Where the money actually goes
| Trial | System that runs | What we quote | |
|---|---|---|---|
| The calculation itself | Most of the budget | Roughly a fifth | Priced as one line |
| Data and integrations | Skipped | Most of the budget | Scoped before pricing |
| Upkeep and alerts | None | Monthly, ongoing | Named upfront, not hidden |
| Ends up in daily use | Rarely | That is the point | Fixed price to live |
Before the call
What does a first AI project cost?
The price of a scoped first project, from feasibility check to a working solution in the existing systems, is fixed after the Data Impact Scan. What moves it is how clean the data is and how many systems have to be touched, not the model. A larger implementation across multiple processes is scoped the same way, and a proposal only comes when the saving in hours and errors clearly outweighs the price.
What does it cost per month after go-live?
For a typical project, hosting and running costs are small next to the build, and upkeep can sit on a small maintenance arrangement. We put those running costs in the quote, because a build price without running costs is not a real price.
Why do quotes differ by a factor of ten?
Because they are quoting different things. A trial on sample data is genuinely cheap and genuinely useless in daily work. A system that runs every day, handles bad input, logs what it did and sits inside the existing software is a different piece of work. Ask each party which of the two they are pricing.
How much of our time does this take?
The call takes 30 minutes. After that we ask for two years of history of the process; we handle the rest. The team does not have to run a project alongside its work.
Our data is messy. Does that change the price?
It can, and that is why we look at it first. The Data Impact Scan shows what is usable and what needs cleaning, and that goes into the price before anything is built. If the data is not ready, we say so.
Can subsidy bring the cost down?
Usually yes. WBSO reimburses 36-50% of the development labour and MIT covers 35% of the broader project costs. That does not make a bad project good, but it does shorten the payback on a sound one. We can file both applications alongside the build.
How do we know it will return more than it costs?
We put a number on it before anything is spent: how many hours the current process burns, and what share of that realistically disappears. If that calculation does not comfortably clear the project cost, our advice is to leave it, and there is no proposal. We would rather say that in the first call than in month four.