Use when a deal needs the money case: value proposition, demo plan, proof-of-concept scope, ROI model, or the proposal that carries them.
Instructions your experts follow when using this skill.
Use this when a deal needs the money case. Start from the deal sheet with qualification state, the buyer's stated metrics and pains with quotes, what the user sells and at what price band, and the proof they are allowed to cite.
The problem and its cost in their quotes, the measurable outcome they stated, and the consequence if nothing changes. A metric the buyer never said stays out — our description of their problem does not count.
Three buyer outcomes, the click-path per outcome, the proof line per outcome, and the trap questions to avoid — not a feature tour. Write per-stakeholder variants: business case for the CFO, workflow for end users, risk mitigation for legal and procurement. Score proof-of-concept trials with entry and exit criteria, a dated owner each side, and what a pass earns.
Current-state cost, future-state cost, the delta, payback period, total cost of ownership, and net present value, plus a risks and mitigation box. Every input is FACT with a source or it stays out; assumptions get their own box with the reason stated. Never invent a number.
Scope, price band, terms, and the one ask with a date. Price and terms stay inside the approved ladder bands — anything beyond is flagged, never promised. Every concession names its paired buyer give (term, timing, scope), sequenced easy to hard with diminishing size, and the walk-away is stated before any external draft; one-time discounts are confirmed in writing to protect the renewal anchor, and price realization (actual over list) is tracked. Counter procurement with the champion-armed ROI case and legal redlines with a deadline that holds implementation resources. Before any send: pricing verified, delivery timeline confirmed, similar-use-case proof attached, proofread — then owner yes. After every verbal yes, send a written recap memo (final terms, deliverables, milestones, contacts) and log each concession in the CRM with give, get, approver, and rationale.
The ROI business case with sourced numbers, the demo or proof-of-concept plan, and the proposal draft, saved to file. Show them in chat, take one round of edits, then save.
No buyer-stated metric means you name the gap and write the one question the next call must answer before the case goes anywhere. No approved price band means scope-only drafts until they give it.
The proposal, statement of work, and any priced page ship only with 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.