跳到正文
cccskills
免费在 GitHub 公开

partner-and-channel-co-sell

Use when a deal moves with a partner: software vendor, channel, distributor, or consulting partner, from joint plan to joint close.

中文简介正在准备中。当前显示原文说明。

实测评分 未实测

查看安装方法

包含的文件(1)

  • SKILL.md1.9 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Partner and channel co-sell

Use this when a deal moves with a partner: an independent software vendor (ISV), a channel partner, a distributor, or a consulting partner. Start from the partner name and type, the joint accounts or deals, what each side brings, and any existing partner agreement terms.

The joint play

Write the joint play in one schema both sides can run: trigger, ICP overlap, value story, land motion, owners one per side, target account list, and exit criteria. Name the exec sponsor on both sides up top.

Split the work

Split the work plainly: who sources, who technical-wins, who owns paper, who owns the renewal. A split nobody agreed to is a draft, never presented as agreed.

Standup and joint metrics

Run the partner standup like the deal-team pulse: moved, stalled, one action per side, most-stuck-first. Grade the joint metrics (sourced pipe, co-sell win rate, partner-attached revenue) from ledger numbers only.

Partner drafts

Draft the partner-facing messages — the ask, the intro, the escalation — as text they approve first. Never commit the partner's resources or your own discounts inside a draft.

What you hand back

The joint co-sell play with owners and joint metrics, plus the staged partner drafts, saved to file. Show the play and the read in chat, take one round of edits, then save.

Fallbacks

A partner with no named sponsor means you name the gap and draft the sponsor ask first. No shared CRM view means you reconcile from both sides' exports and label each number's source. Anything partner-facing waits for your yes.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Write ad variants that each test one idea, within platform limits and supported claims.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.

中文简介正在准备中。当前显示原文说明。

Significant-Gravitas/skills-catalog22026年10月22日 更新

查看 Significant-Gravitas 的全部技能

报告此技能的问题