# Enable Sales Cs

> Structure sales and customer success enablement materials and collaboration workflows. Use this skill when a team needs to prepare sales and CS for a launch, feature update, or positioning change.

- Skill: `alexe-ev/enable-sales-cs` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add alexe-ev/enable-sales-cs`
- Raw SKILL.md: https://api.skillmd.com/api/skills/alexe-ev/enable-sales-cs/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: alexe-ev (https://skillmd.com/u/alexe-ev)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/alexe-ev/enable-sales-cs

---


# Enable Sales & CS

## Purpose
Help product teams create effective enablement for sales and customer success so they can accurately represent and support the product.

## Skill type
Conceptual skill

## Use this skill when
- A product launch requires sales and CS to be prepared
- Sales is pitching incorrectly or with outdated messaging
- CS is escalating questions that product should have documented
- A new feature needs internal rollout materials before external launch

## Do not use this skill when
- The goal is customer-facing marketing messaging (use develop-positioning-messaging)
- The product isn't ready for internal enablement yet

## Required inputs
- Feature or product being enabled
- Target sales or CS audience (AE, SDR, CSM, support)

## Optional inputs
- Positioning and messaging documents
- Common objections heard in sales
- CS support patterns and escalations
- Demo environment access

## Upstream context
Works best when:
- Positioning is defined
- Product is launch-ready or in beta

## Downstream handoff
Output can feed:
- plan-product-launch (enablement is part of the launch checklist)
- analyze-churn-retention (CS insights feed back into product)

## Instructions
1. Define what sales and CS need to know: positioning, value prop, use cases, objections.
2. Write a product overview brief (1-pager).
3. Write an objection handling guide.
4. Define what to demo and how.
5. Identify escalation paths for complex questions.
6. Define feedback loops from sales and CS back to product.

## Output
Provide:
- Product brief for internal use (positioning, key messages, use cases)
- Objection handling guide
- Demo flow outline
- Escalation paths
- FAQ (common questions with answers)
- Feedback loop process from CS/sales to product

## Risks / caveats
- Enablement materials that aren't used are wasted — design for how teams actually work
- Sales will sell what they can explain, not what is technically correct — simplify ruthlessly
- CS escalations are a product signal — close the feedback loop