home / skills / refoundai / lenny-skills / enterprise-sales

enterprise-sales skill

/skills/enterprise-sales

This skill guides enterprise sales through stage identification, buying committee mapping, and procurement navigation to close large deals.

npx playbooks add skill refoundai/lenny-skills --skill enterprise-sales

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
4.3 KB
---
name: enterprise-sales
description: 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.
---

# 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:

1. **Identify the stage** - Determine if they're prospecting, in discovery, navigating procurement, or closing
2. **Map the buying committee** - Help them identify the champion, economic buyer, and other stakeholders
3. **Address indecision** - Focus on overcoming customer fear of messing up, not just building FOMO
4. **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

Overview

This skill helps sales leaders and individual contributors navigate complex enterprise deals. It focuses on stages from prospecting to procurement, with practical frameworks to reduce indecision, arm champions, and convert product-led usage into enterprise contracts. Use it to structure outreach, discovery, POCs, and procurement handoffs for predictable closes.

How this skill works

I first identify the deal stage and map the buying committee, highlighting the champion, economic buyer, and operational stakeholders. I then diagnose risks—especially indecision—and recommend tactics: de-risking proposals, building collaborative business cases during POCs, and proactively handling procurement tasks. Finally, I provide play-by-play scripts, decision criteria, and checklists to move the deal to signature.

When to use it

  • Closing large, multi-stakeholder deals with long sales cycles
  • Converting product-led growth users into enterprise contracts
  • Navigating procurement, security, or compliance reviews
  • Building or validating an ROI-driven POC or pilot
  • Re-engaging stalled opportunities at risk of 'no decision'

Best practices

  • Map the buying committee early and identify the internal champion; equip them with tailored assets for Legal, IT, and Finance
  • Focus on fear of messing up (FOMU) over fear of missing out; remove blame and operational risk
  • Frame POCs as collaborative business-case exercises, not feature demos
  • Proactively own procurement tasks: provide forms, contract templates, and compliance artifacts
  • Under-promise and over-deliver: build conservative, achievable ROI assumptions
  • Use the JOLT approach: judge indecision, offer a recommendation, limit exploration, and de-risk the purchase

Example use cases

  • A champion at a 500-employee company needs an ROI model and legal artifacts to convince procurement
  • A PLG product shows high usage in an account and you want to escalate to an enterprise pilot and contract
  • A deal is stalled because stakeholders fear change; run a de-risking plan to remove single points of blame
  • You must design a POC that proves business outcomes and creates a scalable case for expansion
  • Preparing contract and security documentation before procurement asks so the process moves quickly

FAQ

How do I spot the real champion vs. a friendly user?

Look for the person who coordinates others, has influence across functions, and repeatedly volunteers to drive internal alignment. Confirm they have access to decision-makers or can pull the economic buyer into discussions.

What’s the fastest way to kill ‘no decision’ outcomes?

Identify the buyer’s biggest fear of messing up and remove it: offer pilot guardrails, conditional commitments, conservative business-case assumptions, and clear rollback or success criteria so stakeholders feel safe signing.