PPactDocs
Sales Engineering

Playbook & demo-script library

A versioned library of playbooks, battlecards, and demo scripts with hybrid semantic-plus-keyword search, per-playbook usage analytics, and AI-assisted gap detection.

The playbook library is your team's institutional knowledge, kept current instead of rotting in a wiki. It holds the reusable assets of a technical sale — discovery guides, battlecards, ROI frameworks, objection libraries, and demo-script narratives — each versioned, searchable, and measured.

Facets and versioning

Every playbook is written in markdown and organized by facets: vertical, deal-size band, competitor, and type. That makes the library filterable to the exact situation you're in — "enterprise fintech, competing against X." Full version history is kept per playbook, so you can see how an asset evolved and roll back if an edit misfires.

Pact ships a curated starter library so you're not staring at a blank shelf on day one. The starter content is tenant-owned and fully editable — a seed to build on, not fixed content you're stuck with.

Search blends semantic similarity with keyword overlap, so you find the right playbook whether you remember its exact wording or only the gist of it. When no AI embeddings are available, search degrades gracefully to keyword-only — you still get results.

Usage analytics

Each playbook tracks how it's actually used: viewed, used in a deal, dismissed, and won. Over time this tells you which assets are earning their place and which are dead weight — the difference between a library people trust and one they route around.

Demo scripts

Structured demo scripts are a distinct builder alongside the playbooks. A demo script is an ordered sequence of blocks you can customize for a specific prospect and mark as rehearsed as you prepare. It's the difference between a freeform narrative and a repeatable, staged walkthrough.

Gap detection

Pact can analyze your library against your active deals and surface gaps — topics, competitors, or objections your playbooks don't yet cover — as AI-assisted suggestions you can accept or dismiss. It's a way to keep the library ahead of what your reps are actually hitting in the field.

Gap suggestions are assistive, not automatic

Detected gaps are proposals. Nothing is added to your library until you accept a suggestion, so the library stays curated rather than auto-filled.

What's next