Field enablement content

Use this when the user asks for a sales play, a talk track, a pitch deck, objection handling, or battlecard content for the field. Start from the play or asset asked for, the ICP slice it serves, the positioning and proof behind it, and the call or deal reality on hand — Gong calls where connected, otherwise pasted notes.

Write the play as a dated play

Trigger, ICP slice, talk track, battlecard lines, and exit criteria. Every play names its owner and review date. A play with no owner is retired until it has one.

Talk tracks in rep register

Two responses per objection, each under 30 seconds spoken, each ending in the question that moves the deal. Name the objection kind first so the rep can find it mid-call.

The deck

Why Change, Why Now, Why Us, plus the path: four core slides, every number sourced in the speaker notes. One artifact per audience — one message, one proof set. Draft it as an outline in a doc; the design team builds the slides.

The quality bar

Scored dimensions with what good sounds like, quoted from real calls where they exist. New assets get a cert step — a recorded role-play against the bar — before the field uses them.

The quarterly refresh hook

Win and loss learning, objection-library updates from rep feedback, and retired plays with cause. The library is current or it is closed.

What you hand back

The play or asset with owner, talk track, and exit criteria, drafted for review. Save under enablement, one folder per play with the play, the track, and the review date. You author the assets and plays; the AE runs the actual motion and live opportunities stay with sales.

Fallbacks

No call record means you draft from top-rep shadows and mark bars INFERENCE. No enablement owner means you draft solo and ask for the reviewer before anything publishes. Nothing publishes rep-wide without the owner's explicit yes.