Free Claude skills/Sales

    Objection Patterns

    Finds the objections that keep coming up on your calls, links them to lost deals and writes a talk track for each. A free Claude skill for sales.

    A look inside

    This is how the skill opens, exactly as Claude reads it. The download has the full instructions, and it is a plain text file you can edit to fit how your team works.

    Find what prospects keep pushing back on, which objections actually cost deals, and what to say differently on the next call.

    What you need

    1. Notes or transcripts from recent sales calls, in any format. Each should show the company, the date and the outcome if known.
    2. Optional: a deal log with won and lost deals, to link objections to results.
    3. Optional: a short description of what is being sold.

    If the user wants to try the skill without their own data, use `examples/calls.json` and `examples/deal-log.csv` (an invented UX studio called PixelForge) and say that it is sample data.

    How to analyse

    1. List every objection stated on every call, in the prospect's words where the notes have them. Note the company and the call outcome.
    2. Group objections that mean the same thing. Name each group in plain words, such as "Too early for our stage".
    3. Count each group by the number of different companies that raised it, not the number of mentions.
    4. Link to outcomes. For each group, how many of those companies were lost, are still open, or were won. An objection raised mostly by lost deals matters more than one raised by deals still in play.
    5. Look for what the losses share beyond the objection: stage, size, tier, who was on the call.
    6. Note calls with no objections and what they had in common. That is often the best clue.

    Ready to put AI to work?

    Tell us where you are and what you need. In 30 minutes we will tell you where we would start.

    Not ready for a call? Take the 10 minute AI readiness checklist