enterprise-sales▌
refoundai/lenny-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Navigate enterprise sales deals through buying committee dynamics, procurement, and overcoming customer indecision.
- ›Helps identify deal stage, map stakeholders (champion, economic buyer, decision-makers), and arm internal advocates with role-specific materials
- ›Addresses the root cause of deal loss: customer fear of messing up and being blamed, not just competitive pressure or missing urgency
- ›Guides procurement navigation by proactively handling administrative burden, compliance requi
Enterprise Sales
Help the user navigate enterprise sales using frameworks from 9 product leaders who have closed large enterprise deals at companies from Stripe to Superhuman.
How to Help
When the user asks for help with enterprise sales:
- Identify the stage - Determine if they're prospecting, in discovery, navigating procurement, or closing
- Map the buying committee - Help them identify the champion, economic buyer, and other stakeholders
- Address indecision - Focus on overcoming customer fear of messing up, not just building FOMO
- Navigate procurement - Guide them through the administrative and compliance requirements
Core Principles
40-60% of deals die to indecision
Matt Dixon: "Our analysis showed that anywhere between 40 and 60% of the average salesperson's qualified pipelines will be ultimately marked as closed loss, no decision." Most deals are lost not to competitors, but to customer inertia and fear.
Identify and arm the champion
April Dunford: "Typically we have between five and seven people involved in what we call making the decision. By far the most important persona is what we call the champion - this person's job is to get consensus and champion the deal across everybody." Arm them with materials for IT, Legal, and the Economic Buyer.
FOMU beats FOMO
Matt Dixon: "The omission bias is the fact that people don't want to be blamed for making decisions that lead to a loss. People are okay with missing out. They are not okay with messing up and being blamed." Address Fear of Messing Up, not just Fear of Missing Out.
Make procurement's job easy
Jen Abel: "When you get to procurement, you're going to have to do all the work. Make their job easy. Give me the forms that you need to fill out. I'll fill them out for you." Proactively handle the administrative burden to avoid being sidelined.
POCs are for business cases, not demos
Madhavan Ramanujam: "The POC should be framed as the entire goal of the POC is to create a business case, period, full stop. It is not to demonstrate product functionality." Treat POCs as collaborative exercises to build ROI models.
PLG to enterprise is an escalator
Elena Verna: "Product-led sales converts the usage that you've generated via self-serve into a sales opportunity and it attaches a salesperson to close a much larger contract." Identify the escalator from individual use case to enterprise-level solution.
Under-promise, over-deliver
Matt Dixon: "What great salespeople do is they know that while they'll stand by those claims, they try to under-promise and over-deliver. Build your business case around a 5X improvement, then let's set up to over-deliver against that." Build cases around conservative, 100% achievable numbers.
Use the JOLT method
Matt Dixon outlines four steps to overcome indecision: Judge the level of indecision, Offer a firm recommendation, Limit exploration by building trust, Take risk off the table by de-risking the deal.
Questions to Help Users
- "Who is the champion inside the account and what do they need to succeed?"
- "What would cause this deal to die to 'no decision'?"
- "What's the buyer's biggest fear about messing up?"
- "Have you identified the final signatory and what they care about?"
- "Are you building the business case collaboratively or presenting it?"
- "What can you do to de-risk this decision for the buyer?"
Common Mistakes to Flag
- Relying on FOMO alone - Dialing up urgency without addressing the fear of being blamed for failure
- Ignoring the champion - Selling to the economic buyer directly instead of arming an internal advocate
- Passive procurement - Waiting for buyers to navigate internal processes instead of doing it for them
- Demo-focused POCs - Treating proof of concepts as technical tests instead of business case exercises
- Best-case projections - Building business cases around optimistic numbers that set up for disappointment
Deep Dive
For all 25 insights from 9 guests, see references/guest-insights.md
Related Skills
- Founder Sales
- Building Sales Team
- Partnership & BD
- Product-Led Sales Strategy
How to use enterprise-sales on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add enterprise-sales
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches enterprise-sales from GitHub repository refoundai/lenny-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate enterprise-sales. Access the skill through slash commands (e.g., /enterprise-sales) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★46 reviews- ★★★★★Kwame Bhatia· Dec 16, 2024
Keeps context tight: enterprise-sales is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Anaya Anderson· Dec 16, 2024
Useful defaults in enterprise-sales — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Pratham Ware· Dec 12, 2024
enterprise-sales has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Liam Sharma· Dec 4, 2024
Registry listing for enterprise-sales matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Ama White· Nov 23, 2024
enterprise-sales fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Henry Bhatia· Nov 19, 2024
enterprise-sales reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Ama Harris· Nov 7, 2024
enterprise-sales is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Ama Park· Nov 7, 2024
We added enterprise-sales from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Sakshi Patil· Nov 3, 2024
Solid pick for teams standardizing on skills: enterprise-sales is focused, and the summary matches what you get after install.
- ★★★★★Ama Huang· Oct 26, 2024
enterprise-sales fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 46