Scope Creep: How 'One More Question' Kills SOW Margin by 40-60%

Every consulting engagement faces same risk. Client pays for defined scope. Discovery reveals adjacent problems. Client asks "one more question." Then another. Project manager says out of scope. Client says it is small. Consultant does work. SOW hours inflate 40-60% beyond original estimate. Margin erodes. Engagement becomes loss leader disguised as strategic partnership.

Pattern is structural, not malicious. Growth-stage companies operate with compressed decision cycles and minimal internal analytical capacity. When they access experienced consultant, they maximize that access. Problem: SOW defines fixed set of deliverables, not unlimited advisory retainer. The "one more question" pattern converts defined engagement into de facto T&M advisory at fixed price.

ORI framework provides structural defense. 12 indicators define assessment scope. Client asks about issue mapping to indicator outside baseline scope. Response: "That indicator not included in current engagement scope. We can add via change order with incremental budget." Framework gives consultant principled boundary.

SOW inflation pattern follows consistent lifecycle. Phase 1, Discovery (weeks 1-2): client provides data, baseline collection begins. Phase 2, Small Questions (weeks 2-4): client starts adjacent requests not in scope. Phase 3, Scope Blur (weeks 4-6): original 4-week discovery expands to 6 weeks. Client believes expanded scope implicit. Consultant believes they are being helpful. Phase 4, Margin Recognition (week 8): engagement is 50% over hours, 40% over timeline, client asking for additional analysis before deliverable.

Governance structure with five elements. Element 1: Zero-exception scope document. Every deliverable listed with page count, data source, analysis method, output format. Not in document = not in scope. Element 2: Change order protocol published in engagement letter. Request outside scope triggers change order within 24 hours. Includes incremental cost, timeline impact, priority trade-off.

Element 3: Weekly scope reconciliation. Each weekly status meeting includes 5-minute scope check: "Any requests discussed not reflected in SOW?" If yes, change order process starts immediately. Element 4: Parking lot for adjacent issues. Issues outside scope logged in numbered tracker. Items above materiality threshold — typically $10K+ or 20+ hours — trigger change order. Items below aggregated monthly.

Element 5: ORI indicator boundary. Framework draws its own scope line. Most defensible boundary because methodology-driven, not relationship-driven.

T&M versus fixed-fee dynamics. Under T&M, scope creep still erodes margin if consultant underprices original estimate. But client pays for overage. Fixed-fee concentrates all scope risk on consultant. Growth-stage companies prefer fixed-fee for cost certainty. Consultants should price with explicit scope guardrails and overage clause: hours exceeding 110% of estimate convert to T&M at 1.25x rate.

SOW structure that protects margin. Section 1: Problem statement — one paragraph. Section 2: Scope — bullet list of deliverables with page ranges and data requirements. Section 3: Exclusions — explicit list of what is NOT included. Section 4: Assumptions — dependency conditions (client data quality, stakeholder availability). Section 5: Change order process — written protocol with threshold, response time, approval chain. Section 6: Timeline and milestones. Section 7: Fee structure. Section 8: ORI indicator scope reference — which indicators assessed, which excluded.

Client pushback pattern and response. Client: "We thought assessment included supply chain." Consultant: "SOW specifies supply chain excluded. ORI indicators covered: F1-F3, O1-O3, C1-C3. Supply chain maps to indicator O4, not included. Can add via change order." Specific, framework-referenced, non-confrontational.

Closing takeaway: Scope creep is engagement design problem, not relationship problem. Well-structured SOW with zero-exception scope document, published change order protocol, ORI indicator boundary prevents margin erosion. Client respects consultant who protects process.