# Design partner program plan · [Product or capability] · [Dates] **Owner:** [PM] **Executive sponsor:** [Name] **Program length:** [one to three quarters] ## Learning goals 1. [What we must learn about workflow] 2. [What we must learn about adoption and approval] 3. [What we must learn about pricing or packaging] ## Selection criteria - Matches target segment: [criteria] - Willing to share data: [what, under which agreement] - Executive sponsor on their side: [required] - Mix: [include at least one partner unlike the most enthusiastic one] - Number of partners: [typically five to eight] ## Commitments | Partner commits to | We commit to | |---|---| | Feedback sessions every [n] weeks | Early access to builds | | Usage and outcome data shared | Named PM contact | | [Reference or case study if successful] | [Pricing protection for first term] | | [Security review in parallel] | [Roadmap visibility under NDA] | ## Rules for what ships - A partner-requested feature ships only if [at least n] partners need it. - Single-partner requests go to a separate log, reviewed at program end. - No custom branches or one-off integrations. ## Cadence and evidence - Weekly: synthesis of feedback, every theme traced to partners - Monthly: progress against learning goals - Thresholds that end the program early (positive or negative): [list] ## Exit - End date: [date] - Conversion terms to standard commercial contract: [summary] - What happens to partners who don't convert: [plan] - Data handling at exit: [return or delete]