# Objection Cheat Sheet > Builds a one-page objection sheet from your own lost deals, call notes and email replies, so the answers come from what buyers actually said rather than from a generic script. Use when the same three objections keep landing, or when onboarding someone into sales conversations. - Skill: `mardab96/objection-cheat-sheet` (Agent Skill) - Install (CLI): `npx skillmds@latest add mardab96/objection-cheat-sheet` - Raw SKILL.md: https://api.skillmd.com/api/skills/mardab96/objection-cheat-sheet/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Productivity - Author: mardab96 (https://skillmd.com/u/mardab96) - Updated: 2026-09-21 - Page: https://skillmd.com/skills/mardab96/objection-cheat-sheet --- # Objection Cheat Sheet ## Use this skill when The same objections keep arriving and the answers are improvised every time. Most objection handling advice is generic, which is why it does not work: it answers the objection as written rather than the one being made. "It is too expensive" is four different objections depending on who says it, and only your own lost deals can tell you which one you actually face. This builds the sheet from your evidence, not from a framework. ## Required input At least one of: - lost deal reasons from the CRM, with free text if it exists - call notes or transcripts where objections came up - email replies that declined, especially the longer ones Better with: - won deals where the same objection appeared and was overcome - your pricing and what is included - who the competitor usually is - which stage each objection tends to land at ## Analysis workflow 1. Collect every objection instance verbatim before interpreting any of them. The exact words matter, because "we already have something" and "we just signed with someone" lead to opposite responses. 2. Cluster them by what the buyer means rather than by what they said. Price objections in particular split into at least three: it costs more than the budget, it costs more than it is worth to me, and I cannot justify it internally. 3. Count each cluster and note which stage it lands at. An objection that appears once is an anecdote; the sheet is for the ones that repeat. 4. For each cluster, find the cases where it appeared and the deal still closed. That is where the real answer lives, and it usually is not what the sales deck says. 5. Write the response as something a person would say out loud. If it needs to be read from a screen it will not be used on a call. 6. Mark which objections are real disqualifiers. Some objections are correct, and the useful response is to agree and end the conversation rather than to handle it. 7. Note what would change the objection upstream. Several of them are messaging problems that arrived late, not conversation problems. ## Decision rules - Every response must trace to something a real buyer said. An answer with no evidence behind it goes in marked as untested. - Do not write a rebuttal for an objection that is true. If the product genuinely does not do the thing, the sheet says so and says what to offer instead. - Rank by frequency, not by how uncomfortable each one feels. - An objection that consistently appears before a demo belongs upstream with positioning, and a cheat sheet will not fix it. - Never manufacture social proof to answer an objection. A named customer who did not consent is a legal problem, and an invented one is worse. ## Output format ### The sheet | Objection, in their words | What they usually mean | How often | Stage | What to say | Evidence | |---|---|---|---|---|---| Ordered by frequency. Ten at most, and fewer is better. ### Real disqualifiers The objections where the correct answer is to agree and walk. ### Fix upstream Objections that should never reach a call, and what would stop them. ### Untested Responses with no won-deal evidence behind them, marked so nobody mistakes them for proven. ## Practical example Twenty-two lost deal records and eleven call notes go in. Clustering shows "too expensive" appearing nine times, but splitting cleanly: six are companies below a headcount where the product cannot pay for itself, and three are companies who could afford it and did not see the value. That split changes everything. The six are a disqualifier, and the sheet says to name the size threshold early rather than discount. The three are a value articulation problem, and the response comes from two won deals where the same objection appeared and was answered with a specific number the buyer could take to their finance lead. The sheet also flags that "we already have something" arrives before the demo in seven cases, which is a positioning problem, not an objection to handle. ## Guardrails - Do not invent customer quotes, names or results. - Do not write responses that pressure, guilt or manufacture scarcity. - Do not treat every objection as something to overcome. Some are information. - Do not build the sheet from a single deal. - Do not include personal or identifying customer details in a document that will be shared with a sales team.