close-enterprise-deals

name	Close Enterprise Deals
description	Navigate complex enterprise sales cycles by mapping buying committees, quantifying ROI, and managing multi-stakeholder negotiations. Prevents single-threaded deals and premature discounting. When to use it: long sales cycles (6+ months), multiple approval layers, procurement requirements, large contracts ($100K+). Trigger on: 'procurement', 'buying committee', 'security review', 'legal review', 'enterprise deal', 'stakeholder alignment'.
dependencies	[]
connectors	[{"name":"Salesforce","reason":"Track deal stages, multi-threaded contacts, and procurement timelines in a unified pipeline view"},{"name":"HubSpot","reason":"Map buying committee relationships and communication history with all stakeholders"},{"name":"Google Calendar","reason":"Coordinate complex multi-stakeholder meetings and executive sponsor alignment sessions"}]
author	Harmony
version	1.0.0
icon	sparkles
cover
screenshots	[]
category	Sales

Purpose

Enterprise deals fail not because of product problems but because you didn't navigate the buying process. This skill teaches you to:

• Map the decision-making unit (economic buyer, technical buyer, user buyer, coach) before you spend six months with the wrong person
• Quantify value in the customer's language — show ROI tied to their specific pain (not generic ROI)
• Manage procurement as the real sales motion — security questionnaires, legal reviews, and compliance checks aren't obstacles, they're the actual sale
• Multi-thread deals — never depend on a single champion; build relationships across the organization
• Execute proof of concept strategically — position it as validation, not a test
• Maintain pricing discipline — negotiate on value, not discounts

Enterprise sales is predictable if you understand that you're selling to a buying committee, not an individual.

When to Use This Skill

• Deal size exceeds $100K — complexity justifies the effort
• Multiple approval layers required — your contact isn't the final decision-maker
• Procurement process is mandated — security, legal, and compliance reviews ahead
• Longer cycles detected — 6+ months from first meeting to signature
• Stakeholder expansion needed — you've hit a plateau with your initial contact
• Reference customers requested — buying committee wants industry-specific proof points
• Value negotiation stalled — customer wants to cut price instead of discussing ROI

Instructions

1. Map the buying committee before first pitch

   • Identify the economic buyer (controls budget), technical buyer (evaluates fit), user buyer (daily use), and coach (your internal champion)
   • Use LinkedIn and your contact to build the org chart
   • Ask directly: "Who else will be involved in this decision?" in discovery calls
   • Document each person's priorities and concerns in your CRM

2. Conduct value-based discovery

   • Focus on quantifiable business outcomes they care about (reduce time-to-market, lower operational costs, minimize security risk, increase revenue)
   • Ask about current state metrics: "How much are you spending on this today?" "What's the cost of the current problem?"