# Discovery Call No-Go Decision Framework

> A branching decision tree that identifies the five core disqualification triggers mid-discovery, maps them against deal size thresholds, and gives you word-for-word exit lines for each scenario. Use it to end bad-fit calls cleanly without burning the relationship or your pipeline credibility.

Free framework for sales reps. Topic: [Discovery & Qualification](https://www.peerlab.ai/library/topic/discovery-qualification/). Published by PeerLab in the [Sales Enablement Resource Library](https://www.peerlab.ai/library/). Source: https://www.peerlab.ai/library/discovery-call-no-go-decision-framework/

## How to use it

Print or pull up this framework before every discovery call and keep it visible alongside your call notes. When a disqualification signal appears, run it through the relevant branch to get a go/no-go verdict before you invest another thirty minutes. Use the exit scripts verbatim until the logic becomes instinct.

## What's inside

- Five named disqualification triggers with clear definitions and signal examples
- Deal size thresholds that adjust the go/no-go verdict for each trigger
- A branching decision tree you can follow in real time during a call
- Word-for-word exit scripts for each disqualification scenario
- A "stay in the call" override checklist for ambiguous signals
- Two named failure modes with the specific behaviours that cause them
- A "when NOT to disqualify" section covering the most common false positives
- A post-call logging prompt to build your personal signal accuracy over time

## What this is for

Most qualification frameworks tell you what a good deal looks like. This one tells you what to do when you are twenty minutes into a discovery call and it is clearly not a good deal. The decision to exit is a skill. Done badly, you waste another forty minutes and leave the prospect feeling misled. Done well, you free both parties and leave the door open for a future fit.

This framework covers five disqualification triggers, the thresholds at which each trigger becomes a hard no-go, and the exact words to use when you end the call.

---

## The five disqualification triggers

| # | Trigger | Definition |
|---|---------|------------|
| 1 | Budget ceiling | Confirmed maximum budget is below your minimum viable deal size |
| 2 | No articulated pain | Prospect cannot name a specific, felt problem, only vague curiosity |
| 3 | Wrong authority tier | Your contact has no budget ownership and no path to the decision-maker |
| 4 | Competitor lock-in | Active contract with a direct competitor, no stated dissatisfaction |
| 5 | Timeline fantasy | Stated urgency is aspirational with no event, deadline, or consequence driving it |

---

## The decision tree

Work through each trigger in order. Stop at the first hard no-go verdict and use the corresponding exit script.

---

### Branch 1: Budget ceiling

**Signal questions:**
- "What budget have you set aside for solving this?"
- "Has finance approved a number, or is this still exploratory?"

**Verdict logic:**

| Confirmed budget vs. your floor | Deal size threshold | Verdict |
|---|---|---|
| Below your minimum by more than 30% | Any deal size | Hard no-go |
| Below your minimum by 10-30% | Sub-£10k deals | Hard no-go |
| Below your minimum by 10-30% | £10k-£50k deals | Conditional: only continue if they confirm budget review is possible this quarter |
| At or above your minimum | Any | Continue |

> **Exit script (budget ceiling):**
> "Based on what you've shared, the investment required to get you [specific outcome they named] sits above what you've budgeted for right now. I don't want to take more of your time on a fit that isn't there today. Can I suggest we pick this back up when your budget cycle opens in [month]? I'll send you one resource that's directly relevant to what you described, so the conversation has a head start."

---

### Branch 2: No articulated pain

**Signal questions:**
- "What specifically prompted you to take this call today?"
- "What happens if you don't solve this in the next six months?"

**Red flags:**
- "We're just exploring options."
- "Our CEO saw something about this and asked me to look into it."
- No consequence stated when you ask the second question.

**Verdict logic:**

| Signal | Verdict |
|---|---|
| Prospect names a specific, measurable problem | Continue |
| Prospect names a vague dissatisfaction but engages when you probe | Conditional: run one more probe before deciding |
| Prospect cannot name any problem after two direct questions | Hard no-go |

> **Exit script (no articulated pain):**
> "It sounds like you're at the awareness stage rather than the 'we need to fix this now' stage, and that's completely fine. The honest truth is our process works best when there's a specific problem on the table. Rather than walk through a full discovery that doesn't map to where you are, let me send you [specific piece of content] that tends to help people at this stage sharpen what they're actually trying to solve. When something crystallises, I'm genuinely worth calling."

---

### Branch 3: Wrong authority tier

**Signal questions:**
- "When a decision like this gets made at your company, who else is typically involved?"
- "Are you the person who would sign off on this, or does it go to someone else?"

**Verdict logic:**

| Contact's position | Path to decision-maker | Verdict |
|---|---|---|
| Budget owner or economic buyer | N/A | Continue |
| Influencer or champion with confirmed access to decision-maker | Can get them on a follow-up call | Conditional: agree next step before ending this call |
| Influencer with no access or no willingness to facilitate access | N/A | Hard no-go |
| Gatekeeper on explicit research task, decision-maker unknown | N/A | Hard no-go |

> **Exit script (wrong authority tier):**
> "I want to make sure I'm being straight with you. What you've described is genuinely worth solving, but the conversation I need to have involves [budget / strategic direction / final sign-off], and it sounds like that sits with [role they named]. I don't want to put you in an awkward position by going around you, so I'd rather do this properly. Would you be comfortable introducing me to [that person], or would it make more sense for me to reach out to them directly with your name attached?"

*Note: if they say no to both options, that is your no-go signal. Use the budget ceiling exit script substituting "fit" for "budget".*

---

### Branch 4: Competitor lock-in

**Signal questions:**
- "Are you currently using anything to manage this?"
- "How happy are you with what you have?"

**Verdict logic:**

| Situation | Verdict |
|---|---|
| No current solution | Continue |
| Current solution, actively unhappy, contract ending within 6 months | Continue |
| Current solution, neutral or happy, no stated reason to switch | Hard no-go |
| Current solution, locked into multi-year contract, no dissatisfaction | Hard no-go |

> **Exit script (competitor lock-in):**
> "It sounds like you're well served right now, which is a good position to be in. I'm not going to try to create a problem that isn't there. What I would suggest is this: keep our details somewhere accessible. If anything changes with your current setup, or when your renewal comes around, I'd welcome the chance to show you what's changed on our side. I'll drop you a short note so you have my contact ready."

---

### Branch 5: Timeline fantasy

**Signal questions:**
- "What's driving the timeline you mentioned?"
- "What happens internally if this slips to Q3 instead of Q1?"

**Red flags:**
- "We'd love to have something in place by [date]" with no event or consequence behind it.
- Timeline shifts freely when you probe.
- No internal project, launch, compliance deadline, or leadership mandate attached.

**Verdict logic:**

| Signal | Verdict |
|---|---|
| Hard deadline with named consequence (contract, launch, audit, board commitment) | Continue |
| Soft preference, but prospect acknowledges it and wants to create urgency | Conditional: only if budget and authority are already confirmed |
| Aspirational date with no consequence and no flexibility to create one | Hard no-go |

> **Exit script (timeline fantasy):**
> "I appreciate the honesty. What I'm hearing is that the timing is flexible, which usually means this will move at the pace of other priorities. I'd rather not run a full evaluation process and then have it sit in a queue. Here's what I'd suggest: let's agree a specific trigger, a date or an event that makes this real, and I'll put a reminder in to reach out then. That way we're not wasting each other's time on a cycle that isn't ready to move."

---

## Override checklist: when to stay in the call despite a weak signal

Check these before exiting. If two or more apply, continue the call.

- [ ] The signal is ambiguous, not confirmed. You heard one phrase, not a consistent pattern.
- [ ] The deal size is large enough that partial qualification warrants a second call.
- [ ] The prospect has high strategic value (reference account, beachhead into a new vertical).
- [ ] The disqualification trigger is the type that can change within one quarter.
- [ ] You have not yet asked the follow-up probe question for this branch.

---

## The two failure modes to watch for

**Failure mode 1: The activity addict.**
You know the call is going nowhere but you keep going because you need to hit call targets or because an empty pipeline is more uncomfortable than a bad-fit deal. The tell is that you are asking questions you already know the answers to. Exit rates below 15% on discovery calls are a warning sign that you are not disqualifying enough.

**Failure mode 2: The surface-signal sniper.**
You disqualify on the first piece of friction. The prospect hesitates on budget and you wrap up before asking whether budget review is possible. The tell is that your pipeline is clean but your conversion from discovery to proposal is below 40%. Run the full branch logic before you exit.

---

## When NOT to use this framework

- On inbound leads from known high-intent sources where procurement is already involved. Those calls warrant patience.
- On calls where the contact has explicitly said they are building the business case and need your help. That is a different conversation.
- On deals referred to you by a mutual contact who has already pre-qualified the fit. Verify, but do not run a disqualification process out of the gate.

---

## Post-call log prompt

After every discovery call where you used a no-go verdict, record:

1. Which trigger fired?
2. What was the exact signal that confirmed it?
3. Did the prospect respond to the exit script positively, neutrally, or negatively?
4. In 90 days, was the no-go verdict correct?

After ten calls, review your accuracy by trigger type. Most reps are over-sensitive on one trigger and under-sensitive on another. The log tells you which.