SKILL.md

name

sales-enablement

description

Produces collateral the sales team will actually use — pitch decks, one-pagers, demo scripts, objection-handling docs, ROI talking points, and persona cards. Scannable-first; every claim ties to a measurable business outcome. Use when the user asks for "a deck for {customer}", "one-pager on {feature}", "demo script for {use case}", "objection handling for {scenario}", or "help my sales team with {situation}".

sales-enablement

Inspired by coreyhaines marketing-skills/sales-enablement and revfactory sales-enablement. Adapted for Amaro's data-app-driven motion.

Operating principle: Sales uses what sales trusts. If reps rewrite the deck before sending, the deck failed. Reps need answers in 3 seconds, not 30 — every output is scannable-first.

When to trigger

• "deck for {customer/situation}"
• "one-pager on {topic}"
• "demo script for {use case}"
• "objection handling" / "rebuttal for {objection}"
• "ROI talking points"
• "persona card for {persona}"
• "playbook for {sales motion}"
• "help my sales team with {situation}"

Asset types

Asset	When to use	Length	Format
Pitch deck	Mid/late-stage discovery; structured walk-through	10–15 slides	Outline + speaker notes
One-pager	Leave-behind after a meeting; cold outreach attachment	1 page (~250 words)	Headline + outcome + 3 proof points + CTA
Demo script	Live or recorded product walk; rep-led	8–12 min spoken	Scene-by-scene with timing + objection handles
Objection-handling doc	Looked up during a call	1–2 pages	Q&A table
ROI talking points	Procurement / business-case conversation	1 page	Concrete outcome math, named comparable
Persona card	Onboarding new reps; pre-call prep	1 page	Context, pain, language, anti-language
Playbook	Repeated sales motion (e.g. discovery → demo → POC)	2–4 pages	Stage gates, plays per stage, decision criteria

Inputs

• Asset type — from the matrix above
• Audience — which buyer / persona (e.g. CDO, head of sales ops, IT director). Default executive.
• Use case — specific named workflow Amaro solves (e.g. "Salesforce-to-Snowflake join match-rate audit")
• Stage — discovery / mid-funnel / late-stage / closing. Affects tone and depth.
• Existing context — prior decks, customer stories, win/loss notes, related collateral

Workflow

1. Read the style guide + existing brand sources.
2. Confirm the asset type and the buyer. If unclear, one short clarifying question.
3. Pull the right framing. Sales language, not marketing jargon. Outcome-first headlines. Measurable proof.
4. Build the asset using the matrix template below.
5. Trust check. For every claim: is there a number, a named customer, or a Fidelity-Score caveat? If not, rework or cut.
6. Scannability check. Can a rep find the answer to "why is this better than {competitor}?" or "what's the price?" in under 3 seconds? If no, restructure.
7. Run brand-voice lint.
8. Write to drafts. assets/drafts/{YYYY-MM-DD}-{asset-type}-{slug}.md.
9. Append to tasks.
10. Push to #marketer-approve if the asset will be sent externally to a named customer or land on a partner site. Internal sales-team distribution is #marketer.

Templates

One-pager template

# {Specific outcome — one line, ≤ 12 words}

{Subhead — 1 sentence that names the workflow and the named persona who feels this.}

## What this delivers
- **{Outcome 1}** — {one-line concrete claim with number / customer / measurable}
- **{Outcome 2}** — {ditto}
- **{Outcome 3}** — {ditto}

## How it works
{2-sentence explanation. Use canonical Amaro vocabulary: data app, integration, business rule, Fidelity Score, MCP endpoint.}

## Why now
{1 sentence — why this matters this quarter / this year.}

## What to do next
{Specific CTA. Demo link, intro to AE, link to data app gallery.}

Demo script template

# Demo: {use case}

**Audience**: {persona}
**Length**: {N min}
**Goal**: {what the buyer should feel/believe at the end}

---

## Scene 1 (0:00 – 1:30) — Opening
**Set**: {what's on screen}
**Say**: "{exact words for the opener — outcome-led, not feature-led}"
**Show**: {first interaction}
**Watch for**: {buyer reaction signals}

## Scene 2 (1:30 – 3:30) — {Workflow}
{Same structure}

## Scene 3 ...

---

## Likely objections + handles
| Objection | What they mean | Response |
|---|---|---|
| "How is this different from Glean?" | They're testing positioning | "{2-sentence answer per battlecard}" |
| "What about data security?" | Procurement gate | "{one-line + link to security doc}" |

## Close
**Say**: "{specific CTA, named next step, calendar option}"

Objection-handling doc template

# Objection handling — {topic / deal stage}

| Objection | What they really mean | Response (≤ 3 sentences) | Proof point |
|---|---|---|---|
| "Too expensive" | {decode} | {response} | {customer name + outcome} |
| "Already use {tool}" | {decode} | {response} | {differentiation, not dismissal} |
| ... | ... | ... | ... |

## When to pivot to PoC
{Decision criteria — when to stop arguing and offer a 2-week POC}

Persona card template

# Persona — {title}, {function}

## Pain (their words, not ours)
- "{quote}"
- "{quote}"

## What they want
- {Outcome they're optimizing for}

## What they don't want
- {Failure mode they're avoiding}

## Language they use
- "{their term}" → we hear / translate to "{our term}"

## Anti-language (don't say these to this persona)
- {Filler that gets tuned out — varies by function}

## Common objections
- {Top 3, with cross-link to objection-handling doc}

## Buying authority
- {What they can sign / approve unilaterally}
- {What needs procurement / IT / legal sign-off}

Don't

• Don't write pitch language. Sales hates marketing jargon. Cut adjectives. Cut adverbs. Lead with what it does, what it costs, what they get.
• Don't trust unverified claims. Every "10x faster" or "50% reduction" needs a customer name or a Fidelity caveat — or it doesn't go in.
• Don't ship a deck without speaker notes. Reps need to know what to say, not just what to show.
• Don't ship for an unnamed buyer. "Generic exec" doesn't exist. If the buyer isn't specified, ask.