PE-201a · Module 2

When One Pipeline Fails

3 min read

A single pipeline works when every deal follows roughly the same buyer journey. An enterprise software company selling one product to one buyer type can use one pipeline effectively. But the moment you have materially different sales motions — new business versus expansion, SMB versus enterprise, product-led versus sales-led — a single pipeline forces fundamentally different deal types into the same stage structure. The conversion rates become meaningless because they are averaging across deal types with completely different behaviors.

Do This

  • Create separate pipelines when deal types have different stage sequences, cycle times, or conversion patterns
  • Use a shared reporting layer that aggregates across pipelines for total revenue visibility
  • Keep each pipeline simple — the complexity is in the architecture, not in individual pipelines

Avoid This

  • Force all deal types into one pipeline and wonder why the conversion rates do not make sense
  • Create a new pipeline for every minor variation — separate pipelines for deal types, not deal sizes
  • Manage multiple pipelines without a unified view — leadership needs to see the total picture

The three most common multi-track patterns are: new business versus renewal/expansion, SMB (self-serve or low-touch) versus enterprise (high-touch), and inbound (marketing-generated) versus outbound (sales-generated). Each pair has fundamentally different stage sequences, velocity profiles, and conversion rates. Analyzing them together produces averages that describe neither.