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 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 headline value proposition, a problem statement, three differentiators, one proof point or customer quote, and a clear CTA with a named contact. Keep it scannable in 30 seconds with bold headers, short bullets, and generous whitespace on a single page.

No. Public-facing competitor comparison and alternatives pages are handled by the competitors skill, which focuses on SEO-oriented content. This skill covers internal sales collateral like battle-card-style objection responses and competitive positioning within playbooks.

Define inputs the prospect provides (team size, current tool costs, time on manual work), formulas computing time and cost savings, and outputs showing annual ROI, payback period, and 3-year value. Keep assumptions conservative and transparent, and validate them live during the call.

Avoid generic decks when selling to distinct personas or deal stages. A CTO deck should emphasize architecture and integrations, while a CFO deck leads with ROI and payback. Reps rewriting your deck before sending it signals the deck was too generic.