
A sales technique is a structured method a salesperson uses during prospecting, discovery, presentation, objection handling, negotiation or closing. A technique may define the questions to ask, the order of a conversation or the way value should be explained.
A sales process and a sales technique are related but different:
A sales process describes the organization’s stages, such as prospecting, qualification, discovery, proposal and close.
A sales methodology provides broader principles for how representatives should sell.
A sales technique is a practical way to conduct a conversation or complete a step.
For example, a company may have a six-stage sales process while using SPIN questions during discovery and SNAP principles when writing follow-up emails.
Consider:
Product price and complexity
Length of the buying cycle
Number of decision-makers
Whether buyers already understand the problem
How much education the market requires
Level of customization
Transactional versus relationship-based selling
Inbound, outbound, retail or enterprise setting
Availability of proof such as case studies and ROI data
A simple consumer purchase may require clarity and convenience. A complex business sale may require deeper discovery, stakeholder alignment and financial justification.
SPIN selling organizes discovery around four types of questions: Situation, Problem, Implication and Need-payoff. The approach helps the buyer articulate current conditions, recognize the consequences of a problem and describe the value of improving it.
Situation questions establish useful context. Ask only for information you cannot obtain through research or existing account data.
Examples:
How does your team currently prepare the monthly forecast?
Which systems are involved in the approval process?
How many people use the current platform?
What changed recently that made this project a priority?
Too many basic questions can make the conversation feel like an interrogation. Research the company before the call and explain why a detail matters when necessary.
Problem questions uncover friction, risk or unmet needs.
Examples:
Where does the current process usually slow down?
Which errors require the most rework?
What do users find difficult about the existing tool?
Which goals are hardest to achieve with the current approach?
Do not assume the buyer has the problem your product solves. Let the customer confirm the issue in their own words.
Implication questions explore the wider effect of a problem. They may connect an operational issue to cost, time, customer experience, revenue or risk.
Examples:
What happens to delivery dates when approval is delayed?
How much staff time goes into correcting those errors?
How does inconsistent reporting affect leadership decisions?
If the issue continues for another year, what becomes more difficult?
Use judgment and empathy. Do not exaggerate fear or pressure the buyer into agreeing with consequences that are not credible.
Need-payoff questions encourage the buyer to describe the value of a better outcome.
Examples:
What would your team be able to do with a two-day faster approval cycle?
How valuable would a single source of reporting data be?
If onboarding took half as long, where would you reinvest the time?
Which outcome would make this project worthwhile?
The buyer’s answer can help define success criteria and build a business case.
SPIN is useful for consultative, complex or high-consideration sales where the customer’s needs require discovery. It may be excessive for a simple transaction with an obvious requirement.
A representative sells inventory software to a regional retailer.
Situation: “How do your stores update inventory after returns?”
Problem: “Where do discrepancies occur most often?”
Implication: “How do inaccurate counts affect reordering and customer availability?”
Need-payoff: “If store and warehouse counts synchronized automatically, what would improve first?”
The representative can then demonstrate only the features connected to the buyer’s confirmed priorities.
Solution selling starts with a customer problem and builds a tailored combination of products, services and expertise around the desired outcome. The salesperson behaves more like a consultant than a catalog presenter.
Review the organization’s business model, recent changes, market, likely stakeholders and relevant challenges. Research creates hypotheses, not conclusions.
Use discovery to identify the current state, desired state, barriers, impact and urgency. Confirm who experiences the problem and who owns the outcome.
Determine whether the issue is important enough to address, whether your offering can help and whether there is a credible decision process. Qualification protects both parties from investing in a poor fit.
Map capabilities to the buyer’s requirements. A solution may combine software, implementation, training, support and process changes. Remove elements that do not contribute to the intended result.
Explain how the proposed approach changes the current state. Use demonstrations, relevant case studies, a pilot, technical validation or an ROI model where appropriate. State assumptions clearly.
Clarify responsibilities, timing, risks, adoption needs and measures of success. Closing a contract without a workable implementation plan creates future dissatisfaction.
This method suits specialized products, professional services, enterprise software and other purchases requiring configuration or stakeholder education. It works poorly when representatives force every prospect into the same predetermined “solution.”
A manufacturing company reports repeated production delays. Rather than immediately proposing scheduling software, the salesperson discovers that inconsistent supplier updates cause most planning errors. The proposed solution combines supplier data integration, workflow changes and user training. The presentation focuses on fewer manual updates, earlier risk visibility and the agreed production measures.
SNAP selling is designed for busy buyers with competing priorities. The acronym commonly represents four principles: Keep it Simple, Be iNvaluable, Always Align and Raise Priorities.
Reduce the mental and administrative effort required to understand the offer and take the next step.
Use concise emails and clear subject lines.
Explain one primary value proposition at a time.
Provide an agenda before meetings.
Limit options to relevant choices.
Make actions, owners and dates explicit.
Simple does not mean incomplete. Complex risks, pricing and terms still require accurate explanation.
Provide insight that helps the buyer make a better decision. This might include a benchmark, diagnostic question, implementation lesson or clearer way to frame the problem.
Value should not be used to create dependency. The goal is to become a credible resource through relevant expertise and honest guidance.
Connect the proposal to the buyer’s objectives, constraints and decision criteria. Use the customer’s confirmed language and update the approach as priorities change.
Alignment also means being willing to say when the product does not fit. A poor-fit sale creates churn, support burden and reputational damage.
Help the buyer understand why the issue deserves attention among many initiatives. Quantify the cost of delay where evidence supports it, relate the project to a strategic goal and identify a manageable next step.
Do not manufacture urgency with false deadlines. Credible urgency comes from business consequences the buyer recognizes.
SNAP principles work well with executives, overloaded buying committees and customers who already recognize the basic problem but struggle to move the decision forward. The method is also useful for outbound communication and follow-up.
Instead of emailing a 30-page proposal without context, a salesperson sends a one-page summary showing the buyer’s three requirements, the recommended option, expected implementation effort and a single decision needed before Friday’s planning meeting. Supporting detail remains available, but the immediate next step is simple.
RAIN selling uses four ideas to guide a value-centered conversation: Rapport, Aspirations and Afflictions, Impact and New Reality.
Rapport is professional trust built through preparation, relevance, listening and reliability. It is not superficial small talk or pretending to share the buyer’s interests.
Build rapport by respecting time, remembering prior context, acknowledging uncertainty and doing what you promised.
Afflictions are the difficulties a buyer wants to reduce. Aspirations are the positive outcomes the buyer hopes to create. Effective discovery examines both.
Questions might include:
What is preventing the team from reaching its target?
What would an ideal process allow people to do?
Which customer experience are you trying to create?
What would success make possible next year?
Selling only against pain can make the conversation negative. Aspirations reveal strategic value beyond removing a problem.
Impact translates the issue and desired outcome into business or personal significance. It may involve financial value, time, risk, customer outcomes, employee capacity or strategic flexibility.
Collaborate on calculations and label assumptions. A range with transparent inputs is more credible than a precise but unsupported promise.
Describe what work could look like after successful implementation. Make the future concrete through a workflow, prototype, demonstration, phased plan or customer example.
Include the effort required to reach that state. A believable new reality acknowledges adoption, training and operational change rather than implying instant transformation.
RAIN works well for relationship-based and value-focused sales in which both current problems and future ambitions matter. It can support professional services, strategic technology, advisory work and major account development.
A consultant establishes rapport by demonstrating knowledge of a healthcare organization’s expansion. Discovery identifies an affliction—slow staffing approvals—and an aspiration—opening new clinics without increasing administrative overhead. The impact discussion estimates capacity and delay costs. The consultant then presents a new operating model, timeline and pilot rather than only describing consulting hours.
| Technique | Primary focus | Best suited to | Key risk |
|---|---|---|---|
| SPIN | Discovery through structured questions | Complex needs and consultative conversations | Asking too many questions without insight |
| Solution selling | Tailoring an offering to a diagnosed problem | Specialized or configurable products and services | Forcing a preferred solution before diagnosis |
| SNAP | Simplifying decisions for busy buyers | Executive and overloaded stakeholders | Removing necessary detail in the name of simplicity |
| RAIN | Trust, goals, problems, impact and future state | Relationship-based and value-focused sales | Describing an unrealistic future outcome |
These methods can complement one another. A salesperson might use SPIN during discovery, solution selling to design the proposal, SNAP to simplify decision materials and RAIN to frame the business impact.
Identify where the sales process breaks down. Do representatives struggle to uncover needs, communicate value, reach decision-makers or move deals forward? Choose a technique that addresses a real performance gap.
Create examples of good discovery questions, call preparation, follow-up and value summaries. Avoid training that teaches acronyms without showing how behavior should change.
Specify where the technique fits your stages. Situation questions may belong in discovery; a new-reality demonstration may belong in validation; SNAP principles may guide every follow-up.
Use role plays based on actual customer types and common objections. Pause to discuss what the buyer said, which follow-up is neutral and where the representative made an unsupported assumption.
Review recordings or notes in line with consent, privacy and company policies. Give feedback on a few behaviors at a time, such as question quality, listening or agreed next steps.
Ensure discovery guides, demonstrations, proposals and case studies support the chosen approach. A customer-centered conversation loses credibility if the proposal returns to a generic feature list.
Possible indicators include:
Discovery-to-next-stage conversion
Percentage of opportunities with confirmed business impact
Number of engaged decision stakeholders
Proposal-to-close conversion
Sales-cycle length
Average discount
Win and loss reasons
Implementation success and early retention
Do not judge a method only by immediate revenue. Qualification may initially reduce the pipeline while improving fit and forecast quality.
Use available information so the customer does not have to explain basic facts. Bring a relevant hypothesis and invite correction.
Do not rush to match the first problem mentioned with a feature. Ask how the problem works, who it affects and why it matters.
Repeat your understanding in concise language: “I heard three priorities…” This gives the buyer a chance to correct assumptions.
Connect the offer to a defined outcome. Clarify the baseline, desired change, assumptions, costs and time frame behind financial estimates.
Understand who uses, approves, finances, secures and implements the solution. Do not treat one enthusiastic contact as the entire buying process.
End meetings with an action, owner, purpose and date. A vague promise to “follow up soon” often leads to avoidable delay.
Each message should contribute something: a requested answer, a summary, a useful example or a clear decision point. Persistence is not a reason to send repetitive reminders indefinitely.
Be honest about fit, limitations, pricing and implementation effort. Do not create false scarcity, hide material conditions or pressure a customer who lacks the information to decide.
Following a framework so rigidly that the conversation feels scripted
Asking questions that research could have answered
Diagnosing the problem before listening
Focusing on pain while ignoring customer aspirations
Presenting every feature regardless of relevance
Assuming verbal enthusiasm equals decision authority
Quantifying value with unsupported numbers
Treating objections as arguments to defeat
Creating false urgency
Closing a deal that the company cannot successfully deliver
Measuring activity without examining customer outcomes

Sales representatives, managers and revenue teams can use Dokie to turn discovery notes, customer priorities, solution details and business-impact evidence into a professional presentation. Its AI presentation workflow can help create account plans, proposals, sales training and executive summaries without requiring every slide to be designed manually.
Dokie also supports slide-level revisions, consistent visual themes and PowerPoint export, making it easier to update one recommendation or proof point without rebuilding the full deck. Before sharing, verify all customer information, calculations and product claims, and remove confidential details that the audience is not authorized to receive.
There is no single best method for every sale. SPIN supports discovery, solution selling supports tailored offers, SNAP simplifies decisions and RAIN connects trust, needs and value. Choose based on the buyer and sales context.
Yes. Many teams combine compatible elements across the customer journey. The result should remain coherent and helpful rather than becoming a collection of scripted acronyms.
SPIN refers to Situation, Problem, Implication and Need-payoff questions. Together, they help a buyer explain the current state, difficulty, consequences and value of improvement.
They overlap because both prioritize customer needs and expertise. Solution selling specifically emphasizes diagnosing a problem and assembling an appropriate solution, while consultative selling is a broader relationship and advisory approach.
Use realistic role plays, review calls with permission, create question and follow-up examples, and coach a few observable behaviors at a time. Measure both sales outcomes and customer fit.
Learn the purpose behind each step rather than memorizing exact sentences. Listen to the answer, ask a relevant follow-up and use the customer’s language when summarizing.
They can be when they help customers understand choices and make informed decisions. Ethical selling requires accurate claims, transparent terms, respect for consent and a willingness to acknowledge poor fit.