Home / Services / Pricing
Pricing for AI consulting and development

Fixed AI prices, and a production-ready MVP for €20,000.

Three steps, each scoped and priced in writing before work starts. You keep the code, each step builds on the last, and the same senior engineer stays from scope to handover.

What you get at each step

Three steps, three fixed prices, each one building on the last: an AI Audit & Strategy at €2,500, a Production-ready MVP at €20,000 and a Production Launch from €50,000, all excl. VAT.

  1. 01
    1–2 weeks · €2,500

    AI Audit & Strategy

    Where AI pays off in your workflows, what to build first, and a fixed price for that first build.

    Your roadmap, with the first build priced
  2. 02
    4–6 weeks · €20,000

    Production-ready MVP

    The first version of the workflows that matter most in your case, running on your own data, used by your team and judged against numbers we agree before we start. Built to stay.

    Your first workflow live, with production priced
  3. 03
    from 8–12 weeks · from €50,000

    Production Launch

    That workflow wired into your ERP, CRM or warehouse system, with roles, monitoring, documentation and training.

    Your system, with a support period

Go on to the MVP within 60 days and the €2,500 audit fee is credited in full. Every step leaves you with something you keep: first the roadmap, then the software.

Three steps, three fixed prices

What each step delivers, and what it costs

AI Audit & Strategy

Where AI pays off in your business, what to build first, and what it will return. Including the cases where a setting in a system you already own does the job.

€2,500
fixed price · excl. VAT
1–2 weeks
  • Review of your workflows, data and systems under a mutual NDA
  • A ranked shortlist of use cases, each with a feasibility and ROI estimate
  • Every candidate checked against its EU AI Act risk tier and GDPR before it is recommended
  • A build-or-buy call per case, including when a setting in a system you already own is enough
  • A written roadmap with a fixed price for the next step, yours to keep

Production Launch

The MVP rolled out as the system your business depends on every day. Each workflow after it is scoped and priced before it is built.

from €50,000
priced per scope · excl. VAT
from 8–12 weeks
  • Robust connections to your ERP, CRM, warehouse system and internal tools through documented APIs
  • Deployed in your own cloud or on-premise, with monitoring, logging, alerts and rollback
  • Roles and access control, data handling and EU AI Act / GDPR alignment built into the rollout
  • Documentation, a runbook and training for the people who will run it
  • A post-launch monitoring and support period as standard; ongoing operation is a separate fixed agreement
  • Further workflows added per scope, at a fixed price
Every step includes Scope and price fixed in writing before work startsOne named senior engineer from scoping to handoverEverything produced is yours: the roadmap, and for a build the source code, models, prompts and test setEvery step checked against GDPR and the EU AI Act

How it runs

Four steps, the same on every engagement. This is what sits behind the numbers above.

  1. Two people discussing notes across a table
    Scope

    We scope it before we price it

    A call and a short written scope that names the process, the systems it touches and what done means. The fixed price comes after that conversation, because a price before scope is a guess with a number on it.

  2. Developer writing code at a two-monitor desk
    Build

    Senior engineers, no handover to juniors

    The person who scoped the work builds it, against your own systems and data rather than a demo environment. Weekly contact means you see it working during the build, not only at handover.

  3. Colleague showing work on a laptop to a coworker
    Handover

    Delivered running, with the keys

    You get the code, the documentation and the accounts. No lock-in clause, no proprietary layer you have to keep paying to read your own data through.

  4. Support engineer with a headset monitoring screens
    Support

    Support priced as plainly as the build

    Monitoring, model updates and a named person when something breaks, at a fixed monthly figure agreed in writing before launch. The number in that agreement is the number on the invoice.

What happens after you request a proposal
  1. 01
    A written proposal within one business day

    Scope, fixed price and dates for your case, from Tom Joseph: the document you can put in front of procurement.

  2. 02
    A readout with your decision-maker in the room

    We walk the plan through with whoever signs off, so the scope and the boundary are understood by the people who will judge the result.

  3. 03
    You approve one step at a time

    Each step is a separate fixed-price agreement. Approve the audit on its own, and decide on the build with the roadmap and its price on the table.

Every figure on this page in one shareable overview, free to reuse with attribution: download the AI cost benchmark 2026 (PNG)

Request a proposal

Describe the workflow that costs you the most hours

You are requesting: a written proposal for the right first step
Side by side

What you sign for at each step

Production-ready describes the build: real data, a number it has to reach, code you keep. The Production Launch is the rollout: the systems it is wired into, the people who depend on it, and how it is kept running every day. The usual route is the audit first and then the build; if the workflow is already chosen, you can request the MVP proposal directly.

What you sign forAI Audit & StrategyProduction-ready MVPProduction Launch
Price (excl. VAT)€2,500€20,000from €50,000
Duration1–2 weeks4–6 weeksfrom 8–12 weeks
How it is pricedfixedfixedper scope, in writing
Scopethe workflows you put forwardthe workflows scoped for your case, on their source systemsfull system, per scope
Working software on your own data
Acceptance metric agreed before work starts, result measured
Used by your team during the engagementin parallel with the current process, or a test-set run
Connected to your other systemsthe source systems the workflows draw fromERP, CRM, warehouse, as scoped
Roles, monitoring, logging, alerts, rollback
Documentation, runbook and team trainingthe roadmapcode, prompts and test set
Post-launch support period
Everything produced is yours at handover
€2,500 audit fee credited against this step (within 60 days)
Choosing a step

Which step fits where you are

“We know something here should be automated. We do not know what first.”

Commission the AI Audit & Strategy. In one to two weeks you have a ranked shortlist with a return estimate per use case, a check against the EU AI Act and GDPR per idea, and a fixed price for the first build. If a setting in a system you already own does the job, the audit says so and saves you the build; that answer is worth the same €2,500. Go on to the Production-ready MVP within 60 days and the fee is credited in full.

“We know the workflows. We want working software, not a study.”

Commission the Production-ready MVP. Skip the audit; we confirm scope and data access, then build the first version of those workflows in four to six weeks on your own data. You judge it on the number agreed before we started, and everything built is transferred to you, whatever you decide.

“It runs. Now the business has to be able to depend on it.”

That is the Production Launch. We make the connections to your ERP, CRM or warehouse system robust, add roles, monitoring, logging, alerts and rollback, document it, train the people who will run it, and deploy it in your own cloud or on-premise. Scope and price are set before the build starts, from €50,000.

Procurement questions

What a buyer needs to know before signing

Is the €20,000 Production-ready MVP a proof of concept or working software?

Working software. At the end of the step the first version of your key workflows runs on your own data, your team has used it alongside the current process or it has been measured against a test set your own experts write, and the code, model, prompts and test set are yours. Production-ready describes the build: it is written to be kept and extended when it goes live. It is also not the clickable prototype we show on the second call; that one shapes the scope, this one is the fixed-price build. The Production Launch adds the rollout: roles and access control, integrations with your systems of record, monitoring, logging, alerts and rollback, documentation, a runbook, training and a post-launch support period. Your key workflows, ready for production, are the MVP. The business depending on it every day is the launch.

How is acceptance defined and measured?

The acceptance metric and the baseline it is measured against are agreed before work starts, so the criterion exists before the software does: accuracy against a test set your own experts write, hours saved against the current manual process, or an error rate against the old way. At the end of the build the measured result is reported in writing and walked through with you. What you accept is a number against a number, not an impression from a demo.

What if the first version needs another round?

Then you know exactly where to improve: you have the working software, the test set and the measured result, and the readout names what to adjust in the data, the process or the scope. The number turns the next round into a precise piece of work, and it keeps the production budget pointed at what has already proved itself. Whatever you decide next, everything built is yours.

Who owns the code, the models and the data?

You do, at every step. Source code, trained models, pipelines, prompts and test sets are transferred to you at handover, and for a Production Launch the documentation and runbook with them. Crux Digits keeps no rights to what is built for you and does not license its work back to you; third-party and open-source components keep their own licences. Your data is used only for your own build and never to train models for Crux Digits or anyone else, and a mutual NDA is signed before any data is shared.

How does the €20,000 MVP relate to the Production Launch from €50,000?

The MVP delivers the workflows scoped for your case, production-ready, on the systems they draw from, and leaves working software in your hands. The Production Launch takes that workflow and adds what daily dependence requires: robust connections to your ERP, CRM or warehouse system, roles and access control, monitoring, logging, alerts and rollback, documentation, a runbook, training and a post-launch support period, plus any second or related workflow. One integration is quick; five is a different project, which is why the launch is priced per scope before the build starts. €50,000 is the floor because none of that list is optional for a system people depend on every day.

How are the steps invoiced, and is anything billed hourly?

Each step is a separate fixed-price agreement with a written scope, approved on its own. The proposal names the scope, what is out of scope and the dates. The price in the proposal is the price on the invoice; a material change in scope gets a written change note before it is built, and the invoice follows that note. Prices are in euros and exclude VAT; Dutch VAT is charged to Dutch customers, and for business customers in Belgium or Luxembourg the reverse-charge rule applies. Only advisory work outside the three steps, such as strategy sessions, architecture reviews and guidance for your in-house team, is billed by the hour, at €150 excl. VAT. Build work is never hourly.

How long does each step take, and do we have to start with the audit?

The audit takes one to two weeks and usually starts within five business days of agreeing scope. The Production-ready MVP takes four to six weeks with a delivery date fixed at the start. A Production Launch starts at eight to twelve weeks and is set per scope in the proposal. For a first project, start to finish, that is three to five months. You do not have to start with the audit: if the workflow is already chosen, you can request the MVP proposal directly; we confirm scope and data access before the fixed price is issued. If it is already running and measured, we scope the production launch.

Can WBSO or another subsidy reduce the cost?

Often. The Dutch WBSO scheme covers development labour on R&D work, at roughly 36% of the eligible wage base and 50% for starters; confirm the current rates with RVO. It does not cover software purchase. SLIM, MIT and provincial vouchers can stack on top of it, and the free subsidy check on this site shows which schemes fit your case. A subsidy does not change the fixed price; it changes what you net.

A proposal your board can read

Describe the process in plain words. Within one business day you have a written scope and a fixed price to put in front of whoever signs, whether that is the €2,500 audit or the €20,000 Production-ready MVP.

Request a proposal