PE-301f · Module 1

Single vs Multi-Pipeline Architecture

3 min read

When your organization sells multiple products, the first architecture decision is whether to manage them through a single pipeline with product line items or through separate pipelines per product. The answer depends on how buyers buy. If buyers typically evaluate and purchase products together (a platform sale), a single pipeline with multi-product deals is correct. If buyers evaluate and purchase products independently (a portfolio sale), separate pipelines are correct. Choosing wrong creates either artificial complexity (separate pipelines for bundled products) or lost visibility (single pipeline for independent products).

Do This

  • Use a single pipeline with line items when products are typically sold together in the same buyer evaluation
  • Use separate pipelines when products have different buyer personas, sales cycles, or buying processes
  • Use a hybrid approach for mixed portfolios — one pipeline for the core platform, separate pipelines for add-ons with different buying motions

Avoid This

  • Default to one pipeline for everything because it is simpler — simplicity at the cost of accuracy produces bad analytics
  • Create a separate pipeline for every SKU — pipeline proliferation makes aggregate analysis impossible
  • Change the architecture mid-quarter — architectural changes should happen at quarter boundaries to maintain data continuity

The hybrid model is increasingly common: a primary pipeline for the core product with standard stages and conversion rates, plus satellite pipelines for expansion products with shorter stages and higher conversion rates. The primary pipeline drives new customer acquisition. The satellite pipelines drive expansion revenue within existing accounts. Each pipeline has its own conversion physics, but they share a common account-level view.