Cost components
Costs split into three buckets: build, run, and change management.
- Build — discovery, design, integration, eval harness, deployment.
- Run — LLM inference, vector DB, observability, on-call coverage.
- Change — training, SOP rewrites, governance reviews, audit prep.
What drives variance
The biggest cost drivers are integration surface (number of MCP/API endpoints), data quality remediation, and the strictness of the evaluation bar. Regulated industries (healthcare, finance, legal) add 20–40% for compliance reviews.
What drives the number up or down
Cost tracks integration surface and governance burden far more than model choice. An agent reading two well-documented APIs and writing to one system is a different project from one that has to reconcile entities across a legacy ERP, a ticketing system, and a shared mailbox with no stable identifiers.
- Number and quality of source systems, and whether write paths already exist.
- Whether permissions can be resolved per user, or need to be modelled first.
- Regulatory review, audit requirements, and data-residency constraints.
- Whether an outcome metric is already recorded, or has to be instrumented.
- How much of the judgment can be validated against existing historical decisions.
The two costs people forget
The first is run cost: tokens, retries, retrieval, and the compute behind evaluation runs. It is modest per run and material at volume, and it should be modelled per workflow before build rather than discovered on the first invoice.
The second is operating cost. Agents sit on top of systems that change — schemas move, policies tighten, models are deprecated. Budgeting a build without budgeting upkeep is the most common reason a working pilot quietly stops being used a few months later.
How to keep the first commitment small
Our engagement structure is deliberately staged so the expensive commitment comes after the evidence: a short readiness assessment on one candidate workflow, then a fixed-scope pilot only if the assessment supports it, then ongoing operations only if the pilot's evaluation results hold. Each stage is designed to be able to end in 'do not proceed' without stranding the work that came before.
Current engagement pricing and durations are listed on the services page, and the assessment output includes an ROI model and a buy-versus-build recommendation for the specific workflow — including the case where an off-the-shelf product is the cheaper answer.
