Partnerships Architect
Partnerships Architect helps startups evaluate prospective partners by classifying them into one of five tiers (referral, reseller, OEM, SI-consulting, strategic alliance), designing a 90-day joint go-to-market plan, and modeling revenue share against direct-sale economics. It produces a tier verdict, GTM plan, revshare band, and kill criteria to support human decision-making.
✨ What it does
- Classifies partners into 5 tiers with deterministic floors based on evidence of independent demand.
- Generates a 90-day joint GTM plan with tier-validated motions and success criteria.
- Models revshare bands, break-even partner ROI, and long-term economics vs. direct sales.
- Surfaces mandatory kill criteria for unwinding underperforming partnerships.
- Includes a forcing-question library to validate partner substance before structuring.
- Detects anti-patterns like discount hunting, channel conflict, and unfunded OEM support.
🎯 When to use it
- A prospective partner approaches asking for reseller, OEM, or 'strategic' terms.
- You are designing a new partner program tier structure.
- You are reviewing an underperforming existing partnership and need to decide whether to re-tier, restructure GTM, or unwind.
- A large company wants a 'strategic alliance' and you need to validate it's real, not just preferential terms hunting.
- A consulting firm or SI wants services revshare on your product.
🚀 How to use
Trigger: /cs:grill-commercial
Trigger by describing a partnership evaluation scenario, e.g., 'A company wants to resell our product, should we sign them?' The skill expects inputs like partner name, evidence of independent demand (named accounts, sales team size), strategic value, and commitments offered. Run the three scripts in sequence: partner_tier_classifier.py, joint_gtm_planner.py, revshare_modeler.py. Example prompts:
A mid-sized VAR approached us wanting reseller terms. They claim to have 10 customers interested. Should we sign them and at what tier?
We're considering an OEM deal with a platform vendor. Model the revshare and GTM plan.
📄 Output: A tier verdict, 90-day joint GTM plan, revshare band, and kill criteria, typically as markdown reports from the scripts.
📦 Add this skill to Claude Code
# 1. Get the skills repo
git clone --depth 1 https://github.com/alirezarezvani/claude-skills /tmp/claude-skills
# 2. Copy this skill into your project (or ~/.claude/skills for all projects)
mkdir -p .claude/skills
cp -r /tmp/claude-skills/commercial/skills/partnerships-architect .claude/skills/partnerships-architectSkill source: commercial/skills/partnerships-architect/SKILL.md
⚠️ Good to know
Requires honest completion of the intake template; if the partner cannot provide evidence of independent demand, the skill stops. Revshare bands are recommendations; contract negotiation and exclusivity terms are human decisions.
❓ FAQ
What are the five partner tiers?
The tiers are REFERRAL, RESELLER, OEM, SI-CONSULTING, and STRATEGIC. Each has deterministic floors; for example, STRATEGIC requires at least 5 named accounts, a multi-year commitment, and dedicated resources.
What happens if a partner cannot provide evidence of independent demand?
The skill recommends signing them at most at the REFERRAL tier, if at all, because they are likely hunting preferential terms rather than bringing customers.
Are kill criteria optional?
No, kill criteria are mandatory. A partnership without a written unwind trigger can become a permanent obligation, so the skill requires documenting them in the contract.
🤖 Overview, features, install steps and FAQ were generated from the project's SKILL.md on Sep 4, 2026. Always check the original source before running commands.