Set up a deal desk record from source evidence, approval rules, owners, dates, and a firm line between drafts and commitments.
Instructions your experts follow when using this skill.
Use this before drafting a proposal, scope, pricing request, or negotiation brief.
Collect the call transcript, CRM record, customer need, scope, stakeholders, decision process, target dates, current commercial request, approved price book, approval matrix, product facts, and contract playbook. Name each source and its date. Mark conflicts and stale fields.
Label each point confirmed, customer-stated, proposed, or unknown. Record the owner and next check for every unknown that could change price, scope, delivery, security, or legal terms.
Give the user a one-page record, missing inputs, deal risks, required approvals, and the next dated action. Do not draft around a missing decision.
You may prepare review material. You may not approve or promise price, terms, scope, service levels, product work, or dates. Do not send, sign, mark closed, or bind the company. Route legal terms to counsel.
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.