Objection Pre-Handling Content System for Coaches

Every coach has a mental list of the objections they hear on sales calls: “it’s too expensive,” “I don’t have time right now,” “I think I can figure this out myself.” You’ve gotten good at answering them live. But here’s the quiet cost: for every prospect who books a call and raises an objection, several more had the same objection, never booked, and you never got the chance to answer it.

This skill helps you pre-handle objections in your coaching content. You give the AI one real objection in your prospect’s own words, and it produces a piece of content that names the objection out loud, reframes it, and dissolves it, so by the time someone books a call the hardest part of the conversation is already over. By the end of this page you’ll also understand the mechanics, so you can write objection content that sounds like you and not like a sales script.

When to use this

• You keep hearing the same objection on calls and you’re tired of answering it from scratch.
• Prospects go quiet after seeing your price and you never learn why.
• You want your content to do sales work, not just build a vague brand.
• You’re writing a sales page, email sequence, or FAQ and need each section to remove a specific doubt.
• You have testimonials and case studies but people still hesitate, and you suspect the real blocker is unspoken.

The skill

Paste this whole block into a ChatGPT Custom GPT’s Instructions field, or a Claude Project’s custom instructions:

ROLE
You are a sales-savvy content strategist for coaches. You specialise in turning a single real sales objection into one piece of content that quietly dissolves that objection before a prospect ever books a call. You understand that the goal is not to argue or pressure, but to reframe the prospect's thinking so the objection no longer feels true to them.

INPUTS
You will be given:
- NICHE: the coach's niche
- OFFER: the offer they sell
- PRICE_RANGE: roughly what it costs
- OBJECTION: the exact objection, ideally in the prospect's own words
- IDEAL_READER: who tends to raise this objection
- FORMAT: the content format requested (e.g. LinkedIn post, email, short video script, FAQ answer)
- TONE: the coach's tone

Before you do anything else, ask up to 3 clarifying questions if any input is missing, vague, or contradictory (for example, if the OBJECTION is a surface excuse hiding a deeper fear, or if the FORMAT is unclear). If everything is clear, skip the questions and proceed.

PROCESS
1. Diagnose the objection. State in one line what the prospect is REALLY saying underneath the words. Most objections ("too expensive", "no time", "I can do it myself", "let me think about it") are proxies for a deeper fear: risk, doubt that it will work for them, or doubt in themselves. Name that fear.
2. Find the reframe. Decide the single new belief the reader must accept for the objection to dissolve. Write it as one sentence.
3. Choose the evidence. Pick the most honest proof for that reframe: a principle, a short client story (kept anonymous), a useful contrast, or a thought experiment. Never invent statistics, testimonials, or results.
4. Write the content in the requested FORMAT and TONE, structured as: hook that names the objection out loud, the reframe, the evidence, then a low-pressure next step. The reader should feel understood, not sold to.
5. End by handling the objection's most likely comeback in one or two lines, so it does not resurface on the call.

OUTPUT FORMAT
Return, in this order:
1. THE REAL OBJECTION: one line naming the underlying fear.
2. THE REFRAME: one sentence (the new belief).
3. THE CONTENT: the finished piece in the requested format, copy-paste ready.
4. THE COMEBACK HANDLED: one to two lines addressing the likely pushback.
5. ONE FOLLOW-UP IDEA: a single suggestion for a companion piece on a related objection.

RULES
- Match the requested TONE exactly. No hype, no buzzwords, no 'in today's fast-paced world', no 'unlock', no 'game-changer'.
- Never fabricate stats, client names, or outcomes. If you use a client example, keep it anonymous and plausible.
- Do not pressure or shame the reader. The objection is legitimate; treat it with respect.
- Keep the content tight. A LinkedIn post is 120-220 words; an email is under 200 words; a video script is under 150 words.
- Speak to one reader, not an audience. Use 'you'.

How to set it up

1. Build it once as a reusable assistant. In ChatGPT, go to ‘Explore GPTs’ then ‘Create a GPT’ and open the Configure tab. In Claude, open Projects and create a new project. Either way, paste the full skill block above into the instructions field and name it ‘Objection Pre-Handler’.
2. Run it with your inputs. Start each message with the seven inputs the skill asks for. The cleaner your inputs, the sharper the content.

3. Answer its questions. If it asks for clarification, answer honestly. That step is where the generic version gets filtered out.

See it in action (full example)

Here is the exact set of inputs a career coach sent to the skill. This is the whole input, nothing hidden:

NICHE: career coaching for senior software engineers
OFFER: a 12-week 1:1 coaching package to land a staff-engineer role
PRICE_RANGE: around $4,500
OBJECTION: I can probably figure the promotion thing out myself, I just need to read more
IDEAL_READER: senior engineers stuck at the same level for 3+ years who keep getting passed over
FORMAT: a LinkedIn post
TONE: direct, calm, no hype

And here is the complete output the model returns:

THE REAL OBJECTION: “I can do it myself” isn’t confidence, it’s a fear of admitting that something they’re already smart enough to solve has them stuck anyway, and that paying for help means conceding they couldn’t crack it alone.

THE REFRAME: The thing keeping you at senior isn’t missing information, it’s the blind spot you can’t read your way out of, because it’s about how you’re perceived, not what you know.

THE CONTENT:

“I just need to read more about getting promoted.”

I hear this from senior engineers who’ve been at the same level for three, four, sometimes five years.

And I get it. You’re an engineer. When something’s broken, you research it, you study it, you solve it. That instinct got you to senior.

But here’s why it stops working at this level.

Promotion to staff isn’t an information problem. There is no doc you haven’t read. The gap is almost always how your work is perceived by the people in the room you’re not in: whether your name comes up when scope gets handed out, whether your impact is legible to a director, whether you’re seen as someone who already operates at the next level.

You cannot read your way to a blind spot. By definition, it’s the thing you can’t see.

That’s the entire reason a second set of eyes is worth it. Not because you’re not smart enough. Because you’re too close.

If you’ve been “about to figure it out” for two promotion cycles, the reading isn’t the missing piece.

Happy to point you to where the actual gap usually is, no pitch. Just comment “STAFF” and I’ll share the three signals promotion committees look for.

THE COMEBACK HANDLED: If they think “but my situation is specific to my company” — that’s exactly the point. Generic advice can’t account for your specific room; that’s what a person who’s seen dozens of these cases is for, not another article written for everyone.

ONE FOLLOW-UP IDEA: A companion post for the “I’ll wait until after the next review cycle” objection, reframing waiting as another year spent on the strategy that already isn’t working.

That is publish-ready. Swap the CTA for whatever you actually use, give the first line a human pass, and it goes live today.

Why this works

Four LLM principles are doing the work here. Learn them and your prompting gets sharper across the board:

1. Role priming sets the lens. “You are a sales-savvy content strategist for coaches” tells the model to reason like a salesperson, not a copywriter. That single line is why the output opens by diagnosing the fear instead of jumping straight to a post. The role you assign decides which slice of the model’s knowledge it draws from. “Write me a post about objections” pulls the bland average; “act as a sales strategist who dissolves objections” pulls the good stuff.
2. Specificity in, specificity out. The output is only as sharp as your OBJECTION. “It’s too expensive” produces a generic price-justification post. The exact phrase “I just need to read more” let the model find the real fear underneath, and the whole post pivots on that diagnosis. Feed it the prospect’s literal words, not your paraphrase.
3. Constraints are quality control. The rules block (no fabricated testimonials, no hype words, keep it tight, speak to one reader) each kill a specific failure mode. Telling the model what NOT to do is as powerful as telling it what to do. The “never invent statistics or results” line is what keeps the example honest instead of stuffing it with fake numbers.
4. Clarifying questions beat guessing. The instruction to ask up to 3 questions first is the single biggest fix for generic AI output. When an objection is a surface excuse hiding a deeper fear, the model can ask instead of assuming, and that one exchange is the difference between content that lands and content that sounds like a template.

Do this now

1. Open your call notes and write down the last objection you heard, word for word, in the prospect’s voice.
2. Paste the skill into ChatGPT or Claude, fill in the seven inputs, and send it.
3. Answer any clarifying questions honestly, then read the diagnosis line first. If it nailed the real fear, the content will land.
4. Tweak the hook and CTA in your own words and publish it this week.

Pro tips

• Keep a verbatim objection log. After every call, capture the exact words. A list of real objections is worth more than any swipe file, and it feeds this skill directly.
• Run the same objection through three formats. Ask for a LinkedIn post, then an email, then an FAQ answer. One objection becomes a week of content that all points the same direction.
• Trust the diagnosis step. If the ‘real objection’ line feels wrong, your input was probably a paraphrase. Re-run it with the prospect’s literal words and watch it improve.
• Pre-handle in sequence. Map the order objections show up in your sales process and pre-handle them in that order across an email sequence, so each message clears the next doubt before it forms.

Related

• Objection Crusher: Rebuttals to the 12 Most Common Coaching Objections
• ‘It’s Too Expensive’ Reframe Script Generator for Coaches
• ‘I Need to Think About It’ Follow-up Response Writer
• Objection-Crushing Copy Generator for Coaches Closing Hesitant Buyers