· 8 min read

Discovery & Qualification

The "Trojan Question" for Discovery: One Question That Surfaces Pain, Budget, and Authority at Once

"If we made this work, what would success look like 12 months from now, and who else would notice?" One sentence pulls future-state, ROI, and stakeholder map. The full mechanic and 4 variations for different niches.

The "Trojan Question" for Discovery: One Question That Surfaces Pain, Budget, and Authority at Once

Most discovery questions pull one piece of information at a time. The Trojan Question pulls three: where the buyer wants to go, how much it’s worth to them, and who else is in the room that you haven’t met yet. It works because the compound structure is invisible to the buyer, they just think they’re describing success.

The Problem With Single-Layer Questions

Standard discovery questions are single-layer. “What’s your goal here?” surfaces vision. “What’s the budget?” surfaces money. “Who else is involved?” surfaces authority. Each question is useful, but each one also signals that you’re running a checklist. Buyers feel processed, not understood.

The Trojan Question collapses three qualification layers into a single conversational sentence. The buyer experiences it as one genuine question about their future. You receive it as a complete qualification signal covering future-state, ROI, and stakeholder map.

This is the core mechanic that Keenan’s Gap Selling surfaces: when you understand the full gap, current state, problem, impact, and future state, you can sell to the actual driver of the decision, not just the stated need.

Anatomy of the Classic Trojan Question

“If we made this work, what would success look like 12 months from now, and who else would notice?”

Break it into three parts:

Part 1: “If we made this work”, This presupposes engagement and frames the question inside a collaborative future. The buyer isn’t answering a hypothetical; they’re describing a co-created outcome. It subtly shifts them from evaluator to co-designer.

Part 2: “What would success look like 12 months from now”, This is the future-state question, set at 12 months because that’s long enough to imply strategic ROI, short enough to feel real. “Look like” is intentionally visual, it activates the buyer’s imagination rather than their analytical brain, which produces richer, more honest answers.

Part 3: “And who else would notice”, This is the Trojan payload. The buyer now tells you who in their organization cares about this outcome, their boss, their team, their clients, their board. That’s your stakeholder map. And because they’re describing who would notice the success, they’re implicitly telling you what it’s worth internally.

The genius of the Trojan Question is that it asks about success, but the answer reveals the full decision ecosystem. Buyers freely describe their stakeholders when you frame it as “who would notice the win”, they’d never answer that directly if you just asked “who else is involved in this decision.”

What the Answer Tells You

When a buyer answers well, you get:

Future-state clarity. “We’d have a pipeline that doesn’t require me to chase every deal” tells you they want systematic lead flow, not just a one-time project. Your proposal should emphasize process and documentation, not just deliverables.

ROI anchor. “We’d be closing 30% more of what we’re already seeing” puts a number on the gap. That number becomes your value proposition in the proposal: “Based on what you shared, closing 30% more of your current pipeline at your average deal size means X per year. The investment is Y.”

Stakeholder map. “My COO and the sales team would definitely notice” tells you the decision doesn’t live with just the person on the call. You need to either get in front of the COO or give your contact the materials to sell internally on your behalf.

Four Variations for Different Niches

For brand designers: “If the new identity completely landed, if it worked the way you’re hoping, what does the business look like in 12 months? And which clients or partners would notice first?”

For copywriters and content strategists: “If the messaging really clicked with your audience, what would change in your pipeline over the next year, and who internally would feel that shift most?”

For web developers: “If the new site performed the way you’re imagining, what does that do to your lead volume or conversion rate 12 months out, and who else in the company would care about that?”

For consultants and coaches: “If the changes you’re trying to make actually stuck, what does your operation look like at the end of next year, and which person on your team would feel the biggest difference?”

All four follow the same structure: hypothetical success frame + 12-month future state + social proof anchor. The domain language changes. The logic doesn’t.

When the Answer Is Weak

A weak answer to the Trojan Question sounds like this: “Things would just be running more smoothly.” That’s not usable. It tells you nothing about ROI or stakeholders.

Weak answers usually mean one of three things:

  1. The pain isn’t acute enough. If the buyer can’t describe success concretely, the gap may not be painful enough to motivate purchase. Follow up with: “When you say smoother, what specifically is rough right now that you’re most eager to fix?”

  2. They don’t trust you yet. Specificity requires vulnerability. If the buyer is still in guard mode, they’ll answer vaguely. Use a softer mirror: “Smoother in which ways?” and give them silence to fill.

  3. The stakes are low. For small engagements, the Trojan Question may be over-engineered. Use it selectively on mid-to-high-ticket projects where decision complexity justifies the depth.

The Follow-Up That Extracts the Budget Layer

The Trojan Question doesn’t directly ask about budget, but you can bridge to it naturally: “That’s a real outcome. What would it be worth to you to get there, not in terms of project cost, but in terms of the business impact?”

This question, asked after the buyer has described their success picture, lands completely differently than “What’s your budget?” The buyer has already invested emotionally in the future state. Now they’re more willing to quantify it. That self-reported number becomes your proposal anchor.

Logging Trojan Question Answers in Waco3

After each discovery call, log the buyer’s answer to the Trojan Question directly in Waco3’s deal notes. Use three fields: future-state summary, ROI signal, and stakeholders mentioned. This data structures your proposal and your follow-up sequence automatically, you’re not guessing what the buyer cares about, you’re reflecting it back to them in writing.

One Sentence That Does the Work of Ten

The Trojan Question is worth practicing before your next call. Write it out. Say it aloud. Make it sound natural. The first time you ask it and a buyer spends four minutes answering without any follow-up prompting, you’ll understand why single-layer questions are a tax on your discovery calls.

One question. Three answers. Full picture.