B2B sales: how to manage long sales sycles, decision-makers, and next steps in a CRM
November 19, 2026
6-minute read
Dmytro Suslov
A long B2B sales cycle moves forward when everyone understands who makes the decisions, what needs to be approved, and what happens next. Keep this context in your CRM, coordinate team activities, and build forecasts based on confirmed customer agreements.
A sales representative has presented an IT solution implementation service, sent a proposal, and received positive feedback. However, the finance director has not yet approved the budget, the technical specialist has questions, and the primary contact cannot provide a decision date. In the CRM, the deal is still marked as "promising," even though the path to purchase remains unclear.
Managing this type of sale requires visibility into the company's needs, pending approvals, and next steps for both parties. This article explores how to organize a lengthy sales cycle, account for the perspectives of different stakeholders, and develop a realistic sales forecast. We'll follow a hypothetical sales scenario throughout the article and demonstrate how to manage it in a CRM using Uspacy as an example.
What B2B sales are and why complex deals require a different approach
B2B sales involve selling products or services to other businesses. Some business purchases require an extended evaluation process, although routine orders from an established supplier may be completed quickly.
Long sales cycles occur when a company needs to assess its requirements, verify technical compatibility, and secure budget approval. Additional time may be needed to compare vendors, complete procurement procedures, and conduct legal reviews. Each approval stage involves specific stakeholders and timelines.
In our example, an operations manager is interested in implementing an IT solution to handle incoming requests. However, their positive response to the presentation does not necessarily mean the company is ready to make a purchase. The sales representative needs to understand the underlying problem, expected outcomes, key stakeholders, purchasing process, and desired implementation date.
Before preparing a detailed proposal, clarify what needs to be approved before work can begin and who is involved in the decision-making process. This allows the sales representative to manage the opportunity based on the company's actual purchasing requirements.
Working with decision-makers and the buying committee: how to account for every stakeholder
A decision-maker is the person who makes the final purchasing decision, while a buying committee is the group of stakeholders involved in the purchasing process. Decision-making influence is often shared among multiple people, so simply recording someone's job title in a contact record is not enough to understand their role.
When selling an implementation service, identify who performs the following roles:
- Initiator: Raises the need for change and explains the underlying problem.
- End user: Evaluates how well the solution fits into everyday workflows.
- Internal champion: Supports the proposal and helps coordinate discussions within the company.
- Technical expert: Evaluates compatibility, integrations, and data requirements.
- Budget owner: Approves spending and evaluates the expected return on investment.
- Procurement specialist: Evaluates the vendor and oversees the purchasing process.
- Authorized signatory: Has the authority to sign the contract.
One person may perform multiple roles. However, the person authorized to sign the contract does not necessarily define technical requirements or approve the budget.
In our scenario, end users need a simple way to process incoming requests, the technical specialist requires integration with the company's accounting system, and the finance director needs a clear cost estimate. If a quick launch conflicts with the scope of technical work, discuss a compromise, such as a phased implementation.
In your CRM, store contact details, relationships between contacts and the company, and each person's involvement in the deal. Distinguish between a person's job title and their role in a specific purchasing decision: a department manager may support the project without having budget authority. Keep any unknown responsibilities or positions as questions to clarify.
B2B sales funnel: which stages and transition criteria to define
Funnel stages should reflect verified outcomes achieved when working with a company. For our scenario, we'll build a sequence that accounts for solution evaluation, approvals, and payment.
A sample sales funnel would include the following stages:
- Lead qualified: The problem has been confirmed, and the service is a potential fit.
- Needs and criteria confirmed: The customer has confirmed their requirements and expected outcomes.
- Solution validated: The technical team has approved the results of the demonstration or evaluation.
- Commercial terms approved: Authorized stakeholders have confirmed the scope, pricing, and timeline.
- Contract signed: The agreed-upon commitments of both parties have been formally documented.
- Awaiting payment: Payment documents have been sent, and the payment deadline has been agreed upon.
In this example, a deal is considered successfully closed once the advance payment has been received, allowing the implementation team to begin work. Record unsuccessful outcomes separately, along with the reason, such as project cancellation or the customer's decision to choose another vendor.
Simply sending a proposal does not mean the terms have been approved. Technical and legal reviews may take place simultaneously, and a new requirement may bring both parties back to discussing the proposed solution. The funnel stage should reflect the overall status of the deal, while individual approvals should be tracked through fields, activities, and tasks.
For a purchase that has been postponed, record the reason for the delay and the date or event that should trigger renewed discussions. This helps distinguish potential future business from deals that can realistically be expected to close in the near term.
Next steps, proposals, and approvals: how to keep long sales cycles moving
In a long B2B sales cycle, the sales representative coordinates the efforts of the customer, technical specialists, and their own team. Keeping the deal moving requires connecting requirements, documents, and approvals to specific actions. In Uspacy, the deal record provides the foundation for this process.
Keep requirements and outstanding questions in one place. In our scenario, a company is purchasing the implementation of an IT solution for processing incoming requests. In the CRM card, the sales representative documents the expected outcomes, adds technical requirements, and records notes from meetings. Custom fields can be configured to track recurring details, such as "Accounting system," "Required integrations," "Target launch date," and "Budget approval." This gives the team visibility into what has already been confirmed and what still needs clarification.
Turn agreements into activities and tasks. The customer promises to provide a description of their accounting system by Wednesday. The sales representative schedules an activity linked to the deal to review the materials once received and creates a task for the technical specialist to evaluate the integration by Friday. The task includes the requirements, files, and expected deliverables: a list of necessary work, potential limitations, and a preliminary estimate. Once the assessment is complete, the representative schedules a meeting with the customer and sets a reminder.
Build proposals using data from the specific deal. Services can be added as products, including auditing, configuration, data migration, and training. Each line item can include a quantity and price, while the total deal value is calculated based on the products added. This makes it easier to discuss the proposal's scope, such as which services are included in the first phase and which will be delivered later.
Using the document generator, the sales representative prepares a proposal using a configured template. The document can automatically populate information from CRM fields, company details, and product lists with their corresponding attributes. Before sending it, verify the scope of work, pricing assumptions, and current terms. Save the sent version in the deal record and note the date so colleagues know which version the customer is reviewing.
Track individual approvals separately from the overall deal stage. While the customer's technical specialist reviews the integration, the finance director may be evaluating the cost estimate. Record the status of each approval in separate fields, document discussion outcomes in notes, and schedule follow-up interactions as activities. Move the deal to the approved terms stage only after receiving the necessary confirmations.
After each meeting, send the customer a summary outlining what was agreed upon, which questions remain open, and who is responsible for the next steps. Save this context in the deal record. If the sales representative changes, another colleague with the appropriate access can review the requirements, current proposal, and scheduled actions and continue the negotiations without losing context.
Active B2B deals and sales forecasting: how to assess deal progress
Managing ongoing sales requires visibility into active deals, their values, funnel stages, and expected closing dates. This collection of opportunities is known as the sales funnel, but its total value does not represent a forecast for any specific month.
During regular funnels reviews, check for reliance on a single contact, budget approval status, and the approval process. Pay particular attention to deals with no scheduled next steps or repeatedly postponed closing dates. Ask what supports the expected timeline and which customer decisions are still pending.
For example, a sales representative expects to receive an advance payment for an implementation project by the end of the month. However, the budget has not been approved, and the legal department has not yet received the contract. Including this deal among the most likely incoming payments would be risky. The first step is to clarify the approval process and expected timeline.
Build your forecast based on customer confirmations and historical data from similar sales. Analyze sales cycle length, transitions between funnel stages, closing date changes, and reasons for lost deals. Probability estimates help predict the expected outcome across a group of deals, but they do not guarantee that any individual deal will close.
Start with your largest active deals: review the stakeholders involved, outstanding questions, and the evidence supporting an expected sale within the projected timeframe.
Conclusion
Managing a long B2B sales cycle requires a shared understanding of the customer's needs, the stakeholders involved, and the purchasing process. Positive feedback after a presentation does not necessarily mean the budget has been approved or the company is ready to sign a contract. A CRM helps keep track of requirements, stakeholder positions, current proposals, and agreements, while linked activities and tasks define the team's next steps. This context allows negotiations to continue even when the sales representative or the customer's primary contact changes.
Start with a typical deal: identify stakeholder roles, establish criteria for moving between funnel stages, and agree on the next steps with both parties. Test the approach in practice and use it as a model for similar sales opportunities. Regular reviews of pending approvals and deadlines will help the team identify obstacles early and enable the sales manager to build more accurate forecasts.
Updated: November 19, 2026
FAQ
What are B2B sales?
Who is involved in B2B purchasing decisions?
Which stages should a B2B sales funnel include?
How do you keep a deal moving through a long sales cycle?
How do you forecast long B2B sales cycles?
How does a CRM help manage complex B2B sales?
Uspacy is improving and developing at an incredible speed
Learn about product development plans
Uspacy roadmap 🚀