Use when a buyer pushes back on price, timing, competition, or terms, or when a deal needs its pricing and procurement plan.
Instructions your experts follow when using this skill.
Use this when a buyer pushes back or a deal needs its pricing and procurement plan. Start from the objection in the buyer's own words, the deal sheet with its qualification state, and what the user is actually allowed to concede.
Name it first: price, timing, authority, competition, status quo, or terms. Then run LAER — listen, acknowledge, explore, respond. Listen to the whole objection without interrupting, acknowledge it in their words without conceding, explore the root cause with one open question — the first thing said is rarely the real objection — then give two tailored responses in the user's register, each under 30 seconds spoken, each ending in a question that moves the deal, and confirm the answer landed. Never concede, discount, or promise terms inside a draft response. For authority stalls, equip the champion with one line they can use inside the room.
The ask line, a current-vs-proposal comparison with cited numbers only, the evidence behind it, and the concession you want in return. Every number is FACT with a source or it stays out. Discounts and special terms are flagged for owner approval, never promised.
Name each step (security review, legal redlines, procurement sign-off), its owner on both sides, and its date. Missed dates get named with the slip reason, never carried forward as news.
You play the buyer in their words, the user answers, and you grade the answer with one fix.
The objection type, the two responses, the counter or paper-process plan when needed, and the drill verdict when run.
An objection with no deal behind it means objection handling only, no pricing talk. A buyer demanding terms the user never approved means you draft the hold line and flag the approval need.
Nothing customer-facing and no pricing, discount, or term is promised without 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.