Enablement Content Generation

Field enablement content has a perverse economics problem. The senior field engineer who could write the perfect battlecard is the same person whose hour is most expensive — they spend it on customer calls instead. So battlecards get written by whoever has bench time, get out of date by the next quarter, and quietly stop being trusted.

This workflow inverts that. The senior FE provides the judgment; the agent provides the drafting. They produce 10x more enablement content at the same FE cost.

The cadence problem

The pre-agent version of this workflow had the FE writing the draft from scratch — a 2-3 hour task they kept deferring. The agent-assisted version takes 30-40 minutes total: 5 for the brief, 5 for the agent run, 15-25 for the edit.

That cadence change is the whole story. When new content is cheap to produce, you produce it when it's actually needed. The library stops being a museum of last year's positioning.

What the FE brief looks like

The brief is structured deliberately to match the agent's downstream prompt. Five bullets, every time:

• Why this exists now — what triggered it (lost deal, comp launch, new ICP segment)
• Specific audience — role + industry + size
• The two or three claims they make — what the competitor says or the prospect asserts
• The one thing we usually fumble in response — the move we want sharper
• The piece of evidence we have — a real customer story, a real metric, a real architectural fact

The brief is the work. Once it exists, the agent draft is straightforward.

The system prompt that travels

You are a senior field engineer producing internal enablement content for AEs.
Tone: terse, confident, no marketing language, no exclamation points.
Output: Markdown matching the team's battlecard template.

Sections, in order:
1. The setup (1-2 sentences on when this objection lands)
2. The wrong response (what AEs reflexively say that doesn't work)
3. The right response framing (one paragraph, in AE voice)
4. The evidence to cite (the real customer / metric / architectural fact)
5. The pivot (if they push back further, where to take it)
6. The disqualifier (when to walk away rather than win this argument)

Length: 350-500 words. Density beats completeness.

The reader is a working AE who has read 100 battlecards. Write for them.

The "disqualifier" section is the senior-FE move. Junior content writers never include it because they're trying to win every objection. Senior FEs know that some prospects aren't a fit and the right move is to name that clearly. Forcing the section makes the output feel senior.

The review step nobody skips

Skipping the review is the most common adoption failure. The math is seductive: "the draft is already 90% there, let's just publish it." It's not 90% there. It's 80% there, and the missing 20% is exactly the high-stakes 20%.

Adoption pattern

The FE who first adopts this becomes the bottleneck for ~3 weeks, because they're the only one with both the workflow and the editorial taste. Then their templates spread, junior FEs start using them, and the bench-time-vs-content-quality tradeoff inverts permanently.

The KPI worth tracking: time from trigger to shipped content. If it stays under 48 hours, the workflow is working. If it slips past a week, the bottleneck has moved (usually to legal review or to the central enablement team's calendar) and that's the next problem to solve.