Scope Negotiation

Scope negotiation is where the architecture meets the budget. The client wants more than the budget allows, or the architect believes the scope needs expansion to deliver a viable solution. The negotiation is a design exercise — not a sales exercise. The architect identifies which components are essential, which are valuable but deferrable, and which are scope creep that adds cost without proportional value. The phased delivery design is the negotiation tool.

1. MoSCoW Architecture Classify every architectural component as Must have (the solution does not work without it), Should have (significant value, but the solution functions without it), Could have (nice to have, defer to Phase 2 or 3), and Won't have this time (explicitly out of scope). The classification connects every budget dollar to a specific component and a specific value delivery. When the budget needs to shrink, the Could haves move first.
2. Value-Per-Component Analysis For each component, articulate the business value it delivers. The ML model delivers automated categorization (core value). The feedback loop delivers model improvement over time (extension value). The custom dashboard delivers executive visibility (reporting value). When the client asks "can we cut $50K from the budget?" you can answer: "Yes — we defer the custom dashboard to Phase 2, which removes $48K and delays executive reporting by 6 weeks but does not affect the core categorization capability."
3. Non-Negotiable Components Name the components that cannot be cut without making the solution unviable. "The API integration layer is non-negotiable — without it, the ML model has no data to process. The monitoring layer is non-negotiable — without it, we cannot detect accuracy degradation. The model training pipeline is non-negotiable — without it, the model cannot improve from production data." Non-negotiables are the architect's red lines. State them clearly and explain why.