Welcome
Consultative Selling Mastery Portal
Your complete Consultative Selling training system for selling ODeX and Creating Future Ready Organizations to Entrepreneurs and CEOs — grounded in Neil Rackham's research from 35,000+ real sales calls across 23 countries.
0
XP Earned
0/10
Cases Studied
0
Badges Earned
—
Quiz Score
Your Learning Path
About the Methodology
Consultative Selling was developed by Neil Rackham after analysing 35,000+ B2B sales calls in 23 countries. It is the most empirically validated sales methodology for complex, high-value sales — exactly the context of ODeX and Future Ready Organizations.
Recent Badges
Complete modules to unlock badges
The Four Core Questions of Consultative Selling
S
Situation
Understand their current reality. 3–5 questions max.
P
Problem
Surface hidden pain — not just stated problems.
I
Implication
Amplify consequences. This is where deals are won.
N
Need-Payoff
The buyer articulates the value — before you pitch.
Quick Start — Featured Cases
Theory Hub · Module 1
Consultative Selling — Foundation
The most empirically validated B2B sales methodology ever developed. Not opinion — a finding from 35,000+ analysed sales calls across 23 countries and 12 years of research by Neil Rackham and the Huthwaite Institute.
"In major sales, success comes not from what you tell the buyer, but from the questions you ask. The seller who talks most wins least."
Neil Rackham — SPIN Selling
Why SPIN was created
Traditional sales training taught techniques designed for small, transactional sales — closes, objection handling, product features. Rackham's research proved these techniques actually harm success rates in complex, large-value sales. SPIN was the first methodology built specifically from evidence gathered in high-stakes B2B conversations.
Why it matters with CEOs
Senior buyers have seen every pitch. They resist being "sold to." SPIN works because it makes the CEO the author of their own buying decision. You guide the thinking through questions; they reach the conclusion through their own reasoning. The product arrives as the answer to their own stated need — not a pitch they have to evaluate.
The 4 Stages of Every Sales Call (Rackham)
Every sales call moves through four stages. SPIN dominates the most important one.
1
Preliminaries
Opening, rapport, context-setting
2
Investigating ★
This is where SPIN questions live. The longest, most critical stage.
3
Demonstrating
Only introduce the product after Investigating is complete
4
Obtaining Commitment
Aim for an Advance — a concrete next step, not just "I'll think about it"
Implied vs Explicit Needs (Critical Distinction)
Implied Needs — Vague dissatisfactions: "We have some issues with our management team." Problem questions surface these.
Explicit Needs — Clear statements of want or desire: "We need a structured way to develop our managers." Need-Payoff questions convert Implied into Explicit. Only when a need is Explicit can you successfully present your product as the solution.
Features vs Advantages vs Benefits
Feature — A fact about your product. Neutral.
Advantage — How a feature could help. Can backfire if no explicit need exists.
Benefit — How a feature meets an Explicit Need. This is what persuades. This is why Need-Payoff must come before product presentation — without explicit needs, you can only show Advantages.
From SPIN Selling Fieldbook (Rackham): "A question only works as a SPIN question if it develops needs — not because it fits a definition. Ask yourself: 'Is this question moving the buyer toward an explicit need?' If not, it's background data, not investigation."
ODeX — What it solves
The founder bottleneck. ODeX gives organisations a structured system so managers operate at the founder's quality of judgment — without requiring the founder's personal involvement in every decision. Scale without dilution.
Future Ready Organizations — What it solves
Leadership misalignment on the future. A CEO workshop that equips leadership teams with a shared mental model for disruption, a unified strategic posture, and the decision speed to match market pace. For leaders who know the current model won't be enough.
Theory Hub · Module 2
How to Prepare Your Questions
Great SPIN conversations are never improvised. Each question type requires a distinct preparation discipline. The SPIN Selling Fieldbook identifies question preparation as the most underinvested skill among experienced salespeople.
Rackham's Practice Rule (Fieldbook): "Practise no more than two new question techniques per sales call. Trying to master all four question types simultaneously produces awkward, mechanical conversations. Build each skill in sequence."
S
Preparing Situation Questions
Research first. Ask only what you cannot know.
⌄
Before writing any situation questions, do your research. CEOs are highly attuned to whether you've prepared or not. Every question you ask that could have been answered by 10 minutes on LinkedIn signals disrespect.
Pre-call research checklist
- →Company LinkedIn: headcount trend, recent hires, leadership team tenure
- →CEO/Founder LinkedIn: career history, recent posts, previous companies, education
- →Company website: products, stated values, "About" page, leadership bios
- →News & press: funding rounds, expansion announcements, awards, controversies
- →Glassdoor/Ambitionbox: culture signals, attrition themes, leadership reviews
- →Referrer intelligence: what does your mutual contact say the CEO cares about most right now?
- →Industry news: what is disrupting their sector in the last 6–12 months?
The hypothesis method: Convert situational knowledge into testable hypotheses. "Given your expansion to 3 cities, I imagine leadership bandwidth is stretched — am I reading that right?" This shows you've thought about them, not just read about them.
P
Preparing Problem Questions
Build a problem map. Prepare 8–10, use 3–4.
⌄
Problem questions are most powerful when they're grounded in patterns — the predictable pains of CEOs at a specific stage. Prepare more than you'll use, then select based on what Situation reveals.
Problem sources to map before the meeting
- →Role-based pains: What do founders/CEOs at 50–500 people universally struggle with?
- →Stage-based pains: Growth, stabilisation, turnaround, succession — each has signature problems
- →Signal-based pains: Glassdoor mentions micromanagement? High leadership churn on LinkedIn?
- →Product-linked pains: Reverse-map from ODeX/FRO benefits — what problems must exist for these to be valuable?
Problem question starter templates
How difficult is it to ensure your managers execute consistently when you're not in the room?
When your best people get promoted into management, how smoothly does that transition tend to go?
How satisfied are you with the quality of decisions being made at the middle-management level?
How confident are you that your current business model will be competitive 5 years from now?
The "3 problems deep" technique: For each surface problem, prepare 2 follow-up questions that go deeper. If they say "managers aren't consistent," your next P question should go one layer down: "When that inconsistency shows up, where does it hurt most — decisions, culture, or customer experience?"
I
Preparing Implication Questions
Build consequence maps. For every P, prepare 3 I questions.
⌄
Implication questions are dynamic — they must follow the specific problem the buyer just named. Pre-build a "consequence map" for each likely problem. When the buyer names the problem, you already know exactly which implication questions to use.
"The purpose of Implication questions is to make problems larger — to help the buyer feel the full weight of leaving a problem unresolved."
Neil Rackham — SPIN Selling
Consequence map: 5 dimensions to probe
Revenue & profit: What does this problem cost the business financially?
Talent & retention: How does this affect who stays and who leaves?
CEO time drain: How much of the founder's week does this absorb?
Competitive position: How does this affect ability to compete and grow?
Founder's personal experience: What does this feel like to live with every day?
Culture & brand: How does this show up for customers and employees?
First, second, third-order implications: Manager inconsistency (problem) → CEO pulled in constantly (1st) → Strategic work not done (2nd) → Company stalls, talent leaves, founder burns out (3rd). Your sharpest I questions target the 3rd order.
N
Preparing Need-Payoff Questions
Write the bridge from pain to your product — in their voice.
⌄
Need-Payoff questions must be written with precision. They describe the outcome your product delivers, using language the buyer would use, so that when they answer, their answer is essentially a brief for buying your solution.
N question templates
If your managers could operate with your quality of judgment — without your involvement — how would that change your ability to lead growth rather than manage chaos?
How valuable would it be if your organisation could scale without diluting the culture and quality that make you who you are?
If your entire leadership team came out of an experience with a shared mental model for disruption, what would that unlock for you strategically?
The Reflection Rule (Fieldbook): After every strong Need-Payoff answer — never pitch immediately. Reflect first: "So if I understand, the biggest win would be [their exact words] — is that right?" When they confirm, you have explicit permission to present your solution as the answer to their own stated need.
Theory Hub · Module 7 — Advanced
NIPS Reverse Planning Method
NIPS is the preparation framework that runs in the opposite direction to SPIN. You use NIPS before the meeting to design your questions from the outcome backwards — so every question is purposeful and navigates precisely toward the ideal CEO response.
The core insight: SPIN is the conversation. NIPS is the planning.
Most salespeople plan forward: "What do I know? What problems might they have?" This produces unfocused, reactive conversations. NIPS starts with N — the ideal outcome — and reverse-engineers every question needed to get there. You still execute the conversation in SPIN order (S→P→I→N). But every question was designed in NIPS order (N→I→P→S).
N
Step 1: Need
What must the CEO say for this meeting to succeed? Write it in their voice.
I
Step 2: Implication
What consequences make that outcome urgently desirable?
P
Step 3: Problem
What problems must exist to create those implications?
S
Step 4: Situation
What context confirms these problems likely exist? What did research reveal?
Planning: N→I→P→S
→
Execution: S→P→I→N
→
CEO says their ideal outcome
N — Ideal Need-Payoff Answer (ODeX)
Write the exact words you want the CEO to say — in their voice, not product language.
"If my managers could operate at my level of judgment — without me being in the loop — I could finally do the job I'm supposed to do as CEO. That would fundamentally change how this company runs."
I — Implications that make this urgent
Work backwards: what consequences must the CEO have acknowledged for that outcome to feel urgent?
- 1.They're spending 50–70% of their week on operational decisions that should be handled below them
- 2.That time drain means strategic work — new markets, new products, key relationships — isn't getting done
- 3.Best people leave because managers can't lead — and replacements are expensive and risky
- 4.Expansion is at risk of diluting quality and culture — which are the brand's competitive moat
→ Implication questions to surface these:
What does the amount of time you spend on operational decisions cost you in terms of the strategic moves only you can make?
When managers aren't equipped to lead independently, what impact does that have on your ability to retain the best people below them?
If the expansion dilutes the culture and decision quality you've built — what does that mean for the brand you've spent years creating?
P — Problems that cause those implications
- 1.Strong individual contributors are promoted to management without the people leadership skills the role requires
- 2.There is no structured system for developing managers — it happens informally, through the founder, or not at all
- 3.Decision quality varies widely across the management team — consistency depends on individual talent, not on systems
- 4.Culture lives in the founder's head — it is not yet embedded in operating norms, rituals, or management behaviours
→ Problem questions to surface these:
When a strong performer steps into a management role, how smoothly does that transition to leading people tend to go in the first 6 months?
How consistent is decision-making quality across your management team — if you're not in the room, how confident are you in the outcome?
S — Situational signals that confirm these problems exist
Most of this you research before the meeting. You only ask about what is genuinely unknowable from public sources.
- RCompany is scaling fast — headcount growth visible on LinkedIn over last 12–24 months
- RLeadership team mostly internally promoted — check their direct reports' LinkedIn career histories
- RFounder has been CEO since day one — no COO, no clear No. 2 named publicly
- RRecent geographic expansion or new market entry announced
→ Opening situation questions (only what research couldn't answer):
You're expanding into new markets — how many of the managers leading those expansions came up internally versus were hired from outside?
What does your current process look like for getting new managers ready to lead independently — is that something you've built formally, or is it more ad hoc?
N — Ideal Need-Payoff Answer (Future Ready Organizations)
"If the whole leadership team had a shared framework for reading disruption and could make strategic decisions in days instead of weeks — we'd be a completely different company. Faster, more decisive, more attractive to the people we need."
I — Implications that make this urgent
- 1.Strategic decisions that should take days take weeks because there's no shared framework — and some never get made at all
- 2.The company has already delayed or missed key bets because leadership couldn't align on when or how to move
- 3.Top talent is choosing companies that appear more directional — the company looks reactive, not like a place where future leaders want to build careers
- 4.The CEO feels increasingly isolated — they see the disruption coming but can't get the team to feel the same urgency
→ Implication questions:
When your competitors respond faster to market shifts, what has been the commercial impact of that lag — in customers, revenue, or perception?
If your best people are choosing companies that look more directional, how does that affect your ability to build the leadership bench you need at the next stage?
If the business model isn't deliberately evolved, what does the next 3 years look like — and how does that change the options you have, including for exits or investment?
P — Problems that create those implications
- 1.The leadership team has no shared mental model for evaluating disruption — every strategic conversation restarts from scratch
- 2.Strategy and operations compete for the same leadership attention — strategy consistently loses
- 3.The CEO is the only one actively thinking long-term — everyone else is managing the current quarter
→ Problem questions:
How much of your leadership team's thinking is consumed by this quarter's operations versus building the company you want to be in 3–5 years?
When you try to have strategic conversations with your leadership team, how aligned do they tend to be — or does every conversation start from different assumptions?
S — Situational research signals
- RFast-growing company in a sector with high disruption (AI, platform shifts, regulatory change)
- RCEO LinkedIn posts frequently about macro trends, disruption, or the future — they're already thinking about it
- RNo public evidence of a structured strategy retreat or future-planning process beyond annual review
How often does your leadership team specifically set time aside to discuss where the industry is heading — not just the numbers, but the structural shifts that could change everything?
When you and your team disagree on how to respond to a major market change, how does that typically get resolved?
NIPS Pre-Meeting Planner — Complete this before every important CEO meeting
Prospect Name & Company
Product
N — Ideal Need-Payoff answer (write in their voice)
I — 3 key implications + my implication questions
P — 3 likely problems + my problem questions
S — Research done (what I already know) + 2–3 opening questions
My pivot phrase (after their Need-Payoff answer)
The NIPS/SPIN Refinement Loop: After every meeting, revisit your NIPS plan. Did the buyer's actual answers match your assumptions? Which implications landed hardest? Use this to calibrate your NIPS templates over time — building a progressively more accurate model of your ideal buyer's patterns.
Case Library
10 CEO Case Studies
Study real consultative selling conversations across industries, stages, and problems. Each case includes a full annotated conversation, 6-point analysis, and a practice exercise. Difficulty increases progressively — start with Easy cases.
Practice Arena
Write & Score Your Questions
For each scenario, write a question of the specified type. The scoring system evaluates your question across 5 dimensions and gives specific coaching to help you improve. Rackham's Fieldbook emphasises that deliberate question practice — more than any other activity — accelerates SPIN mastery.
EXERCISES DONE
0/15
AVG QUALITY
—
Fieldbook · Call Planning Lab
Plan Every Call to Win an Advance
The Fieldbook's core planning discipline: every sales call needs a written objective defined as an Advance — a concrete action the buyer agrees to that moves the sale forward. Without this, you're running conversations, not sales calls.
"Before every call, ask yourself: what is the single most important thing I want the customer to do at the end of this meeting? If the answer is anything other than a specific action — you haven't defined your objective yet."
Neil Rackham — SPIN Selling Fieldbook
The 4 Call Outcomes — Only Two Are Acceptable
Order
The buyer agrees to purchase. The best possible outcome — but rare on a first CEO call.
Advance
An agreed specific action that moves the sale forward: a demo, board intro, proposal request, pilot approval. Target this.
Continuation
"Great meeting, let's stay in touch." No commitment, no next step. The call felt good but achieved nothing.
No Sale
The buyer explicitly says no. At least it's clear — you can stop investing in this opportunity.
The Fieldbook insight: Most salespeople celebrate Continuations as success. Rackham's research proves Continuations are the enemy of pipeline velocity. A call that ends with "I'll think about it" is a failed call — even if the buyer seemed engaged. Always define and pursue an Advance.
Advances vs Continuations — Real Examples
| Stage | ❌ Continuation (avoid) | ✅ Advance (target) |
|---|---|---|
| First CEO meeting | "Send me some more information and I'll have a look." | "Can we bring your business partner and COO to a second meeting next week so they can hear this directly?" |
| After SPIN conversation | "Sounds interesting — let me think about it." | "Can we do a 2-hour working session with your top 3 managers to show them how ODeX addresses what you've described?" |
| After demo/presentation | "This looks good. I'll discuss with the team." | "Who else needs to be involved in this decision? Can we set up a time with them this week?" |
| Commercial discussion | "The pricing seems high. I'll need to consider it." | "If the numbers worked, is there anything else that would prevent you moving forward? If not, can we meet with your CFO on Tuesday?" |
| Post-proposal | "Thanks, I'll review the proposal." | "Can we schedule 30 minutes in 3 days to walk through any questions — and have a decision made by end of week?" |
| Long-running opportunity | "Still interested, just very busy right now." | "You've mentioned timing 3 times. What specific thing needs to happen inside your business before you're ready to move? Can we map that out together?" |
Fieldbook principle: Before you leave a meeting, ask yourself: "What specific action has the buyer agreed to?" If you can't name it, you have a Continuation, not an Advance — no matter how positive the meeting felt.
3 Effective Call Opening Strategies (Fieldbook)
The opening of a call establishes your right to ask questions. It should be brief, professional, and create permission — not consume the conversation. Rackham identifies three proven opening approaches.
1
The Purpose Opening
State why you're there and what you want to explore.
⌄
State your purpose clearly — not your product, your purpose. This creates immediate permission to ask questions and signals professional intent.
Mr Sharma, I asked for this meeting because a number of founders scaling into multiple cities have been sharing a common set of challenges with how leadership capability keeps pace with that growth. I wanted to explore whether any of that resonates with what you're experiencing — and if there's a conversation worth having.
Why it works: You're not selling anything yet. You're positioning yourself as someone who has observed a pattern and is testing whether it applies. The CEO is curious, not defensive.
2
The Referral Opening
Use a mutual connection's observation to establish relevance.
⌄
A referral from a trusted source dramatically increases opening credibility. Use their exact words — don't paraphrase, because the CEO often talks to that person.
Priya, Anand suggested I reach out. He mentioned that your leadership team's ability to align on long-term strategy was something you'd been thinking about — especially with the AI shift accelerating. He thought it was worth us having a conversation. I have 30 minutes of your time — can I ask a few questions to understand whether there's something useful here for you?
Why it works: The referral transfers trust instantly. Asking for permission ("can I ask a few questions") gives the CEO a sense of control and dramatically reduces defensiveness.
3
The Observation Opening
Lead with a specific insight about their business or sector.
⌄
Open with a sharp, specific observation about their business that shows deep preparation. This immediately positions you as someone who has done their homework — not a generic vendor.
Kavya, I read that you closed your Series B last month — congratulations. I've worked with three other EdTech founders at exactly this stage, and the single biggest challenge they all described was building the operational and GTM capability to match the product capability their investors funded. I wanted to understand if that pattern is playing out for you, or if you've found a different way through it.
Why it works: You've shown research, named a specific pattern, and asked whether it applies — without pitching. The CEO is invited to confirm, correct, or add nuance. The conversation begins with them talking.
"The most common opening mistake: talking about yourself or your company for the first 3 minutes. By the time you ask a question, the CEO has already categorised you as a vendor — and vendors get screened out."
Neil Rackham — SPIN Selling Fieldbook
Pre-Call Planning Sheet
Complete this before every important CEO call. The Fieldbook recommends spending at least 15–20 minutes on this for any significant opportunity.
01 — The Buyer
Prospect Name & Company
Product to Position
What do I already know about this buyer? (research summary)
02 — Call Objective (Advance)
My Advance for this call (specific, concrete action the buyer agrees to)
If I don't get my Advance — what's my fallback Advance?
03 — NIPS Question Plan
N — Target Need-Payoff answer (in their voice)
I — 3 implications I need them to acknowledge
P — 3 problems I expect and my questions to surface them
S — What I know from research + 2 opening questions
04 — Capability Demonstration
Which specific ODeX / FRO features/benefits am I planning to present — and only after which explicit needs?
05 — Opening Statement
How will I open this call? (write the exact first 3 sentences)
Objection Prevention — Not Objection Handling
The Fieldbook's most important insight about objections: most objections in large sales aren't caused by buyer resistance — they're caused by the seller presenting capabilities before establishing needs. SPIN doesn't teach objection handling scripts. It teaches objection prevention.
"In our research, we found that skilled sellers had far fewer objections than average sellers. Not because they were better at handling them — but because they'd learned to not create them in the first place."
Neil Rackham — SPIN Selling
The 3 Root Causes of Objections (Fieldbook)
⚠ Root Cause 1: Presenting too early
You described ODeX before the CEO had articulated an explicit need for it. They don't yet feel the problem is big enough to justify the investment. Prevention: Complete the full S→P→I→N sequence before any capability demonstration. The explicit need must be spoken — not assumed.
⚠ Root Cause 2: Showing Advantages, not Benefits
You described how ODeX could help rather than how it meets a specific, stated need. Advantages provoke objections ("but we already have training programs"). Benefits — responses to explicit needs — rarely do. Prevention: Only present a feature/benefit after the buyer has named the need it solves.
⚠ Root Cause 3: Insufficient implication development
The buyer sees the problem but doesn't feel the cost of inaction is high enough. "Yes, it's an issue but not a priority." Prevention: Spend more time on Implication questions before moving to Need-Payoff. Map 3rd-order consequences. Make the cost of doing nothing undeniable.
If an Objection Still Arises — The SPIN Response
| Objection type | What it really means | SPIN response |
|---|---|---|
| "It's expensive." | The value doesn't yet outweigh the perceived cost — implications not fully developed. | Return to Implication questions: "Can I ask — when [the problem] continues for another 6 months, what's the actual cost to the business in [specific dimension]?" |
| "We tried something similar before." | They've been sold Advantages without meeting explicit needs before. Mistrust of category. | Acknowledge and probe: "What was the specific outcome you were hoping for that didn't happen?" Then re-establish needs from there. |
| "I need to think about it." | You have a Continuation, not an Advance. No explicit need has been created. | Surface the hesitation: "What specifically would you want to think through? Is there an aspect of the problem or the solution that isn't clear?" Then resume needs development. |
| "We have this covered internally." | They believe an existing solution meets the need. Challenge the assumption gently. | "Tell me about how that works — specifically [the dimension where ODeX/FRO differs]. When that solution is in place, how consistently does [the outcome they want] get achieved?" |
| "Now isn't the right time." | The problem isn't urgent enough. Implication questions weren't strong enough. | "What specifically needs to change before the timing is right? Is there a trigger — a milestone, a hire, a decision — that would make this the right time?" |
The Commitment Framework — Closing Without Closing
Rackham's research found that traditional closing techniques (summary close, alternative close, urgency close) actively harm large sales. SPIN replaces closing pressure with a 4-step commitment process that feels natural — because the buyer has already sold themselves.
Fieldbook: "Don't ask 'Would you like to buy?' Ask 'Who else needs to be involved in this decision, and how do we get them in the room?' The Advance question is always about the next concrete step — not the final purchase."
Commitment Script — ODeX & Future Ready
✓
Step 1: Check — Are there any concerns still unaddressed?
⌄
"Before we talk about next steps — is there anything about what we've discussed that you'd want to explore further, or any aspect of how ODeX works that isn't clear?"
"Based on everything you've shared, the core need seems to be [reflect their exact Need-Payoff words]. Have I understood that correctly — is there anything I've missed?"
Why this matters: Unaddressed concerns become post-meeting doubts. The check step surfaces them now, when you can respond, not after you've left.
Σ
Step 2: Summarise — reflect their key explicit needs back
⌄
"Let me make sure I've captured what matters most to you. You mentioned that [explicit need 1], and that [explicit need 2] is what's making it urgent — and ideally [their Need-Payoff answer in their exact words]. Is that a fair summary?"
Why it works: The summary creates an irresistible bridge to the Advance. The buyer has just confirmed their needs — agreeing to a next step now feels logical, not pressured.
→
Step 3: Propose — suggest a specific, appropriately-sized Advance
⌄
"Given what you've described, the most useful next step I'd suggest is bringing 2–3 of your key managers into a working session with us — so they can see how the ODeX framework directly addresses the gaps you've named. We can do that in about 90 minutes. Does Tuesday or Wednesday work?"
"What I'd propose is a 2-hour Future Ready workshop with your leadership team — not a sales meeting, an actual experience of the methodology. Based on what you've said today, I think it would change how your team sees the disruption you're facing. Would next week work?"
The right-size principle: The Advance should be proportional to the commitment the buyer has shown. A first-meeting CEO gets a "working session" proposal, not a contract request.
★
Step 4: Confirm — get a specific commitment before leaving
⌄
"So to confirm: we'll meet Tuesday the 15th at 10am, with you, your COO, and your Head of People. I'll send a calendar invite tonight. Does that work?"
"Before I go — who specifically should I reach out to on your end to coordinate the logistics for the working session?"
Never leave without a named next action, a named person responsible, and a named deadline. Vague agreements evaporate. Specific commitments persist.
Fieldbook · Practice Drills
6 Fieldbook Practice Drills
These drills come directly from the Fieldbook's structured practice methodology. Rackham's data shows that sellers who use deliberate solo drills between calls improve question quality 3–4× faster than those who only practise on live calls.
"Don't practise new skills on your most important customers. Practise deliberately — alone or with a colleague — then use what you've built in the field."
Neil Rackham — SPIN Selling Fieldbook
01
The Open Question Conversion Drill
Take any closed or leading question and rewrite it as a genuine open-ended consultative question. This builds the reflexive habit of open questioning before you're in front of a CEO.
CONVERT THESE CLOSED QUESTIONS
| Closed / Leading Question | Your Open Version |
|---|---|
| "Do your managers make decisions independently?" | |
| "I suppose you're worried about the AI disruption?" | |
| "Would it be useful to have better systems?" | |
| "Is the talent situation getting worse?" | |
| "Don't you think the culture has drifted?" |
02
The Implication Map Drill
Take a single problem and map every possible implication across 6 business dimensions. Then write one implication question for each. This is the Fieldbook's core preparation exercise for building Implication depth.
Starting Problem
"The CEO is the final decision-maker on everything — managers won't act without approval."
MAP THE IMPLICATIONS ACROSS 6 DIMENSIONS
CEO Time & Bandwidth
Talent & Retention
Growth & Scalability
Customer & Brand Experience
Competitive Position
Founder's Personal Cost
03
The FAB Analysis — Features, Advantages, Benefits
Map each ODeX and Future Ready capability through the FAB framework. This forces you to identify the exact explicit need each feature requires before you can legitimately present it as a Benefit — preventing premature pitching.
The rule: A Feature stated without an Explicit Need = neutral. A Feature linked to an Explicit Need = Benefit. A Feature linked to an assumed need = Advantage (risky — can trigger objections). Only Benefits reliably advance large sales.
| ODeX / FRO Capability (Feature) | Advantage (how it could help) | Explicit Need Required | Benefit (how it meets that need) |
|---|---|---|---|
| ODeX structured decision framework | Reduces founder involvement in operational decisions | "I need my managers to make decisions at my standard without me being in every conversation" | Gives managers a repeatable decision-making framework calibrated to your standards — so they can act independently without needing you as a fallback |
| Culture codification system | Translates values into operating behaviours | "The culture I built is diluting as we scale — new leaders don't carry it" | Encodes your culture into how managers actually operate — so it lives in systems and norms, not just in the people who were there from the start |
| Future Ready leadership alignment workshop | Aligns leaders on strategy and disruption | "Every strategic conversation starts from scratch — we have no shared framework for making decisions" | Gives your entire leadership team a common mental model for disruption — so strategic alignment that currently takes weeks happens in days |
| ODeX leadership pipeline development | Develops next-generation leaders | ||
| Future Ready scenario planning tools | Prepares leaders for multiple futures |
04
The Call Debrief Drill — One Call Per Day
Rackham's Fieldbook identifies post-call reflection as the single highest-leverage skill development habit. Complete this after every significant CEO call. The discipline of written reflection accelerates learning faster than any other method.
Call Debrief
Meeting with / Date
What was my planned Advance? Did I achieve it or get a Continuation?
Situation — Did I ask too many? Which ones were unnecessary (I could have researched them)?
Problem — Which P questions landed best? Which missed?
Implication — Did I develop implications fully enough, or did I rush to Need-Payoff?
Need-Payoff — What was the buyer's strongest N answer? Did I reflect it before presenting?
Did I present capabilities before needs were explicit? If so — what should I have done instead?
One thing I will do differently in the next call
05
The "One Problem — Six Implications" Sprint
Choose any problem a CEO might name. Set a 10-minute timer. Write 6 distinct implication questions — one for each business dimension. This solo drill builds the Implication question depth that transforms average SPIN sellers into exceptional ones.
Choose your problem scenario
Selected Problem
"Our managers wait for me on everything — they won't act without my approval."
I1 — CEO Time / Bandwidth
I2 — Talent & People
I3 — Revenue / Growth
I4 — Competitive Position
I5 — Customer / Brand
I6 — Founder Personal Cost
06
The Observer Drill — Classify Any Sales Conversation
Watch or listen to any sales conversation — a colleague's call, a YouTube demo, or your own recording. Classify every question as S, P, I, or N. Count how many of each type were used. Then evaluate: was the sequence right? Did the seller present before explicit needs were established?
S Count
P Count
I Count
N Count
What was the call outcome? (Order / Advance / Continuation / No Sale)
What caused it? Was it question sequence, premature pitching, insufficient implication development, or something else?
What would you have done differently at the critical moment?
Field Workbook
Your Personal Sales Toolkit
Build your personal consultative selling toolkit over time. Document your best questions, plan upcoming meetings with NIPS, and reflect after each call. Rackham identifies post-call reflection as one of the highest-leverage improvement activities for B2B sellers.
Situation Questions
Your best Situation questions — the ones that show preparation and open up Problems:
Problem Questions
Your best Problem questions — the ones that surface the hidden pain:
Implication Questions
Your sharpest Implication questions — the ones that build urgency:
Need-Payoff Questions
Your most powerful Need-Payoff questions — the ones buyers love to answer:
NIPS Pre-Meeting Planner
Prospect & Company
Product to Position
N — Ideal Need-Payoff answer (their voice)
I — Implications + my questions
P — Problems + my questions
S — Research done + opening questions
My pivot phrase
Post-Meeting Reflection Log
Rackham's Fieldbook: "The single most powerful improvement habit for a SPIN seller is to reflect on one call per day — specifically on which questions moved the conversation forward and which were missed opportunities."
Meeting with
Best question I asked — and why it worked
Question I wish I'd asked — what was I missing?
Did the conversation follow my NIPS plan? What deviated?
The buyer's Need-Payoff answer (their exact words)
What I will do differently in the next meeting
Active Opportunity Advance Tracker
Track every active CEO opportunity. For each one: what was the last Advance achieved, and what is the planned next Advance? If any cell says "Continuation," treat it as a red flag that needs immediate action.
Fieldbook: "Review your pipeline weekly. Every opportunity that hasn't moved to a new Advance in the past 10 days is stalling. The question isn't 'is this a good opportunity?' — it's 'what Advance am I pursuing next?'"
| CEO / Company | Last Advance | Next Planned Advance | Stage | Risk |
|---|---|---|---|---|
Assessment Centre
Knowledge Check
20 questions across consultative selling theory, question classification, Rackham principles, case analysis, NIPS planning, and Fieldbook call frameworks. Score 17+ to earn your Certified SPIN Practitioner badge.
Recall & Retention
Flashcard Deck
Click each card to reveal the answer. Review all 24 cards to earn your Recall Master badge — 8 new cards cover the Fieldbook's call planning and commitment frameworks.
Card 1 of 24
6% complete
Your Journey
Achievements & Badges
Every badge represents a real skill milestone — not just time spent, but demonstrated capability.
Overall mastery progress
0% complete — 0/22 badges earned