Using Claude Code for sales enablement materials

How I use Claude Code for sales enablement: building battle cards, one-pagers, and objection-handling docs from existing content and competitive data.

· Page Sands

Sales enablement materials are one of those things every GTM team knows they need and nobody has enough of. Battle cards go stale. One-pagers exist for the flagship product but not the new feature. Objection-handling docs live in someone’s head instead of a shared folder.

I started using Claude Code for sales enablement after realizing most of these materials follow predictable structures. The inputs already exist somewhere in the company. The work is pulling them together into a format a rep can use on a call.

What sales enablement materials actually are

If you’re on the marketing side and haven’t spent much time building these, here’s what sales teams typically need:

Battle cards. One-page comparisons against a specific competitor. Pricing differences, feature gaps, positioning angles, objection responses. Reps pull these up before or during a call when a prospect mentions a competitor by name.

One-pagers. Single-page summaries of a product, feature, or use case. Written for the buyer, not the internal team. These get attached to follow-up emails or shared in a deal room.

Objection-handling guides. Common pushback and how to respond. “We already have a tool for that.” “It’s too expensive.” “We’re not ready for AI yet.” Each objection paired with a response framework and proof points.

Call prep briefs. Background on a specific prospect before a meeting. Industry context, likely pain points, relevant case studies, competitive landscape for that account.

Most teams have some of these. Few have all of them. Fewer still keep them current.

Why Claude Code works well here

These documents share a pattern. They take information that already exists (product docs, pricing pages, competitive analysis, blog posts, case studies) and repackage it for a specific audience and moment.

Claude Code can read multiple source files in one session and produce structured output. It’s reorganizing what you already have into the format a rep needs.

The competitive intel workflow I wrote about produces structured competitor data. That data is one of the primary inputs for battle cards. The two workflows connect directly.

Building a battle card with Claude Code

Here’s how I build a battle card in a single Claude Code session.

I start by pointing Claude Code to three sources: the competitive analysis file for that competitor, our own product’s feature list or docs, and any existing positioning notes from brand/positioning.md.

Then I ask it to produce a battle card following this structure:

# [Competitor Name] Battle Card

## Overview
One paragraph on who they are and where they compete with us.

## Where we win
- Point 1 (with specific evidence)
- Point 2

## Where they win
- Point 1 (be honest, reps need to know this)

## Pricing comparison
| Tier | Us | Them |
|------|----|----- |

## Common objections when this competitor comes up
- "They have [feature X]" → Our response
- "They're cheaper" → Our response

## Proof points
- Customer quote or case study reference
- Metric or result

## Last updated: [date]

The “where they win” section matters. Reps lose credibility fast if they pretend a competitor has no strengths. An honest battle card builds trust with the sales team and prepares them for real conversations.

The whole process takes about 15 minutes per competitor. Most of that time is reviewing the output and tightening the language.

Building one-pagers

One-pagers follow a similar process but with different inputs. Instead of competitive data, the primary source is product documentation and customer outcomes.

I ask Claude Code to read the relevant product docs and any case studies, then produce a one-pager with:

  • A headline that states the value proposition in one line
  • Three to four bullet points on what the product or feature does
  • One specific customer result or metric
  • A clear next step (demo link, contact, free trial)

It has to fit on one page. Claude Code’s first draft is usually too long. I ask it to cut by 30% and the second version is closer to what works.

Objection-handling docs

For objection docs, the input is different. It comes from actual sales conversations. If your team logs call notes or records calls, those are the source material.

I collect the five or six most common objections from the sales team (or from call recordings if available), then run a Claude Code session that produces a response framework for each:

## "We already use [competitor]"

**Acknowledge:** They're a solid tool for [use case].
**Reframe:** Where we differ is [specific capability].
**Evidence:** [Customer name] switched from [competitor] because [reason].
**Ask:** What's the one thing you wish [competitor] did better?

The structure gives reps a pattern without a script. They can adapt the response to the conversation instead of reading a canned answer.

Keeping materials current

Stale battle cards with old pricing do more harm than no battle card at all. Reps learn to ignore materials they can’t trust.

This is where the competitive intel workflow pays off. Every time I run a competitive analysis session, I check whether the battle cards still reflect current competitor data. If a competitor changed their pricing or launched a new feature, the battle card update takes five minutes because the new data is already structured.

I add a “Last updated” date to every document. If a rep sees a date more than 60 days old, they know to flag it.

What I’d do differently with a larger team

This workflow is built for a small team where one person handles both marketing and sales enablement. On a larger team, I’d set up a shared folder structure where battle cards, one-pagers, and objection docs each have their own directory. I’d also create a Claude Code command that checks all materials against the latest competitive data and flags anything outdated.

The inputs would also get richer. Call recording transcripts, CRM notes on lost deals, customer interview summaries. More source material means better output.

But the core workflow stays the same: read existing source material, produce a structured document for a specific sales moment, review and ship.

Getting started

Pick one competitor and build a battle card. That’s the fastest way to see whether this workflow produces something your sales team would actually use.

If your team doesn’t have competitive data structured yet, start with the competitive intel workflow first. The sales enablement layer works best when it has structured inputs to draw from.

If the battle card is useful, do the next competitor. Then build a one-pager for your most common use case. Each document takes 15 to 20 minutes. Within a couple of hours you have a Claude Code sales enablement library that would have taken a week to build from scratch.