{"slug":"business/16-value-proposition","title":"16 — Value Proposition","section":"business","sectionLabel":"Business","status":"unclassified","type":"document","path":"business/16-value-proposition.mdx","bytes":7867,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nStatus: CANONICAL · Commercial OS\nOwner: Product Marketing\nLast verified: 2026-07-21\n\n---\n\n## Purpose\n\nThe value we create, stated in the customer's currency: time, risk, and compounding memory. Every ROI claim, pricing defense, and renewal conversation draws from here.\n\n**Target audience:** Sales, marketing, CS, founders.\n\n**Objectives:** (1) Three value streams, each quantified. (2) Persona-level value statements. (3) The value equation used consistently in every deal.\n\n---\n\n## 1. Master Value Proposition\n\n> IntegrateWise returns the hours your team spends being the Human API, makes AI trustworthy enough for consequential work, and turns your organization's context into a compounding asset that survives tools, models, and turnover.\n\nThree value streams. Every deal quantifies at least the first; great deals quantify all three.\n\n---\n\n## 2. Value Stream 1 — Time Returned (the wedge)\n\n**Mechanism:** The workbench opens on assembled context (Entity360 < 200ms). The Twin prepares briefs, drafts, and analyses. The Empty Context Tax — auth again, search again, explain again, reconstruct again — stops being paid.\n\n**Quantification (canonical numbers, keep consistent everywhere):**\n\n| Input                             | Canonical value                                       |\n| --------------------------------- | ----------------------------------------------------- |\n| Context gathering today           | 2–4 hours/day per knowledge worker (use 3 for CSMs)   |\n| Fully loaded hourly cost          | $65–80/hr (use $65 in team math, $80 in per-CSM math) |\n| Annual waste per CSM              | ~$62,000                                              |\n| Time reclaimed with IntegrateWise | 60–80% of gathering time in month one                 |\n| QBR prep (design partner)         | 4 hours → 12 minutes                                  |\n\n**The value equation (quote in every proposal — matches [Close Playbook](../../sales/close-playbook.md)):**\n\n```\nTime reclaimed/user/day × affected users × loaded hourly cost × 22 days\n= Monthly team value reclaimed\n```\n\nWorked example: 2.5 hrs × 20 CSMs × $65 × 22 = **$71,500/month reclaimed**, against 20 Command seats at $119 = $2,380/month. **30x monthly return.** (See [29 ROI Framework](../05-value-pricing/29-roi-framework.md) for conservative/base/aggressive variants.)\n\n---\n\n## 3. Value Stream 2 — Trustworthy AI (the differentiator)\n\n**Mechanism:** Evidence chains on every Twin intervention; TruthLayer approval on every memory write; governed proposal → approval → execution → audit on every action. The Quiet Demotion reverses: AI graduates from writing emails to doing real work — with the human still deciding.\n\n**Quantification:**\n\n| Value                                         | How it's counted                                                               |\n| --------------------------------------------- | ------------------------------------------------------------------------------ |\n| Churn signals surfaced before the score moves | churn saves attributed via signal evidence chains ($8M origin-story anchor)    |\n| Missed-expansion capture                      | expansion opportunities surfaced across billing/usage/conversation per quarter |\n| Risk avoided                                  | zero unapproved AI actions; zero hallucinated facts in board material          |\n| AI spend consolidation                        | replaces per-app copilot seats that deliver email-drafting only                |\n\n**Statement:** _\"You already pay for AI your team doesn't trust. This is AI your team can put in front of a customer — because every claim shows its evidence and every action shows its approval.\"_\n\n---\n\n## 4. Value Stream 3 — Compounding Continuity (the moat, the renewal)\n\n**Mechanism:** Every approved fact, decision, and outcome enters the Spine. Handovers carry full context. New hires inherit institutional memory. Model/vendor switches don't reset anything.\n\n**Quantification:**\n\n| Value                       | How it's counted                                                                                                                                                                                                              |\n| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Ramp time for new CSM/AE    | weeks → days (context inherited, not reconstructed)                                                                                                                                                                           |\n| Handover cost               | multi-hour file assembly → transfer-ready context                                                                                                                                                                             |\n| Knowledge attrition         | departing employee no longer takes the account's story with them                                                                                                                                                              |\n| Continuity math (canonical) | Month 1: one week of memory replaces three status meetings · Month 3: the Twin knows patterns before the team does · Month 6: fewer duplicates, fewer surprises · Month 12: institutional memory no longer leaves with people |\n\n**Statement:** _\"Point solutions solve a moment in time. Continuity compounds. Twelve months in, the question isn't whether to renew — it's how you'd ever reconstruct what the Spine now knows.\"_\n\n---\n\n## 5. Value by Persona\n\n| Persona       | Value headline                                                                                   | Stream emphasis |\n| ------------- | ------------------------------------------------------------------------------------------------ | --------------- |\n| CSM / AM      | \"Start the day knowing what changed, what needs you, and what's already prepared.\"               | 1               |\n| VP CS / CCO   | \"Churn signals before the score moves; QBR prep measured in minutes; a team that trusts its AI.\" | 1 + 2           |\n| COO / Founder | \"One surface over the whole business; context that survives org changes.\"                        | 1 + 3           |\n| RevOps        | \"Governed truth across the stack without replacing anything; reporting latency in minutes.\"      | 2 + 3           |\n| CIO / CISO    | \"AI that structurally cannot write truth or act unapproved; full audit; no lock-in.\"             | 2               |\n\n---\n\n## 6. Value Proof Discipline\n\nRules for using value claims (enforced in [71 Internal Enablement](../13-operations/71-internal-enablement.md)):\n\n- Design-partner numbers (\"4 hours → 12 minutes,\" \"89% DAU\") are quoted as design-partner results until three named case studies exist ([64 Case Study Templates](../12-corporate/64-case-study-templates.md)).\n- The $8M account save is the founder origin story — always told as story, never as a customer statistic.\n- Every proposal includes the value equation filled with the prospect's own numbers from discovery, never generic numbers.\n\n**KPIs:** % of proposals with customer-specific value math (target 100%); value stream 2/3 mentioned in renewal conversations (target 100%); realized-value reviews completed per customer per quarter ([75 CS Metrics](../13-operations/75-customer-success-metrics.md)).\n\n---\n\n**Related:** [29 ROI Framework](../05-value-pricing/29-roi-framework.md) · [28 Customer Outcomes](../05-value-pricing/28-customer-outcomes.md) · [12 Messaging](12-messaging-framework.md) · [37 Sales Playbook](../07-sales/37-sales-playbook.md)\n"}