Engagement models scoped for your environment.
Understand how we structure engagements, what's included by default, and what drives cost—so you can evaluate with confidence.
Discovery / Pilot
30–45 days
Validate one workflow end-to-end with production-grade controls. Scoped to reduce risk and establish success criteria before broader investment.
- 1 workflow scoped and delivered
- Up to 2 integrations
- RBAC basics + audit logging
- Eval harness v1
- Pilot deployment + runbook
- Success criteria and rollout recommendation
Production Pilot
8–12 weeks
Scale a validated pilot to production across multiple workflows with monitoring, governance, and stakeholder review gates.
- 2–3 workflows with cross-system integration
- Human-in-the-loop approval gates
- Monitoring dashboard + alerting
- Expanded eval suite + CI regression gates
- Staging → production pipeline
- Stakeholder review at every sprint gate
Rollout / Managed Optimization
12–16+ weeks
Build a governed AI program with a control matrix, red-teaming, and cross-department deployment—with optional managed service.
- Governance framework + control matrix
- Red-teaming + incident response playbooks
- Audit-ready security evidence packet
- Cross-department deployment support
- Managed service option with SLA
- Ongoing eval tuning and model updates
What's included by default
Available add-ons
What drives cost
Number of integrations
Each connector adds scoping, authentication, and testing work. More integrations increase engagement effort.
Workflow complexity
A single RAG pipeline costs less than a multi-step agentic workflow with tool use and approval gates.
Data readiness and sensitivity
PII/PHI/PCI workloads require additional controls, documentation, and review cycles.
Compliance and governance requirements
Regulated industries need additional audit artifacts, review workflows, and security documentation.
Review and approval workflows
Human-in-the-loop gates, stakeholder reviews, and change management add coordination effort.
Monitoring and eval depth
Deeper eval suites, ongoing regression testing, and production monitoring increase scope.
Pricing is scoped based on your environment, workflow complexity, and risk profile. We provide a detailed scope document before any commitment.
Typical engagement timeline
Week 1–2
Discovery & scoping
Map workflows, data sources, integrations, and security requirements. Define pilot scope and success criteria.
Week 3–6
Pilot build
Deliver working software in 2-week sprints with eval reviews, security gates, and stakeholder checkpoints.
Week 6–8
Pilot evaluation
Measure against success criteria. Validate with stakeholders. Document findings and rollout recommendation.
Week 8+
Production rollout
Controlled deployment with monitoring, rollback plans, expanded integrations, and hypercare.
Frequently asked questions
Ready to scope your engagement?
Book a discovery call and we'll map the workflow, integrations, and controls—then outline a pilot scope you can evaluate with confidence.