AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

sales-enablement

When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps,' 'cold call script,' or 'voicemail script.' Use this for any document or asset that helps a sales team close deals. For public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure), see offers.

Original source
coreyhaines31
License
MIT
Pinned revision
88c79f6528a9347420e57ceb1fff9a60de651768

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read coreyhaines31--sales-enablement at revision 88c79f6528a9347420e57ceb1fff9a60de651768, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 7

references/one-pager-templates.md

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: [email protected]]

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