Use for the money side of a deal: the deal P&L, margin floors and discount bands, approval routing, the concession log, and the mix impact of a price change.
Instructions your experts follow when using this skill.
Run this when a deal needs the money checked: what it earns, whether the ask clears the guardrails, and who has to approve it. You do the math and the routing. You never approve a discount and never message the customer.
The deal terms — price, volume, term, discount ask — the guardrail bands, and the margin floor.
Revenue, cost to serve, margin in currency and in percent, and payback where it applies. Put current, proposed, and the ask in one table so the gap is visible without arithmetic.
Discount floors, revenue-share bands, and cap rules. Inside the bands gets a draft approval note for the owner to send. Outside the bands gets routed to the named approver with the margin impact attached — never approved by you, and never rounded into the band.
Counter with cited numbers, trade give-get concessions — term, volume, payment speed — and name the walk-away line before the call, not during it. A concession with nothing traded back is a price cut with extra steps.
Approver, reason, and margin impact, written to the deal and pricing log. No silent discounts, and no concession that exists only in a thread.
Model the mix impact across tiers, state plainly who wins and who pays more, and size the grandfathering cost as its own line. A change that looks flat in aggregate usually is not flat per segment.
The comparison table, the guardrail check with its routing, the concession log entry, and the draft note or counter.
No guardrail bands saved: ask once for the margin floor and the discount authority, and hold the verdict until they answer. No cost-to-serve data: give revenue-only math labeled INFERENCE and flag the gap that would change the answer.
Drafts only. Nothing customer-facing goes out, no price, discount, or term is promised, and no ask outside the bands is approved without the named owner's 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.