PE-101 · Module 1

Pipeline Is Infrastructure

3 min read

Most organizations treat pipeline like a spreadsheet — a list of deals with dollar amounts and close dates that someone updates before a forecast call. That is not pipeline. That is a wish list with formatting. Real pipeline is infrastructure. It is a system of stages, definitions, entry criteria, exit criteria, and measurable conversion rates that tells you exactly how much revenue your organization will produce, when it will arrive, and where the system is failing. The difference between pipeline-as-spreadsheet and pipeline-as-infrastructure is the difference between guessing and knowing.

Do This

  • Define each pipeline stage with explicit entry criteria, exit criteria, and a verifiable buyer action
  • Treat stage definitions as contracts — a deal does not move until the criteria are met
  • Instrument every stage transition with a timestamp so you can measure velocity

Avoid This

  • Let reps self-report stage based on gut feel or optimism
  • Use stages like "Interested" or "Warm" that describe your perception, not the buyer's behavior
  • Skip timestamps — without them, velocity analysis is impossible

The first principle of pipeline engineering is that stages must reflect observable buyer behavior, not seller perception. "Qualified" means the buyer confirmed budget, authority, need, and timeline — not that the rep had a good feeling after the first call. "Proposal Sent" means the buyer requested a proposal — not that the rep sent one hoping for a response. Every stage should answer the question: what did the buyer do to get here?