Sales AI Skill
Enterprise Deal Execution Strategy
Execute complex enterprise deals requiring multi-stakeholder coordination, custom proposals, extended sales cycles, and cross-functional team alignment. Use when managing enterprise deals, coordinating deal teams, creating executive alignment, managing RFP...
Enterprise Deal Execution Strategy
Execute complex enterprise deals requiring multi-stakeholder coordination, custom proposals, extended sales cycles, and cross-functional alignment — converting $50K–$5M+ opportunities into closed-won revenue.
Workflow
- Deal qualification: Confirm budget, authority, need, timeline (BANT) for enterprise fit.
- Deal team assembly: AE, SE, Solutions Architect, CSM, Legal, Finance.
- Discovery deep-dive: Understand organizational needs, technical requirements, decision process.
- Solution design: Custom proposal aligned to business outcomes and ROI.
- Executive alignment: C-level meetings, strategic value presentation.
- RFP/RFI response: Structured response to formal procurement process.
- Proof of concept (POC) or pilot: Demonstrate value in customer environment.
- Negotiation: Pricing, terms, SLAs, professional services scope.
- Legal review and contract finalization.
- Close and handoff to implementation/Customer Success.
Deal Team Structure
ENTERPRISE DEAL TEAM ROLES
=============================
Role 1 — Account Executive (AE) — Deal Owner:
→ Primary customer relationship and deal champion
→ Manages deal timeline, next steps, and deal strategy
→ Coordinates deal team activities
→ Leads negotiation and closing
→ Owns revenue target and commission
Role 2 — Solutions Engineer (SE) / Pre-Sales:
→ Technical discovery and requirements gathering
→ Product demonstrations tailored to customer use cases
→ Technical RFP response and architecture design
→ POC/pilot execution and success metrics definition
→ Addresses technical objections and concerns
Role 3 — Solutions Architect (for complex deals):
→ Integration design and technical feasibility assessment
→ Custom solution architecture documentation
→ Engineering feasibility review
→ Implementation timeline and resource planning
Role 4 — Customer Success Manager (CSM):
→ Joins later stages (post-POC or negotiation)
→ Implementation planning and onboarding strategy
→ Success metrics and adoption plan
→ Post-close transition and relationship continuity
Role 5 — Legal and Deal Desk:
→ Contract review and negotiation support
→ Terms and conditions standardization
→ Risk assessment (liability, compliance, data security)
→ Approval workflows for non-standard terms
Role 6 — Finance / Revenue Operations:
→ Pricing validation and discount approvals
→ Revenue recognition assessment
→ Margin analysis and deal economics
→ Forecast accuracy and pipeline reporting
DEAL TEAM CADENCE:
════════════════════════════════════════════════════════════════════════
Meeting | Frequency | Participants | Purpose
════════════════════════════════════════════════════════════════════════
Deal strategy call | Weekly | AE + SE | Next steps, obstacles
Deal team sync | Bi-weekly | Full deal team | Status, coordination
Executive review | Monthly | AE + VP Sales | Strategy, escalation
Customer meeting | Bi-weekly | AE + SE + stakeholders| Relationship building
POC review | Weekly | AE + SE + customer | POC progress
════════════════════════════════════════════════════════════════════════
Discovery and Solution Design
ENTERPRISE DISCOVERY FRAMEWORK
================================
Phase 1 — Business Discovery (Weeks 1–2):
→ Current state: What are they using now? What's working/not working?
→ Pain points: What keeps their executives up at night?
→ Goals: What does success look like in 6, 12, 24 months?
→ Budget: What's the investment range? How is it approved?
→ Timeline: When do they need this implemented? Why that timeline?
→ Decision process: Who decides? What's the approval workflow?
Phase 2 — Technical Discovery (Weeks 2–3):
→ Current tech stack: What systems do they integrate with?
→ Requirements: Functional and non-functional requirements
→ Constraints: Compliance, security, data residency
→ Migration: How will they transition from current solution?
→ Scale: Expected users, data volume, growth projections
Phase 3 — Stakeholder Mapping (Ongoing):
════════════════════════════════════════════════════════════════════════
Stakeholder | Role | Influence | Interest | Engagement Strategy
════════════════════════════════════════════════════════════════════════
CEO/President | Champion | High | Medium | Business value, ROI
CTO | Decision | High | High | Technical fit, security
VP Operations | User | Medium | High | Efficiency, use cases
IT Director | Influencer | High | High | Integration, deployment
End Users | User | Low | High | Usability, training
Procurement | Gatekeeper | High | Low | Pricing, terms, competition
Legal | Gatekeeper | High | Low | Contract, compliance
════════════════════════════════════════════════════════════════════════
SOLUTION DESIGN DOCUMENT:
→ Executive summary: Business problem and proposed solution
→ Solution overview: How our product addresses each requirement
→ Technical architecture: Integration diagram, deployment model
→ Implementation plan: Timeline, phases, milestones
→ Success metrics: KPIs, measurement approach, reporting
→ Investment: Pricing, ROI calculation, total cost of ownership
→ Risk mitigation: Known risks and mitigation strategies
→ References: Similar customers, case studies, testimonials
RFP Response Process
RFP RESPONSE WORKFLOW
======================
Day 1 — RFP Received:
→ AE reviews RFP and confirms: Go/No-Go decision
→ Go criteria: > 30% win probability, qualified budget, strategic fit
→ Assemble response team: AE (owner), SE (technical), Marketing (collateral)
→ Assign sections to team members with deadlines
→ Schedule daily standups (15 minutes) until submission
Day 2–5 — Response Development:
→ Section owners draft responses (use templates where applicable)
→ SE addresses technical requirements and architecture questions
→ Marketing provides case studies, references, company information
→ Legal reviews compliance and contract-related questions
→ Pricing team prepares commercial response
Day 6 — Review and Refine:
→ Full team review: Consistency, completeness, competitive positioning
→ Executive review: VP Sales approves strategic tone and positioning
→ Final edits: Formatting, branding, page numbers, table of contents
Day 7 — Submission:
→ Final quality check: All questions answered, no typos
→ Submit before deadline (not last minute)
→ Confirmation: Written acknowledgment of submission
→ Follow-up: Thank customer for opportunity; schedule debrief
RFP RESPONSE QUALITY CHECKLIST:
→ Every question answered (no skipped items)
→ Direct answers first (not evasive or marketing-heavy)
→ Evidence provided (data, case studies, screenshots)
→ Consistent pricing and terms throughout
→ Branded and professionally formatted
→ Proofread for typos and errors
→ Page limits and formatting requirements met
Deal Metrics and Tracking
ENTERPRISE DEAL METRICS
=========================
Deal Stage Timeline:
════════════════════════════════════════════════════════════════════════
Stage | Duration | Activities | Win Rate
════════════════════════════════════════════════════════════════════════
Qualification | 1–2 weeks | BANT, stakeholder map | 40%
Discovery | 2–4 weeks | Business + technical | 35%
Solution Design | 2–3 weeks | Proposal, architecture | 30%
POC/Pilot | 3–6 weeks | Proof of value | 55%
Negotiation | 2–4 weeks | Pricing, terms, legal | 70%
Closed Won | 1 week | Contract, handoff | 100%
════════════════════════════════════════════════════════════════════════
Average enterprise sales cycle: 10–24 weeks
Deal Health Score:
════════════════════════════════════════════════════════════════════════
Factor | Weight | Score (1–5) | Weighted
════════════════════════════════════════════════════════════════════════
Budget confirmed | 20% | |
Decision process mapped | 15% | |
Champion identified | 15% | |
Technical fit validated | 15% | |
Competitive position | 10% | |
Timeline realistic | 10% | |
Executive buy-in | 15% | |
════════════════════════════════════════════════════════════════════════
Deal health > 4.0: Healthy → Push to close
Deal health 3.0–4.0: At-risk → Address gaps
Deal health < 3.0: Critical → Re-qualify or disqualify
Win Rate Benchmarks:
→ Overall enterprise win rate: 20–35% (from qualification to close)
→ Post-POC win rate: 55–70%
→ Post-negotiation win rate: 70–85%
→ Target: Improve by 5% quarter-over-quarter through process optimization
Integration Points
- CRM (Salesforce, HubSpot): Deal tracking, stage management, pipeline reporting
- CPQ Tools (Dealdesk, PandaDoc, Conga): Quote generation, pricing, proposal creation
- E-Signature (DocuSign, HelloSign): Contract execution, e-signature workflows
- Proposal Software (Plusly, Better Proposals): Interactive proposals, analytics
- Communication (Gong, Chorus): Call recording, conversation intelligence
- Project Management (Asana, Jira): POC management, implementation planning
- Contract Management (Ironclad, Avaloq): Legal review, term tracking
- Analytics (Tableau, Power BI): Deal pipeline, win rate, sales cycle analysis
Edge Cases
- Deal stalls in negotiation for 60+ days: Legal/procurement delays
- Diagnosis: What's blocking? (legal terms, pricing, internal approval?)
- Escalation: Our executive to their executive
- Concession strategy: What can we give without damaging margin?
- Timeline pressure: "This pricing valid until [date]"
- Walk-away point: Know when to disqualify (cost of chasing > deal value)
- Competitor undercuts on price: 30%+ cheaper alternative
- Value defense: ROI analysis showing higher total value
- Differentiation: Features, security, support, implementation advantages
- Case studies: Similar customers who chose us over competitor
- Creative pricing: Payment terms, bundled services, multi-year discount
- Last resort: Match price with executive approval (if strategic account)
- POC doesn't meet success criteria: Customer not convinced after pilot
- Root cause: Wrong use case? Technical issues? User adoption problems?
- Remediation: Extended POC with different use case
- Evidence: Show POC success with other customers in same industry
- Alternative: Reference calls with similar customers
- Acceptance: Some deals won't close; don't over-invest in lost causes
- Customer adds new stakeholders mid-deal: New decision-maker changes dynamics
- Welcome: Introduce new stakeholder; understand their concerns
- Education: Tailored demo/presentation for new stakeholder's role
- Alliance: Build relationship; don't assume opposition
- Impact assessment: Does new stakeholder change timeline or budget?
- Champion coordination: Brief champion on how to influence new stakeholder