{"slug":"internal/operations/customer-zero","title":"Customer Zero — Canonical Operating Model","section":"internal","sectionLabel":"Internal","status":"unclassified","type":"document","path":"internal/operations/customer-zero.md","bytes":1375,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"<!-- DOCUMENT CLASS: INTERNAL | SOURCE: 33_CUSTOMER_ZERO.md -->\n<!-- STATUS: Aligned with Founder Canon (31 August 2026) -->\n\n# Customer Zero — Canonical Operating Model\n\n## The Tier-0 Principle\n\n> **Business Context is the semantic foundation of SpineWorkspace.** Customer Zero must exercise the establishment, maintenance, and serving of Business Context. Without Business Context, Customer Zero has nothing to prove.\n\n## Purpose\n\nIntegrateWise runs SpineWorkspace on its own operations before generalizing patterns.\n\nThe live Customer Zero surface should exercise:\n\n- sales;\n- marketing;\n- onboarding;\n- support;\n- product;\n- finance;\n- internal operations.\n\nThe existing Customer Zero material describes this as the operational backbone used internally to test approval flows, handoffs, Twin recommendations and integrated signals.\n\n## Customer Zero loop\n\n```text\nInternal Need\n→ Work\n→ Business Context\n→ Workbench\n→ Twin\n→ Governance\n→ Execution\n→ Reconciliation\n→ Business Context Updated\n→ Product Improvement\n```\n\n## Required proof\n\nCustomer Zero should generate evidence for:\n\n- Business Context assembly time;\n- work completion;\n- tool-switch reduction;\n- governance;\n- reconciliation;\n- Twin usefulness;\n- continuity;\n- operational cost.\n\n## Rule\n\n> Customer Zero is a proving environment, not the source of customer architecture assumptions.\n"}