设计与多媒体

co-selling-strategy

mbfinotti/partn…s-skills

Design the operating model for how direct sales and partner sellers collaborate on shared deals - deal registration policy (protection windows, approval SLA, rejection grounds), deal credit and attribution split (partner-sourced vs partner-influenced, comp neutrality), and channel rules of engagement between direct and partner sellers. Covers B2B co-sell motions at the policy level. Use whenever the user mentions co-selling, partner deal registration, deal credit splits, partner attribution policy, or reps and partners working the same account, even if they never say co-sell. Do NOT use for adjudicating a live contested deal - use mbfinotti/partnerships-skills@partner-channel-conflict instead.

  • 1.5万 次安装
  • 2 星标
  • 收录于

安装命令

npx skills add https://github.com/mbfinotti/partnerships-skills --skill co-selling-strategy

SKILL.md

Co-Selling Strategy

Define how direct sales and partner sellers collaborate on shared deals: the policy layer, never the deal-by-deal execution. This skill designs three artifacts as one coherent operating charter, and validates it with the user section by section:

  • Deal registration policy - how a partner formally claims an opportunity and what that claim grants.
  • Credit and attribution model - who gets counted and paid when a deal has more than one parent.
  • Rules of engagement - between direct and partner sellers.

Co-selling is a B2B discipline with no true B2C analogue. It presupposes named accounts, quota-carrying reps, a consultative sales cycle, and an opportunity record - none of which exist in a consumer transaction.

The consumer-side counterparts are trade marketing, co-op advertising funds, and shelf-placement/channel agreements: a different discipline with different mechanics, so never force-fit deal registration or comp neutrality onto retail partnerships. The one part that transfers to any context, B2B or B2C, is the governance discipline itself: unambiguous ownership rules, documented tiebreakers, published criteria.

Interview

Ask before proposing anything. One question per message; offer multiple-choice options when possible. Skip anything the user already answered. If your harness has persistent memory, check it for a previously approved charter first and confirm what changed instead of re-interviewing.