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. Customize emphasis based on whether the buyer is technical, economic, or a champion.

Categorize objections into price, timing, competition, authority, status quo, and technical buckets. For each, document the objection verbatim, the underlying concern, a response approach, a proof point, and a follow-up question. Provide both a quick-reference table for live calls and a detailed version for training.

A one-pager needs a problem statement, your solution, three differentiators, one strong proof point or customer quote, and a clear CTA with a specific contact. It must fit on a single page, be scannable in 30 seconds, and use bold headers with short bullets.

A first demo script should run 30-45 minutes: 5 minutes opening and discovery recap, 25 minutes walking through 3-4 workflows mapped to the prospect's stated pain, a brief proof point, and 5 minutes closing with specific next steps and a scheduled follow-up.

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.

Define inputs the prospect provides (team size, current tool costs, time on manual processes), a calculation methodology for time and cost savings, and outputs showing annual ROI percentage, payback period, and 3-year value. Keep assumptions conservative and validate them live during the call.