We don't publish a price list. The tiers below describe the most common program shapes we deliver — each priced after a short technical discovery so integrations, data sensitivity, and acceptance criteria are explicit. No surprise change orders. No open-ended retainers by default.
Fixed SOW
Scoped before build
Milestone acceptance criteria
Discovery
Quote after technical scope
No surprise change orders
You own IP
Code & artifacts transfer
Unless agreed otherwise
Program shapes
Sized to your stack, compliance needs, and team overlap. All include written milestones and code ownership unless otherwise agreed. Specific numbers follow a 30-minute scoping call.
Validate architecture and ship a working slice on staging.
Timeline
4–6 weeks
Investment
Comparable to a single month of one senior staff engineer, fully loaded.
Full implementation hardened for real users and SLAs.
Timeline
8–12 weeks
Investment
Comparable to one senior hire's first quarter—without the recruiting cycle or ramp tax.
Multi-service systems, compliance, and long-term scaling paths.
Timeline
12–16+ weeks
Investment
Sized to a small dedicated AI team across multiple quarters—delivered without a year of recruiting drag.
Compare
Use this matrix to start the conversation — we confirm details in discovery.
| Dimension | Proof of concept | Production ready | Enterprise scale |
|---|---|---|---|
| Typical duration | 4–6 weeks | 8–12 weeks | 12–16+ weeks |
| Best for | Validate feasibility | Ship to real users | Multi-team / regulated |
| Production deployment | Staging | Yes | Yes + scale path |
| Evals & guardrails | Baseline | Production gates | Program-wide |
| Post-launch support | 2 weeks | 4 weeks | 8+ weeks |
| Team handoff | Summary | Full KT | Extended KT optional |
Principles
Commercial clarity is part of delivery discipline — not a separate negotiation after the fact.
01
We confirm data, integrations, risk, and success metrics in a short technical scope—then quote a fixed program. We don't publish a price list, so every number is sized to your scope rather than anchored to a generic tier.
02
Payments tie to written deliverables: architecture sign-off, staging cutover, production launch, and handoff. Scope shifts go through change control.
03
Every proposal lists environments, support window length, eval requirements, and who attends steering—so procurement and engineering align early.
Process
Four steps. No obligation until you have a written proposal with price and milestones in hand.
30 minutes on outcomes, constraints, and timeline—no obligation to proceed.
We document assumptions, integrations, data sensitivity, and acceptance tests.
Written SOW with price, milestones, deliverables, and support window.
Weekly demos, shared metrics, and change control if scope materially shifts.
Always included
Regardless of tier, these items are non-negotiable inclusions in every SOW.
Optional line items quoted when they reduce delivery risk or accelerate adoption.
Multi-tenant platforms, long procurement cycles, and compliance-heavy workflows are scoped as dedicated programs — with milestone billing, RACI, and security artifacts mapped to your review process.
Discuss enterprise scopeFAQ
For MSAs, insurance certificates, and vendor forms, mention your procurement contact after initial fit.
Ready to scope?
Share your outcomes, timeline, and constraints. We'll respond within one business day with a written scope shape and budget range before you commit.
