---
title: "Rollout Phases"
description: "From pilot to Scale & Deepen to deep integration in ongoing operations"
canonical_url: "https://meingpt.com/en/docs/rollout-guide/rollout-phases"
language: en
---

# Rollout Phases

For larger organizations, a 3-phase model works best. Key point: from phase 2 onward, broad adoption and deeper integration run in parallel.

## Typical timing model

- Phase 1 Pilot: about 3 months
- Phase 2 Scale & Deepen: about 6-12 months
- Phase 3 Deep Integration & Autonomy: ongoing from month 16

## Phase 1: Pilot (about 3 months)

Goal: fast startup with visible outcomes.

- build a small champion group
- deliver first production use-cases
- define standards for prompting, assistants, and workflows
- connect first core integrations

Outcome:

- core team and role model in place
- first assistants/workflows in production
- adoption baseline measurable

## Phase 2: Scale & Deepen (about 6-12 months)

Two tracks run at the same time.

Track A Broad adoption:

- onboard additional teams/sites in a structured way
- establish training, FAQ, and office-hour routines
- roll out standard use-cases for broad user groups

Track B Champions & depth:

- champions build internal assistants and use-cases
- continuously deepen integrations
- transfer AI know-how into the organization

Outcome:

- adoption grows steadily across functions
- repeatable patterns per team/function
- deep use-cases evolve alongside broad rollout

## Phase 3: Deep Integration & Autonomy

This phase focuses on deep data integration while keeping adoption stable.

Track A Operations & adoption:

- institutionalize internal enablement
- anchor champions as internal multipliers
- establish playbooks per function

Track B Deep data integration:

- ERP integration and other complex systems
- deeper data pipelines, SQL/DWH, RAG extensions
- advanced automations and process agents

Outcome:

- internal team operates largely independently
- deep integrations deliver measurable process impact
- champions continue to receive targeted coaching

## Which rollout unit first?

- Site-based: if plants/countries work very differently
- Function-based: if sales, service, procurement have distinct needs
- Process-based: if end-to-end flows cross multiple teams
- Hybrid: often the most stable path in practice

## Decision rule

Choose the unit where you can deliver visible outcomes in 6-8 weeks.

## Visual one-pager

- [Executive OnePager](/en/docs/rollout-guide/executive-summary)

## Next pages

- [Rollout Design](/en/docs/rollout-guide/rollout-design)
- [Operating Model](/en/docs/rollout-guide/operating-model)
- [Responsibility Model](/en/docs/rollout-guide/responsibility-model)
- [Tailoring Playbook](/en/docs/rollout-guide/tailoring-playbook)