Ask most service business owners where a job is up to and you get an accurate answer in about four seconds. That is the problem, not the proof it works.
It works because you are holding it. Twenty or thirty live jobs, each with its own next step, sitting in one person's head and partly in a spreadsheet that is updated on Sundays if the week was calm.
It fails in exactly three situations, and all three happen every month. When you are on a roof. When two things land at once. And when somebody who is not you needs to know what happens next.
A pipeline is not a list of jobs. It is a list of promises with dates attached. Once it is written down, it stops needing you to run it.
What the mental pipeline costs
The cost of the mental pipeline is not dramatic. It is a slow tax.
Put numbers on a normal month. Thirty live opportunities. On memory alone, four or five slip past their natural follow-up window each month. That is not carelessness, it is arithmetic: nobody tracks thirty parallel timers reliably while also running crews.
| Per month | By memory | With a pipeline |
|---|---|---|
| Live opportunities | 30 | 30 |
| Slipped past follow-up | 5 | 0 to 1 |
| Jobs recovered at a 45% close rate | n/a | 2 |
| Monthly value at $850 | n/a | $1,700 |
| Annual value | n/a | $20,400 |
Twenty thousand a year from writing down what you already know. And that is before the hours you get back, and before the part where somebody else can finally cover the office without a handover meeting.
The build, step by step
Six stages. Each one gets an exit rule and a timer. That is the whole design.
Every timer above is a rule the system enforces, not a task somebody remembers. That is the difference between a pipeline and a list.
The two rules that keep it honest
Rule one: no record without a next action date. Make the field required at every stage except Won and Lost. It sounds bureaucratic until you watch what happens to a pipeline without it, which is that half the records quietly become archaeology within six weeks.
Rule two: every stage has a timer, and the timer belongs to the system. If moving a job forward depends on somebody noticing that eleven days have passed, it is not a rule, it is a wish. The system chases, escalates and reminds. People make decisions.
Those two rules are worth more than any feature you will be sold. A basic pipeline that enforces them beats an expensive one that does not, every time, and the difference shows up in the Quoted stage first.
One warning about stages: resist adding a seventh. Every extra stage feels like precision and behaves like friction, because it is one more place a job can sit while everybody assumes somebody else owns it. If you genuinely need more detail, add a field, not a column. Six stages fit on a screen, and a pipeline you can see in one glance is a pipeline people actually keep current.
What changes once it is in
Before: you were the pipeline. Every question routed through you, and every day you were out on a job was a day the follow-ups paused.
After: the stages hold the promises, the timers do the chasing, and the office can answer any question without calling you. You still know where every job is. You are just no longer the only place that knowledge lives.
If the answer to what happens next lives in one person's head, you do not have a pipeline. You have a hostage.
The measurable: opportunities with no next action date, and days in stage. When nothing sits in Quoted for eleven days any more, the pipeline is running itself and you have your Sundays back.
