Write a sales enablement brief

You are a product marketing manager writing enablement for sales and customer success. Reps read enablement minutes before a call, so the brief must be scannable and give them words they can say. The two biggest risks are reps not knowing who the feature is for, so they pitch it to everyone, and reps over-promising (roadmap items, unsupported plans, unproven results), which creates churn and support escalations later.

Only if [TARGET_CUSTOMERS] is given: Target customers: [TARGET_CUSTOMERS]

Feature:

1. Write what shipped in one sentence a rep could say out loud.
2. Define who it is for: the ideal customer, the buyer and user roles, the trigger situations that signal a fit, and who it is not for.
3. Explain why it matters: the customer problem, the before-and-after, and the business value, using only proof in the feature notes.
4. Write a 30-second talk track and a two-minute version, in natural spoken language.
5. Give four to six discovery questions that reveal whether the customer has the problem.
6. Handle likely objections (price, "we already use X", timing, security or compliance, effort to adopt): objection, response, and proof or next step.
7. List what not to say or promise: unreleased capabilities, plans or regions where it is not available, performance claims without proof, and comparisons the company cannot support.
8. Summarise availability, pricing and packaging, and how to enable it for a customer.
9. Write an FAQ with six to ten questions reps and customers will ask, and the resources to link (placeholders).

• Use only facts in the feature notes. Missing facts become [CONFIRM: what] in the brief, never guesses, especially for pricing, availability and competitor claims.
• Competitive positioning only from information given; if none is given, write how to handle "how is this different from X" without naming specific competitor weaknesses.
• Scannable: short bullets, bold lead words, no paragraph longer than three lines.
• Internal only: mark it as not for forwarding to customers.

A heading "Internal - not for customers", then these H2 sections in order: In one line, Who it is for, Why it matters, Talk track, Discovery questions, Objections (as a table: objection | response | proof or next step), What not to say, Availability and pricing, FAQ, Resources.