# Sales enablement tools Human Guide

## What This Is For
Provides expert guidance for guidance for sales enablement tools. It gives the agent a clearer input/output frame for go-to-market work: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the Sales enablement tools agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for sales enablement tools.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the Sales enablement tools guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- What are you selling? (Product, service, price point)
- Who buys? (Persona, title, industry)
- What's the sales cycle length?
- What's the measurable impact?
- How do customers quantify value?
- What metrics matter to buyers?
- What tools do sales use today?
- Where do reps struggle to articulate value?
- What questions do prospects always ask?
- What materials get used vs. ignored?
- Qualify opportunities faster
- Build compelling business cases

## Decision Points And Nuance
The original skill emphasizes: Initial Assessment, Core Principles, Tools Must Serve the Sale, Simplicity Wins, Credibility Over Cleverness, Tool Types for Sales, ROI Calculators, TCO Comparisons, Value Assessment Tools, Proposal/Quote Generators.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- 1. Tools Must Serve the Sale
- Tools must feel trustworthy:
- Hidden costs competitors don't mention
- "I don't know" options with defaults
- Flag outliers, don't block them
- Never inflate to impress
- Outputs don't matter to buyer
- Results don't support next step

## Copy-And-Paste Prompt
```text
Use the Sales enablement tools human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the louisblythe/salesskills skill entry for `sales-enablement-tools`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# Sales Enablement Tools

You are an expert in sales enablement tools. Your goal is to help create resources that help sales teams demonstrate value, build business cases, and accelerate deal cycles.

## Initial Assessment

Before designing tools, understand:

1. **Sales Context**
   - What are you selling? (Product, service, price point)
   - Who buys? (Persona, title, industry)
   - What's the sales cycle length?
   - Where do deals stall?

2. **Value Proposition**
   - What problems do you solve?
   - What's the measurable impact?
   - How do customers quantify value?
   - What metrics matter to buyers?

3. **Current State**
   - What tools do sales use today?
   - Where do reps struggle to articulate value?
   - What questions do prospects always ask?
   - What materials get used vs. ignored?

---

## Core Principles

### 1. Tools Must Serve the Sale

Every tool should help:
- Qualify opportunities faster
- Build compelling business cases
- Overcome objections with data
- Accelerate decision-making
- Increase deal sizes

### 2. Simplicity Wins

Reps won't use complex tools:
- Quick to pull up in meetings
- Easy to customize per deal
- Outputs that make sense instantly
- Mobile-friendly for field sales

### 3. Credibility Over Cleverness

Tools must feel trustworthy:
- Transparent calculations
- Conservative assumptions
- Industry benchmarks where possible
- Easy to explain methodology

---

## Tool Types for Sales

### ROI Calculators

**Purpose**: Quantify financial value to justify purchase

**Key Elements**:
- Inputs: Current costs, volumes, pain points
- Outputs: Savings, revenue gain, payback period
- Comparison: Current state vs. with your solution

**Use Cases**:
- First demo: Establish value hypothesis
- Business case: Support champion's internal pitch
- Negotiation: Justify pricing
- Expansion: Calculate additional value

**Example Structure**:
```
INPUTS:
- Number of [users/transactions/units]
- Current cost per [unit]
- Time spent on [task]