Purpose
Turn scattered customer stack data and ecosystem intuition into a prioritized, scored list of integration partners worth pursuing — separating high-leverage integrations that drive retention and expansion from low-value logo-collecting. Eliminates the "which integration do we build next" debate with a defensible qualification framework.
When to Use
Invoke this skill when the user asks to:
- Build or prioritize an integration roadmap
- Find integration partners for a SaaS platform or product
- Identify ecosystem gaps competitors have filled that you haven't
- Decide which integration to build or launch next
- Evaluate a specific integration idea against alternatives
- Prepare a partnership target list for a business review or planning cycle
Inputs Required
Before starting, collect:
- Product category: What the platform does and where it sits in the customer's workflow
- Target customer profile: Company size, industry, and role of the primary user
- Customer stack data: Tools customers already use alongside the product (from surveys, sales calls, integrations analytics, or known patterns)
- Existing integrations: What the platform already connects to today
- Strategic goal: Whether the priority is retention, expansion/upsell, new-customer acquisition, or distribution/co-selling
- Build constraints: Engineering capacity, preferred integration method (native / API / iPaaS like Zapier/Make), and rough timeline
- Known competitor integrations: Any competitors whose integration marketplace can be referenced
If customer stack data is thin, infer the likely stack from the product category and target profile, and flag those as assumptions rather than observed data.
Instructions
Step 1: Generate 25 Partner Candidates Across 5 Discovery Lenses
For each candidate include: partner name, category, why it surfaced, and the specific customer job the integration serves.
Lens 1 — Customer Stack Overlap (7 candidates) Tools that appear most frequently in the customer's existing stack. Highest signal — these are already in use and adjacent to the workflow.
- Prioritize tools where data flows naturally to or from the platform (a shared object like a contact, order, ticket, or document)
- Rank by estimated prevalence in the customer base
- Note whether the integration removes a manual copy-paste step (strongest retention driver)
Lens 2 — Ecosystem Gaps (5 candidates) Categories where customers clearly need a connection but no strong option exists yet — either the platform lacks it or existing integrations are weak.
- Identify the workflow break: where does a customer currently leave the product to get a job done?
- Favor gaps that recur across multiple customer segments, not one-off requests
Lens 3 — Competitor Integration Parity (5 candidates) Integrations competitors offer that the platform lacks, creating a switching or evaluation disadvantage.
- Flag any integration that shows up on a competitor's marketplace but not yours as a parity risk
- Distinguish "table-stakes parity" (must-have to compete) from "differentiation" (a competitor's bet you may skip)
Lens 4 — Adjacent Workflow Tools (5 candidates) Tools one step upstream or downstream in the customer's process — where the platform could capture more of the workflow.
- Map the end-to-end customer job and identify the handoff points before and after the product
- These integrations expand the platform's footprint and increase stickiness
Lens 5 — Strategic Distribution Plays (3 candidates) Larger platforms with app marketplaces or co-sell motions that could drive new customer acquisition, not just utility.
- Prioritize marketplaces with high traffic in the target category
- Note the distribution mechanic (marketplace listing, co-marketing, embedded install, referral)
Step 2: Score Each Candidate on a Qualification Matrix
Rate all 25 candidates 1–5 on each dimension:
- Customer demand: How many customers want or would use it
- Strategic fit: Alignment with the stated strategic goal (retention / expansion / acquisition / distribution)
- Build effort (inverted): Lower effort scores higher — factor in API quality, docs, and integration method
- Revenue impact: Effect on retention, expansion, or new logos
- Partner willingness: Likelihood the partner will co-market or reciprocate
Compute a weighted total (weight the two dimensions most tied to the stated strategic goal at 2x). Present as a table sorted by total score.
Step 3: Build the Top 8 Shortlist
For each of the top 8:
- Integration thesis: 2 sentences on why this partner, tied to the customer job and strategic goal
- Recommended integration depth: Native / API / iPaaS — with reasoning based on effort vs. value
- Key data flow: The specific objects or actions that sync
- Outreach angle: One sentence on how to approach the partner and what's in it for them
- Effort estimate: T-shirt size (S / M / L) with the main technical dependency
Step 4: Sequencing Recommendation
Group the top 8 into three waves — Build Now (high value, low effort), Build Next (high value, higher effort), and Watch/Partner-Led (strategic but dependent on partner willingness or demand signal). Name the single first integration to ship and why.
Output Format
- Structure: 5 discovery lenses as labeled lists → scoring matrix as a table → top 8 shortlist as structured bullets → sequencing waves
- Length: 1,100–1,500 words
- Format: Mixed — lists for candidates, a table for the scoring matrix, structured bullets for the shortlist
- Sections: Candidate discovery (5 lenses) → Qualification matrix → Top 8 shortlist → Sequencing recommendation
- Tone: Partnerships strategist — analytical and decisive, oriented toward what to build and who to call, not exhaustive market survey
Quality Checklist
Before delivering output, verify:
- [ ] All 25 candidates are generated with the correct count per lens (7, 5, 5, 5, 3)
- [ ] Every candidate names the specific customer job the integration serves — not just the tool name
- [ ] The scoring matrix rates all 25 candidates on all 5 dimensions with a computed total
- [ ] Weighting reflects the stated strategic goal (the two aligned dimensions are 2x)
- [ ] Each of the top 8 includes a recommended integration depth with reasoning — not just "build it"
- [ ] A single first integration is named in the sequencing recommendation, not left open
Notes
- The strongest integration signal is a workflow break where customers currently copy-paste between tools — those integrations drive measurable retention
- Distribution plays (Lens 5) are tempting but slow; treat marketplace listings as acquisition bets, not utility wins, and don't let them crowd out high-demand stack-overlap integrations
- Build effort is routinely underestimated — a partner with weak API docs can turn an "S" into an "L"; when uncertain, size up and note the dependency
- If customer stack data is genuinely unavailable, recommend instrumenting integration-intent signals (survey question, "request an integration" button) before committing engineering time
How to use this skill
This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.
Installing in Claude Code:
~/.claude/skills/<folder-name>/SKILL.md— auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)<your-project>/.claude/skills/<folder-name>/SKILL.md— auto-loads only when working in that project (recommended for project-specific skills)
Restart Claude Code or open a new session to register.
Using in Claude.ai, ChatGPT, Gemini, or other AI tools:
- Drag this file into a new chat, or copy and paste its contents
- Send your task or request as your next message — the AI will apply the skill where it fits
For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills