Introduction

Most small businesses have something they call a sales pipeline. It might live in a CRM, a spreadsheet, or a shared document. It has stages with names like “prospect,” “proposal,” and “closed.” It gets updated occasionally, usually before a team meeting or when someone asks how the numbers are looking.

But it is not really a pipeline. It is a list of deals with labels on them.

A real sales pipeline is not just a way of organising leads. It is a structured system that tells the business exactly where every opportunity sits, what needs to happen next, who is responsible for it, and what the likely revenue outcome is at any given point in time. When a pipeline is built properly, it removes the guesswork from sales. When it is built badly, or not built at all, it creates the illusion of visibility without any of the substance.

The difference between the two is not the software. It is the structure underneath.

Not sure which systems your business needs? Take the 5-minute Systems Health Check.

Why This Happens

The reason most small business pipelines do not work is that they were never designed. They were assembled.

Someone set up a CRM or a spreadsheet, added a few column headers that seemed logical, and started dropping deals into it. The stages were created based on intuition rather than on a clear understanding of how the business actually sells. Nobody defined what it means to move a deal from one stage to the next. Nobody established what action is required at each stage, or who is responsible for taking it. And nobody agreed on what a deal needs to look like before it counts as a genuine opportunity rather than a vague expression of interest.

The result is a pipeline that grows over time but becomes progressively less useful. Deals sit in stages for weeks without moving because there is no clarity on what should happen next. Old opportunities clog up the system because nobody has a clear rule for when to remove them. Pipeline value looks impressive until someone realises that half the deals in it are months old and have had no meaningful activity. And because the data is unreliable, the pipeline stops being used as a decision-making tool and becomes something that gets tidied up before meetings.

What Good Looks Like

A well-structured pipeline is built around the actual sales process of the business, not around a generic template. It has a small number of clearly defined stages, each with a specific meaning and a specific action attached to it.

For most small service businesses, five to seven stages is the right number. Fewer than that and the pipeline lacks the granularity needed to manage deals properly. More than that and it becomes unwieldy, with too many decisions required to move a deal forward.

Each stage should represent a meaningful moment in the sales process, a point where something specific has happened or needs to happen. A stage called “prospect” is too vague. A stage called “initial conversation booked” is specific and actionable. The language of each stage should reflect what the business actually does, not what a CRM vendor decided to call it by default.

Every stage also needs a clear exit criterion. What needs to be true for a deal to move to the next stage? This is the most important design decision in building a pipeline, and it is the one that most businesses skip entirely. Without exit criteria, deals drift. With them, the pipeline becomes a reliable picture of where the business actually stands.

The pipeline also needs structured fields alongside the stages. At minimum, each deal should capture the contact name, company, deal value, expected close date, and the last action taken. These fields turn the pipeline from a list into a reporting tool. They make it possible to calculate pipeline value, identify deals that are stalling, and forecast revenue with some degree of confidence.

Practical Examples

Example 1: The pipeline with no exit criteria

A consulting firm had a pipeline with six stages. Deals moved between stages based on gut feel, and there was no agreement on what each stage meant. As a result, one team member considered a deal “qualified” after a single email exchange, while another required a full discovery call before moving anything forward. The pipeline value varied wildly depending on who had updated it last, and leadership could not trust it as a forecasting tool. When exit criteria were introduced for each stage, the pipeline immediately became more reliable. Deals that should not have been there were removed, and the remaining ones reflected a genuine picture of the business’s sales position.

Example 2: The pipeline that was too complex

A recruitment agency built a pipeline with fourteen stages because they wanted to capture every nuance of their sales process. The result was that deals required constant management just to stay in the right place, and the team spent more time administering the pipeline than actually selling. When the stages were consolidated to seven, with clear actions and exit criteria at each point, adoption improved immediately and the pipeline became something the team used daily rather than avoided.

Example 3: The pipeline with no deal value

A small agency tracked opportunities by name and stage but never captured deal values. When the founder tried to forecast revenue for the following quarter, there was no basis for any estimate. Adding a deal value field and an expected close date to every opportunity transformed the pipeline from a contact list into a genuine forecasting tool. Within a month the founder could see, at any point in time, what the likely revenue for the next ninety days looked like.

How Systems Solve It

Building a pipeline that works is first a design exercise and then a systems exercise.

The design comes first. Before any tool is configured, the business needs to agree on its sales stages, the exit criteria for each one, the fields that matter, and the rules for keeping the pipeline clean. This is the thinking that most businesses skip because it feels like admin. It is actually the most valuable work in building a sales system.

Once the design is clear, the right environment can be built around it. For smaller teams, a well-structured spreadsheet pipeline with disciplined data entry will serve the business effectively. For teams that need automation, multi-user access, and real-time reporting, a platform-level CRM built around the specific pipeline design is the right investment.

At Castlane, every CRM project starts with pipeline design before any system is built. The stages, exit criteria, and field structure are agreed before a single row or record is created. That sequence is what separates a pipeline that works from one that looks like it should but does not.