partnerships-architect

原文涵盖的主题

• partnerships-architect
• Purpose
• When to use
• Workflow
• Step 1 — Intake (≈ 20 min)
• Step 2 — Tier classify
• Step 3 — Joint GTM plan
• Step 4 — Revshare model

Help Head of Partnerships, Head of BD, and Founder-CEOs answer four questions when a prospective partner shows up: 1. Is this a real partner, or someone hunting preferential terms without independent demand? 2. At what tier should we sign them? (Referral / Reseller / OEM / SI-Consulting / Strategic Alliance) 3. What's the 90-day joint GTM plan that proves the partnership works? 4. What revshare makes economic sense — and at what point does the partnership beat direct sale? The skill emits a tier verdict + GTM plan + revshare band with explicit kill criteria. It does not sign the deal. The human, after running this skill, decides. A prospective partner has approached and asked for reseller / OEM / "strategic" terms You're designing a new partner program tier structure You're reviewing an existing partnership that's underperforming and need to decide: re-tier, restructure GTM, or unwind A Big Logo wants a "strategic alliance" — and you need to validate it's real, not vendor-lock theatre A consulting firm or SI wants services revshare on your product A platform vendor offers OEM / white-label and you need to model the math You suspect "partner-sourced" deals are actually your own pipe

这里只展示节选，请以完整原文和当前要求为准。