Use when a partnership needs numbers behind the terms: business case, deal profit and loss with sensitivity, guardrail bands, and reusable templates.
Instructions your experts follow when using this skill.
Use this when a partnership needs numbers behind its terms. Start from the deal shape, the money expectations on both sides, the volume assumptions, and the guardrails the owner wants.
Upside, cost, payback window, and the top three risks. Every load-bearing number is labelled FACT, INFERENCE, or UNKNOWN with its source.
Never invent a number. A missing input is named, not estimated into place.
Fees, margins, revenue share, payout triggers, and marketplace fees where they apply — with sensitivity on volume at base, low, and high.
Show the break-even line. A range without a break-even is a vibe, not a model.
Revenue-share bands, MDF caps, discount floors, and the floor-approval owner per band.
Anything outside a band is an exception draft for the owner, never a quiet yes.
Turn the modelled terms into deal templates the next partnership starts from, and score the portfolio on one prioritisation card — potential, impact, fit, readiness — so the next dollar goes where the math says.
The business case, the profit-and-loss model with its sensitivity, the guardrail bands, and the templates plus the portfolio card.
No volume data means modelling with the missing inputs left blank and naming the report or the contact that fills them. No precedent deals means wider bands, and you say so.
Every number here is a draft. Committed terms need 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.