Enterprise Discovery Call Playbook

Why Single-Threaded Discovery Fails at Enterprise Scale

In deals with six or more buying-committee members, one great discovery call with one champion produces a false-positive qualified deal. Enterprise discovery isn't one call — it's a deliberate sequence engineered to touch every functional stakeholder before a proposal gets built.

The Buying-Committee Map — 6 Roles to Identify Before Building a Proposal

1. Economic Buyer — controls/releases budget, final sign-off
2. Champion — internal advocate who sells on your behalf when you're not in the room
3. Technical Evaluator — security, IT, integration, data; can veto on technical grounds
4. End User Representative — the people who'll actually use it daily; adoption risk lives here
5. Procurement/Legal Gatekeeper — controls paper process, contract terms, vendor risk review
6. Influencer / Coach or Skeptic — no formal authority but shapes the room's opinion

Pre-Engagement Research Checklist (before Call 1)

• Org chart pulled for the buying function
• Recent public signals reviewed: earnings calls, job postings, leadership changes, press releases
• Existing relationships/warm paths mapped (mutual connections, existing customers, prior touchpoints)
• Known incumbent vendor(s) identified if this is a replaceable category
• Hypothesis document drafted: which of the 6 roles you expect to encounter, and who they might be

The 5-Call Enterprise Discovery Sequence

Call 1 — Business Discovery (Champion / initial contact)

Goal: Confirm the business pain, quantify impact, get the champion to help map the room.

• Context-setting (2 min)
• Situation & pain questions (15 min)
• Impact quantification (10 min)
• "Who else needs to be part of this" mapping (10 min)
• Next steps: agree who Call 2 is with

Call 2 — Economic Buyer Alignment

Goal: Validate the pain resonates at the budget-holder level; confirm what "success" means in their terms.

• Business context from their vantage point (10 min)
• Confirm/challenge the pain and impact numbers from Call 1 (10 min)
• Decision process and timeline from their seat (10 min)
• What makes this an easy yes vs. a hard no (5 min)

Call 3 — Technical / Security Discovery

Goal: Surface technical requirements early enough to design around them, not discover them at contract stage.

• Current stack and integration points (15 min)
• Security/compliance requirements and review process (10 min)
• Data migration/implementation constraints (10 min)
• What's killed similar projects technically before (5 min)

Call 4 — End-User Discovery

Goal: Understand day-to-day workflow reality and adoption risk.

• Current workflow walkthrough (15 min)
• Pain points in their own words (10 min)
• What would make them resist a new tool (10 min)
• Early reaction to a rough solution outline (10 min)

Call 5 — Mutual Close Plan Session (Champion + Economic Buyer, ideally both present)

Goal: Build a jointly-owned timeline from today to signed, with named owners on both sides.

• Recap validated pain + quantified impact across stakeholders (10 min)
• Walk the mutual action plan template line by line (20 min)
• Confirm procurement/legal process and paper timeline (10 min)
• Lock the next call date before ending this one (5 min)

Reusable Meeting Agenda Template

``` Call [#]: [Purpose] — [Date] Attendees: [Names + roles]

1. Context/recap (2-3 min)
2. [Primary discovery objective] (X min)
3. [Secondary objective] (X min)
4. Open questions / risks surfaced (X min)
5. Next steps + owners + date (X min)

```

Stakeholder Alignment Tracker

Mutual Action Plan Template

Risk Register for Stalled Enterprise Deals

Internal Deal-Review Cadence for Leaders

• Weekly: any enterprise deal without documented touches to at least 3 of the 6 roles gets flagged.
• Bi-weekly: forecast call requires the Stakeholder Alignment Tracker to be current, not verbal-only updates.
• Monthly: risk register reviewed for any deal in Proposal stage 45+ days.