The short answer
There is no sticker price for an AI build, because the cost is set by the workflow, not the label. Five things move it: how much of the workflow is in scope, how many systems it integrates with, how reachable the data is, how much evaluation and hardening production demands, and the handover. The number comes as a fixed quote after a Workflow Audit, not from a rate card.
"How much does an AI system cost?" is a fair question with an honest answer that sounds like a dodge: it depends. But it depends on a small, knowable set of things, and understanding them tells you more than any published price ever could, including how to make the number smaller.
Why there is no sticker price
A production AI system is not a product on a shelf; it is a system scoped to your workflow. The same-sounding feature can be a week of work or a quarter, depending on what it has to connect to and survive. A firm that quotes before seeing the workflow is guessing, and a guessed price is what turns into change requests and an overrun. That is why we, and any serious partner, keep no public pricing and quote after discovery instead.
The five things that move the cost
- 01Scope of the workflow. One step versus the end-to-end process. A tightly bounded slice is the single biggest lever on cost.
- 02Integrations. How many systems it must connect to, and how modern they are. Two clean APIs are cheap; a legacy system with no API is not.
- 03Data reachability. Clean, accessible, well-understood data is fast to build on. Data that is scattered, locked, or messy becomes its own project.
- 04Evals and hardening. How much reliability, security, and compliance production demands. A low-stakes internal tool and a regulated, audited system are different builds.
- 05Ownership handover. Documentation, runbooks, and capability transfer so your team can run it. This is part of the build, not an upsell, and a build that skips it is cheaper only until you need to change anything.
Fixed scope, quoted after the audit
Scope first, then a fixed number. Not a number first, then a fight about scope.
The point of a Workflow Audit is to turn those five variables into a definite scope, so the quote can be a fixed price rather than an open meter. That is the difference between fixed scope and time-and-materials: you know the number and the boundary before work starts, and uncertainty lives between phases where you can stop, not inside a running clock.
What makes it cheaper, and what makes it dearer
The cheaper builds share a shape: a narrow workflow, a decision-maker who owns it, and data that is already reachable. The dearer ones add integrations with brittle systems, locked or scattered data, and heavy compliance. None of that is a reason to inflate scope; it is a reason to start with one team and one workflow, ship it, own it, and let the result decide the next investment. For an enterprise team, that is also the lowest-risk way to put a real number on the table: the enterprise page covers how the engagement is scoped and de-risked.