Implementation vendors routinely propose multiphase statements of work that carry TBDs on scope, no acceptance criteria between phases, and assumptions clauses that shift schedule risk onto the client. By the time discovery surfaces what the project really requires, the client is already contractually committed and facing change orders.
This article makes the case for a Phase 0: contracting the discovery phase as its own statement of work with a detailed project plan as the deliverable. We cover what a Phase 0 SOW must establish, where standard vendor SOWs fall short, when this approach is the right call, and what a client should expect to walk away with — including a fixed-fee milestone structure, refined ROI and cost estimates, and client ownership of the Phase 0 deliverables. We also address when to buy the software relative to the Phase 0 engagement and how to preserve negotiating leverage. A worked example contrasts the standard multiphase path with the Phase 0 path for the same implementation. The attached Phase 0 IT Project Planning Framework provides a deliverables checklist, the sequence in which Phase 0 runs, and a sample milestone showing the level of contractual detail to hold out for.