Sales enablement
Skill fabioc-aloha/Alex_Skill_Mall/plugins/domain-expertise/sales-enablement
284 curated plugins for AI assistants across 16 categories: security, Azure, documentation, code quality, cloud infrastructure, and more. Works with GitHub Copilot. Drop into .github/skills/local/ and go.
npx -y skills add fabioc-aloha/Alex_Skill_Mall --skill sales-enablementAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Sales methodology, pipeline management, negotiation frameworks, and customer engagement patterns.
SKILL.md
7.4 KB, as published. Nobody here has run it
Sales Enablement Skill
Sales methodology, pipeline management, negotiation frameworks, and customer engagement patterns.
Core Principle
Selling is structured problem-solving. You diagnose a customer's pain, match it to a solution, and guide the decision. Process beats personality.
Sales Methodologies
MEDDPICC (Enterprise/Complex Sales)
| Letter | Stands For | Question |
|---|---|---|
| M | Metrics | What measurable outcome does the buyer need? |
| E | Economic Buyer | Who has budget authority? |
| D | Decision Criteria | What factors drive the decision? |
| D | Decision Process | What are the steps to close? |
| P | Paper Process | What legal/procurement steps are required? |
| I | Implicate Pain | What happens if they do nothing? |
| C | Champion | Who inside the account is actively selling for you? |
| C | Competition | Who else is being evaluated? |
SPIN Selling (Consultative)
| Phase | Question Type | Example |
|---|---|---|
| S — Situation | Understand current state | "How do you currently handle X?" |
| P — Problem | Surface pain points | "What challenges does that create?" |
| I — Implication | Expand the pain | "What impact does that have on Y?" |
| N — Need-Payoff | Let buyer articulate value | "How would solving that help?" |
Challenger Sale
- Teach: Provide insights the buyer didn't know
- Tailor: Customize the message to stakeholder type
- Take control: Guide the buying process, push back constructively
Solution Selling (Simpler Deals)
| Step | Action |
|---|---|
| 1 | Identify the pain |
| 2 | Qualify the opportunity |
| 3 | Map solution to pain |
| 4 | Demonstrate value |
| 5 | Negotiate and close |
Pipeline Management
Deal Tracker (MEDDPICC)
{
"deal": "Acme Corp - Platform Expansion",
"value": 250000,
"stage": "negotiation",
"close_date": "2026-06-30",
"meddpicc": {
"metrics": { "score": 3, "note": "10% efficiency gain target confirmed" },
"economic_buyer": { "score": 3, "contact": "CFO Jane Smith" },
"decision_criteria": { "score": 2, "note": "Waiting on technical eval results" },
"decision_process": { "score": 3, "note": "Procurement involved, legal review next" },
"paper_process": { "score": 2, "note": "MSA required, 2-week legal cycle" },
"implicate_pain": { "score": 3, "note": "$500K annual loss without solution" },
"champion": { "score": 3, "contact": "VP Ops Mike Chen" },
"competition": { "score": 2, "note": "Competitor X shortlisted" }
},
"total_score": 21,
"next_step": "Send ROI calculator to CFO before 4/20"
}
Pipeline Stages
| Stage | Definition | Exit Criteria |
|---|---|---|
| Prospecting | Initial outreach, cold/warm | Meeting confirmed |
| Discovery | Needs assessment, pain qualification | Pain confirmed, budget discussed |
| Proposal | Solution presented, pricing shared | Decision criteria agreed |
| Negotiation | Terms, pricing, legal | Verbal commitment |
| Closed Won | Signed contract | Revenue booked |
| Closed Lost | Deal lost | Loss reason documented |
Pipeline Metrics
| Metric | Formula | Healthy Range |
|---|---|---|
| Win Rate | Closed Won / Total Opportunities | 20–35% (enterprise) |
| Average Deal Size | Total Revenue / Deals Closed | Varies by segment |
| Sales Cycle Length | Avg days from creation to close | Track trend, not absolutes |
| Pipeline Coverage | Pipeline Value / Quota | 3–4× for enterprise |
| Stage Conversion | Opportunities advancing / Total in stage | Monitor each stage |
Forecasting Categories
| Category | Definition | Commit Level |
|---|---|---|
| Commit | High confidence, expected this period | 90%+ probability |
| Best Case | Could close if things go well | 60–89% |
| Pipeline | Active but early stage | 10–59% |
| Upside | Stretch opportunities | <10% |
Prospecting & Outreach
Cold Outreach Framework
Email structure (3-sentence max):
- Relevant observation about their business (shows research)
- One sentence connecting their challenge to your solution
- Low-friction ask (15-minute call, not a demo)
Qualification Framework (BANT)
| Criterion | Question | Disqualifier |
|---|---|---|
| B — Budget | Is there budget allocated? | No budget and no path to budget |
| A — Authority | Can this person make or influence the decision? | No access to decision maker |
| N — Need | Is the pain real and urgent? | Nice-to-have, no urgency |
| T — Timeline | When do they need to decide? | No timeline = no deal |
Negotiation Frameworks
Principled Negotiation (Fisher & Ury)
- Separate people from the problem — Address emotions, maintain relationships
- Focus on interests, not positions — Ask why, not just what
- Invent options for mutual gain — Expand the pie before dividing
- Use objective criteria — Industry benchmarks, precedents, standards
Common Negotiation Tactics (and Counters)
| Tactic | Description | Counter |
|---|---|---|
| Anchoring | Extreme first offer | Re-anchor with data |
| Flinch | Physical reaction to price | Hold steady, stay silent |
| Nibbling | Adding small asks after agreement | "That would require re-opening terms" |
| Good cop/bad cop | Paired pressure | Address the issue, ignore the dynamic |
| Deadline pressure | "Offer expires Friday" | Verify deadline is real |
Discount Discipline
- Never discount without getting something: Shorter term, larger volume, case study, referral
- Discount from value, not from list: Show the full value before any reduction
- Document the justification: Every discount needs a recorded business reason
Customer Success Handoff
Post-Sale Transition
| Step | Owner | Deliverable |
|---|---|---|
| 1 | Sales | Handoff document (pain, solution, stakeholders, commitments) |
| 2 | CS/AM | Welcome call within 48 hours |
| 3 | Both | Joint account plan (90-day) |
| 4 | CS/AM | Onboarding kickoff |
Real Estate Sales Patterns
Property Presentation
- CMA (Comparative Market Analysis): 3–5 comparable recent sales, adjusted for features
- Days on Market (DOM): Track vs market average — high DOM signals pricing issue
- Absorption Rate: Monthly sales / Available inventory — measures market speed
Client Communication
- Buyer's journey: Discovery → Pre-approval → Viewings → Offer → Inspection → Close
- Seller's journey: Valuation → Staging → Listing → Showings → Offers → Negotiation → Close
- Follow-up cadence: 24h post-showing, 72h if no response, 2-week check-in for nurture
Anti-Patterns
- Pitching features before understanding the problem
- Discounting to win without addressing the real objection
- Forecasting based on hope instead of evidence
- Skipping discovery to rush to demo
- Single-threading (only one contact in the account)
- Not documenting loss reasons (repeats same mistakes)
Gives 0 of the 12 instructions most sales crm skills give
Counted across 361 of the 361 authors here whose files we hold, read 2026-08-06
- Read product marketing context before writing if it existsin 22 of 361, across 14 files
- keep the ask low-frictionin 16 of 361, across 7 files
- Call RUBE_SEARCH_TOOLS firstin 15 of 361, across 5 files
- personalize every outbound messagein 13 of 361, across 4 files
- confirm connection status is activein 13 of 361, across 4 files
- Keep forwardable blurbs under 100 wordsin 13 of 361, across 4 files
- State if personalization context is missingin 13 of 361, across 4 files
- Cut any sentence that does not drive a replyin 13 of 361, across 4 files
- Use proof instead of adjectivesin 12 of 361, across 3 files
- Use a single, low-friction call to actionin 12 of 361, across 4 files
- Calibrate tone to the specific audiencein 12 of 361, across 3 files
- Make each follow-up email add new valuein 12 of 361, across 6 files
Said here and by no other author read
- Diagnose customer pain before matching a solution
- Track deals through defined pipeline stages
- Limit cold outreach emails to three sentences
- Disqualify opportunities using the BANT criteria
- Focus negotiation on interests rather than positions
- Secure a concession for every discount given
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.