accelerator-applicatio…
When the user wants to apply to startup accelerators, incubators, or fellowship programs. Also use when the user mentions "YC…
When a founder needs to write partnership or BD emails, craft integration pitches, or create co-marketing proposals. Activate when the user mentions partnerships, business development, integration proposals, co-marketing, channel partnerships, or strategic alliances.
$ npx -y skills add shawnpang/startup-founder-skills --skill partnership-outreach --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/partnership-outreachContext preview
The summary Claude sees to decide when to auto-load this skill.
When a founder needs to write partnership or BD emails, craft integration pitches, or create co-marketing proposals. Activate when the user mentions partnerships, business development, integration proposals, co-marketing, channel partnerships, or strategic alliances.
name: partnership-outreach description: When a founder needs to write partnership or BD emails, craft integration pitches, or create co-marketing proposals. Activate when the user mentions partnerships, business development, integration proposals, co-marketing, channel partnerships, or strategic alliances. related: [cold-outreach, proposal-generation] reads: [startup-context]
Activate when a founder needs to identify and reach out to potential partners, write partnership emails, propose integrations, or create co-marketing proposals. Also use when the user says "I want to partner with X," "help me write a BD email," "how do I propose an integration," "co-marketing opportunity," or "I need a channel partner strategy."
From `startup-context` or the user:
1. **Gather context** — Read startup-context if available. Understand the product, traction, and partnership goals. 2. **Identify partner fit** — Use the Partner Evaluation Framework to assess whether this is a strong partnership opportunity. 3. **Map the win-win** — Define what each side gets from the partnership. If you cannot articulate both sides, the proposal will fail. 4. **Find the right contact** — Identify the BD, partnerships, or product person at the target company. Avoid generic inboxes. 5. **Draft the outreach** — Write the partnership email or LinkedIn message using the frameworks below. 6. **Prepare the proposal** — If the initial outreach gets a response, draft a lightweight partnership proposal (1-2 pages). 7. **Define success metrics** — Propose how both sides will measure whether the partnership is working.
Deliver the appropriate materials based on the partnership stage:
Before reaching out, score the potential partner on these dimensions:
| Dimension | Strong Signal | Weak Signal | |-----------|--------------|-------------| | **Audience overlap** | You share the same ICP but do not compete | Marginal audience overlap or direct competition | | **Complementary value** | Your products are better together than apart | Nice-to-have integration with limited user benefit | | **Stage alignment** | Similar company stage or the larger partner has an active partner program | Massive stage mismatch with no partner program | | **Distribution leverage** | Partner has distribution you lack (or vice versa) | Neither side brings meaningful new distribution | | **Strategic timing** | Partner is expanding into your space or just launched relevant features | No clear strategic reason for them to partner now |
**Score each dimension 1-5. A score of 20+ suggests a strong partnership opportunity. Below 15, reconsider whether it is worth pursuing.**
| Type | What It Is | Best For | Typical Structure | |------|-----------|----------|-------------------| | **Integration** | Build a technical connection between products | Complementary SaaS tools | Joint engineering effort, shared docs, marketplace listing | | **Co-marketing** | Joint content, webinars, or campaigns | Companies with overlapping audiences | Shared leads, co-branded content, cross-promotion | | **Referral** | Informal lead sharing | Trusted companies in adjacent spaces | Referral fees or reciprocal introductions | | **Reseller/Channel** | Partner sells your product | Agencies, consultants, system integrators | Revenue share, tiered pricing, enablement materials | | **Strategic alliance** | Deep collaboration on product or GTM | Companies with highly aligned vision | Joint roadmap, executive sponsorship, shared metrics |
Partnership emails differ from sales emails. You are proposing a collaboration, not selling a product. The tone should be peer-to-peer and the value proposition must be bilateral.
**Structure: Shared Audience - Mutual Benefit - Proof - Lightweight Ask**
1. **Open with the shared audience** — Show you understand who they serve and that you serve the same people 2. **Name the mutual benefit** — Be specific about what each side gains. Vague "synergies" get ignored. 3. **Provide proof of your value** — Traction metrics, shared customers, or a specific integration use case 4. **Make a lightweight ask** — Request a 20-minute call, not a signed partnership agreement
Hey friends. Shawn here. I've been bootstrapping and starting companies for the past 10 years (still working hard at 996 level).
When the user wants to apply to startup accelerators, incubators, or fellowship programs. Also use when the user mentions "YC…
When the user needs to design or evaluate system architecture — service boundaries, data models, API contracts, infrastructure…
When the user needs to write a monthly or quarterly investor update, prepare a board deck, or communicate company progress to…
When the user needs to identify at-risk accounts, understand why customers are leaving, reduce churn rate, build health scores,…
When the user needs to set up or improve CI/CD pipelines — GitHub Actions, GitLab CI, deployment automation, or says "set up CI",…
When the user asks for a code review, shares code for feedback, or says "review this", "check my code", "what's wrong with this".…