How to Run Your Sales Enablement Department on Four Persistent Threads

Your enablement team is two people. Maybe three. And right now, somewhere in your Slack, a rep is about to walk into a competitive deal with a battlecard that hasn’t been updated since your last product launch. Your onboarding deck still mentions the pricing tier you retired eight months ago. A new rep finished their first week and you haven’t had time to review a single call recording.

This isn’t a resourcing problem. It’s a structure problem. The volume of things that need to stay current — battlecards, call coaching, onboarding materials, certification tracking, competitive response — was designed for a team five times the size of the one you have. And because you’re always behind on the last thing, you never get ahead of the next one.

Claude Cowork changes the structure. Not by giving you more hours, but by running the parts of enablement that are high-frequency and low-creative-lift on your behalf — so you can focus on the judgment calls that actually require you.

---

What You’ll Build

Four persistent threads, each owning a specific slice of enablement:

1. Playbook Watchdog — monitors competitive news and flags which battlecard sections need updating

2. Call Coaching Brief — processes transcripts from Gong or Chorus and returns structured coaching output

3. Onboarding Refresh Monitor — maps product and pricing updates to specific sections of your onboarding materials

4. Rep Readiness Tracker — takes certification data and surfaces who needs attention before a launch or territory change

Plus a fifth on-demand thread — the Competitive Flash Brief — that you trigger manually when a competitor makes a major move.

---

Step 1: Setup

Before you start building threads, gather the context that makes these useful. Enablement Cowork is different from general-purpose Cowork — the output quality scales directly with the structural context you provide upfront.

Before creating each thread, have on hand:

• Your current battlecard template (sections, headers, format)

• Your call coaching rubric (what “good discovery” looks like, what you’re scoring for)

• Your onboarding outline or table of contents

• Your certification list (what programs exist, what completion looks like)

You don’t need perfect documents. A rough outline works. The thread just needs to know what structure you’re working within so it can map its output to the right place.

Claude Cowork runs on Claude for iOS, Android, and Desktop. Each thread is persistent — the context you seed it with on day one stays active. You don’t re-explain the structure every session.

---

Step 2: Playbook Watchdog Thread

Create a new Cowork thread. Name it: Playbook Watchdog.

Seed it with this prompt, filling in your actual battlecard structure:

You are my Playbook Watchdog. Your job is to monitor competitive news I share with you
and flag which sections of our battlecards or objection-handling guides need updating
based on what's changed.

Our battlecard structure is:
[Paste your battlecard template here — competitor overview, differentiators, pricing
comparison, common objections + responses, when we win/lose, discovery triggers]

Our objection-handling guide covers:
[List the main objection categories — pricing, integration, company size, feature gaps, etc.]

When I paste competitive news or announcements, do the following:
1. Identify which competitor the news is about
2. Flag the specific battlecard section(s) affected
3. Draft a suggested update for each flagged section
4. Note any sections that remain accurate and don't need changes

Output format:
**Competitor:** [Name]
**Sections affected:** [List]
**Suggested updates:** [Draft text for each section]
**Sections still accurate:** [Confirm what holds]

I will paste competitive news. You will map it and draft the updates. I review and approve
before anything changes.

Once seeded, the thread runs weekly. You paste in whatever competitive news surfaced that week — a product announcement, a pricing change, a review site trend, an analyst report. The thread tells you what’s stale and drafts the fix.

---

Step 3: First Result

Run it once before moving forward. Paste the most recent competitive news you have — even something small — and see what it returns. The first output tells you whether the battlecard structure you seeded is specific enough.

If the output is vague (”the pricing section may need updating”), add more specificity to your battlecard template in the seed prompt. If it’s mapping correctly to specific objections and drafting credible updates, you’re ready to keep going.

One working thread. That’s your first win.

---