Integration Partnership Go-to-Market

Integration partnerships

by LeadMagic · MIT license · ★ 62 on GitHub

Builds go-to-market for technology integration partnerships: partner selection, integration launch plans, marketplace listings, and co-selling motions. Use when the user is launching an integration, getting listed on a partner…

---
name: integration-partnerships
description: >-
  Builds go-to-market for technology integration partnerships: partner
  selection, integration launch plans, marketplace listings, and co-selling
  motions. Use when the user is launching an integration, getting listed on a
  partner marketplace, or turning an integration into pipeline. Triggers on:
  "integration partnership", "tech partnership", "API partnership", "marketplace
  listing".
license: MIT
compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
metadata:
  version: "1.0.0"
  author: LeadMagic
  category: partnerships
  tags: [partnerships, integrations, technology-partners, marketplace, API]
  frameworks:
    - "Bob Moore — Ecosystem-Led Growth"

Overview

Technology integration partnerships are the highest-ROI partnership type for B2B SaaS. When your product integrates with a platform your ICP already uses, discovery happens inside their workflow. This skill covers integration strategy, GTM launch, marketplace presence, and co-selling.

Manual install (npx, ZIP)

Claude Codenpx skills add LeadMagic/gtm-skills --skill integration-partnerships -g -a claude-code

Claude Code (degit)

npx degit LeadMagic/gtm-skills/skills/partnerships/integration-partnerships#main ~/.claude/skills/integration-partnerships

Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md7.9 KB

Read SKILL.md here

LeadMagic/main1 file shown

SKILL.md7.9 KB

Browse every file on GitHub↗

SKILL.md

Show the full text178 lines

Integration Partnerships

Overview

Authoritative Foundations

Bob Moore — Ecosystem-Led Growth — Prioritize integration partners by customer overlap and co-sell potential, not logo size.
Salesforce AppExchange and HubSpot App Marketplace — Listing requirements — Plan the security review, listing assets, and certification steps into the launch timeline.
Jay McBain (Canalys) — Partner ecosystem influence — Integrations extend the influence of every partner who recommends the tool; brief partner teams, not only customers.

When to Use

"Build integration partnerships"
"Launch a tech partnership"
"Get listed on a marketplace"
"Integration GTM strategy"

Step-by-Step Process

Phase 1: Integration Selection

Prioritize integrations by:

ICP overlap: % of your ICP using this platform (score 1-10)
Workflow adjacency: Does the integration happen where the user already is? (score 1-10)
Build complexity: Hours to build a meaningful v1 integration
Partnership openness: Does the platform have a partner program? marketplace?
Revenue potential: Will this integration drive new deals or expand existing?

Score >35: Build now. Score 25-35: Build soon. Score <25: Deprioritize.

Phase 2: Integration Design

Minimum Viable Integration (MVI): What's the one thing users need the integration to do? Ship that first. Don't build 10 features.
Integration depth levels:
- Level 1: Data sync (push/pull data between systems)
- Level 2: Workflow trigger (event in system A triggers action in system B)
- Level 3: Embedded experience (your UI inside their product or vice versa)
- Level 4: Co-created product (new product built on the integration)
Start at Level 1 or 2. Level 3-4 takes years of partnership maturity.

Phase 3: Partner GTM Launch

Integration announcement: Blog post (both companies), email blast (both), social promotion (both), Product Hunt if appropriate
Joint documentation: Setup guide with screenshots. < 5 minutes to activate.
Co-branded landing page: "How [Partner] + [You] work together" with use cases
Sales enablement: Both sales teams trained on the joint value prop. "If a prospect uses [Partner], mention our integration — it's often the reason they buy."
Customer migration path: For prospects using a competitor + [Partner]: "Switch to [You] and keep your [Partner] integration — here's the migration guide."

Phase 4: Marketplace Presence

App marketplace listing: High-quality listing with: logo, 1-line description, detailed description, screenshots, setup guide, reviews, support link
Category optimization: List in the most relevant categories. Monitor category ranking weekly — it drives discovery.
Reviews: Get 10+ reviews from mutual customers. Ask within 30 days of integration activation. Respond to every review.
Featured placement: Negotiate featured/app-of-the-week placement with the platform's partner team. Requires relationship building.

Phase 5: Co-Selling

Account mapping: Use Crossbeam/Reveal to identify shared accounts without sharing customer lists directly.
Co-selling play: "We noticed you use [Partner]. Our integration with them enables [specific value]. Want to see it?"
Partner-sourced deals: Formal deal registration so partners get credit for referring deals they identified through account mapping.
Joint QBRs: Quarterly with top integration partners. Review shared pipeline, plan joint campaigns, align on roadmap.

Output Format

Integration partnership plan with: partner prioritization matrix, MVI spec, GTM launch checklist, marketplace optimization, and co-selling playbook.

Quality Check

Before delivering, verify:

All required sections are complete
Output matches the user's stated need
Named frameworks are cited for key recommendations
No vague claims — every recommendation has a specific action
Deliverable is ready for operational use, not just conceptual

Common Pitfalls

Skipping research. Building output without understanding the specific context. Fix: always gather required inputs before producing deliverables.
Generic output. "Improve your process" without concrete steps. Fix: every recommendation must include a specific action, timeline, and owner.
Missing framework citations. Advice without named authorities. Fix: ground every recommendation in a cited framework from a recognized authority.

Implementation Depth

Use this section when the user asks for a finished asset, not a high-level explanation.

Diagnostic Questions

What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led?
Which ICP tier is the output for: small business, mid-market, enterprise, or mixed?
What proof is available today: customer stories, usage data, third-party validation, screenshots, or none?
What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow?
What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure?

Framework Application

Map the recommendation explicitly to the named frameworks in this skill:

Technology Partnership Framework: apply only the part that directly improves the requested deliverable.
Platform Ecosystem Strategy: apply only the part that directly improves the requested deliverable.
Crossbeam — Ecosystem-Led Growth: apply only the part that directly improves the requested deliverable.

Deliverable Standard

A strong output from this skill includes:

A crisp diagnosis of the current situation
A recommended path with tradeoffs, not a generic list
A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan
A measurement plan with leading and lagging indicators
Risks and edge cases called out before execution

Adaptation Rules

For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity.
For mid-market: include workflow ownership, handoffs, integrations, and enablement assets.
For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements.

Execution Artifacts

references/framework-notes.md — Named frameworks and reference tables
templates/output-template.md — Deliverable shell for agent output
scripts/check-output.py — Lightweight deliverable validator

partnership-strategy, co-marketing, leadmagic-integrations, api-enrichment, sales-enablement

1	---
2	name: integration-partnerships
3	description: >-
4	Builds go-to-market for technology integration partnerships: partner
5	selection, integration launch plans, marketplace listings, and co-selling
6	motions. Use when the user is launching an integration, getting listed on a
7	partner marketplace, or turning an integration into pipeline. Triggers on:
8	"integration partnership", "tech partnership", "API partnership", "marketplace
9	listing".
10	license: MIT
11	compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
12	metadata:
13	version: "1.0.0"
14	author: LeadMagic
15	category: partnerships
16	tags: [partnerships, integrations, technology-partners, marketplace, API]
17	frameworks:
18	- "Bob Moore — Ecosystem-Led Growth"
19	- "Salesforce AppExchange and HubSpot App Marketplace — Listing requirements"
20	- "Jay McBain (Canalys) — Partner ecosystem influence"
21	related_skills:
22	[
23	partnership-strategy,
24	co-marketing,
25	leadmagic-integrations,
26	api-enrichment,
27	sales-enablement,
28	]
29	---
30
31	# Integration Partnerships
32
33	## Overview
34
35	Technology integration partnerships are the highest-ROI partnership type for
36	B2B SaaS. When your product integrates with a platform your ICP already uses,
37	discovery happens inside their workflow. This skill covers integration strategy,
38	GTM launch, marketplace presence, and co-selling.
39
40	## Authoritative Foundations
41	- Bob Moore — Ecosystem-Led Growth — Prioritize integration partners by customer overlap and co-sell potential, not logo size.
42	- Salesforce AppExchange and HubSpot App Marketplace — Listing requirements — Plan the security review, listing assets, and certification steps into the launch timeline.
43	- Jay McBain (Canalys) — Partner ecosystem influence — Integrations extend the influence of every partner who recommends the tool; brief partner teams, not only customers.
44
45	## When to Use
46
47	- "Build integration partnerships"
48	- "Launch a tech partnership"
49	- "Get listed on a marketplace"
50	- "Integration GTM strategy"
51
52	## Step-by-Step Process
53
54	### Phase 1: Integration Selection
55
56	Prioritize integrations by:
57
58	- ICP overlap: % of your ICP using this platform (score 1-10)
59	- Workflow adjacency: Does the integration happen where the user already is?
60	(score 1-10)
61	- Build complexity: Hours to build a meaningful v1 integration
62	- Partnership openness: Does the platform have a partner program? marketplace?
63	- Revenue potential: Will this integration drive new deals or expand existing?
64
65	Score >35: Build now. Score 25-35: Build soon. Score <25: Deprioritize.
66
67	### Phase 2: Integration Design
68
69	- Minimum Viable Integration (MVI): What's the one thing users need the
70	integration to do? Ship that first. Don't build 10 features.
71	- Integration depth levels:
72	- Level 1: Data sync (push/pull data between systems)
73	- Level 2: Workflow trigger (event in system A triggers action in system B)
74	- Level 3: Embedded experience (your UI inside their product or vice versa)
75	- Level 4: Co-created product (new product built on the integration)
76	- Start at Level 1 or 2. Level 3-4 takes years of partnership maturity.
77
78	### Phase 3: Partner GTM Launch
79
80	- Integration announcement: Blog post (both companies), email blast (both),
81	social promotion (both), Product Hunt if appropriate
82	- Joint documentation: Setup guide with screenshots. < 5 minutes to activate.
83	- Co-branded landing page: "How [Partner] + [You] work together" with use cases
84	- Sales enablement: Both sales teams trained on the joint value prop.
85	"If a prospect uses [Partner], mention our integration — it's often the reason
86	they buy."
87	- Customer migration path: For prospects using a competitor + [Partner]:
88	"Switch to [You] and keep your [Partner] integration — here's the migration guide."
89
90	### Phase 4: Marketplace Presence
91
92	- App marketplace listing: High-quality listing with: logo, 1-line description,
93	detailed description, screenshots, setup guide, reviews, support link
94	- Category optimization: List in the most relevant categories. Monitor category
95	ranking weekly — it drives discovery.
96	- Reviews: Get 10+ reviews from mutual customers. Ask within 30 days of integration
97	activation. Respond to every review.
98	- Featured placement: Negotiate featured/app-of-the-week placement with the
99	platform's partner team. Requires relationship building.
100
101	### Phase 5: Co-Selling
102
103	- Account mapping: Use Crossbeam/Reveal to identify shared accounts without
104	sharing customer lists directly.
105	- Co-selling play: "We noticed you use [Partner]. Our integration with them
106	enables [specific value]. Want to see it?"
107	- Partner-sourced deals: Formal deal registration so partners get credit
108	for referring deals they identified through account mapping.
109	- Joint QBRs: Quarterly with top integration partners. Review shared pipeline,
110	plan joint campaigns, align on roadmap.
111
112	## Output Format
113
114	Integration partnership plan with: partner prioritization matrix, MVI spec,
115	GTM launch checklist, marketplace optimization, and co-selling playbook.
116
117	## Quality Check
118
119	Before delivering, verify:
120
121	- [ ] All required sections are complete
122	- [ ] Output matches the user's stated need
123	- [ ] Named frameworks are cited for key recommendations
124	- [ ] No vague claims — every recommendation has a specific action
125	- [ ] Deliverable is ready for operational use, not just conceptual
126
127	## Common Pitfalls
128
129	1. Skipping research. Building output without understanding the specific context. Fix: always gather required inputs before producing deliverables.
130	2. Generic output. "Improve your process" without concrete steps. Fix: every recommendation must include a specific action, timeline, and owner.
131	3. Missing framework citations. Advice without named authorities. Fix: ground every recommendation in a cited framework from a recognized authority.
132
133	## Implementation Depth
134
135	Use this section when the user asks for a finished asset, not a high-level explanation.
136
137	### Diagnostic Questions
138
139	1. What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led?
140	2. Which ICP tier is the output for: small business, mid-market, enterprise, or mixed?
141	3. What proof is available today: customer stories, usage data, third-party validation, screenshots, or none?
142	4. What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow?
143	5. What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure?
144
145	### Framework Application
146
147	Map the recommendation explicitly to the named frameworks in this skill:
148
149	- Technology Partnership Framework: apply only the part that directly improves the requested deliverable.
150	- Platform Ecosystem Strategy: apply only the part that directly improves the requested deliverable.
151	- Crossbeam — Ecosystem-Led Growth: apply only the part that directly improves the requested deliverable.
152
153	### Deliverable Standard
154
155	A strong output from this skill includes:
156
157	- A crisp diagnosis of the current situation
158	- A recommended path with tradeoffs, not a generic list
159	- A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan
160	- A measurement plan with leading and lagging indicators
161	- Risks and edge cases called out before execution
162
163	### Adaptation Rules
164
165	- For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity.
166	- For mid-market: include workflow ownership, handoffs, integrations, and enablement assets.
167	- For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements.
168
169	## Execution Artifacts
170
171	- `references/framework-notes.md` — Named frameworks and reference tables
172	- `templates/output-template.md` — Deliverable shell for agent output
173	- `scripts/check-output.py` — Lightweight deliverable validator
174
175	## Related Skills
176
177	- partnership-strategy, co-marketing, leadmagic-integrations, api-enrichment, sales-enablement
178