Sales stages: how to build a process from first contact to successful deal closure in CRM

For a sales funnel to help manage sales effectively, each stage must represent a clearly defined outcome. We'll explore the classic model, adapt it to a real-world sales process, and establish rules for moving deals between stages. Using Uspacy as an example, we'll show you how to implement this approach in your CRM—from configuring the sales funnel to tracking payments.

The classic five stages of the sales process describe the sequence of interactions with a prospective customer. Each stage has a specific objective and outcome that moves the conversation forward.

This model includes:

• Making initial contact. Start a conversation and establish communication. The outcome: the prospect understands the purpose of the outreach and is willing to discuss their needs.
• Identifying needs. Determine the customer's challenges, expectations, and constraints. The outcome: a clear understanding of what the customer needs and the criteria they will use to make a decision.
• Presenting a solution. Connect the product's capabilities to the customer's specific needs. The outcome: the buyer understands the proposed solution and its value.
• Handling objections. Clarify concerns and provide the necessary explanations. The outcome: potential obstacles are identified, and an approach to addressing them is agreed upon.
• Closing the sale. Agree on the terms and complete the steps required to make the purchase. The outcome: the company achieves its defined goal, such as receiving payment.

For example, a sales representative at an equipment supplier determines the required capacity, recommends a suitable model, and explains the service terms. After discussing the price, both parties agree on the configuration, delivery timeline, and payment terms.

Six- or seven-stage models provide a more detailed breakdown of this process by treating preparation, qualification, or post-sale engagement as separate stages. The number of stages depends on your sales process and the level of detail required. Use the classic model as a starting point, then assess how purchases actually happen in your business.

Start by reviewing several won and lost deals. Reconstruct the sequence of conversations, decisions, and approvals to understand the customer's actual buying journey.

Determine how the communication began, who was involved in the decision-making process, and what information was needed to prepare a proposal. Identify where delays occurred and why customers decided not to proceed. Recurring patterns will help you determine which intermediate outcomes need to be tracked.

In a short sales cycle, consultation, product selection, and payment may all take place within a single conversation. A complex B2B sales process, however, may involve technical assessments, product demonstrations, contract negotiations, and an upfront payment. Such a process requires a more detailed sales funnel, especially when multiple stakeholders are involved in the decision-making process.

Define the boundaries of your sales process: when a deal is considered closed and what constitutes a successful outcome. If the goal is to receive payment, a signed contract is still an intermediate milestone. Once you have mapped out the customer journey, determine which changes in the process should be represented as separate stages in your CRM.

The classic stages of customer interaction should not be mechanically transferred into CRM columns. A sales funnel should reflect the current status of each deal and provide a clear basis for moving it forward.

Making a call and sending an email are actions performed by a sales representative. A confirmed need and agreed-upon terms are outcomes of customer interactions. Objection handling can occur at different stages, so it does not always need its own funnel column.

For each stage, define the entry condition, required data, next action, and exit criteria. For example, “Proposal sent” means the customer has received a specific solution. The deal record stores the document version and discussion date, while the sales representative schedules a follow-up task. The deal moves to “Terms agreed” once the scope, price, and timeline have been confirmed.

Account for exceptions. Close lost deals with a documented reason; for postponed decisions, set a date to resume the conversation. If requirements change, move the deal back to the relevant stage and record the reason. Clarify vague stage names such as “Considering” and “In progress,” as they do not indicate what has actually been achieved.

Compile these rules into a concise guideline with examples of stage transitions. It will serve as the foundation for CRM configuration and sales team training.

Once the rules are defined, you can configure your CRM sales funnel. Let's look at how to implement this in Uspacy using a hypothetical B2B service where deal management begins after the initial lead qualification.

The intermediate stages follow this sequence:

• Lead qualified. Interest and basic fit for the service have been confirmed; the next step is a detailed discussion.
• Needs identified. Requirements and expected outcomes have been documented; the proposal can now be prepared.
• Proposal sent. The customer has received the document; a discussion of the terms has been scheduled.
• Terms agreed. The scope, price, and timeline have been confirmed; the deal is ready to move to payment processing.
• Awaiting payment. The invoice has been sent and the payment deadline agreed upon; the sales representative monitors the incoming payment.

Mark a deal as successfully closed once payment has been confirmed in accordance with your established rules. Also define an unsuccessful outcome and record the reason for the lost deal, such as choosing a competitor or canceling the project.

In Uspacy, you can create custom intermediate stages and configure sales funnels to match your company's processes. If one-time service sales differ significantly from complex project sales, use separate funnels.

Connect these rules to deal record fields and activities. For example, store the deal amount, service scope, and timeline once the terms have been agreed upon, and record the payment date when awaiting payment. In Uspacy, you can make specific fields mandatory for individual funnels and stages. This ensures that the required information is provided when a deal moves to the next stage, although the sales representative remains responsible for verifying the accuracy of the agreements.

At the “Awaiting payment” stage, the sales representative can manage payments directly in the CRM. In Uspacy, after connecting a payment system, you can create a payment based on the products listed in the deal record, generate a payment link, and send it to the customer. Once the payment is successful, its status is updated automatically. The team can view the payment outcome alongside the sales details and agreed-upon terms.

Payment status and deal stage represent different things. Define in advance who is responsible for closing the sale after payment confirmation and transferring the order to fulfillment. For more details on this process, see the article "Online payment processing in CRM: how to accept and track payments using Uspacy as an example".

Test your funnel using real deals: make sure the team knows where to place each deal and what action to take next.

Check how closely your configured sales funnel reflects the team's actual workflow. Monitor conversion rates between stages, the time deals spend at each stage, the overall sales cycle, and the reasons deals are lost.

For example, in Uspacy, you can use the "Funnel conversion" report for this purpose. It shows how many deals pass through each stage, which stages are skipped, and how much time deals spend at each stage on average. Conversion rates between consecutive stages help identify where the biggest losses occur, while cumulative conversion shows what percentage of deals have reached a particular stage since entering the funnel.

A growing number of deals stuck at the payment stage is a reason to review payment deadlines, whether customers have received their invoices, and the agreements in place. Losses after a presentation call for an analysis of lead qualification, customer needs, and how well the proposal meets those needs. Metrics help identify where to investigate, but the underlying reasons must be determined by reviewing individual deals.

Signs of a poorly structured funnel include stages that are consistently skipped, a lack of follow-up actions, or inconsistent interpretations of stage transitions. If two columns represent the same status, consider merging them. If a separate approval step regularly occurs between them, consider adding another stage. However, skipping a stage does not always indicate a problem: an existing customer may place an order directly without going through the entire process.

Review the rules together with your sales representatives and base improvements on recurring patterns. After making changes, explain the new criteria to the team and monitor how they affect deal progression.