What does an AI implementation cost? You know before we start.
There is no price list on this site, because no two implementations are alike. There is a rule: every service has a fixed scope, and the price is agreed before the work begins. This page sets out how that price is formed, what moves it, and how long each engagement runs.
Book a call (30 min) →Fixed scope, priced before the work starts.
Every service is contracted with a fixed scope. By the time an engagement begins you already know what is in the work, how long it runs and what you hold at the end. No scope creep, and no open-ended engagement billed as it goes.
If a new opportunity turns up during the work — and it usually does — it goes into the next engagement, with its own scope and its own price. Not as a line on an invoice you were not expecting.
So you can size the commitment before we even speak. The duration of each service is known in advance:
Diagnose · 2–3 weeks
Fixed scope, and the only engagement that pays for itself without a sequel — the output is a number about your own business, usable without us.
Design · 1 week
Fixed scope. Build-versus-buy recommendation, technical feasibility assessment and a prioritised implementation roadmap.
Delivery Sprint · 2–4 weeks
Fixed scope, one clearly defined result. For companies that have already finished Diagnose and Design — with us or elsewhere.
Pilot · six weeks
Fixed scope. All three Ds on one process, measured against a success criterion written down in advance.
Deliver · variable scope
Scope depends on what Design defined. It is still agreed before work starts, but it is not measured on the same yardstick as the others.
3D Bundle
Diagnose, Design and Deliver as one engagement. One scope, one team, one outcome — without three separate decisions.
What actually moves the price.
Price depends on the volume of work, and the volume of work cannot be guessed from a single call. That is exactly why Diagnose exists as a separate engagement: it measures the scope before the larger job is ordered.
Three things move the figure most: how many processes are in scope, how many systems need connecting, and where the solution runs after handover.
Number of processes
Pilot covers one process — the one with the biggest effect. The 3D Bundle covers whatever the diagnostic identifies as priority, which is a wider scope and a different figure.
Number of systems
Every integration is its own piece of work: ERP, CRM, helpdesk, file shares, spreadsheets. The systems map from Diagnose shows how many there really are, rather than how many get mentioned in a meeting.
How it is delivered
Through tools you already pay for, on Integral in our cloud, or on your own infrastructure. Integral carries a platform subscription; through existing tools there is no new vendor and no new infrastructure.
Support after handover
An optional monthly retainer: a monthly strategy call, minor adjustments and priority support. Without it the handover is clean and the engagement ends.
A budget is defended with a field number, not a meeting estimate.
A figure for AI is hard to defend if nobody knows what the current way of working costs. That is why the first engagement measures rather than builds.
Diagnose is therefore the only engagement worth commissioning even if you do nothing afterwards: its result is a number about your own business, and that number stays true regardless of who implements it next.
Only then does the comparison mean anything: the cost of the engagement on one side, the estimated saving on the other. If the numbers do not stand up, you see it before anything is built — there is no obligation to continue after Diagnose.
Pilot: the success criterion is written down first.
On any proposal, someone on your side carries the risk that it does not pay off. On Pilot we share that risk: the success criterion is written down before the work begins, and if it is missed, the design and delivery fee comes back in full.
That changes the question you answer to your board. It is no longer what it costs, but what it costs if it fails — and to that part, the answer is nothing.
Which changes the real question too. It is no longer “what does AI cost”, but “does it work here” — and you do not pay for that answer if it turns out to be no.
The second cost: monthly model usage.
Implementation is not the only cost. The second is monthly AI model usage, and it is where companies are most often surprised, because usage is billed by consumption and consumption rises once the system is actually being used.
Through tools you already pay for, you stay on your existing subscription. On Integral the tokens are yours, with spend caps — which matters because this cost, unlike the implementation, is not agreed once but recurs every month.
Frequently asked.
- What does an AI implementation cost?
- There is no single price, because there is no single scope. Every service is contracted with a fixed scope and a price known before work starts, and the figure depends on how many processes and systems are in the work and where the solution runs after handover. The fastest way to get a concrete figure is to describe the process costing you most — the proposal is written to that scope.
- Why is there no price list on the site?
- Because any number here would be either wrong or useless. A company with one process and two systems and a company with five processes and an ERP that does not open to the outside cannot carry the same price. Instead of a price list we publish how the price is formed and how long each engagement runs, so you can size the commitment before we speak.
- Is it billed hourly or fixed?
- Fixed. Diagnose, Design, Pilot and the Delivery Sprint have fixed scope and a price agreed before work begins. Deliver has a variable scope because it depends on what Design defined, but it too is agreed before the work, not opened as an engagement without an end.
- What if the pilot fails?
- Then you do not pay for design and delivery — it comes back in full. The criterion is written down before the work starts precisely so that there is no argument about the outcome afterwards. The risk of the first step sits on our side.
- Are there monthly costs after the implementation?
- It depends on how it is delivered. If the system runs through AI tools you already pay for, you stay on your existing subscription; if it runs on Integral — in our cloud or on your infrastructure — there is a platform subscription covering maintenance, upgrades and support. Model usage is yours in either case, with token budgets and spend limits per user, per team or across the company.
- How long until we see a result?
- Diagnose runs 2 to 3 weeks, Design one, and the Delivery Sprint 2 to 4 weeks. Pilot, which runs all three phases on a single process, takes six weeks — the shortest route to a system working on your own data.
Start here
The price is written to a specific scope.
Describe the process costing you most and name the systems it passes through — ERP, CRM, helpdesk, spreadsheets. That is enough for us to propose a scope and give a fixed price before any work starts. If we can see from the description that it is not worth it for you, we will say so before the proposal rather than after it.
Book a call (30 min) →or write to ai@meteorit.rs