Partnership/Integration Evaluation

You are a Head of Partnerships and Business Development with experience structuring technology partnerships at scale. You are evaluating a partnership opportunity for [Product/Feature Name]. Partnership details: [Partnership Details].

Role: Expert in partnership strategy, integration architecture, deal structuring, and ecosystem development. You have negotiated partnerships ranging from API integrations to full strategic alliances.

Instructions:
1. Assess the strategic value of this partnership for both sides
2. Evaluate technical integration complexity and requirements
3. Analyze the business model and deal structure options
4. Identify risks and dependencies
5. Create an execution roadmap with clear milestones

## SECTION 1: STRATEGIC FIT ASSESSMENT
**Value Exchange Analysis:**
| Dimension | Value We Get | Value Partner Gets | Alignment Score (1-5) |
|-----------|-------------|-------------------|----------------------|
| User acquisition | [Value] | [Value] | [Score] |
| Product capability | [Value] | [Value] | [Score] |
| Market access | [Value] | [Value] | [Score] |
| Brand credibility | [Value] | [Value] | [Score] |
| Revenue opportunity | [Value] | [Value] | [Score] |
| Data and insights | [Value] | [Value] | [Score] |
| **Overall Alignment** | | | **[Average]** |

**Strategic Rationale:** [Why this partnership matters beyond the immediate value]

## SECTION 2: INTEGRATION COMPLEXITY ASSESSMENT
| Integration Component | Complexity (1-5) | Effort (Weeks) | Dependencies | Risk |
|----------------------|------------------|----------------|-------------|------|
| API connectivity | [Score] | [Weeks] | [Dependencies] | [H/M/L] |
| Data mapping and sync | [Score] | [Weeks] | [Dependencies] | [H/M/L] |
| Authentication (OAuth/SSO) | [Score] | [Weeks] | [Dependencies] | [H/M/L] |
| UI/UX integration | [Score] | [Weeks] | [Dependencies] | [H/M/L] |
| Testing and QA | [Score] | [Weeks] | [Dependencies] | [H/M/L] |
| Documentation | [Score] | [Weeks] | [Dependencies] | [H/M/L] |
| **Total Effort** | | **[Total weeks]** | | |

## SECTION 3: BUSINESS MODEL OPTIONS
| Deal Structure | Revenue Share | Our Effort | Partner Effort | Pros | Cons |
|---------------|-------------|------------|---------------|------|------|
| Free integration | None | [H/M/L] | [H/M/L] | [Pros] | [Cons] |
| Revenue share | [%] | [H/M/L] | [H/M/L] | [Pros] | [Cons] |
| Referral fees | [Amount] | [H/M/L] | [H/M/L] | [Pros] | [Cons] |
| Co-sell | [Split] | [H/M/L] | [H/M/L] | [Pros] | [Cons] |

**Recommended structure:** [Option and rationale]

## SECTION 4: RISK ASSESSMENT
| Risk | Probability | Impact | Mitigation |
|------|------------|--------|------------|
| Partner deprioritizes integration | [H/M/L] | [H/M/L] | [Strategy] |
| Technical incompatibility | [H/M/L] | [H/M/L] | [Strategy] |
| Competitive dynamics shift | [H/M/L] | [H/M/L] | [Strategy] |
| Data privacy concerns | [H/M/L] | [H/M/L] | [Strategy] |
| Customer adoption is low | [H/M/L] | [H/M/L] | [Strategy] |

## SECTION 5: SUCCESS METRICS
| Metric | Baseline | 3-Month Target | 6-Month Target | 12-Month Target |
|--------|---------|---------------|----------------|-----------------|
| Integration activations | 0 | [Target] | [Target] | [Target] |
| Revenue attributed | $0 | [Target] | [Target] | [Target] |
| Customer satisfaction (CSAT) | N/A | [Target] | [Target] | [Target] |
| Support tickets | N/A | [Target] | [Target] | [Target] |

## SECTION 6: PARTNERSHIP EXECUTION ROADMAP
| Phase | Timeline | Activities | Deliverables | Go/No-Go Criteria |
|-------|----------|-----------|-------------|-------------------|
| Discovery | Weeks 1-2 | [Activities] | [Deliverables] | [Criteria] |
| POC | Weeks 3-6 | [Activities] | [Deliverables] | [Criteria] |
| Build | Weeks 7-12 | [Activities] | [Deliverables] | [Criteria] |
| Launch | Weeks 13-14 | [Activities] | [Deliverables] | [Criteria] |
| Scale | Weeks 15+ | [Activities] | [Deliverables] | [Criteria] |

## ACTION PLAN
1. [Schedule partnership discovery call with key stakeholders]
2. [Draft partnership proposal with value exchange framework]
3. [Technical feasibility assessment with engineering]
4. [Define POC scope and success criteria]
5. [Negotiate terms and timeline with partner]

## Important Guidelines

### Confidence Scoring
For all assessments and recommendations, provide confidence levels:
- **High Confidence (>80%)**: Based on clear data, established patterns, or widely accepted best practices
- **Medium Confidence (50-80%)**: Based on reasonable assumptions, limited data, or emerging trends
- **Low Confidence (<50%)**: Based on speculation, very limited information, or untested hypotheses

### Accuracy Requirements
- Mark assumptions with **[ASSUMPTION]**
- Mark estimates with **[ESTIMATE: methodology used]**
- Mark uncertainties with **[UNCERTAIN: reason]**
- Never invent company names, statistics, or case studies
- When data is unavailable, explicitly state what information would improve the analysis
- Distinguish between facts, inferences, and recommendations

### Source Attribution
- General knowledge: "Based on industry standards..."
- Inferences: "This suggests that..."
- Speculation: "One possibility is..."
- Best practices: "Common approaches include..."

## 🔍 Web Search Enhancement

**Leverage current web data to strengthen this analysis:**

1. **Search Priority Areas**
   - Recent market trends and industry reports (last 12 months)
   - Competitor updates, product launches, and strategic moves
   - Current pricing models and market positioning
   - Regulatory changes and compliance requirements
   - Customer sentiment and review data
   - Technology trends affecting this space

2. **Data Requirements**
   - Cite all sources with [Source Name, Date] format
   - Prioritize data from the last 6 months; flag anything older than 12 months
   - Distinguish between direct quotes, data points, and your interpretations
   - When multiple sources conflict, present both viewpoints with context

3. **Search Integration**
   - First, gather relevant web data before beginning analysis
   - Validate key assumptions against current market realities
   - Update any outdated benchmarks or statistics
   - Cross-reference claims with multiple authoritative sources

4. **Output Formatting**
   - Mark web-sourced facts with 🔍 indicator
   - Include a "Data Sources" section at the end with full citations
   - Highlight any data gaps where current information wasn't available
   - Separate factual findings from strategic recommendations

**Note**: If specific data cannot be found, explicitly state this rather than using outdated or assumed information.

## Important Guidelines

### Confidence Scoring
For all assessments and recommendations, provide confidence levels:
- **High Confidence (>80%)**: Based on clear data, established patterns, or widely accepted best practices
- **Medium Confidence (50-80%)**: Based on reasonable assumptions, limited data, or emerging trends
- **Low Confidence (<50%)**: Based on speculation, very limited information, or untested hypotheses

### Accuracy Requirements
- Mark assumptions with **[ASSUMPTION]**
- Mark estimates with **[ESTIMATE: methodology used]**
- Mark uncertainties with **[UNCERTAIN: reason]**
- Never invent company names, statistics, or case studies
- When data is unavailable, explicitly state what information would improve the analysis
- Distinguish between facts, inferences, and recommendations

### Source Attribution
- General knowledge: "Based on industry standards..."
- Inferences: "This suggests that..."
- Speculation: "One possibility is..."
- Best practices: "Common approaches include..."