The outcome you are walking toward
A complete picture of how a multi-location organization moves from a first briefing to a self-improving network: five named phases, each with a goal, explicit exit criteria, and the artifacts that carry the decision forward. This is the deployment architecture behind Business-In-A-Box engagements — read it before you scope a pilot, and hold us to it during one.
The deployment philosophy
Six principles govern every engagement:
- Start narrow, prove hard, expand deliberately. Scope is earned by evidence, never granted by enthusiasm.
- Every phase has explicit exit criteria, written before the phase begins.
- No phase assumes the next phase is automatic.
- Local success must be real before network ambition.
- Governance and evidence grow with scale.
- The network must remain coherent at every step.
The aim is long-term network intelligence, not short-term logo collection.
The five phases at a glance
- Phase 0 — Institutional Alignment — shared understanding and authority (typically weeks, not months)
- Phase 1 — Foundation Pilot — prove the deployment on one to three locations
- Phase 2 — Controlled Cohort — prove repeatability on five to fifteen locations
- Phase 3 — Network Activation — roll out across the broader portfolio in waves
- Phase 4 — Compounding Organization — playbook propagation and continuous improvement
Each phase has entry conditions, exit criteria, required artifacts, and pause or rollback provisions.
Phase 0 — Institutional Alignment
Goal. Create a shared, high-resolution understanding of success, authority, risk, and scope before anything is installed.
Alignment work maps executive and operational stakeholders, inventories the current state, selects the pilot locations, defines success metrics, and drafts the policy floor and authority principles the pilot will run under. Data, privacy, and integration boundaries are agreed in writing — the same boundary discipline described in governed agent boundaries and venture & brand onboarding.
Exit criteria.
- A named executive sponsor and operational owner
- Written success criteria for Phase 1
- Agreed pilot locations
- Initial policy and authority principles documented
- A mutual, recorded decision to proceed
Artifacts. Alignment Record, Pilot Charter, and an initial Risk Register.
Phase 1 — Foundation Pilot
Goal. Make one to three real locations into working deployments and prove measurable operational value.
The pilot runs the full stack under observation: the Business OS, the relevant vertical orchestration, a core agent team from the Agents roster, the appropriate STORE kits, and edge runtime with offline resilience. Evidence is reviewed weekly against the criteria written in Phase 0. The pilot rollout checklist is the working sequence; Run a pilot that earns expansion is the judgment around it.
Exit criteria.
- Critical loops running reliably, including offline tests
- Agreed operational metrics improved or clearly trending
- Agent actions reconstructable from the record and trusted by operators
- No unresolved critical safety or integrity issues
- The local team willing to expand
Artifacts. Pilot Evidence Package (categories map — filled packs stay briefing/NDA), conformance status of all deployed components, lessons learned with playbook candidates, and a go/no-go recommendation for Phase 2.
Phase 2 — Controlled Cohort
Goal. Prove the pilot result is repeatable across a meaningful set of locations with different characteristics — size, volume, geography, or format.
The cohort runs five to fifteen locations on standardized deployment runbooks, in waves, with cross-location benchmarking and the first formal playbook evaluations. This is where repeatability stops being a claim and becomes a record.
Exit criteria.
- Core metrics achieved consistently across the cohort
- Deployment time and cost within agreed bounds
- Playbook propagation exercised successfully at least once
- Support and governance model proven under real load
- An executive decision to proceed to Network Activation
Artifacts. Cohort Performance Report, updated reference kits, the first propagated playbooks, and the Network Rollout Plan.
Phase 3 — Network Activation
Goal. Extend the deployment across the broader portfolio in controlled waves while maintaining coherence and safety.
Waves are planned by region, brand, or location type. Standardized kits and runbooks do the heavy lifting, Franchise OS becomes the primary management surface, and the playbook library begins to compound. Local variation is allowed — inside global policy guardrails — and rollback capability is maintained for major changes.
Exit criteria. Network Activation exits into steady-state operation when:
- The majority of target locations are operating coherently
- Network-level metrics are improving
- Playbook propagation occurs regularly and safely
- Support burden per location is decreasing over time
Artifacts. Wave plans with explicit success criteria and pause triggers, propagation records, and conformance monitoring reports.
Phase 4 — Compounding Organization
Goal. Shift from deployment to continuous network intelligence.
The focus moves to systematic playbook discovery and propagation, advanced agent capabilities under governance, and cross-location optimization of labor, inventory, maintenance, and experience. At this stage the network is designed to improve itself under human governance — it is no longer a deployment project.
Exit criteria. None by design — Phase 4 is continuous. Maturity is judged by markers rather than a gate: playbooks actively discovered, evaluated, and propagated; offline resilience proven under real conditions; operators trusting agent actions enough to expand their scope; performance measurably compounding across the portfolio.
Artifacts. An evaluated playbook library, governance review records, and the long-term partnership plan.
Roles and responsibilities
Every engagement names the same roles:
- Executive sponsor — ultimate accountability and decision rights.
- Network owner — day-to-day authority across phases.
- Vertical operators — local success and feedback.
- Deployment lead (MCV.TECH) — technical and operational execution.
- Conformance and trust — evidence integrity across deployed components.
- Agent governance — authority envelopes, observation modes, and approval of major changes.
- Change management — human adoption and training.
Escalation paths for safety, integrity, and major value shortfalls are agreed in Phase 0, not improvised in Phase 3.
Risk principles
- Safety and integrity issues always outrank schedule.
- No phase gate is passed on verbal assurance — evidence is required.
- Every major expansion carries a pause and rollback capability.
- Local failure is contained; network failure is unacceptable.
- Policy and authority are never bypassed for speed.
How the phases map to commercial engagements
Commercial commitment stays matched to proven value:
- Phases 0–1 — Pilot engagement: prove value on a bounded footprint.
- Phase 2 — Cohort expansion agreement: prove repeatability.
- Phases 3–4 — Network platform partnership: scale what the evidence supports.
You are never asked to buy the network before the cohort has earned it. The diligence resources page is the route for reviewing evidence material during any phase, and the audit trail & evidence model describes the record every phase decision draws on.