Prompt: We sell a R500k/year enterprise data platform to banks in SA. Build me a discovery call framework with the 10 most important questions, what great answers sound like, and deal-killing red flags.
Discovery Call Framework
Audience: SA banks evaluating an enterprise‑grade data platform (R 500k / yr).
Goal of the call: surface real pain, quantify impact, identify decision power, and uncover any red‑flag that would make this a poor fit.
> Rule of thumb for discovery – 70 % buyer talk, 30 % you.
> Keep product details off the table until after you confirm the why and the what of their problem.
---
1️⃣ Call Agenda (≈45 min)
| Time | Activity |
|------|----------|
|0–5 m | Warm‑up + agenda & objectives, brief intro of each side |
|5–40 m | Structured discovery – 10 questions + follow‑ups |
|40–45 m | Quick summary of what we heard, next steps (who, when, what) |
---
2️⃣ The 10 Most Important Questions
> Each question is paired with:
> • What the great answer should sound like (the ideal data you’ll use to build a business case).
> • The key deal‑killing red flags.
| # | Category | Question | Why it matters | Great answer | Deal‑killing red flag |
|---|----------|----------|----------------|--------------|-----------------------|
| 1 | Situation / Pain | “Can you walk me through how your data is currently sourced, stored, and consumed across the bank?” | Sets a baseline for all other questions; uncovers fragmentation. | Describes a clear flow: legacy mainframe → ETL tool → data warehouse → BI dashboards. Highlights pain points (e.g., 4‑step manual approval for each data load). | No single source – multiple “data islands”; no clear workflow documented. |
| 2 | Pain – Quantification | “What cost or revenue impact does that data fragmentation cause, in money or time?” | Moves the buyer from a problem to an ROI‑ready metric. | “We lose about R 4 million each quarter because analysts spend 3 days per report on manual reconciliation.” | They can’t quantify – answer is vague or “we’re still measuring it”. |
| 3 | Metrics (Business outcome) | “What business outcomes would you like to see if the issue were solved?” | Provides the value that will drive the business case. | “Reduce data‑related audit findings by 90 %, cut report turnaround from 5 days to 1 day, and free 2 FTEs.” | No clear measurable outcome; answers are high‑level (“better decision making”) with no numbers. |
| 4 | Champion / Influencer | “Who in your organisation would be the biggest beneficiary of an improved data platform?” | Identifies the internal advocate who can push the deal forward. | “Our Head of Risk Analytics will use real‑time dashboards to meet regulatory reporting deadlines.” | No single stakeholder identified; they’re waiting for executive sign‑off without a dedicated champion. |
| 5 | Decision Criteria | “What are the must‑have features or standards your solution needs to hit?” | Clarifies technical, compliance, and vendor expectations early. | “Must support POPI data residency in South Africa, integrate with our SAP system, deliver 99.9 % uptime SLA.” | No clear criteria; they say “whatever you can do” or mention only generic “fast”. |
| 6 | Economic Buyer | “Who ultimately controls the budget for a project of this scale?” | Prevents wasting time on the wrong person. | “The CFO’s office has final approval, but the head of IT drives the vendor selection.” | The rep talks to a middle manager who can’t sign; economic buyer unreachable. |
| 7 | Decision Process / Timeline | “What is your internal decision‑making process and timeline for something like this?” | Reveals cycle length, gatekeepers, and potential bottlenecks. | “We have a four‑step approval: IT Lead → CFO → Board Committee (Q4), so we’re looking to sign before end‑of‑year.” | No defined process; decision left open (“we’ll talk about it next year”). |
| 8 | Competitive Landscape | “Who else are you evaluating and why?” | Uncovers hidden competition and differentiators. | “We’re considering a local vendor that offers an in‑house data lake, but they lack the real‑time analytics layer we need.” | They haven’t done research; no competitors mentioned or only one name that is not serious. |
| 9 | Compliance & Risk | “What regulatory requirements must the platform meet (POPI, ISO 27001, Basel III)?” | Ensures the solution can be delivered without compliance risk. | “Must store all personal data on South African servers, provide audit trails for a minimum of 7 years, and support annual penetration testing.” | No mention of regulatory constraints; they assume all vendors will comply automatically. |
|10 | Budget & Financial Justification | “If we could reduce the manual reconciliation time by X days per week, what would that translate into cost savings or revenue impact for your bank?” | Connects the earlier pain to a concrete financial metric – the sales hook. | “Cutting 3 days of analyst work equates to R 1.2 million in annual salary savings plus risk mitigation worth another R 0.8 million.” | Budget not allocated or they say the project is “future‑phase” with no clear funding path. |
---
3️⃣ How to Use the Red Flags
| Flag | What to Do Immediately |
|------|------------------------|
| No quantifiable pain | Probe deeper: “Can you walk me through an example where a data issue delayed a compliance report? Who was affected and what cost?” |
| Economic buyer unreachable | Ask for a “buddy” or advocate that can facilitate introductions; schedule a 15‑min intro call with the CFO. |
| Unclear decision timeline | Suggest a time‑boxed next step: “Let’s set up a 2‑hour demo in two weeks and identify any blockers that might delay decisions.” |
| No champion identified | Offer to provide a quick workshop for their IT team, positioning your solution as a learning tool to surface hidden pain. |
| Compliance not considered | Immediately present a high‑level compliance checklist; ask if they’ve had audit findings in the last 12 months. |
| Budget not set or future‑phase | Ask: “What would be the financial justification needed for this investment? Who signs off on such a budget?” |
---
4️⃣ Tips for Capturing & Acting on Notes
- Use a shared CRM note template – capture each answer next to the question header.
- Tag red flags immediately (e.g., 🔴 Budget, ⚠️ Champion).
- Quantify if possible – fill in R‑value numbers from the conversation and add a quick ROI placeholder.
- Close with a mutual action plan – list: “Book demo with CFO + IT Lead – 30 Sept”, “Send compliance brief – 5 Oct”.
---
5️⃣ Quick “Great Answer” vs “Deal‑killing” Cheat Sheet
| Question | Great answer (one sentence) | Deal‑killer |
|----------|------------------------------|-------------|
| What data sources do you use? | “We pull from SAP, a legacy mainframe, and a cloud‑based CRM – 3 separate pipelines.” | No single source; data lives in silos. |
| How much does this cost? | “R 4 million per quarter in manual hours & audit penalties.” | Vague, no numbers. |
| What outcome do you want? | “Reduce report turnaround to one day and save 2 FTEs (≈R 1 M).” | Generic “better decisions”. |
| Who will champion it? | “Head of Risk Analytics; he drives the reporting platform.” | No clear internal advocate. |
| Must‑have criteria? | “Must comply with POPI, integrate with SAP, 99.9 % uptime SLA.” | “Whatever you can do”. |
| Budget authority? | “CFO approves; IT Lead selects vendors.” | Only a middle manager. |
| Decision timeline? | “Board approval by Q4; we need to sign before year‑end.” | “We’ll talk next year”. |
| Competitors? | “Local vendor A offers a data lake but lacks real‑time analytics.” | No competitors listed. |
| Compliance needs? | “Data must stay on SA servers, audit trails for 7 yrs, ISO 27001 certified.” | No mention of compliance. |
| Quantify savings? | “3 days/analyst → R 1.2 M saved annually + risk mitigation.” | Budget not allocated yet. |
---
6️⃣ Final Checklist Before the Call
- ✅ Research: recent press releases, annual report, regulatory filings (POPI, Basel III updates).
- ✅ Prepare a quick “data‑pain map” to help the bank visualise fragmentation.
- ✅ Set a 30 min recording or note template to capture exact answers for post‑call analysis.
- ✅ Have a short 3‑slide ROI canvas ready (just in case they ask for a quick example).
---
Quick Action Prompt
After the call, upload your notes into Zoho CRM under “Discovery Notes”, tag any red flags with a custom field, and schedule an internal review meeting. This keeps the discovery findings directly tied to pipeline hygiene and forecasting accuracy.
Happy selling – let me know if you’d like help drafting the ROI slide or setting up a post‑call playbook!