home / skills / gtmagents / gtm-agents / partner-integration-kit

This skill helps coordinate multi-party manufacturing integrations by defining partner matrix, governance, and enablement to accelerate co-delivery and value.

npx playbooks add skill gtmagents/gtm-agents --skill partner-integration-kit

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.4 KB
---
name: partner-integration-kit
description: Toolkit for coordinating system integrators, OEM partners, and service
  vendors in manufacturing pursuits.
---

# Partner Integration Kit Skill

## When to Use
- Pursuits requiring multi-party delivery (automation, MES, IoT, safety systems).
- Onboarding new partners to co-sell or co-deliver solutions.
- Preparing integration readiness reviews or partner governance cadence.

## Framework
1. **Partner Matrix** – catalog roles (SI, OEM, distributor), competencies, certifications, territories.
2. **Integration Requirements** – data flows, protocols, safety/regulatory requirements, testing environments.
3. **Joint Value Narrative** – messaging pillars, proof points, and differentiation with partners.
4. **Enablement & Governance** – training plans, escalation matrix, release/change management.
5. **Performance Dashboard** – pipeline contribution, stage progression, delivery KPIs, CSAT.

## Templates
- Partner kickoff deck (roles, deliverables, SLAs).
- Integration readiness checklist (systems, documentation, test cases).
- Joint success plan with KPIs, review cadence, risk tracker.

## Tips
- Capture NDAs, data-sharing agreements, and export control docs in the same workspace.
- Provide sandbox/demo environments to speed partner validations.
- Pair with `build-technical-bid-plan` and `run-deal-health-review` outputs.

---

Overview

This skill is a partner integration toolkit for coordinating system integrators, OEM partners, and service vendors across complex manufacturing pursuits. It bundles repeatable frameworks, templates, and checklists to accelerate co-selling, co-delivery, and integration readiness. The focus is on practical governance, technical requirements, and measurable joint outcomes.

How this skill works

The skill inspects the pursuit structure and generates a partner matrix that catalogs roles, competencies, certifications, and territories. It maps integration requirements — data flows, protocols, safety and regulatory constraints — and produces readiness artifacts like checklists and test cases. It also creates joint value narratives, enablement plans, governance elements, and a performance dashboard to track pipeline and delivery KPIs.

When to use it

  • Pursuits that require multi-party delivery (automation, MES, IoT, safety systems).
  • Onboarding new partners for co-sell or co-deliver arrangements.
  • Preparing integration readiness reviews and partner governance meetings.
  • Defining contractual and data-sharing boundaries before technical work begins.
  • Coordinating release/change management and cross-party escalations.

Best practices

  • Start with a partner matrix to clarify ownership, competencies, and geographic scope.
  • Capture NDAs, data-sharing, and export-control documents in a single workspace.
  • Provide sandbox/demo environments to accelerate partner validation cycles.
  • Use a standardized integration readiness checklist to reduce rework in testing.
  • Establish a regular governance cadence and an escalation matrix up front.

Example use cases

  • Running a partner kickoff with roles, deliverables, SLAs, and a joint timetable.
  • Building an integration readiness pack with system documentation and test cases.
  • Creating a joint success plan with KPIs, review cadence, and a risk tracker.
  • Coordinating multi-vendor field service and warranty responsibilities.
  • Assessing pipeline contribution and delivery performance across partners.

FAQ

Does the kit include templates for governance and enablement?

Yes — it provides partner kickoff decks, enablement plans, training outlines, and release/change management templates.

How does it handle technical interfacing and testing?

It defines integration requirements, data flows, protocols, and recommended test environments, and generates integration readiness checklists and test case outlines.