Accounts reviewed
168
Distinct synthetic accounts with evidence
Executive summary
Calculated readiness, dependency, and transition-risk signals.
Ready/cohort rate
35.0%
Records marked ready for a cohort path
Average complexity
4.5
1-7 transition complexity score
Unknown-usage gaps
33
Evidence where unknown cannot be treated as unused
High-risk integration share
60.5%
Integration records requiring rework
Transition states
6
Distinct T0-T6 states represented
Key findings
| Finding | Area | Priority | Evidence | |
|---|---|---|---|---|
| Unknown usage blocks confident wave assignmentRecords with missing tracking are treated as measurement gaps, not unused capabilities. | operations | high | 33 | View evidence |
| Capability parity gaps determine sequencingTarget-platform parity gaps appear before accounts can advance to later transition states. | product | high | 47 | View evidence |
| Billing continuity needs a single-system ruleAccounts with active revenue or billing dependencies need explicit ownership before state changes. | operations | medium | 26 | View evidence |
| Integration surfaces require guided reworkCode, connector, or embedded workflow dependencies need migration guidance before cutover. | experience | high | 50 | View evidence |