When the user wants to apply to startup accelerators, incubators, or fellowship programs. Also use when the user mentions "YC application", "Techstars", "accelerator", or "apply to programs".
日本語の概要は準備中です。原文の説明を表示しています。
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.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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:
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
When proposing a co-marketing initiative, include:
When proposing a product integration:
Cold partnership emails work, but warm intros convert 3-5x better. Before going cold, check for shared investors, advisor connections, shared customers who could intro, or conference overlap. Engage with their content on LinkedIn before reaching out.
| Touch | Timing | Angle |
|---|---|---|
| 1 | Day 0 | Primary partnership pitch with mutual benefit |
| 2 | Day 5 | Share a specific data point or customer anecdote that reinforces the opportunity |
| 3 | Day 12 | Reference a market trend or competitor partnership that creates urgency |
| 4 | Day 20 | Brief breakup: "Want to respect your time — should I circle back next quarter?" |
cold-outreach — use for the underlying outreach mechanics (email structure, subject lines, follow-up cadence)proposal-generation — use when the partnership conversation advances to a formal proposal or agreementExample prompt: "I want to reach out to Segment about building an integration. We are a customer data quality tool with 800 users. About 40% of our users also use Segment."
Good outreach email output:
Subject: segment integration — 320 shared users
Hi [Name],
We build [Product], a data quality tool used by about 800 companies. Roughly 40% of our users also use Segment, and "Segment integration" is our most-requested feature.
The integration would let shared customers automatically validate and clean data flowing through Segment before it hits downstream destinations — fewer bad records in warehouses and analytics tools.
We would build and maintain the integration on our end. We would need access to your partner API docs and a technical point of contact for a few questions.
Worth a 20-minute call to see if this makes sense?
Good partner evaluation output snippet:
Partner Fit: Segment
- Audience overlap: 5/5 — 40% of our users are Segment customers
- Complementary value: 5/5 — Data quality is a known pain point for Segment users; our products are better together
- Stage alignment: 3/5 — They are much larger, but they have an active partner/integration program
- Distribution leverage: 4/5 — Their marketplace and integrations page would give us significant visibility
- Strategic timing: 4/5 — They recently launched their new Protocols product, which aligns with data quality
- Total: 21/25 — Strong partnership opportunity
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
When the user wants to apply to startup accelerators, incubators, or fellowship programs. Also use when the user mentions "YC application", "Techstars", "accelerator", or "apply to programs".
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to design or evaluate system architecture — service boundaries, data models, API contracts, infrastructure topology, database selection, or dependency analysis. Also activate for "design the system", "how should I architect this", "monolith vs microservices", or architecture decision records.
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to write a monthly or quarterly investor update, prepare a board deck, or communicate company progress to stakeholders.
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to identify at-risk accounts, understand why customers are leaving, reduce churn rate, build health scores, design save plays, or create win-back campaigns.
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs to set up or improve CI/CD pipelines — GitHub Actions, GitLab CI, deployment automation, or says "set up CI", "automate deployment", "add tests to pipeline", "fix my build".
日本語の概要は準備中です。原文の説明を表示しています。
When the user asks for a code review, shares code for feedback, or says "review this", "check my code", "what's wrong with this". Also activate when reviewing a pull request or diff.
日本語の概要は準備中です。原文の説明を表示しています。