ThinkWithPrompt by SynotticThinkWithPrompt

Build a launch enablement kit for sales and support

Internal talk tracks, FAQs, and objection handling so customer-facing teams can explain a new feature correctly.

SalesRTFStandardFill-in Template

The prompt

Create an internal enablement kit so sales and support can handle a new feature launch. Feature: [WHAT IT DOES] Problem it solves and for whom: [SEGMENT, USE CASE] Availability: [PLANS, REGIONS, PLATFORMS, ROLLOUT DATES] Limitations and known issues: [LIST] Pricing or packaging impact: [DETAILS - or "none"] Proof available: [BETA RESULTS, QUOTES - or "none yet"] What it does NOT do: [COMMON MISUNDERSTANDINGS TO PREVENT] Create: 1. A one-paragraph summary any employee can repeat. 2. Sales talk track: who to bring it up with, a discovery question that surfaces the need, a 3-sentence pitch, and a demo flow in 3-5 steps. 3. Objection handling: 5 likely objections or tough questions with honest answers. 4. Support FAQ: 8-10 questions customers will ask, including setup, permissions, limits, and troubleshooting, with answers. 5. Escalation: what counts as a bug versus a feature request, and where each goes. 6. Do-not-say list: claims, comparisons, or roadmap promises to avoid. Use only facts I provide. Mark anything uncertain [CONFIRM WITH PRODUCT]. Keep the whole kit scannable in under 5 minutes.

Highlighted [brackets] are blanks to replace with your own details.

Fill in the blanks and use this promptMore Sales prompts

What to fill in

  • WHAT IT DOES
  • SEGMENT, USE CASE
  • PLANS, REGIONS, PLATFORMS, ROLLOUT DATES
  • LIST
  • DETAILS - or "none"
  • BETA RESULTS, QUOTES - or "none yet"
  • COMMON MISUNDERSTANDINGS TO PREVENT
  • CONFIRM WITH PRODUCT

How this prompt is built

This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.

Related prompts

Find more prompts like this