Sales CRM: how to build a managed process from lead to payment in Uspacy

Sales CRM helps make this process manageable when the team has agreed on the stages, assigned responsibilities, and defined the next steps. Let’s look at how to organize the workflow in Uspacy using the example of a company that sells business equipment—from a website inquiry to payment confirmation.

The funnel should reflect the customer’s actual journey and show what progress has been made toward closing the deal. Define the criteria for moving to the next stage so that all team members have a consistent understanding of the deal’s status.

In our example, the process follows this sequence: needs assessment → proposal preparation → terms negotiation → awaiting payment → successfully completed. First, the team member handling the sale determines the customer’s equipment requirements, budget, and purchasing timeline. Once enough information has been gathered, they prepare a proposed equipment configuration and cost estimate.

After the proposal is sent and feedback is received, the parties begin negotiating the price, delivery terms, and payment arrangements. A deal moves to the awaiting payment stage once the terms have been approved and the necessary documents have been sent. The deal is marked as successfully completed after payment has been confirmed and any other company-defined requirements have been met.

If equipment sales and service maintenance follow different workflows, it makes sense to configure separate funnels for each. This allows the manager to evaluate each business line according to its relevant stages without mixing different sales processes. The next step is to organize how new inquiries are handled.

Every inquiry should be recorded, its source documented, and a responsible person assigned. The team should also establish a response time for the first contact, such as within one business hour.

A customer submits an inquiry about equipment, but a phone number alone is not enough to prepare a proposal. The team member handling the inquiry clarifies what the equipment will be used for, the required performance specifications, and the planned purchase date. This turns initial interest into a qualified sales opportunity.

In Uspacy, a deal, contact, and company can be created from a qualified lead. The information needed for follow-up includes the buyer’s requirements, timeline, budget, decision-makers involved in the approval process, and agreements reached so far. Custom field mapping should be configured in advance to avoid transferring information manually.

The manager monitors whether every new inquiry has been assigned a responsible person and whether the first contact takes place within the agreed timeframe. After the conversation, it is important to record the next steps.

Every active deal needs a specific next step. That is why the team follows a basic rule: every active deal must have a next action, a responsible person, and a due date.

After sending a proposal, the team member handling the deal schedules an activity to call the customer and discuss it. A clear description, such as “Review the equipment configuration and get a response by Thursday,” provides more direction than “Follow up later.” A reminder helps ensure the conversation happens on time, while the outcome of the interaction determines the next steps.

Emails, calls, and agreements should be documented in the context of the customer and the deal. This allows the team member to review the agreed-upon price, objections, and promised timelines before the next interaction. A colleague stepping in to cover the account also has the information needed to continue the conversation.

A personal follow-up call is recorded as an activity. Preparing a technical specification with input from an engineer is tracked as a separate task with a responsible person, due date, and expected outcome. The manager reviews overdue actions, while the team automates some of the repetitive steps.

Sales automation reinforces the rules the team has already agreed on. For each workflow, define the trigger, action, expected outcome, and person responsible.

For example, changing a deal’s stage can trigger the creation of a follow-up activity. The team member handling the deal receives a scheduled action linked to a specific sale. In Uspacy, this workflow can be configured using conditional actions. Set the appropriate time for follow-up reminders, and notify the manager when nonstandard terms require approval. More complex sequences involving wait periods and condition checks can be built using Processes.

At the final stage, the team member prepares the documents and records the agreed amount and payment deadline. In Uspacy, you can create a payment based on the products listed in a deal record, generate a payment link, and send it to the customer. To do this, connect one of the available payment systems, such as Monobank, LiqPay, WayForPay, or Stripe.

Once the payment is successful, the integrated service sends the result to Uspacy, and the payment status automatically changes to “Paid.” The team member can see the confirmation in the Workspace and continue coordinating order fulfillment. Sending an invoice or payment link alone does not mean the sale is complete.

For partial payments, the team separately tracks the amount received, the outstanding balance, and the next payment date. Order fulfillment is tied to an agreed-upon condition, such as confirmation of the deposit. Payment status and deal stage are tracked separately: receiving payment does not mean all obligations to the customer have been fulfilled.

To evaluate how the entire process performs—from the initial inquiry to payment—the manager needs specific metrics.

Metrics should help managers make informed decisions about active sales. To achieve this, the team must consistently record contact outcomes, stage transitions, and reasons for closing or losing deals.

First-response time shows how quickly new inquiries are handled. Conversion rates between funnel stages help identify where potential customers drop off, while sales cycle length helps reveal delays. Overdue activities point to missed follow-ups, loss reasons explain why deals fall through, and individual performance metrics provide a basis for one-on-one reviews.

If deals stall after proposals are sent, review the proposals themselves and the frequency of follow-up communications. When comparing team members, account for differences in lead sources and sales complexity. Expected revenue and actual payments should also be tracked separately: an agreed-upon deal value does not mean the money has been received.

Start with the metrics that will help you identify bottlenecks in your specific sales process. For each metric, define the required data, the calculation method, and the management decision it will inform.