Use when the user names a vendor to evaluate, asks what renews soon, hands over a quote or statement of work, or wants to buy something and needs it approval-ready.
Instructions your experts follow when using this skill.
Use this when the user names a vendor to evaluate, asks what renews soon, hands over a quote or a statement of work (SOW), or wants to buy something.
The spend source — a connected sheet, an accounting or card export, or a pasted CSV — the vendor list, the quotes or SOWs under review, and the name of the procurement approver.
No spend source means you build the inventory from their pasted list and mark spend UNKNOWN. One quote only means you score it and name the missing comparison.
One row per vendor: purpose in five words or fewer, owner, cadence, trailing spend, last charge, and renewal date. Dedupe on vendor name. A purpose or owner you cannot source stays Unknown, never guessed.
Segment each vendor by spend plus criticality — strategic, preferred, transactional, tail. Review effort follows the tier.
Pick the instrument by purchase type: a request for information (RFI) to explore, a request for proposal (RFP) when solutions differ, a request for quote (RFQ) when the spec is fixed and only price moves.
Agree the weighted 1-5 criteria before quotes arrive — default 35 cost, 30 fit, 20 track record, 15 timeline — and let the composite total decide. Publish the criteria, batch every vendor question and answer to all vendors at once, negotiate only after scoring, and track delivery against the winning proposal. Never score on sticker price alone. Document why the winner won, in one line.
Current terms, usage against commitment, SLA hit rate, and the counter — a comparison table plus a draft note, draft-only. Check the term end and the notice period before you propose anything.
Scope, deliverables, term, price, and exit. Route every SOW to Legal and every purchase order (PO) to the procurement approver. Version each draft. You draft, they sign — never give legal advice.
Strategic vendors monthly or quarterly; the rest semi-annual or annual. Weigh each scorecard so trade-offs are explicit — default fit 30, cost 30, risk 20, delivery 20, summing to 100 — and compute a total per vendor.
Every score cites the SLA or contract clause it is measured against. A vendor with no written SLA gets flagged as a risk. Spend without outcomes gets flagged, never auto-renewed. With the approver's yes, share each strategic vendor's scorecard with the vendor and ask for their feedback on us as a buyer.
Never sign a contract, place an order, or send a vendor note without the approver's yes. Never invent a price, a term, or a renewal date.
Save the inventory as the sheet the team edits, with dated scorecards under vendors.
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.