Pipeline stages that mean something

A pipeline is a list of stages a piece of work passes. Its entire value rests on one condition. Everybody has to read each stage the same way. Most pipelines fail that condition quietly. Ask two people in the same business what Qualified means. The answers differ by a week of work, which makes the count describe nothing in particular.

The symptom is easy to spot. A pipeline where most records sit in one middle stage is not describing a business where most work is at the same point. It is describing a set of stages whose differences are opinions rather than events.

Every stage needs a test anybody can apply

A stage is not a feeling about how likely the work is. It is a fact that either happened or did not, and somebody unfamiliar with the deal should be able to check it. Quoted means a quote reached the customer. Won means the customer accepted. Anybody can confirm both in seconds from the record. That is what makes the count worth showing to anybody.

The discipline this imposes is useful beyond reporting. A stage with a real entry test forces the business to decide what moves work forward. That conversation is often worth more than the pipeline it produces.

Three to five stages, named after the work

Nine stages produce a pipeline nobody maintains, because the differences between stages three, four and five require a judgement call every time. Enquiry, quoted, won, in progress and done describes most small businesses honestly and fits on a board somebody can read at a glance. Diract CRM lets a business name its own stages, which is an invitation to keep the list short rather than a prompt to fill it.

Naming matters as much as counting. Nurturing, developing and progressing describe what somebody is doing about a deal rather than where the deal stands, and a customer cannot be in Nurturing. A quote can be awaiting an answer, and that is a fact anybody can confirm. The better test for a stage name is whether a person outside the business would understand it.

The holding stage, and the losses

Every pipeline eventually grows a stage that collects work nobody wants to close: on hold, maybe later, waiting on client. That stage is not a problem in itself, and it becomes one the moment records enter it without a review date. Without one it becomes a place work goes to be forgotten, while still counting towards the total. That quietly inflates every figure the pipeline produces.

Losses need the opposite treatment. Deleting a lost enquiry destroys the only record of what the business quoted and why it lost. That record is the most useful thing a pipeline produces in a year. A Lost stage with one reason from a short list turns twelve months of disappointments into a usable report. Our guide to recording why you lost the quote covers reading it.

A board gets read, a list gets ignored

A pipeline presented as a list gets opened weekly, usually by one person preparing for a meeting. The same pipeline as a board, where each column is a stage and each card is a piece of work, gets read daily by everybody. The difference is not aesthetic. On a board the act of moving work is the act of updating the record, so the two never drift apart.

In Diract CRM a board groups records by stage, and dragging a card saves the change immediately. Some moves need no dragging at all. Sending a quote and receiving an acceptance are both facts the system already holds. Diract CRM can set the stage itself, which keeps the board honest between reviews.

Count the age, not just the stage

Twelve deals in Quoted is a fact about the business that suggests nothing in particular. Twelve deals in Quoted, four of them older than three weeks, is a morning's work with an obvious order. Age turns a pipeline from a picture into a task list, and most pipelines omit that column.

The same applies to who owns each stage. A pipeline with no owner per stage drifts, because moving work out of a stage is nobody's particular job on any particular day. Naming that turns the board into a routine rather than something somebody tidies before a meeting.

One pipeline per kind of work

A business selling installations and maintenance agreements has two different journeys, and forcing both through one set of stages blurs each of them. The installation moves through a quote and a booking; the agreement moves through a proposal and a renewal date. Two short pipelines report separately, which is what the business wants anyway when deciding where to spend its selling time.

The cost of a second pipeline is small and the cost of one confused pipeline compounds, because every report built on it inherits the confusion. Where the journeys genuinely differ, splitting them early is cheaper than untangling a year of mixed records.

What to change first

• Each stage has a test anybody can apply without asking
• The list stops at five stages
• Stage names describe the work rather than the effort
• A holding stage carries a review date on every record
• Lost records stay, with a short reason
• The pipeline appears as a board, with cards somebody can drag
• Every stage count shows the age of what is sitting in it