Sales techniques: 10 methods and how to integrate them into your CRM process

A shared approach helps make this experience accessible to the entire team. Let's explore ten sales methods and techniques and look at how to document the results of applying them in a CRM system, using Uspacy as an example.

A sales methodology defines the overall approach to working with customers. A sales technique helps accomplish a specific task: identifying customer needs, explaining value, or addressing objections. A sales script provides a conversation structure and examples of what to say.

This overview covers tools that operate at different levels. SPIN is an approach based on asking questions about the customer's situation, problems, the implications of those problems, and the benefits of solving them. Challenger helps sales representatives offer customers a new perspective on their challenges and guide them toward a decision with well-supported arguments. FAB (Features, Advantages, Benefits) explains how to connect a product's features to the value they deliver to the buyer. These tools provide a framework that sales representatives can adapt to individual conversations. Their application depends on the situation, so conversations should never become mechanical recitations of prepared scripts.

A shared approach gives the team clear guidelines on what to uncover, how to present and support an offer with compelling arguments, and which agreements to document. Sales representatives can tailor their questions to each customer, while colleagues gain the context they need to continue working with the account effectively.

These approaches help sales representatives understand a buyer's situation and align their offering with the customer's goals. They are especially valuable when customers need to evaluate a problem, compare alternatives, or make a complex purchasing decision.

• SPIN selling. A structured sequence of questions explores the customer's Situation, Problem, Implication, and Need-payoff. This approach is particularly useful when selling services and the initial customer request needs further clarification. For example: "How do you currently process incoming inquiries? Where do delays occur? How do they affect sales? What would change if you could reduce response times?" In your CRM, document the confirmed problem, its implications, and the expected outcome.
• SNAP selling. This approach is designed for working with busy buyers and focuses on simplicity, the value of interactions, alignment with business objectives, and prioritizing the most pressing problems. Instead of delivering a lengthy presentation, suggest a brief, focused conversation: "You're planning to launch a new department. I'd suggest spending 15 minutes reviewing how to organize lead handoffs between sales representatives." In your CRM, record the customer's priorities and the agreed-upon next step.
• Challenger sale. The sales representative introduces a well-supported new perspective on the customer's problem, tailors arguments to the stakeholders involved in the decision-making process, and helps move the conversation toward a decision. This approach is particularly relevant to complex B2B sales. For example: "Before increasing your advertising budget, let's examine where leads are being lost between submission and the first follow-up." Discuss the impact on revenue with executives and workflow implications with sales representatives. In your CRM, document the hypothesis, supporting facts, customer feedback, and each stakeholder's position.
• Consultative selling. The sales representative analyzes the customer's request and helps them choose the most suitable option based on their needs and constraints. This approach works well when buyers are unsure about the required package or service scope. For example: "Given your current workload, the basic plan should be sufficient. You can consider upgrading once you open another branch." In your CRM, record the selection criteria, limitations, and rationale behind the recommendation.
• Solution selling. This approach connects a customer's problem with a specific configuration of products or services. It is useful when achieving the desired outcome requires combining several components. For example, a service company might be offered a solution that includes inquiry collection, responsibility assignment, and team training. In your CRM, document the use case, solution components, and the conditions under which the proposed solution meets the customer's needs.

These approaches often overlap: identifying needs, making recommendations, and configuring a solution can all be part of the same conversation. Choose an overall approach based on the nature of the sale, and combine individual techniques as needed.

Once the customer's needs are clear, the next step is to explain the value of your offering and assess their readiness to move forward. The following techniques are useful during sales calls, meetings, and email or other written communications.

• AIDA: Attention → Interest → Desire → Action. This model helps structure an initial message or a brief product presentation. For example: "Are you opening a second branch? We'll show you how to consolidate inquiries from both teams so the manager can see who is responsible for each one and what actions are next. Can we schedule a brief demo?" In your CRM, record the offer that caught the customer's attention and the outcome of the interaction.
• FAB: Feature → Advantage → Benefit. This technique helps explain a product feature in terms of its value to a specific buyer. For example: "You can schedule tasks directly in the deal record. Sales representatives can see the next action and its due date. This will help your team follow up on proposals on time." In your CRM, document the key benefit and the customer's confirmation that it is relevant to their needs.
• Active listening. Asking clarifying questions and paraphrasing help verify that you understand the customer's needs before presenting a solution. For example: "If I understand correctly, you receive inquiries regularly, but some of them don't receive any follow-up after the initial conversation, right?" Give the customer an opportunity to confirm or correct your understanding. In your CRM, record the agreed-upon description of the need and any outstanding questions.
• Clarifying objections. This technique is useful when customers say "It's too expensive" or "I need to think about it," but the reason behind their hesitation is not yet clear. Ask: "Is the price above your planned budget, or is it still unclear what results your team will get from the solution?" The answer determines how to proceed with the discussion. In your CRM, document the specific objection, the explanations provided, and any unresolved questions.
• Summarizing and agreeing on the next step. At the end of a meaningful interaction, summarize what has been agreed upon and suggest a specific action with a deadline. For example: "We've agreed to involve both departments. I'll prepare a configuration proposal by Thursday, and on Friday at 12:00 p.m., we'll review it with the head of sales. Does that work for you?" In your CRM, record the action, the person responsible, and the deadline.

A conversation may result in a product demo, a technical consultation, or approval of a proposal. Moving toward payment depends on the customer's readiness and whether all necessary conditions have been met. Compare these techniques with typical sales scenarios to identify which ones are most relevant to your team.

The right choice depends on product complexity, the buyer's level of readiness, and the time available for the conversation. A brief inbound call and a multiweek B2B project approval process require different levels of discovery.

During an incoming call, clarify the customer's request, explain the relevant benefits, and agree on the next step. For active inquiries, SNAP and AIDA can help structure a concise, relevant offer. When selling services, SPIN and consultative selling are particularly useful. For complex B2B deals, focus on needs discovery, engaging decision-makers, and developing well-supported Challenger insights.

For example, a company is looking for a way to organize its incoming inquiries. Using SPIN, the sales representative identifies where customer context gets lost and then uses FAB to explain the benefits of a shared customer record. When the customer raises a price objection, the representative clarifies their budget constraints. The conversation then moves toward scheduling a demonstration with the department head.

Too many questions can overwhelm the customer, while presenting a solution before understanding their needs makes sales arguments too generic. Unsubstantiated promises create unrealistic expectations, and high-pressure tactics interfere with objective decision-making. Start with a few techniques for the most common scenarios and define the expected outcome for each one.

A CRM system helps you document the outcomes of sales conversations and connect them to follow-up activities. Let's look at how to combine several sales techniques using the example of a company that provides advertising setup services and manages its deals in Uspacy.

A prospective customer reaches out with a request: "We want to generate more leads." The sales representative uses SPIN to explore the situation: which channels are already working, how many inquiries come in, and what happens after the first contact. It turns out that some inquiries go unanswered and the company does not compare traffic sources based on the number of customers acquired. The representative explores the implications and asks what outcome the customer would consider successful.

In the deal record, the representative documents the confirmed problem, its impact on sales, and the customer's expectations for the engagement. In Uspacy, you can configure custom CRM fields for this purpose, such as "Customer need," "Expected outcome," and "Selection criteria." This ensures that the insights gathered during the conversation remain available when preparing a proposal.

For the presentation, the representative applies FAB (Feature, Advantage, Benefit): "Our service includes an analysis of advertising sources based on sales performance. This allows you to compare channels by the number of customers they generate. For your business, this provides a basis for making informed budget allocation decisions." The representative then checks whether these benefits align with the customer's priorities and records the response in the deal record.

When the customer says, "That's too expensive for us," the representative uses objection clarification: "Does the price exceed your planned budget, or is it still unclear what exactly is included in the service?" The customer explains that they are not ready to purchase the full-service package right away. The representative discusses the possibility of starting with a standalone audit and records the budget constraint and the agreed-upon proposal format.

At the end of the conversation, the representative summarizes the agreements and confirms the next step: "I'll prepare an audit proposal by Thursday. On Friday at 12:00 p.m., we'll review it together with your head of sales." In Uspacy, the representative creates an activity linked to the deal, specifying the time, person responsible, and meeting objective.

If a colleague with access to the deal record joins the process, they can see the customer's needs, budget constraints, proposed service format, and next action. This makes it easier to continue the conversation without revisiting questions that have already been addressed.

Start with one such scenario: agree on the questions to ask, the fields to use, and the rules for scheduling activities. When reviewing deals, assess whether customer needs have been confirmed, whether the proposal addresses those needs, and whether there is a specific agreement on how to move forward.