Install
$ agentstack add skill-dongcs52-claude-bd-skills-bd-partner-pitch ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Partnership Pitch Generator
Partner pitches are NOT cold sales emails. They're deal proposals. This skill produces a full pitch package: outreach email + 1-pager + deck outline + proposed deal terms.
Input
Required (one of):
partner-candidates.json— produced by/bd-partner-find(preferred — already has mutual value thesis)- A specific partner name + type — ask user for these if not provided
Required:
- Your business context — pulled from
icp-profile.jsonif present, else ask user
Optional:
- Specific partner the user wants to pitch (if multiple in
partner-candidates.json) - Preferred deal model (rev share / referral / co-sell / OEM / co-marketing)
Process
- Confirm target partner — if multiple candidates in
partner-candidates.json, ask which one (or generate top 3) - Read mutual value thesis — already defined in
partner-candidates.json; refine if missing - Choose deal model — based on partner type:
- Channel / Reseller → rev share (10–30%) or margin
- Integration → co-marketing + revenue share on co-sourced deals
- Affiliate → CPA or % rev share
- JV → co-built P&L, equity / shared ownership
- Strategic Alliance → no money flow; co-marketing
- Write the pitch package:
- Outreach email (under 150 words)
- 1-pager (problem / solution / mutual value / proposed model / next step)
- Deck outline (8–12 slides)
- Proposed term sheet skeleton (key deal points, NOT a legal doc)
- Write 3-touch follow-up — bump, value-add, break-up
Output: partnership-pitch-{partner}.md
# Partnership Pitch: [Your Company] × [Partner Name]
## Deal model proposed
[One sentence: e.g., "Revenue share — 20% on co-sourced deals, 12-month exclusivity in [vertical]"]
---
## Section 1: Outreach email
### Subject line options (A/B/C)
- A: "Partnership idea — [[YOUR_CO]] × [[PARTNER_CO]]"
- B: "[[MUTUAL_CUSTOMER]] could be 10x bigger if..."
- C: "Quick partnership thought — 5 min read"
### Email body (target 120 words)
Hi [[FIRST_NAME]],
[Open with mutual context — shared customer / ICP / event]
[Mutual value thesis in 2 sentences — what each side gets]
[Specific data point or proof — why this works]
I sketched a quick proposal. Worth a 20-min chat next week?
[Sender]
---
## Section 2: 1-pager (attach as PDF or paste in email reply)
### Why now
[Trigger: market shift / customer signal / mutual opportunity]
### What we propose
**[Partner Name] gets:**
- Specific value 1
- Specific value 2
- Specific value 3
**[Your Company] gives:**
- Specific commitment 1
- Specific commitment 2
- Specific commitment 3
### How it works (3 steps)
1. [Pilot phase: 30-60 days, scope]
2. [Validation phase: success metric]
3. [Scale phase: rollout]
### Proof points
- [Customer case study or data]
- [Market signal]
- [Mutual customer]
### Proposed terms (high level)
| Term | Proposal |
|---|---|
| Deal model | Rev share / referral / co-sell / OEM |
| Split | XX% / YY% |
| Exclusivity | None / category / geographic |
| Term length | 12 months, auto-renew |
| Co-marketing | Joint webinar, co-authored content |
| Tech / integration | Native API integration, marketplace listing |
### Next step
[Specific 20-min ask]
---
## Section 3: Deck outline (8-12 slides)
1. **Title slide** — "[[YOUR_CO]] × [[PARTNER_CO]]: A partnership thesis"
2. **Why we're here** — the mutual opportunity in one sentence
3. **The market** — TAM / customer pain / inflection
4. **Why us, why you** — our complementary strengths (2x2 matrix)
5. **The customer outcome** — what mutual customers get
6. **Proposed model** — deal structure visualized
7. **Pilot plan** — 30/60/90 days
8. **Co-marketing motion** — joint content, events, sales
9. **Success metrics** — what we'll measure
10. **Investment & commitments** — resources from each side
11. **Risk & mitigations** — channel conflict, brand, execution
12. **Next steps** — 20-min discovery, term sheet, pilot kickoff
---
## Section 4: Term sheet skeleton (NON-LEGAL — directional only)
PARTNERSHIP TERM SHEET — [Your Co] × [Partner] ================================================
- Partnership type: [Channel / Integration / etc]
- Effective date: [Date]
- Term: 12 months, auto-renew unless 60-day notice
- Exclusivity: [None / category / geographic]
- Revenue model: [Rev share %, Referral fee, etc]
- Payment terms: Net 30 from invoice
- Co-marketing commitments:
- Joint webinar (1/quarter)
- Co-authored content (2/year)
- Joint conference presence
- Tech commitments:
- Native integration GA by [date]
- Marketplace listing
- Success metrics:
- X co-sourced deals in 12 months
- $Y joint pipeline generated
- Termination: 60-day notice, no penalty
================================================ [Note: Above is a directional term sheet — final terms via legal]
---
## Section 5: Follow-up sequence
### Day 5 — Bump
[2-line reply: "Hey [[FIRST_NAME]], floating this back up — happy to send the 1-pager to make it easier."]
### Day 10 — Value-add
[Share a specific case study OR a mutual customer success metric]
### Day 20 — Break-up
[Polite exit: "Going to stop reaching out — door's open if priorities shift. In the meantime, here's [content piece] that might be useful."]
---
## Notes for the sender
- **Don't pitch in the first email.** Frame as a 20-min exploratory chat.
- **Lead with their value.** "What you get" before "what we want."
- **Concrete > vague.** "20% rev share on co-sourced deals" beats "we'll figure out economics."
- **Anchor on mutual customers.** If you share customers, say so explicitly.
- **Decision-maker in CC?** Get the partnerships lead first; loop in their CEO only at term sheet stage.
Rules
- Pitch packages must include all 4 sections. Email + 1-pager + deck outline + term sheet skeleton.
- Term sheet is directional, not legal. Add disclaimer.
- Don't propose terms above market. Rev share for SaaS partners is typically 10–30%. Don't say 50%.
- Mutual value first. Always.
- Pitch length: Email under 150 words. 1-pager truly 1 page. Deck under 12 slides.
Next steps to suggest
/bd-partner-evaluate— if pitching multiple partners, score and prioritize/bd-followup— extended follow-up cadence beyond 20 days/bd-strategy— combine into full BD strategy report
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: dongcs52
- Source: dongcs52/claude-bd-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.