Enterprise Sales Discovery Call (MEDDPICC)

Template Overview

Enterprise sales cycles are won or lost in discovery. When account executives fail to rigorously qualify prospects—neglecting to identify the true economic buyer, quantify negative business consequences, or uncover security compliance hurdles—deals stall in procurement purgatory.

The MEDDPICC framework provides an uncompromising qualification discipline. By anchoring sales conversations in verifiable metrics, economic pain, and formal procurement steps, revenue teams focus energy on deals that actually close.

This template organizes enterprise discovery into the MEDDPICC dimensions: current state architecture, quantified business pain, economic buyer identification, decision criteria, and immediate next qualification steps.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Enterprise Discovery: [Prospect Company]"
date: [YYYY-MM-DD]
prospect_company: "Acme Health Technologies"
account_executive: "[[AE Name]]"
solutions_engineer: "[[SE Name]]"
prospect_attendees:
  - "[[Prospect VP Eng]]"
  - "[[Prospect CISO]]"
estimated_acv: "$75,000"
deal_stage: "Stage 2 - Discovery & Qualification"
meddpicc_score: "6 / 8 Qualified"
tags: [sales, discovery, meddpicc, enterprise, qualification]
---

# Enterprise Discovery: [Prospect Company] — [YYYY-MM-DD]

## 1. Executive Opportunity Brief
- **Company Profile:** 850 employees; healthcare SaaS provider subject to strict HIPAA and data sovereignty regulations.
- **Trigger Event:** Recent security audit flagged third-party cloud meeting bots as an unacceptable data exfiltration risk.

## 2. MEDDPICC Qualification Matrix
| Dimension | Findings & Verified Evidence | Confidence |
| :--- | :--- | :--- |
| **M - Metrics** | Losing 4.5 engineering hours per week to manual meeting notes; $380k annual productivity cost. | 🟢 High |
| **E - Economic Buyer** | Chief Information Officer ([[Prospect CIO]]) controls $1.2M discretionary security budget. | 🟡 Medium |
| **D - Decision Criteria** | Zero network egress during audio transcription; native Apple Silicon support; Markdown output. | 🟢 High |
| **D - Decision Process** | Technical PoC (2 weeks) -> Security Review -> Procurement committee approval. | 🟢 High |
| **P - Paper Process** | Standard vendor security questionnaire -> DPA negotiation -> Net 30 payment terms. | 🟡 Medium |
| **I - Identify Pain** | Cloud transcription tools violate hospital data protection agreements, risking $2M enterprise pilots. | 🟢 High |
| **C - Champion** | VP of Engineering ([[Prospect VP Eng]]) actively advocating for on-device deployment. | 🟢 High |
| **C - Competition** | Incumbent cloud transcription bot vendor (currently facing contract termination). | 🟢 High |

## 3. Technical Environment & Constraints
- **Hardware Fleet:** 100% Apple Silicon Macs (M1/M2/M3 MacBook Pro fleet).
- **Security Mandate:** Binary must execute strictly offline with zero external cloud dependencies.

## 4. Agreed Next Action Steps
- [ ] [[SE Name]] Deliver isolated test build and technical architecture white paper by Friday.
- [ ] [[AE Name]] Schedule 30-minute introductory call with Economic Buyer ([[Prospect CIO]]).
- [ ] [[Prospect VP Eng]] Provide corporate security review questionnaire.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Discovery: BioHealth Solutions"
date: 2026-10-06
prospect_company: "BioHealth Solutions"
account_executive: "[[Rachel Adams]]"
estimated_acv: "$90,000"
tags: [sales, discovery, meddpicc]
---

# Discovery: BioHealth Solutions — October 6, 2026

## 1. Core Opportunity
BioHealth needs meeting records for 400 clinical researchers. Third-party cloud transcription tools were banned due to FDA clinical trial data rules.

## 2. Qualification Highlights
Champion is Dr. Aris Thorne (Chief Medical Officer). Economic buyer is the CIO. Primary decision criteria: zero network egress verified via Little Snitch packet capture.

## 3. Account Plan
Deliver technical proof-of-concept build on October 12, 2026.

When to Use and When to Avoid

When to Use

• Use during initial and secondary enterprise sales discovery meetings.
• Use to qualify complex deals using the proven MEDDPICC enterprise sales methodology.
• Use when documenting technical security constraints, buyer pain, and procurement steps.

When to Avoid

• Avoid using for transactional consumer checkout sales or low-touch self-serve purchases.
• Avoid using for internal employee performance reviews or developer standups.

On-Device AI Integration

Process enterprise sales discovery calls locally in Oyma:

Analyze the sales discovery meeting transcript:
1. Synthesize the prospect company background, current pain points, and commercial trigger events.
2. Group findings into the MEDDPICC qualification framework (Metrics, Economic Buyer, Decision Criteria, etc.).
3. Document technical infrastructure details, hardware fleet constraints, and security requirements.
4. Record mutual agreed action steps, designated owners, and next meeting target dates.
Output in structured CommonMark format.

Sensitive enterprise deal terms and prospect pricing details stay confidential on your Mac.