28 — Customer Outcomes
Status: CANONICAL · Commercial OS
Owner: Customer Success + Product Marketing
Last verified: 2026-07-21
Purpose
The outcome catalog: what measurably changes for customers, by department and by timeframe. Value messaging (16) says what we promise; this defines what we count — the outcomes CS commits to, sales sells against, and case studies prove.
Target audience: CS (success plans), sales (business cases), marketing (proof content).
1. The Outcome Model
Every customer outcome is one of three kinds (mapping to the value streams):
| Kind | Definition | Counted as |
|---|---|---|
| Time outcomes | Context reconstruction eliminated; preparation delegated | hours/person/week reclaimed |
| Decision outcomes | Signals surfaced earlier, grounded in evidence | catches: churn risks, expansion signals, missed commitments |
| Continuity outcomes | Knowledge that survives people/tools/models | ramp time, handover time, retention of account memory |
2. Outcome Catalog by Department
Customer Success (wedge — the committed set)
| Outcome | Baseline (typical) | Target (90 days) | Measurement |
|---|---|---|---|
| Morning context assembly | 45–60 min/day, 8 tabs | ≤ 10 min, one workbench | time-to-context; user survey |
| QBR/EBR prep | ~4 hours each | ≤ 30 min (design-partner best: 12 min) | prep-time sampling |
| Churn-risk visibility | after the score moves / after the call | signal with evidence before score moves | risk catches with evidence chains |
| Account handover | multi-hour file assembly, lossy | transfer-ready context, same-day | handover time; receiving-CSM survey |
| Expansion signal capture | scattered across billing/usage/conversations | surfaced on the bench with evidence | expansion catches → pipeline created |
Sales (first expansion)
Deal-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.
RevOps / Operations (second expansion)
Reporting 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.
Executive
One 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.
3. The Outcome Timeline (set expectations honestly — this sequence closes deals and renewals)
| Period | What's real | What's not yet |
|---|---|---|
| Day 1 | Connected tools hydrate; workbench opens on assembled truth; first what changed | Twin's pattern depth (thin history) |
| Week 1 | Morning ritual replaced; first approved Twin actions; first evidence-backed signal | Cross-account patterns |
| Month 1 | Time outcomes measurable (target ≥ 60% of gathering time reclaimed); TruthLayer accumulating verified knowledge | Full continuity value |
| Quarter 1 | Decision outcomes: documented catches; QBR prep at target; first realized-value review | — |
| Year 1 | Continuity outcomes: ramp/handover transformed; the Spine's knowledge is organizationally irreplaceable — the renewal argument (47) | — |
Canonical 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.
4. Outcome Instrumentation Rules
- Baselines are captured in discovery (38) — a deal without baseline numbers cannot have an outcome review later. No baseline, no case study.
- Every success plan (44) commits to ≤ 3 outcomes with numbers and dates.
- Realized-value reviews quarterly; results feed case studies (64) and renewal decks.
- Anti-gaming rule: outcomes are counted from user-visible artifacts (time samples, catches with evidence links), never from raw usage telemetry alone.
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).
Related: 29 ROI Framework · 16 Value Proposition · 44 CS Playbook · 64 Case Studies