Partnerships and Ecosystems
Source-grounded pack with Design Partner Motion, Govern Partner Channels, and Model Partner Economics, plus 2 more.
Get this packGrounded in the complete Partnerships and Ecosystems series.
Open the pack, choose a workflow, and follow its setup and input instructions. You can also open each workflow below.
10 source essays · 5 usable skills · reviewed Jul 2026
Use this pack when
Choose this pack when the work touches Partnerships and Ecosystems and you need a bounded workflow with explicit inputs, a defined output, and human review gates.
Choose the job in front of you.
5 source-grounded skills. Load one workflow at a time.
Design Partner Motion
Use this workflow when a company must decide whether a partnership or ecosystem is justified, select the right referral, reseller, services, technology, marketplace, co-sell, OEM, or alliance motion, and prove one repeatable customer-value path before scaling.
Output specification
Return a partner motion design with customer_job, direct_counterfactual, motion_type_and_boundary, partner_and_customer_value, fit_evidence, internal_readiness, operating_path, trust_and_control, proof_motion, success_and_stop_thresholds, and recommendation.
Govern Partner Channels
Use this workflow when direct sales, partners, services, marketplaces, or co-sell teams overlap on accounts and need explicit ownership, credit, pricing, handoff, exception, and conflict-resolution rules tied to customer outcomes.
Output specification
Return a partner channel rules map with journey_roles, motion_rules, registration_and_credit, pricing_and_marketplace, co_sell_incentive, overlap_resolution, post_sale_ownership, exceptions, outcome_metrics, and review_cadence.
Model Partner Economics
Use this workflow when a partner program must align incentives, tiers, access, and vendor economics with repeated customer outcomes rather than signed partners, sourced leads, certifications, listings, or other shallow activity.
Output specification
Return a partner economics model with partner_segments, customer_value, partner_investment_and_return, vendor_full_economics, incentive_events, tier_and_access_logic, ai_role_shift, quality_thresholds, unit_metrics, and prune_or_deepen_decisions.
Operate Ecosystem Governance
Use this workflow when an ecosystem needs repeatable qualification, permissions, enablement, PartnerOps, integration lifecycle, quality enforcement, platform-dependency controls, or AI-era workflow governance across third parties.
Output specification
Return an ecosystem governance system with capability_permissions, partnerops_record, enablement_and_escalation, surface_lifecycle, quality_consequences, dependency_map, concentration_scenarios, redundancy_and_exit, ai_job_and_control_map, and governance_metrics.
Prioritize Integration Portfolio
Use this workflow when product and commercial teams must classify integration requests as table stakes, workflow depth, distribution, or both and decide what to build, maintain, sequence, measure, or retire.
Output specification
Return an integration portfolio with strategy_scope, integration_classification, evidence_and_score, job_specific_metrics, lifecycle_cost_and_risk, sequence, ownership, portfolio_decisions, and deprecation_plan.
Keep consequential decisions explicit.
These workflows structure analysis and artifacts; they do not authorize autonomous external, personnel, financial, legal, security, or other high-impact action.