Four engagement models
Pick the one that matches where you are
Each has what it includes, what it does not, and the typical range it falls into. Ranges are directional — actual quotes follow discovery.
AI readiness assessment
Fixed-scope discovery to define the use case, understand constraints, and make a go or no-go call before any build work begins.
Deliverables
- Use-case prioritization and scoping
- Data and access review
- Deployment model recommendation (on-prem, private cloud, controlled hosted)
- Risk register and governance requirements
- Roadmap with rollout options and budget envelopes
Best fit
Teams that need a serious architecture and readiness recommendation before funding a pilot, or before approving an internal proposal.
When to start here
Start here if you are early in the decision and need a defensible point of view first.
Scoped project · 6–12 weeks Secure pilot deployment
A controlled first implementation for one use case, one environment, and one team — built around measurable validation criteria.
Deliverables
- Model runtime and retrieval architecture
- Identity, permissions, and logging boundaries
- Pilot workflow integration into an existing tool surface
- Evaluation harness and acceptance criteria
- Admin and user onboarding plus launch review
Best fit
A first use case where the organization wants a controlled deployment with defined success criteria, not a research project.
When to start here
Start here if the use case is already clear and an architecture point of view exists internally, or after an assessment.
Custom quote · 8–16 weeks Production rollout
Expansion of a validated pilot into a production environment with documentation, controls, and operational ownership.
Deliverables
- Security hardening and control validation
- Integration planning across production data sources and tools
- Runbooks, operating procedures, and on-call expectations
- Training for admins, reviewers, and end users
- Change management and rollback procedures
Best fit
A pilot that has demonstrated real operational value and now needs to move from a constrained environment into something the broader team can rely on.
When to start here
Start here when the pilot is stable, leadership is committed, and a broader user base or higher-stakes workflow is next.
Monthly or quarterly retainer Managed governance and support
Ongoing advisory, reviews, optimization, and policy refreshes after go-live — without rebuilding an internal AI team you do not need.
Deliverables
- Quarterly architecture and policy review cadence
- Use-case expansion planning and prioritization
- Logging, retention, and access review
- Performance and architecture tuning
- Operational guidance for model updates, vendor changes, and incidents
Best fit
Teams that want continued advisory presence after launch but do not want to build out a dedicated internal AI function.
When to start here
Start here after a successful rollout, or layer on top of an existing internal owner.
