DG-301e · Module 3

Partner Portfolio Management

3 min read

As your partner program grows beyond two or three partnerships, you need portfolio management — the discipline of evaluating, tiering, and resource-allocating across multiple partnerships simultaneously. Like event portfolio management, partner portfolio management applies kill/scale/maintain logic: partnerships producing pipeline get more investment, partnerships that are not get reviewed, and new partnerships are tested at minimum viable commitment.

  1. Partner Scorecard Score every partner quarterly on four metrics: leads sent (introduction volume), leads converted (introduction quality), pipeline generated (dollar value sourced), and engagement consistency (activity between reviews, not just during them). The scorecard ranks partnerships and identifies which ones deserve more investment and which need intervention.
  2. Tiered Resource Allocation Tier partners by pipeline contribution: tier one gets dedicated partner manager time, co-marketing budget, and joint account targeting. Tier two gets quarterly reviews and co-marketing inclusion. Tier three gets self-service enablement and annual review. Resources follow contribution, not relationship seniority.
  3. Annual Portfolio Review Once per year, review the full portfolio. Cut partnerships that produced zero pipeline in the last twelve months despite enablement investment. Promote partnerships that exceeded expectations. Add new partners that fill gaps in your ICP coverage or solution adjacency. The portfolio should evolve with your market position.

Do This

  • Score every partner quarterly on leads, conversion, pipeline, and engagement consistency
  • Allocate resources proportionally to pipeline contribution, not to relationship seniority
  • Conduct annual portfolio reviews that cut underperformers and add strategically aligned new partners

Avoid This

  • Treat all partners equally regardless of pipeline contribution
  • Maintain partnerships indefinitely because "the relationship is important" when pipeline is zero
  • Add new partners without evaluating capacity to manage them effectively