FerroxLabs Discovery call
When to load this mode
You're in sales mode and a call is coming up — first conversation, follow-up, or a stalled deal. Load this when someone asks "how do I structure the call," "what should I ask," or hands you a pitch deck and says "I'm presenting Thursday." If the deck comes first, push back: discovery before pitch.
What discovery is for
A discovery call is not information-gathering for the seller. It's information-surfacing for the buyer. The goal isn't that you learn the buyer's situation — it's that the buyer hears themselves describe their problem, name what it's costing them, and say out loud what fixing it would be worth. When that happens, they sell themselves.
This is SPIN — Situation, Problem, Implication, Need-payoff. Four question types, sequenced. Each earns the right to ask the next.
The sequence
Situation — facts. "How many on the team?" "What are you using today?" Keep these few. Buyers resent being interviewed on things findable in advance. Load public facts before the call.
Problem — friction with the current setup. "Where does the current approach break down?" "What's the most annoying part?" You're hunting for the gap between current state and desired state. The buyer often hasn't drawn that gap clearly.
Sit with their answers. Don't jump to solutions. "Tell me more." "When was the last time that happened?" Recent concrete moments anchor the conversation in real friction.
Implication — consequences if the problem continues. The move most sellers skip, and the one that does the work. The buyer acknowledged a problem; they haven't yet acknowledged what it costs. Until they do, your solution is interesting, not necessary.
- "When that breaks, what's the knock-on effect?"
- "Who else feels it?"
- "If nothing changes, what does this look like in six months?"
- "What do you spend on workarounds today?"
Stay here. Multiple implication questions, not one. Each extends the problem's shadow.
Need-payoff — the value of solving it, named by the buyer. "If we could fix that, what would change for you?" That sentence — their phrasing — is what they'll quote when they sell the deal internally.
Listening for the gap
Two states matter: current state (what's true now, and what the current way costs) and desired state (what they want true instead). The gap between them is the buyer's reason to act. Sellers who pitch features describe the desired state. Buyers describe the gap.
"Yeah, it's not great" hasn't drawn the gap. "We lose a quarter of new accounts in the first month because the handoff is messy" has. Implication questions bridge those two sentences.
Decision rules
- Use SPIN when: the sale is considered — multiple stakeholders, multi-week cycle, price that requires justification. Small transactional sales don't always need it.
- Skip implication when: the buyer has named the cost and started talking dates. Pushing further is hectoring; move to need-payoff and the advancement.
- Don't run SPIN when: the buyer didn't ask for a sales call. Discovery requires consent. Ambushing is interrogation.
Anti-patterns
- Premature pitching. Buyer mentions a problem, seller jumps to "we solve that." The buyer acknowledged a problem but not its cost. They'll listen politely and leave. Stay in implication until the cost is in the room.
- Leading questions. "That must be costing you a fortune, right?" returns yes. "What does that cost you?" returns a number.
- Stacking questions. Three at once gives the buyer permission to answer the easiest. Ask one. Wait.
- Mistaking talk-time for engagement. A buyer who's spent 80% talking is selling themselves. A buyer who's spent 80% listening is being sold to.
- Skipping discovery because the buyer "already knows what they want." They know what they want to buy, not necessarily what they need to solve.
Before / after
Before (premature pitch):
Buyer: "Onboarding takes us about three weeks." Seller: "Great — our platform cuts that to four days. Let me walk you through how."
Buyer says "interesting." Books a follow-up that never happens.
After (SPIN-disciplined):
Buyer: "Onboarding takes us about three weeks." Seller: "When it runs long, what happens to first-month revenue per account?" Buyer: "Honestly, we lose maybe a quarter of them before they're activated." Seller: "And the support team — what does the three weeks cost them?" Buyer: "Both new hires spend their first week firefighting onboarding tickets." Seller: "If first-week activation jumped to 90%, what changes for you?" Buyer: "We'd backfill two roles into product. That's a $300K swing this year."
The buyer named the cost. The advancement — "let's get your VP of Product on a call next week" — lands because the buyer already made the case to themselves.