We build your AI. You pay when it works.
We scope one workflow with you, sign an agreement defining the deliverables and the acceptance criteria you signed off on, and build it in your environment in two weeks. You pay $10,000 only after every criterion is met. Nothing upfront. One workflow at a time.
Four compressions that make the two-sprint offer possible.
Scope.
Briefs arrive as writing. Fixed scope, the $10,000 price, and acceptance criteria are returned within forty-eight hours. No discovery theatre. No qualification workflows. One reply decides.
Build.
We build with Claude, Claude Code, and automated evaluation pipelines. The engineer-hours that used to define traditional consulting bills are now the exception. The compression is what lets us build a workflow in two weeks and charge a fixed $10,000 with nothing upfront.
Evaluate.
Acceptance criteria are executable. Evaluation harnesses run against your own data. Criteria are signed on day one and re-run as the build progresses. You see what works and what does not, weekly. You pay only after every criterion is met.
Handover.
The system runs in your tenant. Your engineers operate it without assistance from us. The engagement closes when the runbook is countersigned.
Claude · Claude Code Anthropic Cowork Azure · AWS · GCP LangGraph · CrewAI
Scope: hours, not weeks Integration: days, not months Evaluation: continuous Handover: sprint close
SOC 2 · HIPAA · GDPR EU AI Act GxP · 21 CFR Part 11 Client-tenant isolation
Pilots · retainers Open scopes · roadmaps SaaS licensing Software resale
Three building blocks. One price per workflow.
Scope and agreement
We scope one workflow with you, define the deliverables, and write the acceptance criteria. We sign an agreement before any build starts.
- +Stakeholder interviews and system audit
- +Data source and integration inventory
- +Compliance framework mapping
- +Deliverables defined with you
- +Acceptance criteria you sign off on
We build it. You pay when it works.
We build the workflow in your environment in two weeks against the signed acceptance criteria. You pay $10,000 only after every criterion is met.
- +Built in your environment
- +Evaluation harnesses run against your data
- +Working system delivered in your tenant
- +Weekly review. Weekly adjustment.
- +You pay only after every criterion is met.
Portfolio scale
One workflow at a time. When you want several in flight, portfolio scale is priced by agreement with the same acceptance-as-code discipline.
- +Continuous integration with your systems
- +Incremental rollout to production
- +Governance, audit, and role-based access configured
- +Security review aligned to your policies
- +Runbook, training, and handover at close
How the sprints actually run.
Why two weeks, why not a single open-ended project?
A two-week build keeps scope honest. You see working software at the end of the build, not months later. Acceptance criteria are signed on day one and re-run as the build progresses. Fixed price per workflow, no hourly billing, no scope creep.
How many sprints will we need?
Most engagements are done in four to eight sprints. A sprint is one two-week build with its own signed acceptance criteria. Legacy modernization and multi-system RAG tend to the higher end. Single-function copilots and known-scope builds land in four to six.
What happens if the build does not meet the acceptance criteria?
You do not pay. The $10,000 is invoiced only after every criterion in the signed agreement is met. Nothing is due upfront. We fix it until it passes or you owe nothing.
Do you do retainers or open scopes?
No. Every engagement is sprint-by-sprint against signed criteria. We do not sell hours. We do not bill against roadmaps. The scope for each sprint is agreed in writing before the sprint begins.
What happens to the work if the criteria fail?
You pay nothing. The build runs in your environment from day one, so your data and your systems never leave your control.
Who decides whether the acceptance criteria pass?
The criteria are executable checks written in plain language and signed before the build starts. They run as tests, so passing is observable, not argued.
What does it cost after the first workflow?
The first build is one workflow at $10,000. Most clients continue sprint by sprint. Each sprint is one two-week build with its own signed acceptance criteria and the same pay-on-acceptance terms. You can stop after any sprint.
We build it. You pay when it works.
Send a brief. We return a scope and acceptance criteria in 48 hours. No discovery theatre. One reply decides.