Product or Expertise: Why the e-commerce funnel doesn’t work for service businesses

In service businesses, this model breaks almost immediately. Managers don’t understand what the next step should be, the deal status doesn’t guide their actions, and funnel stages turn into a warehouse of vague agreements. This is exactly how flexible statuses such as “Thinking it over” appear—where leads hang for weeks and conversion quietly dies.

This article explains the difference between the logic that works for product sales and the model used in service sales. Most importantly, it shows what proper kanban setup should look like when the deal cycle relies not on logistics, but on trust, lead qualification, and a well-structured progression from first contact to prepayment.

Selling products is mostly a transaction. The customer sees a specific product, knows its features, compares prices, and wants to move quickly to payment. The deal cycle is short—ranging from a few minutes to a day or two. That’s why the sales funnel in a product business has one main goal: to avoid slowing down the order process.

Selling services works differently. The customer isn’t buying a prepacked item. They are buying an approach, a promise of results, the expertise of the team, and confidence that the problem will truly be solved. That’s why service businesses have longer deal cycles—ranging from a week to several months, and in B2B sales, sometimes up to a year.

For this reason, funnel stages in services cannot simply copy the product model. A CRM here shouldn’t just record the fact that a lead reached out. It must guide the lead through qualification, needs clarification, solution preparation, value presentation, and agreement on terms. Otherwise, the manager sees the card but has no clear understanding of the next step.

A product kanban operates like an assembly line. The customer already knows what they want to buy. For example, they may be looking for an iPhone 17, choose a color, select a delivery method, and proceed to checkout. In this model, the manager doesn’t warm up interest but quickly moves the order through the chain.

The typical workflow looks like this: “New order” ➝ “Confirmed” ➝ “Packing” ➝ “In transit” ➝ “Received/Paid”. All these deal statuses describe the movement of goods or money. And that’s fine, because logistics is at the center of the process.

The focus of this kanban is not on persuading the customer, but on execution accuracy. Is the product in stock? Is the address confirmed? Is the invoice prepared? Was the package shipped on time? For a product-focused model, this is sufficient. For services, however, it’s not—because the product still needs to be constructed in the customer’s mind.

This is where CRM plays a critical role, going beyond simply recording contacts. For example, with Uspacy, a service business can build a sales funnel tailored to its own deal cycle, rather than following an e-commerce template. This is especially valuable for teams that need to combine sales, communications, tasks, and subsequent execution in a single environment—without unnecessary switching between systems.

In this scenario, Uspacy functions not just as a CRM for services but as a comprehensive set of tools for process management. Managers can see deal status, interaction history, agreements, and next tasks—all in context. Meanwhile, leaders gain a transparent funnel that shows exactly where service sales slow down and at which stage the team loses conversion.

A service kanban is not an assembly line—it’s a negotiation route. The customer doesn’t come for a ready-made box, but with a problem: declining sales, chaotic requests, weak analytics, or an overloaded team. The solution is shaped during the interaction, and it’s for this solution that they are willing to pay.

Setting up a kanban for services should reflect trust-building, not the movement of documents or shipments. A practical model often looks like this: “New lead” ➝ “Qualification (Audit)” ➝ “Proposal preparation” ➝ “Proposal presentation” ➝ “Contract agreement” ➝ “Prepayment/Start”. Each funnel stage answers a simple question: what value has already been demonstrated to the client, and what step moves the deal closer to a decision.

In service businesses, the focus isn’t on how quickly the card moves between columns, but on the quality of each transition. If a deal is at “Proposal Ppeparation”, the manager must clearly understand what needs to be gathered: client requirements, scope of work, budget limits, and selection criteria. If the status is “Proposal presentation”, it means the proposal has not just been sent as a file—it has been explained, defended, and objections addressed.

That’s why a CRM for services must be flexible, not template-driven. Uspacy gives service businesses a different workflow logic: the funnel can be built around the company’s own deal cycle, the specifics of B2B sales, and the length of approvals—not the e-commerce model. This is critical for agencies, consultancies, law firms, or service companies, where deals pass through multiple points of trust rather than closing in one click.

Another key value of Uspacy is that it is not just a CRM, but a comprehensive business management toolset. Teams get a ready-to-use online service with a simple interface, a flexible no-code platform for customizing workflows, and an API-based foundation for integrations and extensions. The service kanban doesn’t have to be forced into someone else’s logic—it can be built around the real service sales process and scaled with the business.

An incorrect sales funnel doesn’t just affect the interface—it hits the bottom line. When a column doesn’t indicate a clear action, the manager delays contact, the deal ages, and the team loses control over the pace. That’s why service businesses must design their kanban as a decision workflow, not a collection of abstract labels.

1. “Client is thinking” – A dead-end status. This is the worst status in a CRM for services. It doesn’t explain what happened or what the manager should do next. Active labels work much better: “Waiting for proposal feedback”, “Follow-up call scheduled”, “Budget clarified”. Poor: “Thinking”. Good: “Proposal presented” or “Follow-up contact planned”.

2. Mixing sales and production. Often, a board shows “Presentation” next to “Design drafting” or “Work approval” next to “Ad setup”. This is a mistake. Sales should end with a status like “Prepayment received” or “Successfully closed”, after which the deal moves to a separate project or production funnel. Otherwise, the sales team ends up managing execution tasks instead of closing new deals.

3. Passive column labels. Statuses like “Call”, “Meeting”, “Contract” provide no context. They describe the topic but not the outcome. Kanban columns should use action-oriented or completed-step labels: “Qualification completed”, “Meeting conducted”, “Proposal presented”, “Contract agreed”. Poor: “Contract”. Good: “Contract sent” or “Contract signed”.

In a product-based model, businesses usually work with anyone willing to pay. In services, this can be risky. A non-target client consumes team time, drags out proposal preparation, requests unnecessary extras, lacks budget, or expects results that don’t match reality. That’s why lead qualification isn’t a formality—it’s a key filter.

At this stage, the client’s fit is evaluated: budget, timelines, decision-maker authority, task complexity, and realism of expectations. Without this filter, a service business burdens itself with unnecessary work even before a contract is signed.

In the kanban, this should be clearly represented. The stage “Qualification (Audit)” and the status “Qualification completed” must serve as mandatory gates before proposal preparation. Only after this does the lead move forward. This discipline keeps the team focused, shortens the deal cycle, and improves the quality of the sales funnel, leaving only opportunities that truly lead to revenue.