build-co-sell-playbook — Claude Code command: what it does
build-co-sell-playbook is a Claude Code command that builds a partner co-sell playbook with engagement cadences, enablement materials, and deal attribution rules.
Apache-2.0 ★ 450 updated 2026-04-03
.claude/commands/build-co-sell-playbook.mdWhat build-co-sell-playbook does
Command runs five stages: discovery of joint value prop and ICP overlap, play design with responsibilities and approvals, attribution setup with CRM tracking and escalation paths, enablement kit assembly (battlecard, talk track, ROI calculator), and KPI definition with reporting cadence. Output includes playbook PDF with owners and SLAs, enablement bundle, and dashboard spec with attribution requirements.
Command invokes partner-co-sell-lead agent for pipeline governance, partner-program-architect for onboarding hooks, joint-solution-blueprint skill for solution architecture, and co-marketing-governance skill for awareness workflows. Parameters set partner name, motion type (enterprise, midmarket, channel, marketplace, MSSP), incentives (spiff, rebate, MDF, overlay, attach bonus), revenue target, and audience (field, partner-team, exec, async).
Works with Claude Code, Codex, GitHub Copilot, and Gemini CLI — drop the command file into the respective project directory.
What it helps with
- build a partner co-sell playbook with stages and owners
- define co-sell motion steps with SLAs and responsibilities
- package enablement materials and ROI assets for the team
- set up deal attribution rules and CRM tracking
- specify target metrics and reporting requirements
Example prompts for the agent
- Build a co-sell playbook with Nimbus AI, enterprise segment, spiff and rebate incentives, 3MM revenue target
- Create playbook for TechVendor partner, midmarket motion, 1.5MM target, include MDF and overlay
- Run
/partnership-development:build-co-sell-playbookfor a channel partner with attach bonus, field audience
How to install build-co-sell-playbook
Manually: put the files in place
.claude/commands/build-co-sell-playbook.mdCall it with /build-co-sell-playbook. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/build-co-sell-playbook.mdCall it with /prompts:build-co-sell-playbook. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/build-co-sell-playbook.prompt.mdManually: put the files in place
.gemini/commands/build-co-sell-playbook.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about build-co-sell-playbook
How to install build-co-sell-playbook in Claude Code?
Place the .claude/commands/build-co-sell-playbook.md file in your project directory.
What does build-co-sell-playbook do?
Command builds a partner co-sell playbook: designs engagement stages, prepares enablement materials (battlecard, talk track, ROI calculator), sets CRM attribution rules, and defines target metrics with reporting cadence.
Which motion types does build-co-sell-playbook support?
Command supports five motion types: enterprise, midmarket, channel, marketplace, and MSSP. Motion type shapes playbook structure and responsibility split.
Source text
build-co-sell-playbook.md · Apache-2.0
--- name: build-co-sell-playbook description: Creates a partner co-selling playbook with cadences, enablement, and attribution rules. usage: /partnership-development:build-co-sell-playbook --partner "Nimbus AI" --motion enterprise --incentives spiff,spif --targets 3MM --- # Command: build-co-sell-playbook ## Inputs - **partner** – partner or alliance name/ID. - **motion** – sell-with motion (enterprise, midmarket, channel, marketplace, MSSP). - **incentives** – comma-separated incentives (spiff, rebate, MDF, overlay, attach bonus). - **targets** – revenue/opportunity goal for the motion. - **audience** – field | partner-team | exec | async; changes fidelity and outputs. ## Workflow 1. **Discovery & Alignment** – capture joint value prop, ICP overlap, and mutual goals. 2. **Play Design** – define stages, responsibilities, enablement assets, and required approvals. 3. **Attribution & Governance** – outline tracking, CRM stages, and escalation channels. 4. **Enablement Kit** – package talk tracks, ROI assets, pricing guidance, and case studies. 5. **Launch & Measurement** – define targets, reporting cadence, and success scorecard. ## Outputs - Co-sell playbook PDF/deck with steps, owners, and SLAs. - Enablement bundle (battlecard, talk track, ROI calculator references). - KPI dashboard spec with attribution + reporting requirements. ## Agent/Skill Invocations - `partner-co-sell-lead` – drives pipeline governance + enablement. - `partner-program-architect` – ensures onboarding + certification hooks are embedded. - `joint-solution-blueprint` skill – codifies solution architecture and value prop. - `co-marketing-governance` skill – wires in awareness + demand-gen workflows. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents