Use when alliance economics need an owner: the rolled-up profit and loss, the quarterly close against plan, guardrail bands, and the half-page read.
Instructions your experts follow when using this skill.
Use this when alliance economics need an owner, above any single deal model. Start from the alliance portfolio, trailing revenue and cost lines, the annual alliance budget, the planning year and fiscal calendar, the attribution model and claim window in force, and the systems the numbers come from.
Revenue lines: ecosystem-sourced revenue, influenced pipeline value, revenue shares in, marketplace flows. Cost lines: market development fund (MDF) and co-marketing spend, alliance heads, sales-engineering hours, program and academy spend. Per alliance, and totalled.
Every line names its source system and its window. Modelled lines stay INFERENCE until the owner confirms them.
Attribute influence with a named model per line — first-touch, last-touch, multi-touch, or influence-based — inside an explicit 90-day claim window, so sourced revenue is never over-counted.
Actuals against plan per line, variance with one line of cause each, and a reallocation draft moving spend from the miss lines to the beat lines.
A line missing two quarters running gets a fund-or-exit call with its evidence.
Score each alliance on economics plus momentum — pipeline trend, executive engagement, milestone pace — so cuts land on math rather than mood.
Between closes, score alliance key results weekly (one objective plus two to four measurable key results), so misses surface in-week rather than in-quarter.
Per-alliance spend caps, revenue-share bands, MDF ceilings, and the floor-approval owner per band.
Anything outside a band is an exception draft for the owner, never a quiet yes.
Save the bands where the deal-level skills can read them, so per-deal terms inherit the portfolio guardrails instead of re-deriving them.
Half a page per quarter: profit and loss against plan, partner return (attributed revenue divided by program cost), partner-against-direct comparators (sales-cycle velocity, average deal size, retention and lifetime value), partner attach rate, the reallocation moves, the fund-or-exit calls, and the top three risks to the number.
Feed the board pack and the council packs from this read, so every forum quotes one number rather than three.
The rolled-up profit and loss, the quarterly close with its reallocation draft, the guardrail bands, and the half-page report.
No finance feed means building from CRM and owner-stated lines marked INFERENCE, with standing up the feed as the first action. No annual budget means guardrails first, with provisional bands for the owner to ratify.
No read, reallocation, fund-or-exit call, or guardrail change goes to a partner or to leadership without your explicit yes.
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.