Skip to content
Back to skills

Fin Sales Enablement

ASecurity

Builds sales enablement assets — MEDDICC qualification scoring, discovery question sets, demo-to-value flow, and a one-page proposal structure. Use when user says "sales enablement", "MEDDICC", "discovery call", "demo structure", or "proposal structure".

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 9, 2026
ai-agentsgo

Security analysis

A100/100

Scanned October 9, 2026

npx -y skills add meshcode-ai/skills --skill fin-sales-enablement --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Fin Sales Enablement?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Fin Sales Enablement
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/meshcode-ai-fin-sales-enablement/badge)](https://www.skillsdirectory.com/skills/meshcode-ai-fin-sales-enablement)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: fin-sales-enablement
description: Builds sales enablement assets — MEDDICC qualification scoring, discovery question sets, demo-to-value flow, and a one-page proposal structure. Use when user says "sales enablement", "MEDDICC", "discovery call", "demo structure", or "proposal structure".
license: MIT
metadata:
  source: "alirezarezvani/claude-skills (MIT) · commercial"
  category: exec
---

# Sales Enablement

## Qualification — MEDDICC scoring
Metrics (success defined in numbers) · Economic buyer (access to the approver) · Decision criteria (official criteria) · Decision process (approval procedure) · Identify pain (validated problem) · Champion (internal backer) · Competition. Score each 0–2; **below 10 points is excluded from the forecast** — chasing-stage deals don't count as opportunities.

## Discovery — 3-layer question set
Current state (how do you operate today) → cost of the problem (what do you lose if nothing changes) → decision criteria (what do you compare and approve against). Once the last question emerges, the proposal becomes a "solution," not an "introduction."

## Demo = value scenario
No feature listings. First agree on the customer's work scenario → reveal features only within it → after each screen, confirm "how much of the problem is solved by now." Send a summary memo within 24 hours of the demo (directly tied to the repurchase cycle).

## One-page proposal
Summary – problem – solution – proof (similar customer) – price – next action. Design for the assumption that the approver reads the email for an average of 30 seconds.

## Operating principles
An asset's life is its refresh cycle. Fold quarterly loss-review causes (competitor, price, feature) back into assets, and delete low-usage assets — an unused battle card creates false confidence.

## Output
MEDDICC scorecard (score · rationale), 10 discovery questions, demo scenario, one-page proposal draft.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…