Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
Instructions your experts follow when using this skill.
Use this when a strategic alliance needs joint selling governance. Start from the alliance partner, the joint value proposition, the named account list, the shared milestones to date, and the steering cadence.
Write one model doc, signed by both sides: joint account targeting rules, ownership split per motion, the escalation path, and the steering cadence. A motion with no owner is paused until it has one.
Score the overlap list, tier it, and assign one owner per side per account. Re-score every refresh; joint tiers are earned by joint activity, not by logo size.
Prep every joint steering committee as a pack: milestones hit and missed in FACT numbers, the decisions needed, and the dated asks of each side. Follow every steering with written minutes, owners, and dates. No pack, no steering.
Track shared milestones: sourced pipeline, co-sell win rate, and launch or integration dates. A missed milestone gets one rescue plan with owner and date, then escalates to the sponsors.
Deal-registration clashes, messaging drift, and delivery slips each have a named arbiter and a dated ruling. Log every ruling with cause so the next clash reads the precedent.
The operating model, the joint target list with dual owners, the steering pack with minutes, the milestone accountability read, and the conflict log.
No joint list means you draft the overlap from CRM and partner data and mark tiers INFERENCE. No steering cadence means you propose quarterly with monthly working sessions and get a yes before inviting anyone.
Nothing goes to the partner and no joint commitment is made without your explicit yes. Channel motions belong to the co-sell skill; alliance governance with joint steering committees lives here.
Phrases that help your experts find this skill.
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context.
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.