Skip to content
Flow Docs
Flow home Back to the main Flow site

Adoption strategy

Phase 1: Individual adoption

Section titled “Phase 1: Individual adoption”

Adoption begins with engineers who work in high-friction environments. That includes mainframe operations, CI/CD pipelines, and QA workflows.

Delivery: Flow installs locally and does not depend on any infrastructure. The zero-egress architecture removes the need for cloud DPAs and external inference approvals. In regulated environments, the standard IT sign-off for desktop software still applies.

Pilot hardware criterion: the pilot targets a standard engineering workstation with a modern multi-core CPU and enough RAM to run an IDE and inference at the same time. This is a way to pick pilot machines, not an architecture constraint. On lower-spec hardware the platform skips AI steps instead of blocking execution.

Success criteria: engineers choose to use Flow for daily tasks, they reuse saved templates, and manual debugging loops drop in a way you can measure.

Phase 2: Team-level adoption

Section titled “Phase 2: Team-level adoption”

Individual flow templates become shared assets.

New capabilities: this phase adds the template repository, versioned flows, and lightweight governance.

Code-review integration. Because Flow DSL definitions are plain text, this phase fits into the engineering process a team already has rather than adding new tooling. Teams submit flow templates as pull requests, assign code owners, review them for correctness, and promote them through branches.

Success criteria: team members reuse shared flows, new engineers depend less on senior staff to get started, and standardized team flows begin to appear.

Phase 3: Organizational integration

Section titled “Phase 3: Organizational integration”

Flow grows into a cross-team operational platform that integrates with CI/CD pipelines, QA workflows, and operational flows. The governance service, RBAC, and audit logging on the roadmap support this phase.

Success criteria: Flow becomes the operational standard across teams, flows are standardized across teams, and operational friction drops in a way you can measure.

Section titled “Related”