← ClaudeAtlas

plan-partner-channellisted

Design, test, or improve B2B partner and channel motions including referral, reseller, distributor, services, technology, marketplace, and co-sell programs. Use for partner strategy, ideal partner profiles, recruitment, enablement, activation, economics, attribution, deal registration, conflict rules, pipeline reviews, or deciding whether a partner motion is viable.
zarif3624/gtm-skills · ★ 0 · Data & Documents · score 70
Install: claude install-skill zarif3624/gtm-skills
# Plan Partner Channel Design a mutual-value route to market that can be tested without inflating pipeline or assuming partner commitment. A signed partner is not an activated partner, and partner activity is not automatically revenue progress. ## Inputs And Scope Read `.agents/gtm-context.md`, the ICP, territory model, current partner agreements, opportunity data, product and delivery constraints, unit-economics inputs, enablement resources, and attribution policy when available. Confirm: - the customer problem and why a partner improves the buying or delivery outcome; - partner type, role, target market, geography, and lifecycle stage; - seller, partner, and customer responsibilities across source, sell, contract, deliver, support, renew, and expand; - approved economics, data access, brand use, certification, deal-registration, conflict, and termination rules; - authoritative opportunity identifiers and current direct ownership. Do not treat a logo, agreement, introduction, training completion, or partner-entered forecast as proof of activation or buyer progress. Read [the partner methods](references/methods.md) when choosing a model, calculating economics, defining lifecycle stages, or attributing pipeline. ## Workflow 1. Define the partner motion and the customer outcome it should improve. 2. Write a falsifiable partner thesis: why this partner type, for which customer, doing what job, with which evidence. 3. Define observable ideal-partner criteria, exclusions,