{"slug":"strategy/business-strategy/28-customer-outcomes","title":"28 — Customer Outcomes","section":"strategy","sectionLabel":"Strategy","status":"unclassified","type":"document","path":"strategy/business-strategy/28-customer-outcomes.mdx","bytes":6687,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nStatus: CANONICAL · Commercial OS\nOwner: Customer Success + Product Marketing\nLast verified: 2026-07-21\n\n---\n\n## Purpose\n\nThe outcome catalog: what measurably changes for customers, by department and by timeframe. Value messaging ([16](../03-positioning-messaging/16-value-proposition.md)) says what we promise; this defines what we _count_ — the outcomes CS commits to, sales sells against, and case studies prove.\n\n**Target audience:** CS (success plans), sales (business cases), marketing (proof content).\n\n---\n\n## 1. The Outcome Model\n\nEvery customer outcome is one of three kinds (mapping to the value streams):\n\n| Kind                    | Definition                                               | Counted as                                                  |\n| ----------------------- | -------------------------------------------------------- | ----------------------------------------------------------- |\n| **Time outcomes**       | Context reconstruction eliminated; preparation delegated | hours/person/week reclaimed                                 |\n| **Decision outcomes**   | Signals surfaced earlier, grounded in evidence           | catches: churn risks, expansion signals, missed commitments |\n| **Continuity outcomes** | Knowledge that survives people/tools/models              | ramp time, handover time, retention of account memory       |\n\n## 2. Outcome Catalog by Department\n\n### Customer Success (wedge — the committed set)\n\n| Outcome                  | Baseline (typical)                           | Target (90 days)                        | Measurement                          |\n| ------------------------ | -------------------------------------------- | --------------------------------------- | ------------------------------------ |\n| Morning context assembly | 45–60 min/day, 8 tabs                        | ≤ 10 min, one workbench                 | time-to-context; user survey         |\n| QBR/EBR prep             | ~4 hours each                                | ≤ 30 min (design-partner best: 12 min)  | prep-time sampling                   |\n| Churn-risk visibility    | after the score moves / after the call       | signal with evidence before score moves | risk catches with evidence chains    |\n| Account handover         | multi-hour file assembly, lossy              | transfer-ready context, same-day        | handover time; receiving-CSM survey  |\n| Expansion signal capture | scattered across billing/usage/conversations | surfaced on the bench with evidence     | expansion catches → pipeline created |\n\n### Sales (first expansion)\n\nDeal-thread continuity (no lost context between discovery → demo → proposal → legal) · silent-champion alerts · forecast claims backed by evidence chains · outreach drafts grounded in account truth. Counted: cycle time signal→outreach, forecast variance, rep prep time.\n\n### RevOps / Operations (second expansion)\n\nReporting latency hours → minutes · duplicate resolution with human review · integration request backlog → connector enablement · every field with provenance (\"version 3 of the dashboard\" retired). Counted: report turnaround, dedupe backlog, integration queue length.\n\n### Executive\n\nOne governed view over customers/revenue/commitments · surprises converted to signals · institutional memory independent of tenure. Counted: decision latency on flagged risks; exec-visible signal precision.\n\n## 3. The Outcome Timeline (set expectations honestly — this sequence closes deals _and_ renewals)\n\n| Period        | What's real                                                                                                                                                                          | What's not yet                      |\n| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------- |\n| **Day 1**     | Connected tools hydrate; workbench opens on assembled truth; first _what changed_                                                                                                    | Twin's pattern depth (thin history) |\n| **Week 1**    | Morning ritual replaced; first approved Twin actions; first evidence-backed signal                                                                                                   | Cross-account patterns              |\n| **Month 1**   | Time outcomes measurable (target ≥ 60% of gathering time reclaimed); TruthLayer accumulating verified knowledge                                                                      | Full continuity value               |\n| **Quarter 1** | Decision outcomes: documented catches; QBR prep at target; first realized-value review                                                                                               | —                                   |\n| **Year 1**    | Continuity outcomes: ramp/handover transformed; the Spine's knowledge is organizationally irreplaceable — the renewal argument ([47](../08-customer-success/47-renewal-strategy.md)) | —                                   |\n\nCanonical continuity math (verbatim, from canon): _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 that leaves with the people no longer matters._\n\n## 4. Outcome Instrumentation Rules\n\n- Baselines are captured **in discovery** ([38](../07-sales/38-discovery-guide.md)) — a deal without baseline numbers cannot have an outcome review later. No baseline, no case study.\n- Every success plan ([44](../08-customer-success/44-customer-success-playbook.md)) commits to ≤ 3 outcomes with numbers and dates.\n- Realized-value reviews quarterly; results feed case studies ([64](../12-corporate/64-case-study-templates.md)) and renewal decks.\n- Anti-gaming rule: outcomes are counted from user-visible artifacts (time samples, catches with evidence links), never from raw usage telemetry alone.\n\n**KPIs:** % of customers with instrumented baselines (target 100%); outcome attainment rate at 90 days; documented catches per customer per quarter; outcome-backed renewal rate ([75 CS Metrics](../13-operations/75-customer-success-metrics.md)).\n\n---\n\n**Related:** [29 ROI Framework](29-roi-framework.md) · [16 Value Proposition](../03-positioning-messaging/16-value-proposition.md) · [44 CS Playbook](../08-customer-success/44-customer-success-playbook.md) · [64 Case Studies](../12-corporate/64-case-study-templates.md)\n"}