Partner Business Development and Pipeline Cockpit Blueprint
Author a functional brief for a partner revenue pipeline, origination credit, and pursuit velocity analytics cockpit.
Use this template when designing a partner-level CRM and commercial performance dashboard to evaluate pursuit conversion, cross-practice selling, and pipeline coverage against annual origination targets.
Role: Head of Revenue Analytics and Partner Governance with extensive background in partnership performance management for elite advisory firms.
Context
- Industry verticals: {{practice_verticals}}
- Pipeline stages: {{crm_pipeline_stages}}
- Credit governance: {{origination_credit_rules}}
- Conversion benchmarks: {{pursuit_conversion_targets}}
- Update frequency: {{refresh_frequency_sla}}
- Review body: {{partner_governance_council}}
Task
Produce an analytics cockpit design brief that provides partner leadership with clear visibility into origination credits, pipeline velocity, pursuit win-loss rates, and cross-practice expansion opportunities.
Method
- Harmonize stage-gate definitions across {{crm_pipeline_stages}} to standardize weighted pipeline value calculations.
- Translate {{origination_credit_rules}} into multi-party attribution logic supporting split origination and co-selling credits.
- Establish cohort analysis to track deal progression speed against target benchmarks defined in {{pursuit_conversion_targets}}.
- Build comparative performance quadrants mapping individual partner origination volume against proposal conversion efficiency.
- Design whitespace matrix visualizations highlighting cross-selling gaps across {{practice_verticals}}.
- Implement stage-duration tracking to flag stalled opportunities exceeding expected days-in-stage.
- Detail executive summary views prepared specifically for the {{partner_governance_council}}.
Constraints
- MUST strictly enforce multi-partner credit attribution without double-counting pipeline total addressable value.
- MUST NOT display confidential deal notes or sensitive client fee negotiations to unauthorized practice members.
- All conversion metrics must be segmented by both lead partner and originating practice vertical.
- Latency and data pipeline refresh must strictly satisfy the {{refresh_frequency_sla}}.
Output format
Present a structured brief formatted as follows:
- Strategic Context & Cockpit Purpose (under 200 words)
- Pipeline & Origination Metric Specifications (table with Metric Name, Source Stage, Calculation, and Attribution Rule)
- Visualization Architecture (Module 1: Partner Scorecard, Module 2: Pursuit Velocity & Stage Health, Module 3: White Space Matrix)
- Partner Governance Data Rules and Dispute Resolution Logic
- Council Reporting Deliverable Template (Summary pack layout)
Self-review
- Verify that credit attribution avoids inflating total aggregate pipeline revenue.
- Confirm that all stages in {{crm_pipeline_stages}} are mapped with conversion criteria.
- Ensure reporting aligns with governance reporting needs for {{partner_governance_council}}.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.