The Discovery Conversation Tree | The Arena Sales Training

Opening Question"What's prompting you to look into this now — what changed?"

Maps to Phase 2 (Trigger) + Phase 3 (Deep Why), Act 1. This is the reference-depth zone — every branch below gets a fully tailored follow-up tree, the model for how deep the other four zones can go.

Lane	Premise to Surface	The Strike (short)
A. Specific incident / scare	Human detection is fast enough to prevent escalation	The gap between start and confirmation exists whether or not this one was nothing
B. "Just being proactive"	Exploring, not a confirmed problem — urgency risk	"Gathering info" often becomes 12 months with nothing changing
C. Compliance / mandate-driven	Compliance alone is the driver — checkbox risk	If something happens anyway, will "we were compliant" feel like enough?
D. Peer-driven	"If it worked for them, it'll work for us" — untested	Check what's actually similar before assuming it copies over
E. "My boss told me to look into this"	The buyer may be a messenger, not the champion	Avoid building a case the boss then guts with questions we can't answer
F. "Saw it, got curious"	Curiosity-driven — no confirmed problem yet	Buyers realize the gap once they see what's possible — look at the gap, not the "need"
G. Strategic / completing the picture	Sophisticated buyer valuing a complete, deliberate build	Earn the right to ask early — map what's already in place first

Branch A — Names a specific incident or scare ▸

Q1: "What happened, and how close did it come to escalating?"

→ "Turned out to be nothing, but the response took too long" leads to: "How long, roughly, from first report to confirmed safe?"
→ "Not the first time" leads to: "How many times has this come up in the last year or two?"

Q2: "What did your response actually look like in that moment?"

→ "We relied on someone physically seeing it and calling it in" leads to: "So if nobody happened to see it, is there any other way it gets caught?"

Premise surfaced: human detection and reporting is fast enough to prevent escalation — nearly every response path above starts to crack that premise on its own.

Objection: "It turned out to be a false alarm — maybe our existing process worked fine."

Steelman: "So the system worked in the sense that nothing bad happened, and your team responded in the time they had — that's real, worth crediting."
Strike: "The part I'd look at is the gap between when it started and when it was confirmed. That gap exists whether or not this one turned out to be nothing — the next one might not give you that gap for free."

Transition to Phase 3: "Given how that day felt in the moment — what would it have meant for you personally if it had gone differently?"

Branch G — No incident, just knows this is a critical layer ▸

Q1: "What would this layer be covering that nothing else today covers?"

→ "Honestly, I'd want you to tell me" leads to: "Fair — before I do, what's your instinct about where the biggest blind spot is today?"

Q2: "What made this rise to the top of the list now?"

→ "Slowly building out the stack, this is the next piece" leads to: "What's already in place, and what made this the next logical step?"

Premise surfaced: a strategic, principled buyer — values completeness of the stack over reacting to a single event. Often the most sophisticated, best-informed buyer type.

Objection: "We want to make sure this integrates cleanly with what we already have, not bolt on."

Steelman: "Makes sense — you've been building this deliberately, piece by piece, and the last thing you want is something that doesn't fit."
Strike: "That's exactly the right question to ask early — let's map what you already have before going further, so we're not proposing something that creates more work than it saves."

Transition to Phase 3: "Since you've clearly thought about this holistically — what would it mean for you personally to be the one who closed this gap, versus leaving it open?"

Phase 3 Gate (mandatory before Act 2, applies after any branch above): "What does it mean to you personally if you get this right?" and "What happens to you personally if you don't, and something happens?" Exit rule: do not advance until personal stakes are actually named — see exactly what happens when this gets skipped in the case study.

Opening Question"How does something like this typically get funded at your organization — existing budget, or a new ask?"

Maps to Phase 5 (Business Case), Act 2 — budget explored and value anchored before price ever gets discussed.

Lane	Premise	The Strike (short)
A. Existing budget line	Budget existing ≠ budget available	It's whether this beats what else that budget could fund
B. Grant / bond-funded	Money may carry strings or a clock	Confirm qualification early or it gets much harder later
C. No budget — new ask	Deal lives or dies on the business case	Build the ROI / cost-of-inaction case in their language, now
D. Budget may not be enough	Wrong-scope / sticker-shock risk	A phased approach beats walking away from the whole thing
E. Guarded — won't share numbers	Budget unscoped, or trust isn't there yet	Pricing lands better with a range — see the case study for what happens when it doesn't

Branch D — Budget exists, but might not be enough ▸

Q1: "What's the range you're working with, roughly?" Q2: "Is that a hard ceiling, or a starting point you could build a case to expand?"

Premise surfaced: real risk of proposing at the wrong scope — too small to matter, or a number so far above expectation it causes sticker shock and silence.

Objection: "We probably can't afford full deployment."

Steelman: "Completely fair, especially before knowing actual costs."
Strike: "Rather than assume full deployment is the only option, let's talk about a phased approach — so we're solving the right first problem instead of walking away from the whole thing."

Transition: "What would a smaller start need to prove to justify expanding later?"

Branch E — Guarded, won't share numbers ▸

Q1: "No problem if you're not ready to share a number — what would need to be true about a proposal for it to feel reasonable?" Q2: "Is the hesitation about sharing a number, or that budget hasn't really been discussed internally yet?"

Premise surfaced: guardedness usually means either budget hasn't actually been scoped internally, or trust in the relationship isn't there yet.

Objection: "Just send us pricing and we'll let you know."

Steelman: "Fair — you don't want to negotiate against yourself before seeing anything."
Strike: "Happy to send pricing — it'll land better if I understand your rough range first, so I'm not over- or under-scoping it. This is exactly the pattern that turns into weeks of silence — see the case study."

Transition: "Setting the number aside — what would this need to deliver, whatever the investment turns out to be, to feel worth it?"

Opening Question"When are you hoping to have something like this in place?"

Maps to Phase 6 (Timeline), Act 2 — tests whether a stated deadline is real or aspirational.

Lane	Premise	The Strike (short)
A. Hard deadline tied to an event	Real only if something external enforces it	Map backward from the date now
B. Vague / soft ("ASAP", "this year")	Masks low urgency or an unstated deadline	"ASAP" quietly becomes 18 months without a forcing point
C. No real timeline — exploring	Indefinite-exploration risk	Agree what would need to change for it to move
D. Blocked by procurement	The constraint is the procurement clock, not interest	Cooperative contract / sole-source / parallel paperwork
E. External deadline (grant/mandate)	Urgency only if the miss is actually felt	Everything upstream takes time — when does the clock start?

Branch A — Hard deadline tied to a specific event ▸

Q1: "What happens if that date slips — is it a real deadline or more of a target?" Q2: "What's driving that specific date — fiscal year, board calendar, something else?"

Premise surfaced: a stated deadline is only real if something external enforces it — otherwise it's aspirational.

Objection: "We really need this by [date], no matter what."

Steelman: "Good to know there's a real target — that helps us map backward on what needs to happen and when."
Strike: "Implementation, procurement, and approvals all take real time. Let's map backward from that date now, so we're not discovering in month two that it was never realistically possible."

Transition: "Given that date — who needs to be involved and approve this for it to actually happen in time?"

Branch D — Blocked or slowed by procurement ▸

Q1: "Walk me through what has to happen procedurally before you could sign anything." Q2: "How long has a process like that taken in the past, for something similar?"

Premise surfaced: the constraint isn't interest — it's the procurement clock.

Objection: "Even if we wanted this tomorrow, our process won't allow it."

Steelman: "That's real, and better to know now than build a timeline that ignores it."
Strike: "Let's see if there's a way to work within it — a cooperative purchasing contract, sole-source justification, or starting paperwork in parallel — so procurement isn't the reason this stalls."

Transition: "Who owns that procurement process, and when's the right time to loop them in?"

Opening Question"Walk me through who else needs to be involved for this to actually get approved."

Maps to Phase 7 (Buying Path), Act 2 — the phase most responsible for deals that stall late.

Lane	Premise	The Strike (short)
A. Single contact claims authority	Self-reported authority, untested at this price	Has anything in this range gone through without a second signature?
B. Clear chain named upfront	Named chain, but economic buyer never in a real conversation	If they first hear it at pricing, that's when deals stall
C. Buyer doesn't know the chain	Uncertainty is itself a signal	Find out together rather than guess
D. Committee, competing stakeholders	Any one function's "no" stalls it	Understand each concern early, especially IT's
E. Hidden veto player emerges late	The dangerous ones aren't on the obvious chain	Name who'd ask the hard question, have the answer ready
F. Sole-source / RFP formality	The process is the biggest timeline and competitive risk	Compete within it — cooperative or sole-source path?

Branch B — Clear chain named upfront (the pattern behind our case study) ▸

Q1: "You mentioned [name] would need to sign off too — what's their role in this exactly?" Q2: "Have they been part of any of these conversations, or hearing about this secondhand?"

Premise surfaced: a named chain is good — but if the real economic buyer has never been in a live conversation, decisions risk getting made without true buy-in. This is exactly what happened in the case study.

Objection: "[Champion]'s handling this — no need to involve leadership yet."

Steelman: "Makes sense to keep this efficient and not pull in leadership before there's something concrete to show."
Strike: "The thing to watch for: if they hear about this for the first time at pricing, that's usually when deals stall. Would 15–20 minutes with them before we're that far along help — not a pitch, just so they're not walking in cold?"

Transition: "When would be a natural point to loop them in without it feeling premature?"

Branch D — Committee, competing stakeholders ▸

Q1: "Who's on that committee, and what does each of them care most about?" Q2: "How does that group typically reach a decision — consensus, majority, or one person's final say?"

Premise surfaced: committees dilute single-threaded risk but create multi-threading risk — a "no" from any one function can stall everything.

Objection: "It's a group decision, so I can't really speak for what they'll think."

Steelman: "That's honest — better to know that now than assume you speak for everyone."
Strike: "Worth understanding each function's likely concern in advance, especially the technical/IT function's — integration questions tend to stall committees the longest."

Transition: "Of that group, who's most likely to raise a concern we should get ahead of now?"

Opening Question"Are you looking at any other solutions or vendors alongside this?"

Maps to Phase 8 (Competitive Landscape), Act 2.

Lane	Premise	The Strike (short)
A. Named competitors	They already have an informal scorecard	Compete on what actually determines outcomes, not the loudest feature
B. Vague "a few things"	No real criteria yet — cheapest/loudest wins by default	Agree the criteria so it's apples to apples
C. Claims none	Exclusivity holds only until a reason appears	If the process required alternatives, would that change?
D. Doing nothing / status quo	The real competitor is inertia	"Worked so far" is true until the day it isn't
E. Incumbent adjacent vendor bolt-on	Incumbents win on convenience, not capability	This is a narrow, hard problem we do exclusively
F. Price-shopping / lowest-bid	Race to the bottom without weighted criteria	The lowest bid becomes the priciest mistake next year

Branch A — Openly evaluating named competitors ▸

Q1: "What have you seen from them so far, and what stood out?" Q2: "What would need to be true about a solution for you to feel confident choosing between them?"

Premise surfaced: the buyer already has an informal scorecard — find out what's on it before being evaluated blind.

Objection: "They're cheaper / have a feature we don't have."

Steelman: "Good to know — that's real and worth taking seriously, not dismissing."
Strike: "Rather than compete on that one point, let's look at what actually matters in your environment — accuracy, real-world speed, and what happens the moment it counts. Those determine whether this works when it matters."

Transition: "Beyond price and features — who else at your org has an opinion on them versus us?"

Branch D — Comparing against doing nothing / status quo ▸

Q1: "What does 'doing nothing new' actually look like day to day right now?" Q2: "What would have to happen for the status quo to stop feeling like enough?"

Premise surfaced: the real competitor here isn't another vendor — it's inertia, and inertia is usually winning right now.

Objection: "What we have today has worked so far."

Steelman: "True, and worth acknowledging — nothing bad has happened yet."
Strike: "'Worked so far' is only true until the day it isn't, with no early warning for which day that is. The question isn't whether today's approach has failed — it's whether you're comfortable with how much notice you'd get if something happened tomorrow."

Transition: "If you pictured the actual moment something happened — what's the first thing today's setup would need to get right?"

Every branch above is drilled in live training sessions with role-play and rehearsal against the actual objections that show up on real calls — see the full curriculum.