Sales Process & Methodologies

Conceptual Selling: Framework, Questions, Green Sheet, and Examples

Conceptual Selling framework connecting a buyer’s current state, desired outcome and relevant solution capabilities

TL;DR

Conceptual Selling is a Miller Heiman methodology for planning customer interactions around the buyer’s concept of success rather than the seller’s feature list. Sellers use the Green Sheet to prepare meeting objectives, ask five types of questions, align their selling process with the customer’s buying process, provide relevant perspective and agree on clear actions for both sides. It works best in complex B2B sales where different stakeholders may define value differently and one generic pitch cannot represent what everyone needs.

Conceptual Selling Is a Meeting Discipline, Not Just a Softer Pitch

Conceptual Selling is frequently summarized as “sell the outcome, not the product.”

That is directionally right, but incomplete.

A seller can replace a list of features with a list of benefits and still spend the entire meeting talking about their own product. The pitch sounds more polished, but the buyer’s actual concept of value remains unknown.

Conceptual Selling puts the customer interaction itself under discipline.

Before an important meeting, the seller should know:

  • What they believe the buyer is trying to achieve
  • Which parts of that belief still need validation
  • What information is missing
  • How the buyer feels about the problem and potential change
  • What useful perspective the seller can contribute
  • What action would meaningfully advance the opportunity
  • What both sides must do after the meeting

The objective is not to make the pitch sound customer-centric. It is to understand what the customer is buying before trying to sell it.

Product-led selling Conceptual Selling
Starts with product capabilities Starts with the buyer's concept of success
Explains what the product does Investigates what the buyer wants to accomplish
Uses a standard value proposition Adapts the value discussion to the specific buyer
Treats discovery as preparation for the pitch Treats the conversation as a joint search for alignment
Measures a meeting by whether the presentation was completed Measures a meeting by the information, value and commitments exchanged
Pushes toward a seller-defined next step Agrees on meaningful actions for both sides

What Is Conceptual Selling?

Conceptual Selling is a buyer-focused sales methodology developed by Robert Miller and Stephen Heiman. Its central premise is that buyers do not purchase products solely for their features. They purchase their own concept of what those products will help them accomplish.

That concept may include:

  • A business outcome
  • A desired future state
  • A problem the buyer wants to eliminate
  • A risk they want to avoid
  • A personal or organizational priority
  • A particular way they believe the change should happen

The seller’s job is to uncover that concept, validate it and determine whether the proposed solution can genuinely support it.

Miller and Heiman developed Conceptual Selling alongside Strategic Selling. The methodologies now sit within Korn Ferry’s sales training portfolio. The current Conceptual Selling with Perspective program focuses on meeting preparation, customer-focused conversations, alignment with the buying process and clear actions for both sides.

The methodology is also detailed in Miller and Heiman’s book, The New Conceptual Selling.

What is the buyer’s concept?

The buyer’s concept is their mental picture of the result they want and how they believe a successful solution should help create it.

It is not necessarily the same as:

  • The product category they requested
  • The feature list in an RFP
  • The problem statement in the CRM
  • The seller’s prepared value proposition
  • The priorities of another person on the buying committee

Suppose a revenue operations leader asks for automatic call summaries.

The requirement is call summaries.

But the buyer’s concept may be:

A trustworthy deal record that stays current without requiring sales managers to chase representatives for notes.

Another stakeholder may have a different concept:

A complete customer history that helps account executives prepare for calls without searching across five systems.

The same feature supports both concepts, but the value, evidence and buying motivations are different.

The concept sale should come before the product sale

The concept sale establishes whether the seller and buyer agree on the outcome, the problem and the intended path forward.

The product sale establishes whether a particular solution can deliver that outcome.

Presenting the product first encourages the buyer to react to capabilities before the team has agreed on what matters. Conceptual Selling reverses that order:

  1. Understand the buyer’s concept.
  2. Confirm what success means.
  3. Explore risks, attitudes and constraints.
  4. Provide useful information or perspective.
  5. Connect the relevant product capabilities.
  6. Agree on a mutual action.

The approach does not ask sellers to hide the product indefinitely. It asks them to earn the right to discuss it in the right context.

The Core Ideas Behind Conceptual Selling

Conceptual Selling is broader than asking open-ended questions. Its operating principles shape how the entire interaction is planned.

Buyers purchase for their own reasons

A seller may believe the strongest value is cost reduction. The buyer may care more about predictability, professional credibility, employee experience or reduced implementation risk.

A sales conversation becomes relevant only when it reflects the buyer’s reasons.

The buying and selling processes happen simultaneously

The seller may be moving from discovery to demonstration. The buyer may still be deciding whether the problem deserves attention.

Korn Ferry explains that Conceptual Selling helps sellers recognize and align these two processes.

A scheduled demo does not prove that the buyer is ready to evaluate products. A proposal request does not prove that every stakeholder agrees on the need.

No single value proposition works for everyone

A product can create different value for different people.

The CFO may care about financial control. The operations leader may care about process reliability. An end user may care about removing repetitive work. IT may care about integration, security and governance.

The product remains the same. The concept does not.

Every interaction should create value

Discovery should not become a one-sided extraction exercise in which the seller asks for information and gives nothing useful in return.

The current Conceptual Selling with Perspective approach explicitly asks sellers to find appropriate ways to provide perspective to each person involved in a sale.

That perspective might include:

  • A pattern observed across similar organizations
  • A risk the buyer has not considered
  • A clearer way to frame the problem
  • A benchmark with an authoritative source
  • A practical implementation lesson
  • A connection between two concerns raised by different stakeholders

The seller should not manufacture a provocative insight merely to sound clever. The perspective must help the buyer make a better decision.

A good outcome should be win-win

Conceptual Selling does not define a seller win as any signed contract.

If the buyer’s concept cannot realistically be delivered by the product, closing the deal creates expectation debt. That debt appears later as poor adoption, implementation conflict, churn or damaged trust.

Win-win means the buyer receives credible value and the seller enters a commercially sound relationship.

How Conceptual Selling Works: From Concept to Commitment

Conceptual Selling process moving from buyer research and questions to perspective, solution alignment and mutual commitment

A Conceptual Selling conversation can be understood through three broad stages:

Conversation stage Seller's objective Buyer-facing outcome
Getting information Understand and validate the buyer's situation, concept, attitudes and constraints The buyer's intended outcome becomes clearer
Giving information Provide relevant evidence, differentiation or perspective The buyer can evaluate a more informed path forward
Getting commitment Agree on a meaningful action from both sides The opportunity advances through mutual action rather than seller persistence

These stages are not rigid agenda blocks. A real conversation moves between questions, clarification and useful information.

What matters is the balance. If the seller gives information before understanding the buyer’s concept, the meeting becomes a pitch. If the seller only gathers information, the buyer may leave without receiving value. If neither side commits to action, the conversation may have been pleasant but commercially inconclusive.

The Concept-to-Commitment Loop

The following is a practical explanatory model, not an official Miller Heiman worksheet.

  1. Prepare a concept hypothesis: Use previous conversations, account research and CRM context to form a starting view.
  2. Confirm what is already known: Verify whether earlier information remains accurate.
  3. Discover what is missing: Learn about outcomes, processes, stakeholders and constraints.
  4. Surface attitudes and basic issues: Understand how the buyer feels and what could prevent progress.
  5. Provide relevant perspective: Add information that improves the buyer’s understanding.
  6. Connect capabilities to the concept: Discuss only the product elements that support the agreed outcome.
  7. Secure a mutual action commitment: Define what the buyer and seller will each do.
  8. Carry the evidence forward: Preserve the buyer’s language and commitments for the next interaction.

What Are the Five Types of Conceptual Selling Questions?

Conceptual Selling conversation annotated with Confirmation, New Information, Attitude, Commitment and Basic Issue questions

The classic Conceptual Selling framework uses five categories of questions. Each category helps the seller understand a different part of the buyer’s concept.

They are not a script to be recited in order. Using all five categories in quick succession can make the buyer feel processed rather than understood.

Question type Purpose Example Common mistake
Confirmation Verify information the seller already has or believes to be true "You mentioned that the board no longer trusts the pipeline report. Is that still the main reason this project has executive attention?" Presenting an assumption as a fact
New Information Discover facts, context and desired outcomes that are still unknown "What happens between the regional forecast calls and the number that reaches the board?" Asking questions that basic research could have answered
Attitude Understand the buyer's opinions, confidence, concerns and personal connection to the issue "How confident are you that the current process can improve without a change?" Avoiding emotions because they appear less measurable
Commitment Test willingness to invest time, access, resources or political capital "If we validate the workflow with your regional managers, would you be comfortable sponsoring a pilot?" Asking for commitment before establishing value
Basic Issue Surface concerns or conditions that could stop the opportunity "What could make the organization decide that changing the process is not worth the disruption?" Waiting for objections to appear late in the deal

Confirmation questions

Confirmation questions show the buyer that the seller has listened, researched and retained important context.

They can verify:

  • Previously stated priorities
  • Baseline metrics
  • Stakeholder responsibilities
  • Decision timelines
  • Current processes
  • Earlier commitments

Useful confirmation questions include:

  • “Last time, you described CRM completeness as the main obstacle to forecasting. Has anything changed?”
  • “You said regional sales managers currently use different review processes. Is that true across all three regions?”
  • “Am I right that reducing administrative work matters only if reporting quality improves at the same time?”

A confirmation question should remain a genuine question. “You agree that automation is the answer, correct?” is pressure disguised as validation.

New Information questions

New Information questions fill meaningful gaps.

Examples include:

  • “How do managers currently verify whether a deal record is complete?”
  • “Which part of the process creates the most rework?”
  • “Who relies on this information after the forecast meeting?”
  • “What would need to change for the board to trust the number?”
  • “How would you know, six months from now, that the project worked?”

The goal is not to collect every available fact. It is to discover what materially affects the buyer’s concept and decision.

Attitude questions

Attitude questions reveal how the buyer interprets the situation.

That matters because two people can agree on the facts and disagree completely about what should happen next.

Examples include:

  • “How do you feel about asking managers to change this process again?”
  • “Which implementation risk concerns you personally?”
  • “What is your view of the previous attempt?”
  • “How do the regional leaders feel about standardization?”
  • “Which part of this outcome matters most to you?”

Attitude questions require trust. They should sound curious, not intrusive or manipulative.

Commitment questions

Commitment is broader than signing a contract.

A buyer can demonstrate commitment by:

  • Introducing another stakeholder
  • Sharing data needed for an assessment
  • Participating in a workshop
  • Agreeing on success criteria
  • Assigning an internal owner
  • Reviewing a mutual action plan
  • Providing access to users for a pilot

A useful commitment question asks for an action proportionate to the value and confidence established so far.

Basic Issue questions

Basic Issue questions deliberately surface reasons not to proceed.

Examples include:

  • “What would make this initiative lose priority?”
  • “Where could internal resistance come from?”
  • “What does the security team need to believe before supporting a pilot?”
  • “What happened the last time the organization tried to solve this?”
  • “Is there any reason this outcome may not justify the disruption required?”

These questions can feel uncomfortable. That is precisely why they matter. An unspoken issue does not disappear. It waits until procurement, implementation or a late-stage executive review.

What Is the Miller Heiman Green Sheet?

The Green Sheet is the meeting-planning tool associated with Conceptual Selling.

Official Miller Heiman Green Sheet used to plan a customer-focused Conceptual Selling meeting
Source: BDM Sales Training

It helps sellers prepare for productive customer interactions rather than relying on a generic agenda, a familiar deck or intuition.

Public Korn Ferry materials describe the Green Sheet as a tool for planning customer interactions. Korn Ferry Sell embeds the Green Sheet alongside the Blue Sheet and Gold Sheet within its methodology platform.

A Green Sheet can help a seller think through:

  • The Single Sales Objective
  • The purpose of the customer interaction
  • What is known about the buyer’s concept
  • What must be confirmed or discovered
  • Which questions will be most useful
  • What information or perspective the seller should provide
  • The best realistic action commitment
  • What both parties should do after the meeting

What is the Single Sales Objective?

The Single Sales Objective describes the commercial opportunity that the customer interaction is intended to advance.

It should be specific enough to prevent the meeting from becoming detached from the larger deal, but it should not turn every interaction into an aggressive closing attempt.

For example:

Secure agreement to run a four-week pilot with the North American enterprise team by October 15, subject to validated security and workflow requirements.

That is clearer than:

Discuss next steps and demonstrate the platform.

Green Sheet vs. Blue Sheet

The Green Sheet plans an individual customer interaction.

The Blue Sheet, used in Strategic Selling, supports the wider opportunity strategy across buying influences, competitive position, risks and actions.

A Blue Sheet may show that the seller needs stronger access to a technical buyer. A Green Sheet helps the seller plan the meeting that could build that relationship.

For a broader explanation of the opportunity-level methodology, read Sybill’s Miller Heiman sales process and Blue Sheet guide.

Conceptual Selling Example: One Meeting, Five Question Types

The following example is fictional.

A seller from a revenue workflow platform is meeting Maya, a Vice President of Revenue Operations at Northstar Systems.

Maya initially asked for better automated call summaries.

A feature-led seller might immediately demonstrate transcription, summaries and CRM fields.

A Conceptual Selling approach starts with a hypothesis:

Northstar may need more consistent customer information across calls, CRM records and forecast reviews.

That hypothesis is useful preparation. It is not yet the buyer’s concept.

1. Confirm the known context

Seller: “You mentioned that managers spend part of every forecast call reconstructing what happened in customer meetings. Is that still the main concern?”

Maya: “Yes, although the larger problem is that nobody trusts the opportunity record unless they have spoken directly to the account executive.”

The seller now knows that summaries are not the end goal. Trust in the deal record matters more.

2. Gather new information

Seller: “Where does that lack of trust create the most serious problem?”

Maya: “Managers can work around it. The problem is when the CRO asks why a commit deal slipped and we cannot show when the risk first appeared.”

The desired outcome is becoming clearer: defensible deal history and earlier risk visibility.

3. Explore attitude

Seller: “How do account executives feel about changing the process?”

Maya: “They are tired of being told to enter more data. If this feels like another inspection system, adoption will be terrible.”

The personal and organizational concern is not simply implementation effort. It is resistance to surveillance and additional administration.

4. Surface the Basic Issue

Seller: “What could stop you from moving forward even if the summaries are accurate?”

Maya: “Security will need to approve the meeting data workflow, and our sales leaders will need proof that representatives are not being asked to maintain another system.”

The seller now understands two conditions that could stop the initiative.

5. Provide perspective

Seller: “Teams often frame this as a note-taking project. The more useful implementation question is whether the meeting evidence can update the systems managers already use without creating a second workflow for representatives. It may make sense to test that before evaluating broader analytics.”

The seller has added a relevant implementation perspective without dismissing Maya’s original request.

6. Confirm the buyer’s concept

Seller: “It sounds as though success is not simply better summaries. You need a deal record managers can trust, without adding data entry or making representatives feel monitored. Is that a fair description?”

Maya: “Yes. That is exactly it.”

The buyer has now confirmed the concept in their own language.

7. Ask for a proportionate commitment

Seller: “If we map one enterprise team’s current workflow and confirm the security requirements, would you sponsor a limited pilot with that group?”

Maya: “Yes. I can involve the sales manager and our security partner. Send me the workshop outline first.”

The meeting ends with mutual action:

  • The seller will send a workflow workshop outline.
  • Maya will involve the sales manager and security partner.
  • Both sides will assess whether a pilot is warranted.

No one has signed a contract. The opportunity has still advanced.

Different Stakeholders May Be Buying Different Concepts

Multi-stakeholder Conceptual Selling map showing how revenue, operations, sales and IT buyers define success differently

Complex buying groups rarely share one perfectly consistent definition of value.

Stakeholder Stated requirement Possible concept of success Evidence required
CRO Better pipeline visibility A forecast they can defend to the board Earlier risk detection and reliable deal evidence
RevOps leader Automated CRM updates Trustworthy data without chasing representatives Accurate field updates within the existing CRM workflow
Sales manager Meeting summaries Faster coaching with complete deal context Clear risks, objections and next actions
Account executive Less administration More customer time without losing control of the account narrative Reduced manual work and reviewable outputs
IT leader Secure integrations Automation that does not create governance or data risk Security, access and integration validation

This creates a challenge we can call concept drift.

As information passes between meetings, stakeholders and internal teams, distinct buyer concepts are often compressed into one generic CRM summary:

Customer wants better sales automation.

That summary is convenient and almost useless.

It hides:

  • Why the initiative matters
  • Who cares about which outcome
  • Where stakeholders disagree
  • What evidence each person requires
  • What could stop the decision
  • Which promises the seller must not make

Conceptual Selling helps uncover these differences. Revenue teams also need a reliable way to preserve them across the deal.

Buyer Readiness in Conceptual Selling With Perspective

Conceptual Selling with Perspective also asks sellers to understand where buyers are in relation to change.

Korn Ferry describes four buyer positions:

Buyer position What it means Appropriate seller response
Growth The buyer wants a better result or new capability Explore the desired improvement and what makes it valuable
Trouble The buyer faces an urgent or visible problem Understand the consequences, constraints and required outcome
Even Keel The buyer is reasonably satisfied with the current state Investigate whether change would create enough value to justify disruption
Overconfident The buyer believes the current approach already solves the problem Provide credible perspective only if there is evidence of an overlooked risk or opportunity

This framework prevents a common sales mistake: manufacturing urgency where the buyer sees none.

A buyer in Growth or Trouble may already be receptive to change. A buyer at Even Keel needs a credible reason to reconsider the status quo. An Overconfident buyer may require new evidence, but challenging them without insight will only create resistance.

Conceptual Selling does not promise that every buyer can be persuaded. Sometimes the right conclusion is that the opportunity should not move forward.

Conceptual Selling vs. Other Sales Methodologies

Conceptual Selling overlaps with several buyer-focused approaches, but each framework has a different job.

Methodology Primary focus Best used for Key difference
Conceptual Selling Understanding the buyer's concept and planning productive interactions Discovery, solution alignment and important customer meetings Organizes the conversation around the buyer's concept and mutual action
Strategic Selling Navigating buying influences, competition and opportunity risk Complex, multi-stakeholder deal strategy Operates at the opportunity level rather than the individual meeting level
Solution Selling Diagnosing a problem and positioning a tailored solution Buyers with a recognizable business problem Begins with problem diagnosis and solution design
Consultative Selling Acting as an informed advisor to the buyer Relationship-led and expertise-led sales Describes a broader selling posture rather than one proprietary meeting methodology
SPIN Selling Developing needs through Situation, Problem, Implication and Need-payoff questions Discovery where the buyer has not fully understood the impact of the problem Uses a defined questioning sequence to develop need and value

For deeper comparisons, see Sybill’s guides to:

These frameworks can complement one another. A team might use MEDDPICC for qualification, Strategic Selling for opportunity planning and Conceptual Selling for important buyer interactions.

The danger is not using more than one methodology. It is mixing their terminology until representatives no longer know what problem each framework solves.

How AI Can Support Conceptual Selling

AI is most useful when it helps sellers prepare, listen and retain context.

It should not decide what the buyer wants based on an isolated phrase or automatically label someone supportive, resistant or ready to buy.

Meeting phase How Sybill can help Human responsibility
Before Pre-Meeting Briefs bring together previous interactions, CRM context, attendee information and open tasks Set the meeting objective and prepare hypotheses rather than assumptions
During Sybill captures the conversation so the seller does not need to transcribe every detail manually Listen, adapt and ask useful follow-up questions
After Magic Summaries can capture needs, objections, outcomes and next steps Review the summary and validate important interpretations
Between meetings Ask Sybill helps teams retrieve buyer language and deal context from previous interactions Decide how new evidence affects the opportunity strategy
During execution CRM updates and AI Tasks help preserve agreed actions Keep owners accountable and confirm commitments with the buyer
Across the deal Deal Workspace keeps opportunity context available Separate confirmed buyer evidence from internal hypotheses

AI can help preserve the buyer’s concept. It cannot decide what that concept is without the buyer.

Useful questions a seller could ask Sybill before a meeting include:

  • “How has each stakeholder described the outcome they want?”
  • “Which customer priorities have been confirmed more than once?”
  • “What concerns did the buyer raise about implementation?”
  • “What did we promise to do after the last meeting?”
  • “Which questions remain unanswered?”
  • “How does the RevOps leader’s priority differ from the CRO’s?”
  • “What evidence has the customer requested?”
  • “Which next actions have not been completed?”
Ask Sybill retrieving stakeholder-specific buyer outcomes for Conceptual Selling meeting preparation

These questions turn accumulated deal context into better preparation. They do not replace direct confirmation with the customer.

Conceptual Selling begins with better meeting preparation. See how Sybill’s Pre-Meeting Briefs bring previous conversations, CRM context, attendee information and open tasks together before the call.

When Should You Use Conceptual Selling?

Conceptual Selling is especially useful when:

  • The product or service is complex
  • The purchase involves multiple stakeholders
  • Different buyers define value differently
  • The customer has described a feature but not the desired outcome
  • The sales cycle requires several important meetings
  • The seller can tailor the proposed solution
  • Long-term customer value matters
  • A poor-fit sale would create implementation or retention risk

It is less useful when:

  • The transaction is simple and low-risk
  • The buyer already knows the exact item required
  • Price and availability are the main decision factors
  • Deep meeting preparation costs more than the opportunity justifies
  • The seller has no ability to adapt the offer or implementation
  • The customer does not want or need an exploratory sales process

Conceptual Selling should make a complex interaction clearer. Applying it indiscriminately can make a simple purchase harder than necessary.

Keep the Buyer’s Concept Intact Across the Deal

The most important question in Conceptual Selling is not:

How can we make this product sound more valuable?

It is:

What is this buyer actually trying to accomplish, and can we credibly help?

Answering that question requires preparation, listening, useful perspective and commercial honesty. It also requires continuity.

The buyer’s concept develops across stakeholders and meetings. Priorities change. New concerns emerge. Commitments are made. Assumptions are corrected. If that context is reduced to a short CRM note, the next seller may return to a generic pitch and force the buyer to explain the situation again.

Conceptual Selling gives teams the meeting discipline. Sybill helps preserve the evidence and actions that allow that discipline to continue from one interaction to the next.

Book a Sybill demo to see how your team can prepare with complete deal context, capture buyer priorities and keep mutually agreed actions from disappearing between calls.

Frequently Asked Questions About Conceptual Selling

What is Conceptual Selling?

Conceptual Selling is a Miller Heiman sales methodology that helps sellers plan customer interactions around the buyer’s concept of success. Instead of beginning with product features, the seller uncovers what the buyer wants to achieve, provides relevant perspective and agrees on meaningful actions for both sides.

Who created Conceptual Selling?

Robert Miller and Stephen Heiman created Conceptual Selling. The methodology is described in their book The New Conceptual Selling and is now part of Korn Ferry’s sales training portfolio.

What are the five types of Conceptual Selling questions?

The five types are Confirmation, New Information, Attitude, Commitment and Basic Issue questions. They help sellers verify what they know, discover missing context, understand buyer opinions, test willingness to act and surface issues that could stop the opportunity.

What is the Miller Heiman Green Sheet?

The Green Sheet is the proprietary meeting-planning tool associated with Conceptual Selling. It helps sellers define the Single Sales Objective, prepare important questions, consider the buyer’s concept, plan useful information and identify an appropriate action commitment.

What is the difference between Conceptual Selling and Solution Selling?

Solution Selling focuses on diagnosing a business problem and positioning a tailored solution. Conceptual Selling focuses more specifically on understanding the buyer’s concept of the desired outcome and planning customer interactions that align the seller’s process with the buyer’s process.

How is Conceptual Selling different from Strategic Selling?

Conceptual Selling helps sellers plan and conduct individual customer interactions. Strategic Selling operates at the wider opportunity level, helping teams understand buying influences, competitive position, risks and the actions needed to win a complex deal.

Is Conceptual Selling still relevant?

Yes. Conceptual Selling remains relevant for complex B2B sales because buyers still interpret value differently, involve multiple stakeholders and expect purposeful interactions. The current Korn Ferry version, Conceptual Selling with Perspective, also emphasizes providing useful perspective and ending meetings with clear actions.

Can AI automate Conceptual Selling?

AI can help sellers prepare for meetings, retrieve previous buyer context, capture conversations and preserve next steps. It cannot independently determine the buyer’s concept, validate stakeholder attitudes or replace human judgment and direct customer confirmation.

Get started with Sybill

Accelerate your sales with your personal assistant

Get Started Free

Frequently Asked Questions

What is Conceptual Selling?

Conceptual Selling is a Miller Heiman sales methodology that helps sellers plan customer interactions around the buyer’s concept of success. Instead of beginning with product features, the seller uncovers what the buyer wants to achieve, provides relevant perspective and agrees on meaningful actions for both sides.

Who created Conceptual Selling?

Robert Miller and Stephen Heiman created Conceptual Selling. The methodology is described in their book The New Conceptual Selling and is now part of Korn Ferry’s sales training portfolio.

What are the five types of Conceptual Selling questions?

The five types are Confirmation, New Information, Attitude, Commitment and Basic Issue questions. They help sellers verify what they know, discover missing context, understand buyer opinions, test willingness to act and surface issues that could stop the opportunity.

Get started with Sybill

Once you try it, you’ll never go back.