FeaturePlaybooks

The playbook is a 90-page Google Doc. Last opened: 4 months ago.

Visual playbooks reps actually follow.

Kanban boards that map content to deal stages. Each card links to the asset, with notes on who it’s for and when to use it. Not a document. A system.

Updated September 2026

Sales playbook software maps your content to each stage of the deal, so reps know exactly what to send and when. Content Camel’s Playbooks are visual Kanban boards, not a PDF: each card links to the current asset, with positioning notes attached.

The Problem

The playbook problem

Your playbook is a Google Doc or PDF. Reps read it during onboarding and never open it again. It’s reference material, not a workflow.

The playbook says ‘send the case study at this stage’ but doesn’t say which case study, where to find it, or which version is current.

When the playbook gets updated, nobody knows. There’s no notification, no tracking, no way to tell who’s running old plays.

Different reps run different plays for the same scenario. No consistency. No best-practice sharing.

The Cost

What happens without visual playbooks

New reps wing it. They don’t know which content to send at which stage. They use whatever the last rep they talked to mentioned.

Best practices live in people’s heads. Your top rep knows exactly which case study to send after a demo. Your bottom three reps don’t. That knowledge never gets documented.

The 90-page Google Doc playbook gets opened once. During onboarding. Then never again. It’s a reference doc pretending to be a workflow.

Content and process are disconnected. The playbook says ‘send relevant case study at Stage 3.’ But which case study? Where is it? Is it current?

The Fix

What Playbooks gives you

Visual Kanban layout

Content in swim lanes matched to your sales stages. Discovery → Evaluation → Proposal → Close. The whole play at a glance.

Linked content, not references

Each card links directly to the asset. One click to open, share, or generate a tracking link.

Positioning notes

For every asset in the playbook: who it's for, when to send it, what to say about it. Context alongside content.

Multiple playbooks

Enterprise motion, SMB motion, vertical-specific plays. Each tailored. Reps get the playbook that matches their deals.

New hire acceleration

Build an onboarding playbook. Day one, new reps have a structured guide with every asset linked and positioned.

See Playbooks in action

Short walkthrough video — coming soon

In Practice

How teams use Playbooks

Marketing builds an Enterprise playbook

Create a Kanban board with stages: Prospecting → Discovery → Demo → Proposal → Close. Drag the right assets onto each stage card. Add notes: ‘This ROI calculator works best when the CFO is in the room.’ Reps see the plays, not a wall of text.

New rep onboarding in week one

Instead of a 90-page PDF, the new hire gets three playbooks: Enterprise, Mid-Market, and Partner. Each one maps content to their sales process. They see what to send, when to send it, and why. Ramp time shrinks.

Competitive deal against a specific vendor

A competitive playbook for deals against Vendor X. Battle card, comparison matrix, case study from a customer who switched, objection-handling one-pager. All linked, all current, all in one view.

Marketing updates the Q2 plays

New case study drops. Marketing drags it onto the right stage in the playbook. Every rep sees the update automatically. No email announcement. No Slack thread that gets buried.

Visual

Kanban, not PDF

Linked

assets, not references

Multiple

playbooks per team

"We're going through the motions of downloading our content, putting it in SharePoint just to have it and reorganizing it."
Content Operations, IT Platform — on their content workflow before a real system
FAQ

Frequently asked questions

What's the difference between a playbook and the content library?

The library is where content lives. A playbook is the workflow layered on top: which asset to send, at which stage, and why. Think of the library as the what and the playbook as the when.

Can I build more than one playbook?

Yes. Most teams run a few in parallel, enterprise, SMB, a specific vertical, or partner motion. Each is a separate Kanban board tailored to that motion.

What happens when I update a playbook?

Drag a new asset onto a stage and every rep sees the update automatically. There’s no email announcement to send and no Slack thread to bury it in.

Do playbook cards go stale like a PDF would?

No. Each card links directly to the live asset in the content library, so if the asset gets replaced, the playbook always points to the current version.

Can I use playbooks for new rep onboarding?

Yes, it’s one of the most common uses. Build an onboarding playbook and new hires get a structured, clickable guide from day one instead of a 90-page PDF. See Sales Onboarding.

What are positioning notes?

Context attached to each card: who the asset is for, when to send it, and what to say about it. It’s the knowledge your best rep has in their head, written down where everyone can see it.

Is a playbook the same as a sales process in the CRM?

No. Your CRM tracks the deal. A Content Camel playbook maps content to your sales stages so reps know exactly what to send at each one; the two work alongside each other.

Ready to replace the PDF playbook?

Build a visual playbook in under an hour. Free plan available.