Pricing follows the workflow boundary. We first confirm systems, access, risk, ownership, and evaluation needs—then provide a written fee and no-surprise scope.
The Blueprint and pilot are professional engagements. Cloud, model, software, support, or user-license costs are itemized separately when they apply.
Decide whether and how to build one workflow.
Implement the approved workflow boundary and prove it against release criteria.
Keep the system reviewable and qualify expansion with production evidence.
*The 15-business-day clock begins after kickoff prerequisites are complete: one workflow owner, required access, stakeholder availability, and agreed boundaries. Production implementation is a separate scope.
Discovery, architecture, controls, engineering, evaluation, enablement, and assurance.
Cloud compute, model usage, storage, monitoring, and third-party system charges.
Only where an approved vendor charges per user, workspace, feature, or environment.