JasonColapietro/suede-creator-skills / skills/suede-sales-enablement
suede-sales-enablement
VerifiedCreate rep-ready pitch decks, one-pagers, objection libraries, demo scripts, battle cards, proposals, buyer cards, and ROI models with a claim-source table. Use when asked to "build a competitive battle card" or refresh sales collateral. Distinguishes sourced proof from modeled value. NOT FOR: pricing strategy (use suede-pricing), offer design (use suede-offers), public comparison pages (use suede-competitors), outreach (use suede-cold-email), or unsupported proof.
| File | Kind | Size |
|---|---|---|
| CARD.md | markdown | 4.3 KB |
| SKILL.md | skill md | 16.3 KB |
| agents/openai.yaml | config | 584 B |
| evals/evals.json | config | 6.3 KB |
| references/deck-frameworks.md | markdown | 7.5 KB |
| references/demo-scripts.md | markdown | 11.4 KB |
| references/objection-library.md | markdown | 13.0 KB |
| references/one-pager-templates.md | markdown | 5.6 KB |
| references/worked-handoff.md | markdown | 1.7 KB |
references/one-pager-templates.md
View on GitHub# One-Pager Templates
Templates for different one-pager use cases, with layout guidance and copy prompts.
## Product Overview One-Pager
The default one-pager. Introduces your product to someone who knows nothing about you.
### Structure
```
[Logo] [Tagline]
HEADLINE: One sentence describing what you do and who it's for.
THE PROBLEM
2-3 sentences describing the pain your buyer faces.
THE SOLUTION
2-3 sentences describing how your product solves it.
WHY [YOUR PRODUCT]
• Differentiator 1: One sentence explaining the benefit
• Differentiator 2: One sentence explaining the benefit
• Differentiator 3: One sentence explaining the benefit
PROOF
"Customer quote with specific result." Name, Title, Company
[Optional: 2-3 metric callouts: "X% improvement", "Y hours saved"]
[CTA Button/Link] [Contact: name@example.com]
```
### Copy Prompts
- Headline: "What do you do, in one sentence, that makes someone say 'tell me more'?"
- Problem: "What is your buyer struggling with before they find you?"
- Differentiators: "If you could only tell them 3 things, what would make them choose you?"
---
## Use-Case Specific One-Pager
Tailored to a specific workflow, vertical, or problem. More targeted than the product overview.
### Structure
```
[Logo] [Use Case: e.g., "For Sales Teams"]
HEADLINE: How [your product] helps [persona] [achieve outcome].
THE CHALLENGE
When [persona] needs to [task], they face [specific pain].
This leads to [consequence]: [time wasted / money lost / risk].
HOW IT WORKS
1. [Step 1]: What happens and why it matters
2. [Step 2]: What happens and why it matters
3. [Step 3]: What happens and why it matters
RESULTS
• [Metric 1]: Before → After
• [Metric 2]: Before → After
• [Metric 3]: Before → After
CUSTOMER SPOTLIGHT
"Quote about this specific use case." Name, Title, Company
[CTA: "See it in action" or "Start a pilot"] [Contact info]
```
### When to Use
- Different buyer personas need different one-pagers
- Industry-specific versions (healthcare, fintech, e-commerce)
- Use-case versions (reporting, onboarding, security)
---
## Post-Meeting Leave-Behind
Designed to reinforce a conversation that already happened. Summarizes what you discussed and proposes next steps.
### Structure
```
[Logo] [Date of Meeting]
MEETING RECAP: [Company Name]
WHAT WE DISCUSSED
• [Pain point 1 they mentioned]
• [Pain point 2 they mentioned]
• [Goal they're trying to achieve]
HOW [YOUR PRODUCT] HELPS
• [Solution to pain 1]: [Specific capability or workflow]
• [Solution to pain 2]: [Specific capability or workflow]
• [How you help them reach their goal]
RELEVANT PROOF
"Quote from a similar customer." Name, Title, Company
[1-2 metrics from a similar customer]
PROPOSED NEXT STEPS
1. [Next step with date]
2. [Follow-up action]
3. [Decision timeline]
[Your name] | [Your title] | [Email] | [Phone]
```
### Tips
- Send within 24 hours of the meeting
- Reference specific things they said (shows you listened)
- Keep proposed next steps concrete and time-bound
- This is the asset your champion forwards to their boss
---
## Champion Enablement One-Pager
Designed specifically for your internal champion to share with their team and leadership. Written to make them look smart.
### Structure
```
[Logo]
WHY WE'RE EVALUATING [YOUR PRODUCT]
THE SITUATION
[2-3 sentences about the internal challenge, written as if the champion
is explaining it to their team. Use "we" and "our" language.]
WHAT [YOUR PRODUCT] DOES
[1-2 sentences. Plain language, no jargon.]
WHY THIS SOLUTION
• [Reason 1]: How it solves our specific problem
• [Reason 2]: How it compares to what we do today
• [Reason 3]: How it compares to alternatives we evaluated
EXPECTED IMPACT
• [Metric]: Current state → Expected state
• [Metric]: Current state → Expected state
• [Time to value]: Live within [X weeks]
WHO ELSE USES IT
[2-3 recognizable company names in their industry]
"Relevant customer quote." Name, Title, Company
NEXT STEPS
• [What we're doing next]
• [What we need from the team]
• [Decision timeline]
Questions? Talk to [Champion name] or [Your name at email].
```
### Why This Works
- Written in the champion's voice, not yours
- Answers the questions their boss will ask
- Includes peer proof from companies they respect
- Clear ask and timeline to drive internal momentum
---
## Layout Guidance
### Visual Hierarchy
1. **Headline**: Largest text, top of page, immediately communicates value
2. **Section headers**: Bold, clear, act as scannable anchors
3. **Body text**: Short sentences, bullet points preferred over paragraphs
4. **Proof elements**: Metrics and quotes should visually stand out (larger font, color, or callout box)
5. **CTA**: Prominent placement, bottom of page or bottom-right
### Whitespace
- Margins: at least 0.75" on all sides
- Space between sections: enough to visually separate (don't cram)
- If it feels crowded, cut content. Never shrink font below 9pt.
### Font Sizing
| Element | Suggested Size |
|---------|---------------|
| Headline | 18-24pt |
| Section headers | 12-14pt bold |
| Body text | 10-11pt |
| Fine print / footer | 8-9pt |
### Color
- Use brand colors for headers and accents
- Keep body text dark (black or near-black) on white
- Limit accent colors to 1-2 for visual consistency
- Use color to draw attention to metrics and CTAs
### File Format
- **PDF** for email attachments and leave-behinds
- **Google Slides / PowerPoint** for editable versions reps can customize
- Always include both: reps will customize, prospects want clean PDFs
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |