Content supply chain rebuilt for retrieval (L6)
Rebuild enablement content as a maintained corpus with owners, expiry dates, and machine readable structure, because agents and reps both read it now. Decks become an output of the corpus, not the corpus itself.
The steps
- 01
Inventory and kill
Tool: Notion
Inventory everything reps and agents can reach. Delete or archive anything without an owner or without use in the last two quarters. Stale content is the main cause of wrong agent answers. Owner: enablement leader. DoD: archive is complete and irreversible for the current quarter.
- 02
Give every asset an owner and expiry
Tool: Notion
No asset enters the corpus without a named owner and a review date. On expiry it is reviewed or removed automatically, not flagged for someone to ignore. Pitfall: review reminders with no removal action. DoD: expiry enforcement is automatic.
- 03
Structure for machines
Tool: Manual
Consistent headings, explicit claims with sources, product and segment metadata. Retrieval quality is mostly a content structure problem, not a model problem. Owner: content ops. DoD: structure standard published and applied to the top fifty assets.
- 04
Generate decks from the corpus
Tool: Claude
Customer facing decks are generated from corpus sections so the source of truth stays single. When the corpus changes, regenerate rather than hand patch. Owner: product marketing. DoD: at least the core pitch deck is generated from corpus sections.
Tools in this playbook
Next playbooks
Unfamiliar terms are defined in the AI and Revenue Dictionary. Related frameworks live in the framework library.