Pipeline Architecture

Pipeline is not a list of deals. It is an engine. And like any engine, it has stages, each with specific inputs, outputs, and conversion rates. The rep who treats pipeline as a list tracks what happened. The rep who treats pipeline as an engine predicts what will happen. I have watched organizations transform their revenue predictability by doing nothing more than defining clear stage definitions and enforcing exit criteria. It is not glamorous work. It is the work that wins.

A well-architected pipeline has five to seven stages. Fewer than five and you do not have enough resolution to diagnose where deals stall. More than seven and reps stop updating because the distinctions feel arbitrary. Each stage needs three things: a clear definition that any rep can apply consistently, exit criteria that must be met before advancing, and a target conversion rate based on historical data. When you have all three, you can look at your pipeline on any given Monday and know — not guess, know — what your quarter is going to look like.

The most diagnostic metric in pipeline is velocity — how fast deals move from one stage to the next. A deal that has been in "proposal sent" for forty-five days is not a deal. It is a hope. Stage velocity tells you where your process is broken, which reps need coaching, and which deals need intervention. Track it by stage, by rep, by deal size, and by segment. The patterns will tell you exactly where to focus.