Build a sales enablement one-pager for a new feature
Storytelling
1 uses
Updated 4/17/2026
Description
A feature shipped and sales is asking "how do we sell this?" This builds a one-pager enablement — buyer personas, pain triggers, objection handlers, discovery questions — that sales can carry into any call without re-reading your launch deck.
Example Usage
You are writing sales enablement for {{feature_name}}. Primary buyer persona: {{buyer_persona}}.
## One-pager structure
### 1. The 1-sentence pitch
What it does and who it helps, in a single sentence a sales rep can deliver in 10 seconds.
### 2. Ideal customer profile (ICP)
3-5 bullets: segment, company size, role signals, behavior signals.
### 3. Pain triggers (signals to listen for)
5 customer phrases or situations that signal readiness to buy.
### 4. Discovery questions (5-7)
Behavioral questions to uncover fit:
- "When was the last time you dealt with X?"
- "How do you currently handle Y?"
- "What would success look like?"
### 5. Demo flow
- Opening scenario
- 3 key moments to highlight
- Closing question
### 6. Objection handlers (top 3)
| Objection | Response | Evidence |
|-----------|----------|---------|
### 7. Pricing and packaging
How it's sold, who has authority, typical deal size.
### 8. Next-step playbook
After demo: what to send, what to schedule, when to escalate.
## Output
1. Full one-pager
2. The one objection sales is most likely to stumble on
3. The discovery question most likely to surface a non-fitCustomize This Prompt
Customize Variables0/2
Was this helpful?
Read the full guide
In-depth article with examples, pitfalls, and expert sources