Back to Skills

enterprise-sales

Help users navigate enterprise sales. Use when someone is closing large deals, managing complex buying committees, handling procurement, or converting PLG users to enterprise contracts.

1,135stars146forksUpdated 7/11/2026

Security Assessment

Safe(100/100)
Security Score100/100

About enterprise-sales

Enterprise Sales equips users to navigate large, complex B2B deals by drawing on frameworks from nine product and go-to-market leaders who have closed enterprise contracts at companies ranging from Stripe to Superhuman. The guidance is organized around the deal lifecycle: identifying the current stage (prospecting, discovery, procurement, or closing), mapping the buying committee, addressing buyer indecision, and navigating procurement. A central premise, drawn from Matt Dixon's research, is that 40 to 60 percent of qualified pipeline is lost not to competitors but to customer indecision and fear, ending up marked closed-lost as no decision. Because of this, the emphasis falls on overcoming the buyer's Fear of Messing Up (FOMU) rather than merely amplifying Fear of Missing Out (FOMO), since people are more averse to being blamed for a bad decision than to missing an opportunity.

Practical plays include identifying and arming the champion, who April Dunford notes drives internal consensus among the five to seven people who typically make the decision, with materials for IT, Legal, and the economic buyer; proactively handling procurement paperwork so the seller is not sidelined (Jen Abel); framing proof-of-concepts as collaborative business-case and ROI exercises rather than product demos (Madhavan Ramanujam); and recognizing the product-led escalator that converts self-serve usage into larger enterprise contracts (Elena Verna). The skill also promotes conservative, achievable business cases, such as building around a 5X improvement and then over-delivering, and Dixon's JOLT method for overcoming indecision: Judge the level of indecision, Offer a firm recommendation, Limit exploration by building trust, and Take risk off the table by de-risking the deal.

To apply these ideas, the skill supplies diagnostic questions (who is the champion and what do they need, what would cause the deal to die to no decision, what is the buyer's biggest fear) and flags common mistakes such as relying on FOMO alone, selling past the champion to the economic buyer, treating procurement passively, running demo-focused POCs, and building business cases on best-case projections. A deeper reference file collects 25 insights from all nine guests, and related skills cover founder sales, building a sales team, partnerships, and product-led sales strategy.

FAQ

What is the JOLT method?

Matt Dixon's four-step approach to overcoming buyer indecision: Judge the level of indecision, Offer a firm recommendation, Limit exploration by building trust, and Take risk off the table by de-risking the deal.

Why do most enterprise deals fail?

According to the frameworks cited, 40 to 60 percent of a salesperson's qualified pipeline is lost to customer indecision and inertia, marked closed-lost as no decision, rather than to competitors.

What is the difference between FOMU and FOMO?

FOMU is Fear of Messing Up and FOMO is Fear of Missing Out. The skill argues you should address FOMU, because the omission bias means people fear being blamed for a bad decision more than they fear missing out.

Who is the most important person in the buying committee?

The champion. April Dunford notes that five to seven people typically make the decision, and the champion's job is to build consensus and carry the deal across IT, Legal, and the economic buyer, so the skill focuses on arming them.

How should a proof-of-concept be framed?

As a collaborative exercise to build a business case and ROI model, not as a demonstration of product functionality, following Madhavan Ramanujam's guidance.

All Files

2 files
SKILL.md4.3 KB
View
references/guest-insights.md16.3 KB
View

Install enterprise-sales

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill