This surface turns vendor overlap, renewal timing, hidden dependencies, migration blockers, and modeled savings into one executive view: replacement score, switching-risk map, savings narrative packets, and board-ready memo language.
| Lane | Owner | Status | Related findings | Focus | Next action |
|---|---|---|---|---|---|
| AI and identity replacement lane This lane is expensive and politically visible when the story outruns the migration reality. | AI platform and security operations | red | 4 | Stop treating agent and identity exits as easy wins while hidden approval and exception debt remains open. | Publish one dependency-clean exit packet before repeating the savings case in a board or investor memo. |
| Growth and analytics replacement lane This lane can fund credibility if it stops overpromising. | Growth analytics | yellow | 3 | Separate true overlap-tax wins from the replacements that still depend on messy attribution cleanup. | Lock one low-drama GTM retirement now and push the partial cases into a cleaner evidence pass. |
| Workflow and collaboration lane This is the cleanest board-friendly starting point. | Platform operations | green | 2 | Take the easy collaboration and workflow wins without pretending they solve the bigger platform sprawl narrative. | Use these ready exits to prove savings discipline while the harder replacements mature. |
| CRM and close-process lane This is where a rushed exit can damage trust instead of creating savings. | RevOps and finance systems | red | 3 | Do not book savings here until the hidden dependencies and close-process exceptions are documented honestly. | Build the dependency map first, then revisit the replacement case. |