How do we defend what we built?
The Operate stage is about defending product boundaries against scope creep. The product that tries to be everything becomes nothing. This stage provides the operational framework for defining, communicating, and defending product boundaries once the product is in the field.
Stage Objectives
- Define four product boundary zones (Core, Configurable, Optional Modules, Excluded Scope)
- Align product boundaries with ATO authorization boundaries
- Build the operational framework for saying no constructively
- Track and categorize scope creep requests
- Protect product margins through clear boundary communication
Key Activities
Boundary Zone Definition
Define your four product boundary zones: Zone 1 (Core Product -- always included), Zone 2 (Configurable Elements), Zone 3 (Optional Modules -- additional CLINs), Zone 4 (Excluded Scope -- professional services only).
ATO Boundary Alignment
Ensure product boundaries and authorization boundaries align. Feature changes that expand the authorization boundary trigger security assessment ($75K-$150K and 2-4 months).
Scope Creep Defense
Build your defense playbook for protecting product margins. Every 'small' customer request has real costs. Offer boundary-compliant alternatives.
Boundary Communication
Create clear communication templates for Zone 3 (optional module pricing) and Zone 4 (custom development estimates) requests.
Run Operate as an engagement
The framework is published in full, so you can run Operate yourself. If you would rather have it done with you, the Operate + Replicate is the engagement that covers it. An operating playbook with scope-creep controls, standardized delivery, and a replication model for taking the offering into additional markets. Where the Build Pilot is a 90-day engagement that ends at its day-90 checkpoint, this is a recurring phase: the work is measured in milestones, and it continues for as long as the offering keeps running and keeps expanding.