sales-enablement

Use the 10-12 slide framework: current world problem, cost of inaction, market shift, your approach, product walkthrough, proof points, case study, implementation timeline, ROI, pricing, and next steps. Tell a story arc rather than presenting a feature tour, and customize emphasis by buyer type.

Categorize objections into price, timing, competition, authority, status quo, and technical groups. For each, document the exact objection, the real concern behind it, a response approach, a proof point, and a follow-up question. Provide both a quick-reference table for live calls and a detailed doc for training.

A one-pager needs a problem statement, your solution summary, three differentiators, one strong proof point or customer quote, and a clear CTA with a specific contact. Keep it scannable in 30 seconds with bold headers, short bullets, and whitespace — literally one page.

A first demo runs 30-45 minutes: a 5-minute opening recapping discovery findings, 2-3 workflows mapped to the prospect's stated pain, a brief proof point, and a 5-minute close proposing specific next steps. Ask interaction questions after each workflow rather than talking uninterrupted.

Public-facing comparison and alternatives pages for SEO belong to a competitors-focused skill, not sales enablement. Sales enablement covers internal materials like battle cards and objection docs that reps use during deals, not published website content.

Generic playbooks fail because reps rewrite or ignore them. Effective playbooks use reps' own language, involve top performers in creation, and are reviewed quarterly with an assigned owner. Untailored templates signal low effort and stall deals.