Pricing
We publish price bands because the alternative wastes a week of your time and ours. If the number is wrong for your budget, you should know that before the first call — not after three meetings and a deck.
The three bands
4–8 weeks · fixed scope
$40K–$120K
One workflow, fully scoped, built, and shipped to production on a fixed timeline and a published price. Architecture, build, integration, evals, launch, runbooks, and 30 days of post-launch support.
See the sprint4–6 weeks · fixed fee
$25K–$60K
Policy framework, risk register, eval infrastructure, vendor evaluation matrix, operations manual, and the executive briefing that gets AI work through security review.
See governanceOngoing · 20–80 hrs / month
$8K–$30K / month
Senior AI engineering bandwidth on retainer: new builds, optimisation, monthly evals, quarterly reviews, and on-call coverage for production issues.
See the retainerDiscovery is free: a 30-minute call, then a one-week scoping phase that ends in a written scope document — architecture, milestones, price, and team — whether or not you go ahead.
Range, explained
A sprint is one workflow either way. The spread is complexity, not padding. These six factors account for nearly all of it.
One well-documented API sits at the bottom of the band. A CRM, a ticketing system, a data warehouse, and a legacy ERP with no sandbox sit at the top.
Clean, permissioned, retrievable content is cheap. Scattered documents with no access model, no ground truth, and no owner means we build that first.
Internal drafting tools carry less burden than anything touching customers, money, health, or legal — those need tighter controls and heavier review.
A representative eval set with a handful of dimensions is one cost. Adversarial cases, per-release regression gates, and human-rated judgment sets are another.
Each human gate is a workflow of its own: queues, routing, escalation, SLAs, and an audit trail that survives inspection. More reviewers, more surface.
Five power users who want the tool costs little. Two hundred people across three time zones who did not ask for it means training, rollout, and support design.
We price the band at the end of scoping, not before it — and the number in the scope document is the number on the invoice. Significant scope changes are handled through change orders that adjust timeline, budget, or both.
Inclusions
Architecture design. System build. Integration with your infrastructure. An eval suite with a representative test set. Approval gates and escalation paths. Audit logging and monitoring. A written runbook and rollback criteria. Production launch. Hands-on handover training. 30 days of post-launch support.
Model and infrastructure spend, which you pay your providers directly. New licences for systems you don't already own. Ongoing operation after the 30-day window — that's what the retainer is for. Net-new data cleanup at warehouse scale. Work outside the one scoped workflow, which becomes its own sprint rather than quiet scope creep.
You own the code and the evals. We sign a mutual NDA before any scoping conversation. More detail on the FAQ and across the three services.