Issue-Importance-Impact: a simple framework for better discovery calls
đŸ§©

Issue-Importance-Impact: a simple framework for better discovery calls

View Details
Link
Apps
Salesforce
Salesforce
Hubs
Sales
Sales
Unsplash Cover
Unsplash Cover
Video
Prompt status
Needs review
Prompt theme mode
Theme
Video theme
Mini masterclass
Short video prompt
INVIDEO AI PROMPT (SHORT-FORM — TikTok/IG Reels, 9:16)

Goal
Create a 20–35 second vertical video that teaches the Issue → Importance → Impact (III) framework to improve discovery calls, prevent premature feature demos, and help consultants sell outcomes, not features.

Source article (must reference)
https://connex.digital/book/website

Audience
Consultants, agency owners, sales reps, and solution engineers who run discovery calls.

Video specs
- Format: Vertical 9:16
- Duration: 20–35 seconds
- Pacing: Fast cuts, punchy jump cuts every 1–2 seconds
- Captions: Burned-in captions (high-contrast, large, centered safe area)
- On-screen branding: Include “Connex Digital” in on-screen text at least once, and show a subtle Connex Digital logo watermark in a corner throughout

Style + tone
- Video theme: Mini masterclass (energetic, crisp, confident)
- Voiceover: Warm US confident, conversational expert
- Music: Upbeat, trendy, low under VO

Structure (timed outline)
1) Hook (first 2 seconds)
- Visual: Presenter on camera (or dynamic kinetic text), quick zoom-in
- On-screen text: “Stop demo’ing too early.”
- VO: “If your discovery calls turn into demos too fast, use this 3-step framework.”

2) The framework (3 quick points)
- Point 1: Issue (what’s broken?)
- Visual: Simple motion graphic of a workflow breaking (handoff, approval, missing info)
- On-screen text: “1) Issue: What’s broken?”
- VO: “First: the Issue. What’s broken in the workflow, exactly?”
- Point 2: Importance (why now?)
- Visual: Calendar / deadline / leadership pressure b-roll
- On-screen text: “2) Importance: Why now?”
- VO: “Second: Importance. Why does it matter, and why does it matter now?”
- Point 3: Impact (cost of staying broken)
- Visual: Quick math overlay (hours × cost × people) + rising cost meter
- On-screen text: “3) Impact: What’s it costing?”
- VO: “Third: Impact. What does ‘staying broken’ cost in time, money, or risk?”

3) Quick payoff line
- Visual: Split screen “Features” crossed out → “Outcomes” highlighted
- On-screen text: “Sell outcomes, not features.”
- VO: “Now you can summarize the problem and demo only what maps to the impact.”

4) CTA (final 3–5 seconds)
- Visual: Clean end card with Connex Digital branding
- On-screen text: “Book a short call: connex.digital/book/short”
- VO: “Want help applying this to your sales process? Book a short call at connex.digital slash book slash short.”

On-screen text rules
- Keep text to 3–6 words per beat
- Use bold keywords: Issue, Importance, Impact
- Ensure readable contrast (white text with dark stroke, or dark text on bright block)

Suggested b-roll / visuals (mix)
- Discovery call laptop / Zoom screens (generic)
- People taking notes
- Simple animated workflow diagram
- Clock / calendar urgency
- Cost meter / calculator

Assumptions
- The public URL for this post is https://connex.digital/book/website (from the post’s link field).
- Connex Digital logo is available to InVideo for a subtle watermark.
Long video prompt
INVIDEO AI PROMPT (LONG-FORM — YouTube, 16:9)

Goal
Create a 6–10 minute YouTube video that teaches the Issue → Importance → Impact (III) framework for running better discovery calls. The video should help viewers avoid jumping into feature demos, ask better questions, quantify business impact, and narrate demos in the buyer’s words.

Source article (must reference)
https://connex.digital/book/website

Target audience
Consultants, agency owners, B2B sales reps, solution engineers, and anyone who leads discovery calls for workflow/automation projects.

Video specs
- Format: 16:9
- Duration: 6–10 minutes
- Voiceover: Conversational expert in warm US confident tone
- Presenter: Avatar talking head. Use Paul (founder) for this video.
- Music: Upbeat, trendy, subtle under VO
- Visual style: Clean SaaS motion graphics + b-roll of meetings, notes, workflow diagrams
- On-screen text: Section headings, key questions, and “key takeaway” callouts

Overall tone
Practical, calm confidence. Teach like a consultant who has run hundreds of discovery calls.

Structure (match article headings)

1) Hook (0:00–0:30)
- Visual: Paul avatar + quick montage of awkward discovery calls turning into demos
- On-screen text: “Discovery call → demo too fast?”
- VO: “If your discovery calls turn into feature demos too early, you’re not alone. Here’s a simple framework to slow down, ask better questions, and connect your recommendations to real business outcomes.”

2) Intro + what you’ll learn (0:30–1:10)
- Visual: Title card + simple 3-step graphic
- On-screen text: “Issue → Importance → Impact”
- VO: “In this video, I’ll walk you through Issue, Importance, and Impact, plus the exact questions to ask and a demo narration template you can copy.”
- Mention Connex Digital briefly on-screen.

3) What is the Issue-Importance-Impact framework? (1:10–2:10)
- Visual: Animated 3-step ladder or flow
- On-screen text:
- “Issue: what’s broken?”
- “Importance: why now?”
- “Impact: what’s it costing?”
- VO: Explain that it prevents “solutioning” too fast and keeps the call focused on value.

4) Step 1: Issue (what is broken?) (2:10–3:40)
- Visual: Workflow diagram with a highlighted failure point (handoff, approval, missing info, rework)
- On-screen text: “Step 1: Get specific”
- VO: Teach the goal: identify workflow, failure point, what “broken” looks like.
- On-screen “Questions to ask” callout (show each as it’s spoken):
- “Walk me through the last time this happened.”
- “Where does it break? What is the failure point today?”
- “Who feels the most pain when this breaks?”
- “When does this problem show up most often?”
- Add “What to listen for” overlay: concrete examples, exact failure moment, who gets blocked.

5) Step 2: Importance (why does it matter?) (3:40–5:10)
- Visual: Deadline calendar, leadership email, scaling team b-roll
- On-screen text: “Step 2: Find urgency”
- VO: Explain importance reveals urgency and business driver.
- On-screen “Questions to ask” callout:
- “Why is this important to solve right now?”
- “What can’t you do today because this is broken?”
- “What happens if this stays the same for the next 90 days?”
- “What other priorities does this compete with internally?”
- On-screen “Signals” list: deadline, leadership pressure, scaling moment, process changes.

6) Step 3: Impact (what is at stake?) (5:10–7:10)
- Visual: Cost meter, calculator, simple charts, time-to-money conversion
- On-screen text: “Step 3: Quantify outcomes”
- VO: Teach impact as cost, risk, and definition of success.
- On-screen “Questions to ask” callout:
- “How much money does this cost you?”
- “How many hours per week does this create?”
- “What errors or risks happen because of this?”
- “What would ‘fixed’ look like?”
- “If we solved this, what changes in the business?”
- Include a short “Quick impact math” segment with animated formula cards:
- “Hours wasted per week × hourly cost × people affected”
- “Delays per cycle × cycles per month × cost of delay”
- “Error rate × cost per error”

7) How to stop feature-selling (and start selling outcomes) (7:10–8:30)
- Visual: “Listen, then tell” graphic
- On-screen text: “Rule: Listen, then tell”
- VO: Walk through the 3-step rule:
1. Ask until you can summarize Issue/Importance/Impact.
2. Then demo.
3. Narrate the demo in the buyer’s words.
- On-screen “Demo narration template” (animate line-by-line):
- “You said the issue is [X].”
- “It’s important because [Y].”
- “The impact today is [Z].”
- “So I’m going to show you [workflow] because it reduces [Z] by [mechanism].”

8) Recap script + common mistakes (8:30–9:30)
- Visual: Checklist + red/green “mistake vs fix” cards
- VO: Share the recap script in a clean on-screen box, then rapid-fire the common mistakes and fixes:
- Mistake: Jumping to demo after first symptom → Fix: Finish all three I’s.
- Mistake: Generic questions → Fix: Ask for last real example + exact failure point.
- Mistake: Features over outcomes → Fix: Translate every feature to impact.

9) CTA (final 20–30 seconds)
- Visual: Connex Digital end card + subtle logo watermark
- On-screen text: “Book a video consult: connex.digital/book/video”
- VO: “If you want help running stronger discovery calls and turning what you learn into a real build plan, book a video consult at connex.digital slash book slash video.”
- Also display the source URL: https://connex.digital/book/website

Assumptions
- The post’s public URL is https://connex.digital/book/website.
- Using Paul as the presenter is acceptable for this video.
- Connex Digital logo is available for watermarking.
General
🔑 Keyword Goals
Generate LK
Generate NL
LinkedIn Post Content
🚀 Are your discovery calls turning into feature demos too quickly? It's time to slow down and focus on what really matters!

I recently shared a framework called Issue → Importance → Impact (III) that helps you ask sharper questions, quantify business impacts, and ultimately sell outcomes instead of just features. This simple yet effective approach transforms your calls into valuable conversations that drive real business results.

Check out the full article to learn how to enhance your discovery calls and create more meaningful connections with clients: Read more here.

#Sales #DiscoveryCalls #Consulting #B2B #BusinessImpact
Hidden
Tags db
đŸ·ïž
Automation Basics
Full URL
Unsplash Cover
Unsplash Cover
Prompt last generated
Mar 31, 2026
KW AI GEN
Discovery calls, sales framework, Issue Importance Impact, business outcomes
Last edited time
Aug 16, 2026 10:09 AM GMT+0
If your discovery calls turn into feature demos too early, use the Issue → Importance → Impact framework to slow down, ask better questions, and connect your recommendations to real business outcomes.

What is the Issue-Importance-Impact framework?

The 3 I’s are a simple call flow for discovery:
  • Issue: What is broken in the workflow right now?
  • Importance: Why does it matter, and why does it matter now?
  • Impact: What does it cost to keep this broken, and what does “fixed” look like?
Used well, this framework helps you avoid “solutioning” too fast and keeps your call focused on value instead of features.

Step 1: Issue (what is broken?)

Your goal is to get specific about the workflow, the failure point, and what “broken” looks like in context.
Issue discovery questions
  • “Walk me through the last time this happened.”
  • “Where does it break? What is the failure point today?”
  • “Who feels the most pain when this breaks?”
  • “When does this problem show up most often?”
What to listen for
  • Concrete examples instead of general complaints
  • The moment the workflow fails (handoff, approval, missing info, rework)
  • Who gets blocked downstream

Step 2: Importance (why does it matter?)

Importance is where you uncover urgency and the business driver. This is also where you learn what the buyer is really trying to protect or unlock.
Importance discovery questions
  • “Why is this important to solve right now?”
  • “What can’t you do today because this is broken?”
  • “What happens if this stays the same for the next 90 days?”
  • “What other priorities does this compete with internally?”
Common signals of importance
  • A deadline or upcoming event
  • Pressure from leadership
  • A new hire, new team, or scaling moment
  • A change in process, tool stack, or reporting expectations

Step 3: Impact (what is at stake?)

Impact turns the conversation into outcomes. You are quantifying cost, risk, and the definition of success.
Impact discovery questions
  • “How much money does this cost you?”
  • “How many hours per week does this create?”
  • “What errors or risks happen because of this?”
  • “What would ‘fixed’ look like?”
  • “If we solved this, what changes in the business?”
Quick impact math (simple and effective)
If you can get even rough numbers, you can turn pain into a clear story:
  • Hours wasted per week × hourly cost × number of people affected
  • Delays per cycle × cycles per month × cost of delay
  • Error rate × cost per error

How to stop feature-selling (and start selling outcomes)

The rule is simple: listen, then tell.
  1. Ask Issue/Importance/Impact questions until you can summarize the real problem.
  2. Only then, demonstrate a solution.
  3. While you demonstrate, narrate the value in the buyer’s words.
Demo narration template
  • “You said the issue is [X].”
  • “It is important because [Y].”
  • “The impact today is [Z].”
  • “So I am going to show you [this workflow] because it reduces [Z] by [mechanism].”

A simple recap script you can use at the end of a discovery call

Use this to close cleanly without getting pushy.
“Let me recap what I heard. The issue is [workflow + failure point]. This is important because [why now]. The impact is [cost, risk, or missed opportunity].
 
Today we looked at [what you demonstrated] as a way to address that. If you want help implementing this properly, I can book a follow-up and map out the full build with you.”

Common mistakes (and how to avoid them)

  • Mistake: Jumping to a demo after hearing the first symptom.
    • Fix: Commit to finishing all three I’s before showing anything.
  • Mistake: Asking generic questions that stay abstract.
    • Fix: Ask for the last real example and the exact failure point.
  • Mistake: Talking about features instead of outcomes.
    • Fix: Translate every feature into a business result tied to Impact.

Discovery call checklist (copy/paste)

I can describe the workflow and the failure point.
I know why this matters now.
I can describe the business impact in time, money, risk, or missed opportunity.
My demo narration ties directly back to Issue, Importance, and Impact.
My recap summarizes Issue, Importance, Impact, and next step.

Book a call

If you want help running stronger discovery calls and translating needs into a build plan, book a free consulting call: https://connex.digital/book/website