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.

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]

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.

## Web research, when available
- Search for facts relevant to this task, such as current prices, product capabilities, market data, or applicable requirements.
- Prefer primary sources. Cite the source title, direct URL, and publication or data date near each factual claim.
- Match source recency to the claim. Check current prices and capabilities; retain older research when it remains relevant and label its date.
- Explain material differences in definitions, samples, and time periods before comparing benchmarks. Report conflicting evidence and access limits.
- Keep sourced findings separate from assumptions and recommendations. Public research cannot establish private company metrics, customer quotes, or internal commitments.
- If browsing is unavailable or a fact cannot be verified, say so. Do not invent sources or imply a search was completed.

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.