Agent Skillscbrock84/headcount › strategic-alliances

strategic-alliances

GitHub

指导如何评估、构建和谈判战略联盟,涵盖伙伴与自建/购买的决策、动机对齐、关键条款设计及合作运营诊断。

plugins/corporate-strategy/skills/strategic-alliances/SKILL.md cbrock84/headcount

Trigger Scenarios

评估或建立技术集成、渠道或合资等战略伙伴关系 决定是合作伙伴还是自行开发功能 谈判联盟的商业条款 诊断已签署但未产生价值的合作关系

Install

npx skills add cbrock84/headcount --skill strategic-alliances -g -y
More Options

Non-standard path

npx skills add https://github.com/cbrock84/headcount/tree/main/plugins/corporate-strategy/skills/strategic-alliances -g -y

Use without installing

npx skills use cbrock84/headcount@strategic-alliances

指定 Agent (Claude Code)

npx skills add cbrock84/headcount --skill strategic-alliances -a claude-code -g -y

安装 repo 全部 skill

npx skills add cbrock84/headcount --all -g -y

预览 repo 内 skill

npx skills add cbrock84/headcount --list

SKILL.md

Frontmatter
{
    "name": "strategic-alliances",
    "description": "Structures partnerships that change what the business can do — technology integrations, channel and reseller arrangements, joint ventures, and OEM relationships. Use this to evaluate or structure a strategic partnership, decide between partnering and building, negotiate commercial terms of an alliance, or diagnose a partnership that is signed but not producing. For audience-borrowing partnerships, use `marketing:partnership-marketing`."
}

Strategic alliances

Distinct from marketing partnerships. Those borrow an audience; these change what the business can do or where it can sell.

Partner, build, or buy

Partner when the capability is genuinely outside your core, the partner is materially better at it, and the arrangement can be unwound. Build when it is core, or when depending on someone else creates unacceptable exposure. Buy when you need control and speed and the thesis holds.

The question that decides it: what happens if this partner becomes a competitor, is acquired by one, or simply loses interest? If the answer is existential, do not partner — that is a build or buy decision wearing a cheaper price tag.

Structure by what each side actually wants

Partnerships fail on asymmetry of motivation more than on terms. Before structuring, establish what the partner gets, whether it is material to them, and who inside their organization is accountable for it.

A partnership that is strategically important to you and a rounding error to them will not be executed, whatever was signed. Being the small partner is workable — being the small and uninteresting partner is not.

Terms that determine whether it works

  • Exclusivity — expensive, occasionally worth it, and always time-boxed. Perpetual exclusivity given away early is a recurring regret.
  • Economics — who books revenue, on what split, and what happens to it if volume grows tenfold.
  • Roadmap commitments — what each side will build and by when, with a remedy if they do not.
  • Data — what flows where, under what basis, and what happens to it at termination.
  • Customer ownership — who holds the relationship, and who may market to them afterward. Most disputed, most often left vague.
  • Termination and transition — notice, and what continues for customers mid-contract. Negotiate the exit while everyone is friendly, because it will not be negotiable later.

Making it produce

Signed is not launched. Partnerships need a named owner on each side, a joint plan with dates, and a regular review that either side can bring problems to.

The characteristic failure: a signed agreement, a press release, and no operational plan. Six months later both sides believe the other did not deliver, and neither is wrong.

Enable the partner properly. Their team needs to know what to say and when to bring you in, and they will not learn it from the contract.

Diagnosing a stalled partnership

Almost always one of: no accountable owner on one side, misaligned incentives at the level of the people doing the work, a promised technical dependency that never shipped, or a partner whose strategy moved.

Say it plainly and early. Partnerships die quietly for a year before anyone admits it, and that year is the cost.

Never

  • Sign a partnership without naming what each side is measured on.
  • Announce before the joint work has a named owner on both sides.
  • Let a partnership run past its review date on goodwill.
  • Grant exclusivity without a performance floor that ends it.

Version History

  • d58a7ee Current 2026-09-02 21:04

Same Skill Collection

plugins/corporate-strategy/skills/chief-strategy-officer/SKILL.md
plugins/corporate-strategy/skills/market-entry/SKILL.md
plugins/corporate-strategy/skills/mergers-and-acquisitions/SKILL.md
plugins/corporate-strategy/skills/portfolio-strategy/SKILL.md
plugins/corporate-strategy/skills/scenario-planning/SKILL.md
plugins/customer-experience/skills/chief-customer-officer/SKILL.md
plugins/customer-experience/skills/customer-onboarding-and-implementation/SKILL.md
plugins/customer-experience/skills/customer-success-management/SKILL.md
plugins/customer-experience/skills/escalation-management/SKILL.md
plugins/customer-experience/skills/self-service-and-knowledge/SKILL.md
plugins/customer-experience/skills/support-operations/SKILL.md
plugins/customer-experience/skills/voice-of-customer/SKILL.md
plugins/data-analytics/skills/ai-ml-governance/SKILL.md
plugins/data-analytics/skills/business-intelligence/SKILL.md
plugins/data-analytics/skills/chief-data-officer/SKILL.md
plugins/data-analytics/skills/data-engineering/SKILL.md
plugins/data-analytics/skills/data-governance/SKILL.md
plugins/data-analytics/skills/data-modeling/SKILL.md
plugins/demand-generation/skills/ai-search-optimization/SKILL.md
plugins/demand-generation/skills/app-store-optimization/SKILL.md
plugins/demand-generation/skills/experimentation/SKILL.md
plugins/demand-generation/skills/landing-page-cro-expert/SKILL.md
plugins/demand-generation/skills/lead-capture/SKILL.md
plugins/demand-generation/skills/lifecycle-messaging/SKILL.md
plugins/demand-generation/skills/listing-distribution/SKILL.md
plugins/demand-generation/skills/marketing-analytics/SKILL.md
plugins/demand-generation/skills/paid-advertising/SKILL.md
plugins/demand-generation/skills/programmatic-seo/SKILL.md
plugins/demand-generation/skills/seo-strategy/SKILL.md
plugins/executive/skills/ai-research-analyst/SKILL.md
plugins/executive/skills/business-growth-consultant/SKILL.md
plugins/executive/skills/chief-executive/SKILL.md
plugins/executive/skills/fundraising-and-investor-relations/SKILL.md
plugins/executive/skills/saas-idea-validator/SKILL.md
plugins/finance/skills/budgeting-and-forecasting/SKILL.md
plugins/finance/skills/capital-allocation/SKILL.md
plugins/finance/skills/capital-structure-and-covenants/SKILL.md
plugins/finance/skills/cost-accounting/SKILL.md
plugins/finance/skills/financial-modeling/SKILL.md
plugins/finance/skills/financial-reporting-and-close/SKILL.md
plugins/finance/skills/financial-statement-analysis/SKILL.md
plugins/finance/skills/internal-controls-and-audit/SKILL.md
plugins/finance/skills/revenue-recognition/SKILL.md
plugins/finance/skills/tax/SKILL.md
plugins/finance/skills/treasury-and-liquidity/SKILL.md
plugins/finance/skills/unit-economics/SKILL.md
plugins/it-operations/skills/backup-and-recovery/SKILL.md
plugins/it-operations/skills/chief-information-officer/SKILL.md
plugins/it-operations/skills/cloud-administration/SKILL.md

Metadata

Files
0
Version
d58a7ee
Hash
46c91d2a
Indexed
2026-09-02 21:04

trang chủ - Wiki
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-09-02 22:04
浙ICP备14020137号-1 $bản đồ khách truy cập$